Using transports from an ECC 5.0 system for config changes in 6.0

Using transports from an ECC 5.0 system for config changes in 6.0

I just joined an organization that is running both an ECC 5.0 system and a 6.0 system. They are considering using transports from the 5.0 system to make configuration changes in the 6.0 system (and even some workbench items). I've never heard of anyone suggesting this before. Besides, the obvious issues with conflicting configuration, is there a technical reason why they should not attempt this?

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Have a look in OSS NOTE 1090842 - Composite note: Transport across several releases, it lists all restrictions in transporting between different SAP releases.

Basically, you can transport development objects between SAP releases if you take the restrictions from the OSS note listed above into account. Transporting customizing is not supported.

This was first published in June 2008

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.