on 03-05-2010 5:10 PM
Hi,
I have two different clients in DEV- One for Configuration and one for Development. I want that consultants working in their respective clients are able to create transport requests and after release from these respective clients, requests get imported to a single client in QAS system.
Can this be acheived by normal TMS configuration (without Extended Transport Control)? If yes how?
Regards
Sourabh Majumdar
Hi,
Can this be acheived by normal TMS configuration (without Extended Transport Control)? If yes how?Yes.
Understand the following basic relationship behind transporting chagnes using TMS
....Repository Objects ->are assigned to-> Package ->are assigned to->Single Transport Layer ->is assigned to-> Single Transport Route -> Target System.
The basic concept behind standard Transport Control is that every repository object in Source System (e.g Dev-System) is assigned (via a package) to a certain transport layer, it follows that a change request can only have one target system. So, you can transport change requests from multiple clients of Development System, which you can import into QUA system's clients upon release.
With the standard Transport control program, it is not possible to create two transport routes with the same transport layer from one SAP System. Thus, The extended Transport Control program is used for transporting the changes based on Client specific Transport Routes by using the concept of Transport Group. Using this, one can transport changes to multiple systems, multiple clients using the same transport layer.
Regards
Bhavik G. Shroff
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bhavik for the crystal clear explanation.
However I have doubt regarding Customization requests? Will it hold the same principle while releasing the requests from the client where customization settings will be done for import to the same client in QA?
That means we don't need to make use of any transport group concept and simply assign the standard transport layer while configuring TMS?
Regards
Sourabh Majumdar
Hi,
Will it hold the same principle while releasing the requests from
the client where customization settings will be done for import to the
same client in QA?Yes.
That means we don't need to make use of any transport group conceptYes.
simply assign the standard transport layer while configuring TMS?Yes.
Regards
Bhavik G. Shroff
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.