This Wiki page provides information related to the transport process during the SAP Support Pack 2023 project.
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 in Dec
The last normal transport to production (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
Upgraded environments - SF3, SF2, SH2
Non-upgraded environments - SH1, PS1 (upgraded on go-live weekend in Dec)
Types of Transports/Changes During Restricted Window
SP2023 Project - To be deployed to PS1 on SP2023 go-live weekend in Dec (path is SF2 -> SH2 -> PS1)
- Fixes to issues related to SAP support packs encountered in upgraded environments
- Non SP2023-related changes for approved projects/enhancements
'Critical' - Considered 'critical' and requiring dual testing, to be deployed to PS1 before SP2023 go-live (path is SF2 -> SH1 -> PS1) - Note: 'critical' changes require for dual testing, and so 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.
- Fixes to issues encountered in PS1
- Changes related to projects/enhancements approved for deployment before SP2023 go-live
SP2023 Project - To be deployed to PS1 on SP2023 go-live weekend in Dec (path is SF2 -> SH2 -> PS1)
- Fixes to issues related to SAP support packs encountered in upgraded environments
- Non SP2023-related changes for approved projects/enhancements
- 'Critical' changes that needed dual testing and will be deployed again to PS1 on go-live weekend
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.
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.
Transport procedures for 'Critical' Transport/Changes which require dual testing
Two ServiceNow tickets will need to be created.
Create the ServiceNow 'test' tickets as usual (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.
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.
These 'critical' changes need to be tested twice, once in SH1, then again in SH2 to ensure correct behavior in both environments. These changes will be deployed again to PS1 from SH2 on go-live weekend
Follow the usual procedure for deployment to PS1 of the SH1 transport/changes.
...