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. Execute ZUTTREQ making sure SH2 is the 'To' environment
6. Enter the transport(s) into the Transport # Sequence field within the SP 2012 ticket 
7. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

...

What to do in ZUTTREQ:
Select SH2 as the 'To' environment. The ZUTTREQ program will send the request to Frank Quern for approval.
After he has given his approval, Ron will move the transport(s) to SH2 twice a day (shortly after 12 noon and ten again after 5pm).

Transports generated during Unit Testing will be accumulated and moved as a group as part of the Support Pack application process in the test system, SH2.
Transports generated during SIT will be imported into SH2 twice a day (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.
These transports must be associated with RT tickets recorded in the Request Tracker SAP::Test Issues queue under project name "SAP Support Pack 2012".

...