on 02-16-2017 9:33 PM
I have three system landscapes, Dev, QA, and Production.
In Development we have a package named "XYZ" with many development objects contained within. Package "XYZ" is mapped to a Delivery Unit "DU_XYZ" on our QA landscape that is used to transport the objects to QA.
Here is the problem.
I am unable to to map the "XYZ" QA package to a Delivery Unit on my Production cluster to enable transports from QA to Prod. It is as though the "XYZ" QA package cannot be mapped/associated with more than one delivery unit because it is already associated with the DU moving the package contents from Dev to QA.
The workaround I am using to address this problem is to create a new package on QA named "ABC", export the objects from "XYZ" , manually update the .xml files with the new package name and import objects into the "ABC" package where I can then activate them and transport them to Production. The work is laborious and opens up many opportunities for human error.
How can I enable "XYZ" on QA to be a source for objects being promoted to my "XYZ" package on my Prod landscape?
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.