Parallel Transport Mechanism

[Former Member]

Hi,

We are planning to have a parallel landscape solution of ECC 6.0 for our client.

Existing landscape-- DEV>QA>PRD

Parallel Landscape-- DEV1--QA1

Whatever we design we will transport in the following path:

DEV1-->QA1

Then the objects will be transported from QA1-->DEV

As the transports reach DEV it would follow the existing route:

DEV>QA>PRD

Client has reviewed the proposed parallel landscape solution with their technical architect and would like to understand how we propose to handle the system ownership of transports. Each transport is stamped with the SID of the originating system. Once we move these transports into existing Development, then we will not be able to change the configuration / code of the transport. How do you propose that we can regain ownership of the configuration / code once in the existing landscape?

Proposal given by us to the client:

The ownership of the transports from Parallel/project landscape to existing landscape can be achieved in multiple ways by Basis function; following SAP standard options are generally followed.

Option 1 - Transports from a system originates with SID and owner ship of the user. When we import this transport to another system, selectively Basis can help to modify and regain the owner ship of the particular transport. The prerequisite for this is the old developer should exist in the system.

Option 2 - We can create a new transport and add the imported transport/objects to new transport request to gain the ownership of the objects of the transport.

Is these the correct options??Is there any other way we can maintain the ownership of the transports??Please guide & suggest me.

[rossmclanachan]

The rekeying (also called dual maintenance) of Business as Usual transports that have reached Production back into your Project landscape, is definitely advisable, as it will ensure that the two landscapes are kept consistent and in sync, and you do not hit unexpected issues when your project cuts over to your BAU landscape that you did not see during Project test phase.

However doing this rekeying manually can be an extremely time-consuming and human-error prone activity, and often introduces new issues and inconsistencies.

As already mentioned by Ashutosh, tools like  Transport Express can automate this activity.

TE Merge capability automatically creates new transports for the objects contained in the BAU transports, and puts them into the Project landscape, avoiding the need for developers to do it manually. You can see a demo of how TE’s Agile Multi-track development functionalities can help make your organisation more efficient and avoid the need for manual rekeying on your multi-tier landscape on the BTI website

http://www.basistechnologies.com/online-demos

If you are interested in finding our more about TE, please contact us via our website.

Thanks

Ross McLanachan

http://www.basistechnologies.com/

For transparency, I should state that I work with Basis Technologies, the software vendor behind Transport Express and other SAP-certified products. Prior to this, I spent almost a decade working in various SAP Change & Release and other delivery roles for a large global SAP consultancy, and so know first-hand the many faced by many SAP customers still delivering their SAP Change using largely manual processes