Extended Transport Control
Extended Transport Control
In releases prior to R/3 4.5 it was only possible to configure the transport route to go from system to system. As a result you might be used to manually adding transports released from DEV 0XX to Clients 0X1, 0X2 etc by having to e the Extra > Other Requests > Add > and enter Number of change requests if you need to add the client dependent change to other clients in the DEV box. Since R/3 Release 4.5, a feature known as Extended Transport Control has been available. Extended Transport Control is another way to set up the Transport Route so that the route is system and CLIENT specific. In other words, when I release a change request in DEV Client 0XX it will not only automatically be added to the Import Queue for QAS but also 0X1, 0X2, of DEV. To set this up requires the steps below: Open the file TP_DOMAIN_DEV.PFL (located on your transport domain controller such as the DEV box. The file will be in usr\sap\trans\bin) Edit with notepad for each parameter on each system: DEV/CTC = 0 Change to =1 Next you need to create Target Group before creating the transport route. Create a Target Group: Access the initial screen of the graphical or the hierarchical editor in change mode. STMS > Overview > Transport Routes (the default editor will appear, either Hierarchical or Graphical, to change the default editor : STMS > Extras > Settings > Transport Routes.