Problem with target system in ChaRM

[FransLelieveld]

We are working with SolMan 7.1 SP 8

We implemented ChaRM about a month ago. The process is working quite well until we run into a problem today with transport requests.

We have a 3 system landscape where we use 2 clients in the development system, 1 for the developments (DDS131), 1 for the testing (DDS130). Our transport route goes from DDS131 --> DDS130 --> QDS130 --> PDS130.

This is working fine for all normal developments. But today we got a change which is in package SAP. For this one it is asking for a transport that has QDS130 as target system. However, all transports created by ChaRM have DDS130 as target system. We also tried to have the transport layer directly from DDS to QDS130 but tha did not have any effect,

Any ideas how to solve this?

[FransLelieveld · Accepted solution]

It seems all is working correctly now. Probably there was some old route still in an old transport.

[Vivek_Hegde]

Hi,

By default, in DEV environment, if you create a TR it will have subsequent QAS system as Target system. The transport within the system need not be part of ChaRM framework since you can use SCC1 to import into different DEV client within the DEV system itself.  But you have already defined Transport Route DDS130 > DDS131 > QDS 130 > PDS 130, which in first place should not have been there. This is because if you create a Workbench request (may be this is the case in package SAP) it will always look for target as QAS system since workbench changes are client independent.

So in my opinion, you can go ahead and create a TR which is having QAS as target. When it comes to testing in DDS 131, the changes made in DDS 130 will always be there.

Regards,

Vivek