‎2011 Feb 09 4:24 AM
hey guys,
we have a 3 system landscape with the following clients:
DEV 100: golden configuration client
DEV 200: unit test
CIQ 100: qa configuration client
ciq 200: quality/test client
cip 100: production client
I have all the clients locked down to "not modifiable for both customizing and repository objects" except the DEV 100 client. One of my analysts wants to make changes to the master data in the unit test client because the master data is not there in the configuration client. Should I open this unit test client for modifications? If I do so, will I need to import the changes to CIQ and CIP through transport method or would those changes be made manually ? any kind of best practices surround the changes to master data ? My main concern is that if I open the unit test client, everybody would start doing development and customizing in that client and the configuration client would go out of sync. Please advise.
thanks
VM
‎2011 Feb 09 5:46 AM
Hi,
Any master data changes to a "non modifiable" client can be sent using one of the two options :
1. Transport Request
2. ALE (IDoc)
Most probably the master data change he wants to transport requires an ALE setup between the two systems.
Regards,
Jovito
‎2011 Feb 09 6:18 AM
thanks jovito, but a quick follow up question:
so which client should master data be normally maintained and how should it be transported to subsequent systems?
VM
‎2011 Feb 09 7:06 AM
Capture your master data changes in DEV 100 under a CTS .
The in the DEV200 client use SCC1 tcode to import the CTS .Specify the soruce client and CTS number
‎2011 Feb 09 9:45 AM
Under "master data" I understand application data like G/L accounts, customer master data, etc. (see S11 delivery class "A")
This can and should of course be maintained directly in each system, irrespective of the client settings. You will even be warned if you try to transport such entries via transport requests.
Are you actually referring to customizing settings (delivery class "C") ?
Thomas
‎2011 Feb 17 5:18 PM