Questions on N+1 DLC TR Retrofit on Different Code Bases

[Former Member]

Dear experts,

We have a Project oriented N1 DLC on ERP6 EHP5 SP5 and a Production Support oriented N DLC on ERP6 EHP4 SP5. In order to prepare the N1 DLC for new projects, we need to retrofit around 2,000 transports from N DLC to N1 DLC, which comprise customizing changes, workbench developments/modifications, and SAP OSS notes. When our team add those transports into the N1 System buffer, the process takes much longer than usual and virtually all the transports have a status u201CDoes not match component versionu201D. Questions we have are:

u2022 Can we import those TRu2019s directly into the N+1 DLC? If we do so, what might be the negative impact?

u2022 What is the recommended best practice to deal with this type requirement?

Thanks,

Joshua Zhang

[Former Member]

Thanks Sunny. So basically your approach will be using manual retrofit since those TR's have to be moved over to the N+1 DLC any way?

When I check the OSS note 1273566, however there seem no issues:

************************************

Transports from SAP_BASIS Release 700/701 to >=702

a) Technical transport problems

None yet known.

b) Logical transport problems

None yet known.

**********************************

Still very confused regarding the most effective technology on this issue. Any further information is appreciated.

Thanks,

Joshua Zhang

Edited by: Joshua Zhang on Oct 25, 2011 2:15 AM

[sunny_pahuja2]

Hi,

Check SAP Note 1090842 - Composite note: Transport across several releases

Thanks

Sunny

[sunny_pahuja2]

Hi,

You are trying to send transport from EHP4 system to EHP5 system which is not supported because version of the objects between the two systems will be different as a result system will become inconsistent if you will transport the objects between 2 systems of different release.

Best practice is don't transport between the systems having different SP releases.

Thanks

Sunny