Versions Compared

Old Version 4

changes.mady.by.user Frank Quern

Saved on

compared with

New Version 5

changes.mady.by.user Frank Quern

Saved on

Key

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

...

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), with a copy sent to John Tuttle Carolyn Fuller (jtuttle@mitfuller@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.

Development will be performed in SF2 both before and after the support and enhancement packs have been applied. While the support and enhancement packs are being applied to SF2, SF2 will be unavailable for development. If an emergency arises during this period, SF8 will be used for development.

Transport path SF2 -> SH2 SH1 (& SH1 SH2 for regression testing)

Approvers to begin the development work:

  • One of the business members of the Steering Committee
  • Frank Quern (PM), Bart Dahlstrom (backup)
  • Wendy Bastos Don Flanders (QA), Amanda Gilbert Jack Kelleher (backup)

The functional team must follow the standard QA Issue Resolution procedure, which includes the PEC and associated test cases or an SAP mini-spec and associated test case documents.

Approvers for importing transports to production:

...

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

...

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

Ongoing Projects with planned install in Production after the Freeze begins

Enterprise Learning 2.0.

Hourly Student Appointments

APR 2.0 (HR Transactions)None scheduled at this time.

Resumption of normal transport cycle

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