Clarification on reverse implementation of S4HANA codes to ECC 6.0.

[ajay_mukundan2]

While there are plenty of resources for migrating codes from ECC 6.0 to S4HANA, we have scenario wherein the S4HANA codes (Incl. enhancements) (over 5000 custom codes) done for a project (say ABC) in EHP8 ERP 6.0 on SAP Netweaver 7.50 (Fig1.0) needs to be implemented for another client (say XYZ) on EHP5 ERP6.0 on SAP EHP2 FOR SAP NETWEAVER 7.0 (Fig 2.0).

Note: We cannot use Transport management tool for transporting TRs as both are different landscapes.

Fig 1.0

Fig 2.0

Q1. Having said that we have over 5000 custom codes spanned across 70 Workbench TRs, and exporting co-files and data files, can we import Transport Requests (Customizing and Workbench) to old ECC 6.0 from SAP S4 HANA system, if yes how easy or challenging that can be?

Q2. Lets say we the Transport requests from S4HANA system have the name starting with KED and the system ID of ECC6.0 is TED. While importing the TRs to ECC6.0 system, can the objects be captured in transport of copies?

Q3. Which activities need caution while 'downporting' the development objects (Inc. IMG Customizing) in the ECC6.0?

Any help is appreciated.

[sumitjais]

Hi Ajay,

It is not recommended to import transport between systems with different releases. This may result either inconsistencies or data loss. This is true for the import between any two EHPs of ECC and between S/4 & ECC.

Also, it really does not matter if the systems belong to same TMS or you require to copy data files and cofiles for the import.

For your case,check 2192251 - Transporting Settings Between S/4HANA Finance (or S/4HANA) and Classic ERP System for the details of the problems.

Hope this helps.

[ajay_mukundan2]

Thanks for your inputs, Sumit!

Would like to know what other ways are there to bring approx 7k objects into target system on different landscape?

[sumitjais]

Hi Ajay,

I am not sure why do you want to bring data from customer ABC to XYZ. I believe you have sorted out the legal implications.

Nevertheless, since you are planning to import data from higher release (EHP8) to lower release (EHP5), you can look forward to upgrade the target from EHP5 to EHP8 and then import the changes from source by copying the respective transport files.

Later, once the changes for the customer XYZ are validated, you can plan the conversion from EHP8 to S/4HANA.