If you are free to play around or tinker with the difference between using the child transport # and parent transport #, feel free to do so. The objects you need are contained in the child transport.
You should see a notification saying “Object Entries from were passed to Select the Include “Object List from Request” radio button and enter the Child Transport # from your “Main Transport”. Click on the Saved TOC# (Orange Box) then click Request / Task > Object List > Include Objects.Ħ. This way, I can easily distinguish TOC’s when it reaches the other SAP Environment/s.ĥ. My personal preference is to include “TOC” and copy the exact text from my main transport. This naming convention depends on your organization or client preferences. In the example below, I use the format “TOC ”. Then click on the save button to proceed. Be sure to include the Target SAP Environment. Copy the same description / text from your Main Transport and append “TOC”. Then click on the Check button to proceed.Ĥ. Click on the Create Request button (highlighted in red below) and select the “Transport of copies” radio button.
Go to Transaction Code SE10 to view that main transport in the Transport Organizer. In reference to the image below, SRD334876 (Green Box) is the Child Transport #.Ģ. In the SAP Development Environments, perform the configurations / code changes and save them in a Transport. You will then release the TOC only and move it to the intended SAP Environment. Once you’re done saving the changes in the “Main Transport”, you will create a Transport of Copy (TOC) – which contains the same content as your “Main Transport”. Let us call this transport as the “Main Transport”. The idea of Transport of Copies (TOC) is to perform your SAP configurations or code changes in the SAP Development environment and save it in a Transport.
How to Create Transport of Copies (TOC) in SAP You can read more about this behavior in this SAP Help Document. Overall, TOC serves as a suitable option for testing purposes in certain SAP environments. It is a lot “cleaner” and you can ensure that it is not imported into the production system. This TOC will not be automatically transported across your SAP system landscape (following the transport track). You can move the TOC to a certain SAP environment of your choice (for example, where you intend to test). This is where the functionality of Transport of Copies (TOC) comes in handy. Given this concern, you would not want the “unfinalized” or “unapproved” or “unintended” transports to be found in other SAP Environments (train stations). You could expect some errors to be reported that would entail code or configuration revisions. Now consider a scenario where the changes need to be tested in other SAP Environments before it is moved to the production environment. What if there are changes that need to be done after testing?”. This means that if you release your transport in SRD (Development System), you will find the transport automatically available in SRQ, SRR, and SRP after some time (following the flow above). The train follows the route provided above where the SAP Environments are the train stations. Let us also consider the scenario where we have a Transport Track setup in the order below. Let us say that we have the following SAP Environments below: SAP Environment
What is the purpose of Transport of Copies in SAP?Īs a Functional Consultant or a Developer, you need to be able to move configurations or code changes to other SAP Environments.
In this post, we will quickly go through the detailed steps needed to create and release your SAP Transport of Copies or TOC.