Page History

Transports

The last normal transports to Production will take place on Thursday, November 1, 2012. After that date, a freeze of non-critical transports to 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 6, 2012. Migrations to the Test environments (SH2SH1 - PreSP QA) and Production will be limited to critical fixes that need to be moved to Production as soon as possible. During the freeze, 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 Carolyn Fuller, Transport Coordinator at jrtuttle@mit, at fuller@mit.edu (mailto: fuller@mit.edu) or 617-323253-6213.

Development/Transport Procedures

...

The following are the steps in the special development process. Questions about this process should be directed to Carolyn Fuller, Transport Coordinator at jrtuttle@mitfuller@mit.edu (mailto: fuller@mit.edu) or 617-323253-6213.

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

...

What to do in ZUTTREQ:
Select SH2 as the 'To' environment. The ZUTTREQ program will send the request to Frank Quern for approval.
After he has given his approval, Ron the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH2 twice a day (shortly after 12 noon and then again after 5pm).

Transports generated during Unit Testing will be accumulated and moved as a group as part of the Support Pack application process in 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 Pack 2012".

...

Before development is begun, it should be clear the business owner considers this change critical and requires an immediate fix. An email message describing the situation must be sent to Frank Quern (fquern@mit.edu (mailto: fquern@mit.edu)), with a copy sent to Carolyn Fuller (fuller@mit.edu (mailto: fuller@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.

...

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 Pack 20112012'. These transports must be double tested, once in the production support path (SF2-> SH2SH1) and then again in the Support Pack path (SF2-> SH1SH2), before the transport(s) can be imported into production.

...

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

...