Page History

...

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

...

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 & SF8.
4. Transport the fix to SH1 & SH2 (as part of SP application process).
5. Perform the usual regression and user-acceptance testing in 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.

...

Ongoing Projects with planned install in Production after the Freeze begins

Facilities Modernization.

SAPweb Help Migration to the KB.

Atlas java changes removing the "Home" button and removing the "inside" from the banner headers of the legacy applicationsNone scheduled at this time.

Resumption of normal transport cycle

...