Page History

...

The last regularly scheduled transport release to Production will take place on Thursday, October 18, 20172018. Development in SF2 will be allowed through Friday, October 19, 2018 after which  a freeze of non-critical transports to SH2 and Production will be in effect until after the Support Pack Project Go Live date. The normal Production transport import schedule will resume on Thursday, December 13, 2018. Migrations to the Test environments (SH1 - PreSP QA) and Production will be limited to critical fixes that need to be moved to Production as soon as possible before the project go-live date. Starting on October 22, a special transport procedure will be enforced for changes to SAP. This section explains the approval process. It lists the necessary approvals and documentation, and what steps you need to take in ZUTTREQ. Questions about this process should be directed to Eping (Lucia) Wei, Transport Coordinator, at lma@mit.edu or 617-253-0231.

...

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

...