Page History

...

For the duration of the development freeze (10/20/2014-12/1009/2014), a special development process should 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).

...

Before development is begun, it should be clear the business owner considers this change the problem is critical and requires an immediate fix. An email message describing the situation must be sent to Frank Quern (fquern@mit.edu), with a copy sent to John Tuttle (jrtuttle@mit.edu), to facilitate consideration of the critical fix. After review Frank will request approval to migrate the fix to Test from one of the business members of the Steering Committee.

...

Approvers for importing transports to production:

• Refer to QA critical transport procedures

...

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SH1. After approval, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH1 and SH2.

Ongoing Projects with planned install in Production

...

with Support Pack Go Live

Atlas 4.0 project. (Will require regression testing in SH2 to confirm proper functioning with support packs.)

Resumption of normal transport cycle

On December 10, 2014 SAP system SH2 will be opened for normal testing activities to all IS&T SAP support personnel and business owners. The normal QA rules 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 10, 2014 will be considered part of the December 11, 2014 transport cycle.

...