Quantcast
Channel: SCN : Unanswered Discussions - SAP Solution Manager
Viewing all articles
Browse latest Browse all 5299

Transport sequences, normal change and java

$
0
0

Hi

 

I have a problem with CHARM, transport sequences, normal change and java.

 

The scenario is we have a normal change with 2 transports, lets say TR:1 and TR:2.

 

 

TR:1 is already assembled (developed) in CMS and done, when we now assembled (developed) in CMS

and put it into TR:2 its creating a new transport of copys in the Normal Change for both TR:1 and TR:2 when we "Pass Normal Change to test".

 

 

The problem is that the TR:2 creates first in the import queue in TMS and then TR:1 when we "Pass Normal Change to test" on the normal change.

The developers have used same component(object) so when we import this we first get the new code(TR:2) imported and then we get the old code(TR:1) imported if we follow the import queue.

 

 

Why its behave like this?

Is it possible to decide which order its get released in TMS or whats decide the release rule to the import queue?

Is the solution to split this two transport into two normal changes?

How can i solve this problem?

 

We have latest and greatest support patch on solution manager.

 

Regards Ulf Lundqvist


Viewing all articles
Browse latest Browse all 5299

Trending Articles