Page History

...

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.

Transport path SF2 -> SF5/SH1

Approver: see above

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 2010'. These transports must be double tested, once in the production support path (SF2-> SF5/SH1) and then again in the Support Pack path (SF2-> SH3), 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.
4. Transport the fix to SF5/SH1 & SH3 (as part of SP application process).
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 SH3.
7. Obtain the required approvals.
8. Transport the fix to Production.

...