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/0526/2009

• 331 332 UnReleased in Dev, Not in Test
• 201 210 Released in Dev, Not in Test
• 135 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.

...

What to do in ZUTTREQ:
     Select SH2 as the 'To' environment. + The ZUTTREQ program will send the request to Wendy Bastos for approval. After she has given her approval, Ron will move the transport(s) to SH2. There is no other destination for these transports other than SH2

No further one-by-one movement of these transports will be necessary. They will be imported into Production as part of the Support Pack Go-Live process.

These transports should be associated with RT tickets recorded in the Request Tracker SAP::Tests Issue queue under project name SAP Support Pack 2009.

...

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SF5. + After Wendy's approval Ron will automatically move the transport(s) to SF5, SH1, and SH2.

These transports should be associated with RT tickets recorded in the Request Tracker Functional team queues.

...

•   Gillian Emmons (primary for business owners), Magdalene Lee (backup for business owners)
•   Bart Dahlstrom (SAIS Admin Comp), Kevin Lyons (backup)
•   Wendy Bastos (SAIS QA), Amanda Gilbert (backup)

 The The functional team must provide the PEC or mini-spec and SAP test cases with results in the Z:\QA\QA\Admin_Testing\ <Business Area> Case_Review folder and forward the ZUTTREQ email to SAP-CHG@mit.edu.

 Ongoing Projects with planned install in Production after the Freeze begins

2009 Projects: Open Enrollment & Union Structures

Transport Path = SF2 to SF5/SH1 to PS1

Normal approval process will be in place. QA will approve the release to move to Production (PS1).

 Ongoing Projects approved for early resumption of migration to Testing

2009 Projects: Appointment Process Redesign; SAPweb RFP

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

Transport Path = SF2 to SH2.

What to do in ZUTTREQ: TBD

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

The QA Team will provide support in the event that If production transport processing is needed during go live weekend (12/11 - 12/13) please call Sharron Sawyer (617-258-0235).  It will remain remains the responsibility of the SAIS team leads to secure the appropriate approvals within the RT ticket in question.

• If the SAP-Chg coordinator has a computer, they will process the RT ticket and call Ron Parker (617-253-1339).
• If the SAP-Chg coordinator does not have a computer, they can call Ron Parker and give verbal approval for the transport request.

 Resumption of normal transport cycle

...