Page History

...

The last regularly scheduled transport release to Production will take place on Thursday, October 1810, 20182019. Development in SF2 will be allowed through Friday, October 1911, 2018 after which  a freeze restricted window 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 13November 20, 20182019. 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 2211, 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) WeiElda Prudden, Transport Coordinator, atlma@mit  eprudden@mit.edu or 617-253-02315153.

Development/Transport Procedures

...

For the duration of the restricted development freeze window  (10/1911/20182019-1211/1220/20182019), a special process will be used for development of fixes to SAP. The aim of this process is to avoid the introduction of non-support pack changes into the Support Pack test system (SH2) or the Production system (PS1).

The following are the steps in the special development process. Questions about this process should be directed to Eping (Lucia) WeiElda Prudden, Transport Coordinator, atlma@mit eprudden@mit.edu or 617-253-02315153.

Fixes for issues found during Unit Testing in SF2 or SIT in SH2

...

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

All transports must be associated with a Request Tracker (RT) ticket recorded in the RT SAP::Test Issues queue under the project name 'SAP Support Packs 2018'2019.  Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

...