Applying support packages in the development box

Applying support packages in the development box

Should we apply support packages in the development server separately and start applying them in the production server separately? Is there any other way to transport things from the development server to the production server?

    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.

You need to apply the support packages in your development box first. If conflicts arise during the import of the patches, you will be prompted to make adjustments, which as a result creates transports on the development box.

Test the system (hopefully you have a sandbox client in your development box). You must release the transports once you're done applying the support packages. If you have a quality assurance box, import the support packages there and import the transports from development so you don't have to make adjustments manually again.

Import the support packages in your production box and import the transports (if any) from development. Do not apply support packages to all systems simultaneously -- always do this first in your development environment. Make sure enough testing is done and that business users sign off their test scripts before you import into production.

Keep in mind that there's no "undo" functionality. You have to restore from a database backup in order to bring the system back to its previous state.

This was first published in June 2005