You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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) starts when SF2 goes down on Friday Oct 20 at 5pm and ends after SP2023 go-live weekend
  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.

Types of Transports/Changes During Restricted Window

  1. Those related to SAP support packs encountered in upgraded environments (e.g. SF2, SH2, SF3)
  2. Those encountered in production which are considered critical (not upgraded environment)
  3. Those related to projects/enhancements approved for migration before SP2023 go-live, which will be considered critical
  4. Those related to projects/enhancements approved for migration during SP2023 go-live weekend

Transport procedures for Support Pack related issues or projects/enhancements migrating during 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 migrating before SP2023 go-live weekend)

Create 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 transports must be tested twice, once in the production support path (SF2 -> SH1), then in the Support Pack upgrade path to confirm proper functioning with support packs.(SF2 -> SH2), before the transport(s) can be imported into production.
The Critical Transport path is SF2 -> SH1 -> PS1

The Support Pack path is SF2 -> SH2 (for regression testing) -> PS1 (with the support pack go live)


Development Steps:
  1. For testing the change as part of the Support Pack application process:
    1. Perform testing required to confirm the proper functioning of the fix in SH2 (as part of the Support Pack application process).
  2. For testing the change as part of the critical production issue process:
    1. Perform testing required to confirm the proper functioning of the fix in SH1
    2. Transport the fix to Production.
Transport Request Procedures:

Send a request to the Project Manager for approval of the ServiceNow ticket(s).
After the necessary approvals have been given, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH1/SH2.


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)

 

  • No labels