Page History

Transports

The last normal transports out of SF2 will take place on Friday, Oct 18, 2013. The last normal transports to Production will take place on Thursday, November 1October 31, 20122013. After that dateOct 18, 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 612, 20122013. 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 . During the freezebefore the project go-live date. Starting on Oct 19, 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 Fuller, Transport Coordinator, at fuller@mit.edu (mailto: fuller@mit.edu) or 617-253-6213.

Development/Transport Procedures

...

For the duration of the development freeze (10/2219/20122013-12/510/20122013), 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).

...

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 2012 2013 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 queue under the project name 'SAP Support Pack 20122013'.  Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.

...

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 20122013".

Transport path = SF2 -> SH2
Approver: Frank Quern

...

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.

Transport path SF2 SF8 -> SH1 (& SH2 -> PS1; SF2 ->SH2 (for regression testing) -> PS1 (with the support pack go live)

Approvers to begin the development work:

...

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 20122013'. 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

On December 612, 2012 2013 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 511, 2012 2013 will be considered part of the December 612, 2012 2013 transport cycle.

...

Transport Coordinator Instructions:

...

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