Page History

...

The last normal transports out of SF2 will take place on Friday, Oct 18October 17, 20132014. The last normal transports to Production will take place on ThursdayTuesday, October 3128, 20132014. After Oct 18October 17, a freeze of non-critical transports to SH1 or Production will be in effect until after the Support Pack Project Go Live date. The normal Production transport import schedule will resume on Thursday, December 1211, 20132014. Migrations to the Test environments (SH1 - PreSP QA) and Production will be limited to critical fixes that need to be moved to Production as soon as possible before the project go-live date. Starting on Oct 19October 20, a special transport procedure will be enforced for changes to SAP. This section explains the approval process. It lists the necessary approvals and documentation, and what steps you need to take in ZUTTREQ. Questions about this process should be directed to Carolyn FullerJohn Tuttle, Transport Coordinator, atfuller@mitjrtuttle@mit.edu (mailto: fuller@mit.edu) or 617-253324-62130097.

Development/Transport Procedures

...

For the duration of the development freeze (10/1920/20132014-12/10/20132014), 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 (SH2) or the Production system (PS1).

The following are the steps in the special development process. Questions about this process should be directed to Carolyn FullerJohn Tuttle, Transport Coordinator, at fuller@mit jrtuttle@mit.edu (mailto: fuller@mit.edu)  or 617-253324-62130097.

Fixes for issues found during Unit Testing in SF2 or SIT in SH2

...

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. Release the transport(s) once unit tested
5. Execute ZUTTREQ making sure SH2 is the 'To' environment
6. Enter the transport(s) into the Transport # Sequence field within the SP 2013 2014 ticket 
7. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

All transports must be associated with a Request Tracker (RT) ticket recorded in the RT SAP::Test Issue Issues queue under the project name 'SAP Support Pack 20132014'.  Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

...

What to do in ZUTTREQ:
Select SH2 as the 'To' environment. The ZUTTREQ program will send the request to Frank Quern for approval.
After he has given his approval, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH2 twice a day (shortly after 12 noon and then again after 5pm).

Transports generated during Unit Testing will be accumulated and moved as a group as part of the Support Pack application process in the test system, SH2.
Transports generated during SIT will be imported into SH2 twice a day (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.
These transports must be associated with RT tickets recorded in the Request Tracker SAP::Test Issues queue under project name "SAP Support Pack 20132014".

Transport path = SF2 -> SH2
Approver: Frank Quern

...

Before development is begun, it should be clear the business owner considers this change critical and requires an immediate fix. An email message describing the situation must be sent to Frank Quern (fquern@mit.edu (mailto: fquern@mit.edu)), with a copy sent to Carolyn Fuller (fuller@mit.edu (mailto: fuller@mit.edu)to John Tuttle (jrtuttle@mit.edu), to facilitate consideration of the critical fix. After review Frank will request approval to migrate the fix to Test from one of the business members of the Steering Committee.

Development will be performed in SF2 both before and after the support and enhancement packs have 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.

...

• One of the business members of the Steering Committee
• Frank Quern (PM), Bart Dahlstrom (backup)
• Don Flanders Debra Wiley (QA), Jack Kelleher Kelliher (backup)

The functional team must follow the standard QA Issue Resolution procedure, which includes the SAP mini-spec and associated test case documents.

...

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

...

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SH1. After approval, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH1 , and SH2.

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 applicationsAtlas 4.0 project.

Resumption of normal transport cycle

On December 1210, 2013 2014 SAP system SH2 will be opened for normal testing activities to all IS&T SAP support personnel and business owners. The normal QA rules (documents in the review folders, all business owner approvals captured, RT tickets updated) will resume at that time as well.  All changes approved on or after December 1110, 2013 2014 will be considered part of the December 1211, 2013 2014 transport cycle.

Transport Coordinator Instructions:

Transport Coordinator Instructions & Audit Process (requires authorization to access to the Tech Services wiki page)