on ‎2013 Oct 13 10:27 AM
Dear SAP Gurus,
My name is Rohit and i have recently put into one big implementation project. So for that i need some clarification.
While configuring Personnel Administration, Time Mgmt. Payroll etc in development client only one customizing request will be created or everytime we have create new customizing requesting.
For E.g - In P.a we configure Personnel Areas, Persoonel Subareas, Actions...etc so for this all configuration only 1 customizing request will be there or separate for each new configuration.
2. If it is same request then will it also be continued for TM & Payroll...for transporting to another client..or not
Please share your views earlier as i am in big trouble...as this is my 1st implementation.
Request clarification before answering.
I basically agree with Omid: this is a guideline project management needs to provide.
Throwing in my experience: in most cases I'd use one transport only until the first transport is to be moved into the QA environment. Using many usually leads to confusion and errors re objects needed in several transports.
From that point onwards, you need to think in testable packages to go onto separate transports and be tested.
Be cautious about schemas as one schema might be involved in two separate activities.
Kedhar's note about sequence is important! Particularly when moving on to production later. Always remember that the objects are on the transport in the version they had, when the transport was released. So, to avoid older versions overwriting current versions, you need to transport in sequence of release - not transport number.
Just my 2p - there are different ways to approach the problem.
Kind regards
Sven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 23 | |
| 21 | |
| 17 | |
| 11 | |
| 8 | |
| 6 | |
| 6 | |
| 4 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.