Transport target system inconsistency

[Former Member]

Hi all,

Initially, we had a three tier landscape with transport routes defined from DEV->QAS-> PRD with DEV as

the domain controller. Now we have changed the landscape and we have new configuration with DEV as

the domain controller and a virtual QAS system like DEV -> Virtual QAS and QA -> PRD.

After this we are getting an inconsistency of modifiable transport requests with respect to their transport paths in DEV system.

The transport requests based on the first config had target system QAS.

Now most of the transports are not having any target systems and are showing as local change requests while few others have got the new target ie Virtual QAS.

Please help as to know the reason what can be the cause of the inconsistency.

Regards,

Sandeep.

[Former Member]

Please make sure all target systems are in Transport route. Once the systems are in same route and distribute to all systems.

[JPReyes]

have you distributed the new configuration from the domain controller to the rest of the lanscape?...

Regards

Juan

[Former Member]

Yes, thats done. New transports do not have a problem and are automatically assigned the new

target system on creation.

[Former Member]

You said some of the old transport requests got adjusted automatically and some are showing as Local request.

Once you activate and distribute the config, all the requests should have adjusted.

Are you sure, the local requests were not already Local in the first place?

Just asked, in case you missed to notice.