Page History

...

1. If necessary, revert each development object to be changed to the version currently in Production. In-process changes should be saved as a non-transportable copy of the object, as a downloaded text file, or as a printed listing.
2. Change the development object(s) to implement the required fix.
3. Perform unit testing in SF2.
4. Release the transport(s) once unit tested
5. Create a ServiceNow 'test' deployment request, making sure to select 'Comprehensive' as the 'Type', in order to trigger the approval work flow.  Fill out the ZUTTREQ fields described below, and include the details in the ServiceNow request as usual.
6. Execute ZUTTREQ making sure SH2 is the 'To' environment, and include the ServiceNow request number from above
7. Enter the transport(s) into the Transport # Sequence field within the SP 2020 ticket 
8. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

All transports must be associated with a Include any associated Request Tracker (RT) ticket recorded in numbers, if they exist, from the RT SAP::Test Issues queue (under the project name 'SAP Support Packs 2020) in the ZUTTREQ 'Purpose' block.  Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

...

Transports generated during Unit Testing will be accumulated and moved as a group as part of the Support Pack application process to the test system, SH2.
Transports generated during SIT will be imported into SH2.
These transports must transports might be associated with RT tickets recorded in the Request Tracker SAP::Test Issues queue under project name "SAP Support Packs 2020".

...

• Refer to QA critical transport procedures

All transports must Transports might be associated with a Request Tracker (RT) ticket recorded in the Functional Team's Support queue and within the  RT SAP::Test Issue queue under the project name 'SAP Support Packs 2020'. These transports must be tested twice, once in the production support path (SH1), then in the Support Pack upgrade path (SF2 -> SH2), before the transport(s) can be imported into production.

...

Ongoing Projects with planned install in Production with Support Pack Go Live

TBD (Will require regression testing in SH2 to confirm proper functioning with support packs.)

Resumption of normal transport cycle

...