Skip to Content

Discussion on Cutover Strategy - Dual Track Environment

Hello All,

I am currently setting up the Retrofit and Cutover strategy for a Customer. My Landscape is as below:

Support Track : DEV --> QAS --> PRE-PROD --> PROD

Release Track : DEV1 -->QAS1 -->DEV -->QAS -->PRE-PROD -->PROD

The Release Track changes are moved till production via the Support Track.

An issue has been highlighted as below:

A change done in DEV1 (example Program 1) has ownership mentioned as DEV1 in the object attributes. This object is moved till PROD.

During Maintenance, the bug fixes have to be initiated from DEV (Support Track - Development system).

Do you think this will cause an issue?


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Oct 16, 2015 at 01:10 AM

    Hello Architha,

    You will face this issue when you make maintenance changes in DEV since these objects have the SRCSYSTEM value as DEV1. But it can be fixed by packaging the transports from DEV1 system into a DEV system transport. By doing this SRCSYSTEM values for all the objects in this transport will change to DEV.

    If you perform maintenance after doing the above steps, the i don't see any issues when you are promoting the transport to subsequent systems.

    Best Regards,

    Aravind Kumar Jagannathan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.