TR release issue

[sandymohan_1551]

URGENT ADVICE needed:

We have 3 clients under Dev 200, 210 and 299.

I did a play run in 299 for creating new movement type.

After this, I started created the mvt type in client 200 and captured in TR. Now I released my TR to client 210. I did SCC1 from 200 to 210 with my TR as input aswell.

But somehow, my config in 299 are reflecting in 210 rather than from client 200.

Need help in resolving this ?

[sandymohan_1551]

Resolution:

We deleted the mvt type which was causing issue and capture a new mvt type.

Transported all the TRs in sequence. It went well.

[DominikTylczyn]

Hello sandymohan.1551

You must have put 299 instead of 200 as the source client in SSC1.

Best regards

Dominik Tylczynski

[sandymohan_1551]

No Dominik. Because in my SSC1 if I input my TR , it would allow me to copy from the correct destination alone, throws error if I gave in 299 as my source.

So would not have happened by overlook as well.

The wired thing is now my config in 299 are in sync with 200 when I checked after some time. But my 210 is not reflecting client 200.

I tried to create a new TR "deleting the config in 200 and recapturing it again" Now after SCC1, again some additional entries are created in my Dev210.

[Neeraj_Jain]

Hello sandymohan.1551,

Please connect with your Basis team to fix this. Actually they now very well how the system landscape is designed for transferring TR.

Regards,

Neeraj Jain