cancel
Showing results for 
Search instead for 
Did you mean: 

New Target group for moving transports automatically into 2 instances.

Former Member
0 Kudos

Hi all, let me explain you the scenario ...

We have an instance called C01 and people (developers) use C01 as target to release their transports.

Todaywe have a new instance called C02 and we are on the end of refresh activities.

We are currently importing all transports that took place during the refresh period to make CBB current with CAA. DAA is now the source system for transports to CAA and CBB, both are configured to run the auto import job every 30 minutes.

We let all developers and application support person know that there is a new transport target group that they must use. Previously it was CAA, the new target group is /XYZ/. By selecting this target group transport will go to both CAA as well as CBB at the same time.

The issue is:

The transport DAAK123456 has configured using XYZ (not CAA, consolidation environment).

The transport was moved automatically from DAA to XYZ but not it has not been moved to CAA.

We have seen that apparently when they do a transport of copies this happens.

QUESTION IS:

what is wrong when they do a transport of copies?

Mean while we have to move the transports manually from DAA to CAA and we do not want to do that anymore.

Please your support to fix this issue.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Sorry, the two first lines have the incorrect name of the instances, these lines are correcto.

Hi all, let me explain you the scenario ...

We have an instance called CAA and people (developers) use CAA as target to release their transports.

Today we have a new instance called CBB and we are on the end of refresh activities.

We are currently importing all transports that took place during the refresh period to make CBB current with CAA. DAA is now the source system for transports to CAA and CBB, both are configured to run the auto import job every 30 minutes.

We let all developers and application support person know that there is a new transport target group that they must use. Previously it was CAA, the new target group is /XYZ/. By selecting this target group transport will go to both CAA as well as CBB at the same time.

The issue is:

The transport DAAK123456 has configured using XYZ (not CAA, consolidation environment).

The transport was moved automatically from DAA to XYZ but not it has not been moved to CAA.

We have seen that apparently when they do a transport of copies this happens.

QUESTION IS:

what is wrong when they do a transport of copies?

Mean while we have to move the transports manually from DAA to CAA and we do not want to do that anymore.

Please your support to fix this issue.

Former Member
0 Kudos

Hi,

Please check for the Target while creating the transport copies.

Regards,

Sanujit