Page History

This Wiki page provides information related to the transport process during the SAP Support Pack 2024 2025 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 Sunday Tuesday Oct 20 21 at 5pm until Wednesday Thursday Oct 23  EOD23

• SH2 unavailable - to be refreshed and upgraded starting EOD Tuesday Wednesday Oct 22 at 23:59 until EOD Friday Nov 1 until Tuesday Oct 28
  

• 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 Sunday Tuesday Oct 20 21 at 5pm and ends after SP2024 SP2025 go-live weekend (Dec 65-87)
  

• The last normal transport to PS1 (until after Support Pack go-live) is Thursday Oct 2423.  This would include any transports that have been tested in non-upgraded SH2 and approved between Thursday Oct 17 16 and Tuesday Oct 22 21 for production deployment.

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

SAP Environments During Restricted Window

1. Upgraded environments - SF3, SF2, SH2

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

3. SE1 (non-upgraded)

   1. While the support packs are being applied to SF2, SF2 will not be available for development. If an emergency arises during this period, SE1 will be used for development

   2. If a critical issue is discovered in PS1 that requires the application of an OSS note, SE1 will be used instead of SF3 for the application and testing of that note (production support path for OSS notes is SE1 -> SH1 -> PS1).  Additionally, scrutiny would then be needed to ensure that the OSS note is included in SAP's support pack.

Types of Transports/Changes During Restricted Window

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

1. For transports related to

   SP2024

   SP2025 Project

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

1. 1. leave the 'State' as ‘Pending’
   2. add Harry Iliopoulos as a watcher
   3. send an email to Harry (harryi@mit.edu) asking for an approval (Olu Brown obrown@mit.edu as backup).

Create a ServiceNow ticket as usual (again, directed to both SH1 and SH2), except for the following SN details:

1. 1. leave the 'State' as ‘Pending’
   2. add Harry Iliopoulos as a watcher
   3. send an email to Harry (harryi@mit.edu) asking for an approval (Olu Brown obrown@mit.edu as backup).

Upon successful testing in SH2, these transports/changes will may be deployed a second time (tbd) to PS1 on go-live weekend, along with all the other SP2024 SP2025 Project transports/changes (i.e. to ensure that PS1 is in synch with SH2 by importing the same transports in the same sequence as they were imported into SH2).