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 2015 2016 ticket 
7. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

...

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SH1 -> SH1 (Prod path); SF2 -> SH2 (SP path). After approval, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH1 SE1/PS1 and SH2.

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

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

...