Versions Compared

Old Version 3

changes.mady.by.user Frank Quern

Saved on

compared with

New Version Current

changes.mady.by.user Frank Quern

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Transports

The last normal transports to Production will take place on Tuesday, November 1, 2011. 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 8, 2011. 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 Tuttle, Transport Coordinator at jrtuttle@mit.edu or 617-324-0097.

Development/Transport Procedures

...

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

...

  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. Transport the fix to SH2 & SH1 (as part of SP application process).
  5. Perform the usual regression and user-acceptance testing in SF5/SH1SH2.
  6. Perform testing required to confirm the proper functioning of the fix in SH3SH1.
  7. Obtain the required approvals.
  8. Transport the fix to Production.

...

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SF5SH2. After approval, Ron will move the transport(s) to SH2, and SH1.

Ongoing Projects with planned install in Production after the Freeze begins

Enterprise Learning 2.0.

Hourly Student Appointments

APR 2.0 (HR Transactions)None planned during this year's project.

Resumption of normal transport cycle

...