2010 SP Transport Management

Transports

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.

Transport Tracking

Transport Statistics

(See attached spreadsheet for details (under construction))

The transport tracking goal is to move as much pending work to production as possible before the 11/10/2010 production freeze.

The transport request utility, ZUTTREQ, will be temporarily modified to send all requests to the Transport Coordinator. The coordinator will use this information to update the tracking spreadsheet and kept the statistics up-to-date.

Development 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).

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

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

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.

Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

Critical fixes for issues found in Production

Before development is begun, it should be clear the business owner considers this change critical and requires an immediate fix.

Development will be performed in SF2 both before and after the support and enhancement packs 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.

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/SH2.
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 SH2.
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.