Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Log On Join Us Hi, Guest Search the Community
Activity Communications Actions
Browse
0 Tweet 0
5 Replies Latest reply: Jan 2, 2013 6:33 PM by Jean Clappier
Share 0 Like
Automatic transport between DEV clients ?
This question has been Answered.
Hello,

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 :

DEV :
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.
Raoul Shiro Jul 24, 2008 11:34 AM
Correct Answer
by Karthic Raj Ganesan on Jul 24, 2008 1:35 PM
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.

Example:
Target System
Target Client
Client Name

DEV
0X1
Sandbox

DEV
0X2
Testing

QAS
0XX
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 !!!.
18977 Views
Average User Rating
(0 ratings)

Reward points if helpful


Hope this helps.
Re: Automatic transport between DEV clients ?
Hi,

Check out these links may be of some use.

http://help.sap.com/saphelp_nw04/helpdata/en/1c/2ddc0901db11d284870000e8a57770/frameset.htm


http://help.sap.com/saphelp_nw70/helpdata/en/3d/ad5bcf4ebc11d182bf0000e829fbfe/content.htm


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

EXtended Transport configuration may be of some help...

Thanks.

Edited by: Vani n on Jul 24, 2008 12:28 PM
Like (0)
Vani n Jul 24, 2008 12:29 PM (in response to Raoul Shiro)
Re: Automatic transport between DEV clients ?
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
Correct Answer
Karthic Raj Ganesan Jul 24, 2008 1:35 PM (in response to Raoul Shiro)
Use a separate line for each client.

Example:
Target System
Target Client
Client Name

DEV
0X1
Sandbox

DEV
0X2
Testing

QAS
0XX
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.
Like (1)
Re: Automatic transport between DEV clients ?
Great answer, I applied the mentionned settings this morning, it works !
Thank you very much.
10 points of course.
Like (0)
Raoul Shiro Jul 28, 2008 9:37 AM (in response to Karthic Raj Ganesan)
0 Tweet 0 Share 0 Like
Re: Automatic transport between DEV clients ?
Hi,
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



Like (0)
Jean Clappier Jan 2, 2013 6:33 PM (in response to Raoul Shiro)
Re: Automatic transport between DEV clients ?
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.
Like (0)
Tsuey Ho Jul 30, 2009 12:48 AM (in response to Karthic Raj Ganesan)
Follow SCN
Site Index Contact Us SAP Help Portal
Privacy Terms of Use Legal Disclosure Copyright