Multiple Dev source client to same target client in QA

[Former Member]

Hi Experts, Need your 1 mins here.

We have a scenario where any transport created in 010 and 210 Development should go 210 QA system. and we have defined in one logical component where is

SU1 DEV 010 Source

SU1 Dev 210 Source

SU2 QA 210 Target

SUP 210 Production

SU1 = Development System (010 , 210 client)

SU2 = Quality System (210 client)

SUP = Production System(210 Client)

Solman->Transport Group-> SU1-> SU2->SUP

As per sap blog.

http://scn.sap.com/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-qu... : reference : 1. How many development clients are possible?

We have defined the specific client in client specific setting SU1 as well.  And we tried to request preliminary import for any transport  created in 010 client, CHARM will showed error"Transport has been imported, preliminary import not applicable" . We have checked in STMS > import history, the tr is not imported actually.    

But any transport created in 210 client, everything go smooth.

Any advice? Thanks

[Former Member]

Hi Raymond,

Configuration of transport route is wrong. There is no transport route defined from SU1 010 to SU1 210.Current configuration will work for SU1 210 --> SU2 210 --> SUP 210.

You need create transport layer looping back to SU1 210(consolidation route) SAP and ZSU1.

SU1 010 --> SU1 210 (consolidation route) looping.

SU1 210 --> SU2 210 (delivery route)

SU2 210 --> SUP 210 (delivery route).

If you need changes to be created in SU1 010 and SU1 210 then :

SU1 010 --> SU1 210 (consolidation route) looping.

SU1 210 --> SU2 210 (delivery route)

SU1 210 --> SU2 210 (consolidation route)

SU2 210 --> SUP 210 (delivery route).

Regards,

Pradhan Surya

[bxiv]

What is the point or reason behind the transport group between SolMan and the remote systems?  Is this all within the same Transport domain?

[Former Member]

solman and remote system is different domain.

[bxiv]

When you have different TMS domains, SolMan can not understand nor control the transport routes.  Can you move a empty transport through the remote systems landscape without using SolMan?

[Former Member]

We have tried to delete solman in the tms and reconfigure as below

SU1(DEV) -> SU2(QA) -> SUP(PRD)

But getting the same error. The transport from multiple dev client can be moved into QA by urgent change but not normal change

[VJain]

Please check:

2116964 - ChaRM: condition check PRELIM_PRD_NOT_IMP gives wrong result if the

project contains multiple transport tracks

2019770 - ChaRM: normal change cannot be set for production import with

incorrect error message

Thanks

Vikram

[VJain]

also check:

1820635 - How to analyze errors when changing the status of a ChaRM

          Document