Page History

...

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 (SH2) 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 John TuttleCarolyn Fuller, Transport Coordinator at jrtuttle@mit.edu or 617-324323-00976213.

Development/Transport Procedures

...

For the duration of the development freeze (10/2422/20112012-12/75/20112012), 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 (SH1SH2) or the Production system (PS1).

The following are the steps in the special development process. Questions about this process should be directed to John TuttleCarolyn Fuller, Transport Coordinator at jrtuttle@mit.edu or 617-324323-00976213.

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

...

SH2

Development steps:

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. During SIT, transport the fix to SH1 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 Issue queue under the project name 'SAP Support Pack 20112012'.  Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

...

What to do in ZUTTREQ:
Select SH1 SH2 as the 'To' environment. The ZUTTREQ program will send the request to Frank Quern for approval.
After he has given his approval, Ron will move the transport(s) to SH1SH2.

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, SH1SH2.
Transports generated during SIT will be imported into SH1 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 20112012".

Transport path = SF2 -> SH1SH2
Approver: Frank Quern

Critical fixes for issues found in Production

...