cancel
Showing results for 
Search instead for 
Did you mean: 

Support Packs & Unreleased Transports - Conflict

Former Member
0 Kudos

It has been explained to us that we will have to release our transports before we can apply SP/SPS. This is a real problem because the project team is not ready to release their transports. There are hundreds of transports for our next project that are not nearly ready to be released in Dev.

How do we solve this conflict: We need to apply a SPS, but we are not ready to release all 500 transports (many of which contain configurations).

Thank you,

John

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Are you releasing these transports to release the locks on the objects? Instead of releasing, you can use the transport tools to unlock the objects manually (and possibly use versioning to save what you already have in the transports).

Hope that helps.

J. Haynes

Denver, CO

Edited by: Joe Haynes on Jan 17, 2008 3:38 PM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi John,

You should only need to release any transports that contain repairs to SAP objects and these objects are contained in the SP that you need to import. Repairs to SAP objects would come from applying SAP note corrections either manually or via the Note Assistant.

I would first analyse how many repaired objects there are contained in open transport requests in your system. These are the ones that you'll have to release in order to get the SP imported into DEV; there may only be a few. You can perform the analysis in SE10 using the Transport Tools.

Releasing these transports is not a big problem for your project because they will be buffered in the import queue of your QA system. As long as they are imported into the QA system before you apply this same SP to QA, then there'll be no issue.

Regards,

Gary