Transport Tracking

Transport Statistics

(See attached spreadsheet for details (under construction))

Transport status

# of Transports
as of 9/7/2010

# of Transports
as of 11/1/2010

# of Transports
as of 11/10/2010

Comments

SF2 transports not released

447

 

 

 

SF2 transports released not in SF5

261

 

 

 

SF2 transports in SF5 not in PS1

101

 

 

 

SF3 transports in transports in SF2 not in SF5

19

 

 

 

SF3 transports in SF5 not in PS1

12

 

 

 

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.