Transport Request Number Range Conflict

199 Views

Hi all,

We are upgrading our existing 3-system landscape u2013 DEV(T09), QAS(C09) and PRD(P09) based on R/3 enterprise 4.7 to ECC 6 EHP5 by performing Combined Upgrade and Unicode Conversion.

Our approach to CUUC was as below u2013

Development System (T09)

u2022 We copied PRD(P09) to new DEV(T09) on different physical hardware

(Note - Existing landscape is not yet modified)

u2022 Upgraded new DEV (T09) from 4.7 to ECC 6 EHP5.

u2022 Performed Unicode Conversion of new T09 by export-import.

u2022 Performed developments like SPAU and retrofitting on new T09 ECC6 EHP5 Unicode system.

Quality System (C09)

u2022 We copied PRD(P09) to new QAS(C09) on different physical hardware

(Note - Existing landscape is not yet modified)

u2022 Upgraded new QAS (C09) from 4.7 to ECC 6 EHP5.

u2022 Performed Unicode Conversion of new C09 by export-import.

u2022 Importing SPAU and retrofitting TRs created in new T09 ECC6 EHP5 Unicode system

Here we have TR conflict issue i.e. TR number series that are created in new T09 Unicode System (ECC 6 EHP5) are similar to the TR number series of old T09 4.7 system. If we import TRs from new T09 Unicode system into new C09 Unicode system then we can no longer see the details of TRs imported from old T09 4.7 system.

The concern is the same issue will occur on Production system (P09) after upgrade and T09 TRs mass import. From auditing perspective, auditor should be able to see details of TRs imported from old T09 4.7 system as well as new T09 Unicode System in ECC6 EHP5 systems (C09 and P09).

We are thinking of following below approach u2013

u2022 Reset TR number range in new T09 Unicode System

u2022 Create Transport Of Copies for all conflicting retrofitting TRs (with new number range)

u2022 Import newly created T09 TOCs in new C09 and P09 systems. So we can see details of old 4.7 TRs as well as new ECC6 EHP5 TRs.

Please let us know your suggestion on this.

Thanks and Regards,

Meghan/ Tej