Versions Compared

Old Version 20

changes.mady.by.user Elda M Prudden

Saved on

compared with

New Version Current

changes.mady.by.user Elda M Prudden

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

  • Sunday Oct

20

  • 22 at 5pm until

Tuesday

  • Wednesday Oct

24

  • 25 at 8am

  • SH2 unavailable - to be refreshed and upgraded starting

Tuesday

  • EOD Tuesday Oct 24 at

5pm until Tuesday Oct 31

  • 23:59 until EOD Friday Nov 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

  • Sunday Oct

20

  • 22 at 5pm and ends after SP2023 go-live weekend

in

  • (Dec 1-3)

  • The last normal transport to

production

  • PS1 (until after Support Pack go-live) is Thursday Oct 26.  This would include any transports that have been tested in non-upgraded 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

  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

  1. 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:
    1. Fixes to issues related to SAP support packs encountered in upgraded environments
(e.g. SF2, SH2, SF3)
    2. Non SP2023-related changes for approved projects/enhancements
  2. 'Critical' transports - Considered 'critical' and requiring dual testing, to be deployed to PS1 before SP2023 go-live (production support path is SF2 -> SH1 -> SE1/PS1). These include:
    1. Fixes to issues encountered
during SP2023
    1. in PS1
(which is not yet an upgraded environment)
    2. Changes related to projects/enhancements approved for deployment before SP2023 go-live
The Support Pack path is SF2 -> SH2 (for regression testing) -> PS1 (with the support pack go live)
The Critical Transport path is SF2 -> SH1 -> PS1

 

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

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 SP2023 Project

Create a ServiceNow

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 (Olu Brown obrown@mit.edu 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.
Transport procedures for Critical changes

 

2. For 'Critical' transports, which require dual testing
(production issues or projects/enhancements being deployed before SP2023 go-live weekend)
Two ServiceNow tickets

To ensure expected behavior in both non-upgraded SH1 and upgraded SH2, dual testing is needed.  Therefore, a ServiceNow ticket will need to be created and directed to both SH1 and SH2. 

Create

the ServiceNow 'test' tickets

a ServiceNow ticket as usual (

one SN ticket

again, directed to both 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 (Olu Brown obrown@mit.edu as backup).
Upon approval, Kevin will then change
each of
the SN
tickets
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 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

Upon successful testing in SH1, follow the usual procedures for deployment to PS1 (FYI, during the restricted window, transports will be staged in SE1 before being imported into 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 (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).

 

...

Resumption of normal transport cycle

On

...

Monday Dec 4, 2023, SH2 will be opened for normal testing activities. All changes approved on or after

...

Monday Dec 4, 2023 will be considered part of the

...

Wednesday Dec 6, 2023 transport cycle

...

.

...

Transport Coordinator Instructions:

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