Skip to Content

Automatic transport between DEV clients ?


SAP release : SAP R/3 Enterprise

We're trying to change our transport strategy, especially concerning the transports requests

from DEV reference clients to others DEV clients.

Systeme Landscape :


Reference Client : 150

Clients: 100,200,300,400,500,600,700,800,900

I know that you should use transaction SCC1 to perform customizing copy between the different

clients of DEV, but I would like to know if it is possible to do automatic transport between thoses clientts ?

I can't use the standard report TMS_BCI_START_SERVICE in DEV, since it is the QAS queue that is filled

one a transaport request is released.

DEV queue contains mostly support package and clients copy transport requests.

I've tried to implement a target group with the QAS client and all the DEV clients but it didn't help.

Transport requets that are released on DEV/100 are only filling QAS transport queue.

The question is : How can I fill automatically DEV transport queue once a trasnport requests is released in DEV100, this way those transport requests will be transported automatically to other DEV cleints using TMS_BCI_START_SERVICE ?

Bets Regards.

Thank you in advance for your help.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 24, 2008 at 11:35 AM

    You can use Extended Transport Control.

    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 you 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:

    1) Open the file TP_DOMAIN_DEV.PFL (located on your transport domain controller such as the DEV box. The file will be in usrsaptrans/bin)

    Edit with notepad for each parameter on each system:

    DEV/CTC = 0

    Change to =1

    2) 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. You can also switch to one or the other from Goto > Graphical Editor.)

    > Configuration > Display Change > (or change icon or F5)

    Edit > Transport Target Groups > Create

    In the dialog box, Create Target Group:

    Enter a name for the target group /GR_QA/ (The name must begin and end with a forward slash /)

    ...and a description Targets for Consolidation route

    Choose "Insert line"

    Enter the required target system/client combinations

    Use a separate line for each client.


    Target System

    Target Client

    Client Name









    Quality Assurance System

    The idea is that we want to include the clients that will get an addition to their import queue when we release a change request from DEV.

    Choose Transfer

    Now you have to change the transport route to include the Target Group you created.

    STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Delete

    Now create a Transport Route with Extented Transport Control:

    STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Create > Extended Transport Control icon at lower left of dialog box. > Consolidation route, enter integration system and transport layer. In Target system/client enter the SID of either an R/3 System and a client or an existing Target Group.

    Each System must be specified by System and Client. The Target Group can be used for the consolidation system.

    Distribute and activate the changes as usual by choosing Configuration > Distribute and activate

    NOTE: After you set up Extended Transport Control there might be requests in an import queue that will show a red status in the CTL column. This is because these change requests need a client specified before they can be imported. These are old requests that were already in the queue.

    From Import Queue Screen Mark the change request

    Choose Request > Target Client > Set

    Enter the Target Client ID and choose Enter.

    To change a target client before starting an import:

    Import Queue Screen > mark Change request > target client > change > enter target client id and choose enter.

    Now you are ready to set the automatic transport/import job

    Goto TCODE STMS -> Overview Menu select Import -> Double click on the SID -> Click on Import all Requests truck -> Select At Start Time -> Enter a time and date -> Press F4 and select the period the job has to run -> Now the background job i scheduled and imports will be done in periodic intervals as mentioned in the job

    Hope this is helps you !!!.

    Reward points if helpful

    Hope this helps.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi there,

      We did the procedure correctly. However, we found error in SLOG####.<SID> saying 'ERROR: <request name> : couldn't locate TA-info in .../cofiles'.

      I found that the first line in the header of the cofiles contains below

      USERNAME W /<group name>/ 3 0 0 0 0 4 0 0 0 4

      TP program does not recognize our group name. What have I missed? Please help.

  • Jan 02, 2013 at 05:33 PM


    May i add to this very helpful post that if you wish to set up automatic transport only for a specific client (and not the entire queue containing requests for other clients), you just need to set a filter on column “client” before clicking on the Import all Requests truck.

    Regards, jean

    1.jpg (25.9 kB)
    2.jpg (13.5 kB)
    3.jpg (24.4 kB)
    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 24, 2008 at 10:27 AM


    Check out these links may be of some use.

    The client specific transpots has to be activated by setting parameter CTC=1

    EXtended Transport configuration may be of some help...


    Edited by: Vani n on Jul 24, 2008 12:28 PM

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 21, 2015 at 12:34 PM

    Hi Karthic Raj Ganesan,

    Please add me as your friends i Need your help regarding TMS

    Hope you will help me



    Add comment
    10|10000 characters needed characters exceeded