Page History

Transports

The last normal transports to Production will take place on Tuesday, November 109, 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

...

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 -> SF5/SH1 Approver: see above(& SH3 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 (QA), Amanda Gilbert (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.

Approvers for importing transports to production:

• Refer QA critical transport procedures

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

...

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

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:

...

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

Ongoing Projects with planned install in Production after the Freeze begins

None planned during this year's project.

Resumption of normal transport cycle

On December 15, 2010 SAP system SH3 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 15, 2009 will be considered part of the December 23, 2010 transport cycle.