Discussion on Cutover Strategy - Dual Track Environment

[ArchithA]

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?

Regards,
Architha

[Aravindkumarj]

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