Transport Management

Transport Tracking

The goal is to move as much pending work to production as possible before the 10/22/2009 production freeze. 

Statistics as of 10/05/2009

• 331 UnReleased in Dev, Not in Test
• 201 Released in Dev, Not in Test
• 135 In Test, Not in Production

See attached spreadsheet for details. It will be updated periodically.

The ZUTTREQ transport request utility has been temporarily modified to send all requests to the Transport Manager, so the transport spreadsheet and statistics can be kept up-to-date.

Development Procedures

For the duration of the development freeze (10/26/2009-12/28/2009), 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 (SH2) 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 Manager at jrtuttle@mit.edu or 617-324-0097.

 Fixes for issues found during Unit Testing in SF2 or SIT/UAT in SH2

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 and UAT, transport the fix to SH2 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.

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.

Transport Procedures

For the duration of the development freeze a special transport procedure will be enforced for changes to SAP.
This section explains the approval process. It lists the necessary approvers and documentation, and what steps you need to take in ZUTREQ. Questions about this process should be directed to John Tuttle, Transport Manager at jrtuttle@mit.edu or 617-324-0097.

 Fixes for issues found during Unit Testing in SF2 or SIT/UAT in SH2

Transport path = SF2 to SH2

Approver: Wendy Bastos (QA)

Transports will be made to SH2 daily after 5pm.

What to do in ZUTTREQ:
     Select SH2 as the 'To' environment.+ The ZUTTREQ program will send the request to Wendy Bastos for approval. After she has given her approval Ron will move the transport(s) to SH2. There is no other destination for these transports other than SH2.

These transports should be associated with RT tickets recorded in the Request Tracker SAP::Tests Issue queue under project name SAP Support Pack 2009.

 Critical fixes for issues found in Production

Transport path = SF2 to SF5 (transport will automatically go to SH1 & SH2)
Please note whether this transport will need to go into Production at 'Close of business' (COB) or 'as soon as possible' (ASAP).

Approver: Wendy Bastos (QA)

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SF5.+ After Wendy's approval Ron will automatically move the transport(s) to SF5, SH1, and SH2.These transports should be associated with RT tickets recorded in the Request Tracker Functional team queues.

These transports must be double tested, meaning tested in SF5/SH1 AND SH2 before going to Production.

After Successful Testing
Transport Path = SF5 to PS1

The SAIS functional team must obtain approvals from all three groups below:

•   Gillian Emmons (primary for business owners), Magdalene Lee (backup for business owners)
•   Bart Dahlstrom (SAIS Admin Comp), Kevin Lyons (backup)
•   Wendy Bastos (SAIS QA), Amanda Gilbert (backup)

 The functional team must provide the PEC or mini-spec and SAP test cases with results in the Z:\QA\QA\Admin_Testing\ <Business Area> Case_Review folder and forward the ZUTTREQ email to SAP-CHG@mit.edu.

 Production (PS1) transport procedure during Support Pack Go Live weekend

The QA Team will provide support in the event that production transport processing is needed during go live weekend (12/11 - 12/13). It will remain the responsibility of the SAIS team leads to secure the appropriate approvals within the RT ticket in question.

 Resumption of normal transport cycle

On December 28, 2009 SAP system SH2 will be opened for testing activities by all SAIS 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 28, 2009 will be considered part of the January 7, 2010 transport cycle.

 Contact Information