Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The last normal transports to Production will take place on Tuesday, November 10, 2010. 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 16, 2010. Ordinary development for support and/or enhancements will continue in SF2 during this period. Migrations to the Test environments (SF5/SH1) 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 Tuttle, Transport Coordinator at jrtuttle@mit.edu or 617-324-0097.

Development/Transport Procedures

...

For the duration of the development freeze (11/1/2010-12/15/2010), 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 (SH3) or the Production system (PS1).

...

  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 SH3 and test to confirm the efficacy of the fix.

...

Transport request procedures:

...

Transport path = SF2 -> SH3

...

Transports will be imported into SH3 during SIT twice daily (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.

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 2010'.  Note  Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

...

Transport request procedures:

...

Transport path = SF2 -> SH3

Approver: Frank Quern

Transports will be imported into SH3 during SIT twice daily (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.

Critical fixes for issues found in Production

...