cancel
Showing results for 
Search instead for 
Did you mean: 

STMS - Transport Routes - Multiple Clients and Systems

former_member229542
Active Participant
0 Kudos

Hi Guys

We are setting up a ERP Landscape based in four systems

AED - Gold Development (Most Development starts from here)

AEC - Customer Development (101,102,103...)

AEQ - Customer QA (401,402,403,...)

AEP - QA Production  (701,702,703,...)

Our main goal is to release transports from AED 100 to all clients in AEC (101,102,103...)

CTC was already set up to 1, and all system share a same Trans Dir

For this purpose I have created a transport Group /SOD_DEV/ and added AEC 101, 102 and new clients would be added

Only customizing request should be replicated on each client, and workbench only for one client.

Then, I need also all the transports from AEC go their respective client transport queue in AEQ and AEP

Example:

AEC 101 --> AEQ 401 --> AEP 701

AEC 102 --> AEQ 402 --> AEP 702

And in the future it should be able to expand to

AEC 103 --> AEQ 403 --> AEP 703 and go on.

My questions are:

Should I create a Transport Group for Customizing and Transport Layer for Workbench? O can I use a single Tranport Layer for both Workbench/Customizing?

How can i create a route from AEC so transports who got imported in 101 are automatically delivered to 401 and then 701?

Thanks

Martin

Accepted Solutions (1)

Accepted Solutions (1)

yakcinar
Active Contributor
0 Kudos

Hello Martin,

You need to configure STMS using Extended Transport Control Using Client Dependent Transport Routes. If you are using client in one of the transport routes you must use clients for all routes.

Firstly /SOD_DEV/ target group is okey. This group will be between AED and AEC clients. ZAEC and SAP will be transport layers. All workbench and customizings will use these layers.

You donot need to create extra transport layer.


Between AED and AEQ you need to define target groups using clients. Another groups for AEQ and AEP.



Here is an example transport routes.


Regards,

Yuksel AKCINAR

former_member229542
Active Participant
0 Kudos

Hi Yuksel, thanks for your input.

We agree with a tranport Group between AED and AEC. Transport layer is ZAED.

All developments made in AED, are distributed to Transport Group /SOD/ to all AEC clients (100,101,102...)

Now comes the tricky part

for example, all requests that were imported in AEC 101 should be delivered to AEQ 401 and then delivered to AEP 701 only

That why I didn't put a transport group between AEC and AEQ, since it should be a dependency.

Any transport that was imported on AEC should follow their respective route

Workbench: AEC 100 --> AEQ 400 --> AEP 700 (Sytem-Wide Workbench requests)

Client 1: AEC 101 --> AEQ 401 --> AEP 701 (Client-Dependent Customizing)

Client 2 :AEC 102 --> AEQ 402 --> AEP 702  (Client-Dependent Customizing)

And it wiil follow with

Client 3 AEC 103 --> AEQ 403 --> AEP 703 (Client-Dependent Customizing)

It created these delivery routes; as example for Client1:  AED101-AEQ401 and AEQ401-AEP701. Is that correct?

See attached the screenshot for better reference, you are welcome to further suggestions

Best

Martin

yakcinar
Active Contributor
0 Kudos

Hello Martin,

Below picture can help you.

We used it in one of our projects.

You need to use target groups with clients.

Regards,

Yuksel AKCINAR

former_member229542
Active Participant
0 Kudos

Thanks Yuksel

Answers (1)

Answers (1)

former_member185239
Active Contributor
0 Kudos

Hi Martin,

Kindly follow the link along with

Using and configuring the Extended Transport Control (STMS)

With Regards

Ashutosh Chaturvedi