This Wiki page provides information related to the transport process during the SAP Support Pack 2023 project. 

Key Dates

  1. SF2 unavailable - to be upgraded starting Friday Oct 20 at 5pm until Tuesday Oct 24

  2. SH2 unavailable - to be refreshed and upgraded starting Tuesday Oct 24 at 5pm until Tuesday Oct 31

  3. 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

  4. 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

  5. After Support Pack go-live, the normal transport to production schedule will resume on Wednesday Dec 6.

SAP Environments

  1. Upgraded environments - SF3, SF2, SH2

  2. Non-upgraded environments - SH1, PS1 (upgraded on go-live weekend in Dec)

Types of Transports/Changes During Restricted Window

Considered 'critical' and requiring dual testing, to be deployed to PS1 before SP2023 go-live (path is SF2 -> SH1 -> PS1) - Note: 'critical' changes require dual testing, and so will need to be tested in both non-upgraded SH1 and again in upgraded SH2 to ensure expected behavior is found in both environments.

  1. Fixes to issues encountered in PS1
  2. Changes related to projects/enhancements approved for deployment before SP2023 go-live

To be deployed to PS1 on SP2023 go-live weekend in Dec (path is SF2 -> SH2 -> PS1)

  1.  Fixes to issues related to SAP support packs encountered in upgraded environments
  2. Non SP2023-related changes for approved projects/enhancements
  3. 'Critical' changes that needed dual testing and will be deployed again to PS1 on go-live weekend

 


Transport procedures for Support Pack related issues or projects/enhancements being deployed on SP2023 go-live weekend (SF2 -> SH2 path)

Create a ServiceNow 'test' ticket as usual (directed to SH2), except for the following SN details:

  1. leave the 'State' as ‘Pending’
  2. add Kevin Lyons as a watcher
  3. 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 changes which require dual testing (production issues or projects/enhancements being deployed before SP2023 go-live weekend)

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:

  1. leave the 'State' as ‘Pending’
  2. add Kevin Lyons as a watcher
  3. send an email to Kevin (klyons@mit.edu) asking for an approval.
Upon approval, Kevin will then change each of the SN tickets '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 changes must be tested twice, once in SH1, then again in SH2 to confirm proper functioning with support packs.
TBD TBD TBD

After approval, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to PS1 and SH2 respectively.Transport paths = SF2 -> SH1 -> PS1 and SF2 -> SH2


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.


Further questions about this process can be directed to Elda Prudden, Transport Coordinator, at  eprudden@mit.edu or 617-253-5153.


Transport Coordinator Instructions:

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