• Created by Unknown User (bartd), last modified by Unknown User (jrtuttle) on Oct 07, 2009 10:46

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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 sbout 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

  • No labels