Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
We are running ECC 6 and we encountered the same issue a couple of years ago. We found and applied an SAP note that opens the tables V_T5K13 and V_T5K14 for update in Prod (13 is for NOC codes associated with jobs and 14 for NOC codes associated with positions). This eliminated the need for us to maintain all jobs and positions in Dev and then transport the updates to the NOC to our QA environment and then to Prod. I know there are also SAP notes for earlier versions, as we found them when searching for ones for ECC 6. (I think it is much easier to do this way than through PO03, as you do not need to bring up each job or position separately, do the update, save, then find and update the next one.)
| | | ---------------Original Message---------------
From: Brian Samples
Sent: Saturday, April 19, 2008 11:55 PM
Subject: Assigning EEO Codes to Jobs
Given that Assigning EEO codes to Jobs is a step in the Config (IMG) and that job numbers/job keys are usually assigned by the system....AND that the job numbers are different in the different systems along the landscape:
How do you maintain this after go live, in that you have a new job that gets created in Poduction and needs an EEO code assigned to it....what is the methodology you use? Do you create that same job number in DEV and transport it along, or copy all jobs periodically back to dev in order to maintain this?
Looking for suggestions!!! |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Popular White Papers
In the Spotlight View the "Managing the Application Life Cycle" webinar and learn how organizations optimize their SAP applications.  _.____.__ |
