Page History

...

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

Statistics as of 10/0826/2009

• 326 332 UnReleased in Dev, Not in Test
• 201 210 Released in Dev, Not in Test
• 117 57 In Test, Not in Production

...

Before development is begun, it should be clear the business owner considers this change critical and requires an immediate fix.

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.

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.

...

2009 Projects: Appointment Process Redesign; SAPweb RFPTransport Path = SF2 to SH2.

Development resumes in SF2 when Support Pack Unit Test is complete (planned 11/09/2009).
Migration to Test (SH6SH2) resumes when Support Pack SIT and UAT are complete (planned 12/0910/2009).

Transport Path = SF2 to SH2.

What to do in ZUTTREQ: TBD

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

...