This Wiki page provides information related to the transport process during the SAP Support Pack 2023 project. Further questions about this process can be directed to Elda Prudden, Transport Coordinator, at eprudden@mit.edu or 617-253-5153.
Key Dates
SF2 unavailable - to be upgraded starting Friday Oct 20 at 5pm until Tuesday Oct 24
SH2 unavailable - to be refreshed and upgraded starting Tuesday Oct 24 at 5pm until Tuesday Oct 31
This year’s “restricted window” (i.e. when the transport path to PS1 changes and dual testing is required for critical production changes) starts when SF2 goes down on Friday Oct 20 at 5pm and ends after SP2023 go-live weekend (Dec 1-3)
The last normal transport to PS1 (until after Support Pack go-live) is Thursday Oct 26. This would include any transports that have been tested in SH2 and approved between Oct 19 and Oct 24 for production deployment
After Support Pack go-live, the normal transport to production schedule will resume on Wednesday Dec 6.
SAP Environments During Restricted Window
Upgraded environments - SF3, SF2, SH2
Non-upgraded environments - SH1, PS1 (upgraded on go-live weekend in Dec)
Types of Transports/Changes During Restricted Window
- Transports related to SP2023 Project - To be deployed to PS1 on SP2023 go-live weekend in Dec (SP2023 upgrade path is SF2 -> SH2 -> PS1). These include:
- Fixes to issues related to SAP support packs encountered in upgraded environments
- Non SP2023-related changes for approved projects/enhancements
- 'Critical' transports - Considered 'critical' and requiring dual testing, to be deployed to PS1 before SP2023 go-live (production support path is SF2 -> SH1 -> PS1). These include:
- Fixes to issues encountered in PS1
- Changes related to projects/enhancements approved for deployment before SP2023 go-live
Note: for dual testing, the changes will need to be tested in both non-upgraded SH1 and again in upgraded SH2 to ensure expected behavior is found in both environments.
Transport procedures
For SP2023 Project Transports/Changes
Create a ServiceNow 'test' ticket as usual (directed to SH2), except for the following SN details:
- leave the 'State' as ‘Pending’
- add Kevin Lyons as a watcher
- send an email to Kevin (klyons@mit.edu) asking for an approval (Olu Brown as backup).
Upon approval, Kevin will then change the SN ticket 'State' to 'Work in progress', along with adding approval notes in the Notes tab.
R3 Admin (r3-chmgt@mit.edu) will then move the transport(s) to SH2.
For 'Critical' Transport/Changes, which require dual testing
To ensure correct behavior in both non-upgraded SH1 and upgraded SH2, dual testing is needed. Therefore, two ServiceNow tickets will need to be created, one SN ticket directed to SH1 and one SN ticket directed to SH2.
Create the two ServiceNow 'test' tickets as usual (again, one SN ticket directed to SH1 and one SN ticket directed to SH2), except for the following SN details:
- leave the 'State' as ‘Pending’
- add Kevin Lyons as a watcher
- send an email to Kevin (klyons@mit.edu) asking for an approval (Olu Brown as backup).
Upon approval, Kevin will then change each of the SN ticket's 'State' to 'Work in progress', along with adding approval notes in the Notes tab.
R3 Admin (r3-chmgt@mit.edu) will then move the transport(s) to both SH1 and SH2.
Upon successful testing in SH1, follow the usual procedures for deployment to PS1.
Upon successful testing in SH2, these transports/changes will be deployed a second time to PS1 on go-live weekend, along with all the other SP2023 Project transports/changes.
Resumption of normal transport cycle
On December 4, 2023, SH2 will be opened for normal testing activities. All changes approved on or after December 4, 2023 will be considered part of the December 7, 2023 transport cycle.
Transport Coordinator Instructions:
Transport Coordinator Instructions & Audit Process (requires authorization to access the Tech Services wiki page)
Overview
Content Tools
Activity