Page History

...

The last regularly scheduled transport release to Production will take place on Thursday, October 1312, 2017. Development in SF2 will be allowed through Friday, October 13, 2017 after which  a freeze of non-critical transports to SH1 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 14, 2017. 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 1516, 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.

...

For the duration of the development freeze (10/1516/2017-12/13/2017), 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).

...

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 20162017'.  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 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 Packs 20162017".

Transport path = SF2 -> SH2
Approver: Frank Quern

...

All transports must 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 20162017'. 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.

...

Resumption of normal transport cycle

On December 713, 2016 2017 SAP system SH2 will be opened for normal testing activities to all IS&T SAP support personnel and business owners. The normal QA procedures (documents in the review folders, all business owner approvals captured, RT tickets updated) will resume at that time as well.  All changes approved on or after December 713, 2016 2017 will be considered part of the December 814, 2016 2017 transport cycle.

Transport Coordinator Instructions:

...