STMS Problem after upgrade

[Former Member]

Hi ,

We recently started upgrading our 4.7EE systems to ECC6 parallely, without disturbing the existing landscape by using backups of each system. Now the doubt ihave is after the upgrade can we import the TP's to ECC6 which are created in 4.7 systems. Should we need to re-configure the STMS after the upgrade

Please suggest.

Thanks,

Pundari

[Former Member · Accepted solution]

Hello,

There is a general rule for transports across different releases:

- Customizing: not allowed

- SAP repository objects: not allowed

- Own (Y, Z) repository objects: mostly allowed

Note 1090842 gives details about objects that can and cannot be transported between systems on different release levels.

The current practice is thta changes made in one landscape are applied manually (not through transports) in the other if they are relevant there. In the old (pre-upgrade) landscape changes should be kept to an absolute minimum, preferably only bug fixing.

Regards,

Mark

[Former Member · Accepted solution]

Thanks for the relpy. Now the problem we have is do we need to configure STMS or should continue with old one in the ECC6 landscape??

Edited by: pundari kakshayya on Mar 11, 2010 3:50 PM

[JPReyes · Accepted solution]

We recently started upgrading our 4.7EE systems to ECC6 parallely, without disturbing the existing landscape by using backups of each system

That means you have 2 environments... so why you want to transport in between them?... Transporting requests in between different versions is simply a no go.

do we need to configure STMS or should continue with old one in the ECC6 landscape??

You will need a new transport domain for your ECC landscape. in any case don't you have a developement freeze in place? usually you want to keep them consistent.

Regards

Juan

[Former Member · Accepted solution]

Thanks Juan my doubt is cleared now.

Pundari