Only one transport instance complete when transporting to multiple clients

[AndreC1]

Hi everyone,

Sorry for the confusing subject line. We have multiple clients in DEV and QA, and we configured the transport system to distribute transports to all clients when a transport is released. For example, if a transport is released from DEV100, it will go to DEV120, DEV140 and so on. In our R3 system, we could multi select all instances of the transport and run the transport into all clients at the same time. Since we have been on ECC6 EHP7, only one of the instances will complete. All the other instances will return to the ready for import state (green square). Is that a due to a design change or is something else at play here? We are very new to ECC, so we are not sure if this is the new normal or not.

[former_member314331]

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

Regards,

Phani

[AndreC1]

Hi Phani,

I want to give you kudos for writing that up. Awesome of you to take the time and type that up. It will be very helpful to many people.

Fortunately, we already completed all these steps before. Our problem is this:

• You release the transport (DEVK900001 for example) to the target group. The transport system now adds it to the import queues of DEV 100, DEV 200, DEV 300 and QAS 100.
• We select DEVK900001 DEV100, DEVK900001 DEV200 and DEVK900001 DEV300 and press the partial transport icon (half truck).
• All three selections change the status icon from the green square to the half truck icons.
• When you refresh, DEVK900001 DEV100 updates its status icon to the green check mark (completed successfully), but the other two selections change their status icons back to the green square (Ready for import).

Only the first selection of a particular transport completes at a time. If we use the transport all (full truck), then all transports complete as normal.