Skip to Content
author's profile photo Former Member
Former Member

HANA Native Transport Across Three Landscapes Dev -> QA -> Prod

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?

Add comment
10|10000 characters needed characters exceeded

  • Hi Garrette.

    If I am not wrong, you are saying that you want to change the DU_XYZ in QA ? But why don't you send the same export which is coming from Dev to QA in Prod also. I think this is the normal practice.

  • Former Member Mrityunjay Pandey

    Hey Mrityunjay, you are close. We want to activate objects in the QA package and send them to Prod using a change ID. We give the developers freedom to develop and activate changes in the development system without restrictions. If we were to transport from Dev to Prod there is a chance that the object was modified in Dev without passing through QA testing, hence the reason we do not also send the object to Prod from Dev.

0 Answers