You can remove the objects from the request (transaction SE09 --> Object Tab Page). Any changes that you or other users made to the object are not reset. The changes are also no longer recorded by version management which can lead to serious inconsistencies during release upgrade. This should be of no concern in your situation as you are going to do the modifications again anyway.
A better option is the use the Unlock Objects tool which is part of the Transport Organizer Toolset (transaction SE03). This tool allows you to unlock the objects from a specific transport request. All objects in the request end up unlocked. You can use the function 'create versions of the objects' to create versions of all objects when you unlock a change request so that you can document their current version. Functions set to 'released' can be used to set the request to release automatically during the unlock. As of then, you can no longer use this request.
Dig Deeper on SAP security
Related Q&A from Bert Vanstechelman
An SAP user wants to know the risks of changing time zones in ECC 6.0. Continue Reading
An SAP user wants to know how to access an SAP IDES 4.7 system via the Internet through SAP GUI. Continue Reading
A SearchSAP.com reader wants to know how an increase of indexes and tables after upgrade to SAP ECC 6.0 will affect the memory requirements of a DB2 ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.