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

Compare with Current View Page History

« Previous Version 13 Next »

Transports

The last regularly scheduled transport release to Production will take place on Thursday, October 15, 2020. Development in SF2 will be allowed through Wednesday, October 21, 2020 at 5pm after which  a restricted window of non-critical transports to SH2 and Production will be in effect until after the Support Pack Project Go Live date. The normal Production transport import schedule will resume on Wednesday, December 9, 2020. Migrations to the Test environments (SH1 - PreSP QA) and Production will be limited to critical fixes that need to be moved to Production as soon as possible before the project go-live date. Starting on October 21 at 5pm, a special transport procedure will be enforced for changes to SAP. This section explains the approval process. It lists the necessary approvals and documentation, and what steps you need to take in ZUTTREQ/ServiceNow. Questions about this process should be directed to Elda Prudden, Transport Coordinator, at  eprudden@mit.edu or 617-253-5153.

Development/Transport Procedures

For the duration of the restricted development window  (10/21/2020-12/09/2020), a special process will be used for development of fixes to SAP. The aim of this process is to avoid the introduction of non-support pack changes into the Support Pack test system (SH2) or the Production system (PS1).

The following are the steps in the special development process. Questions about this process should be directed to Elda Prudden, Transport Coordinator, at eprudden@mit.edu or 617-253-5153.

Fixes for issues found during Unit Testing in SF2 or SIT in SH2
Development steps:
  1. If necessary, revert each development object to be changed to the version currently in Production. In-process changes should be saved as a non-transportable copy of the object, as a downloaded text file, or as a printed listing.
  2. Change the development object(s) to implement the required fix.
  3. Perform unit testing in SF2.
  4. Release the transport(s) once unit tested
  5. Create a ServiceNow 'test' deployment request, making sure to select 'Comprehensive' as the 'Type', in order to trigger the approval work flow. 
  6. When executing ZUTTREQ, make sure SH2 is the 'To' environment, and include the ServiceNow request number from step 5.
  7. Include the ZUTTREQ details in the ServiceNow request as usual.
  8. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the restricted development window.

Transport request procedures:

The ServiceNow approval workflow process will send the request to Lori Singer and others for approval.
After the necessary approvals have been given, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH2.

Transports generated during Unit Testing will be accumulated and moved as a group as part of the Support Pack application process to the test system, SH2.
Transports generated during SIT will be imported as needed into SH2.

Transport path = SF2 -> SH2
Approver: Lori Singer

Critical fixes for issues found in Production

Before development is begun, it should be clear the business owner considers the problem is critical and requires an immediate fix. Send an email message describing the situation to Lori Singer (lsinger@mit.edu), with a copy sent to Elda Prudden (eprudden@,mit.edu), to facilitate consideration of the critical fix. After review Lori will request approval to migrate the fix to Test from one of the business members of the Steering Committee.

Development will be performed in SF2 both before and after the support packs have been applied. While the support packs are being applied to SF2, SF2 will be unavailable for development. If an emergency arises during this period, SH1 will be used for development.

Transport path SH1 -> SE1/PS1; SF2 ->SH2 (for regression testing) -> PS1 (with the support pack go live)

Approvers to begin the development work:

  • One of the business members of the Steering Committee
  • Lori Singer (PM), Olu Brown (backup)

The functional team needs to follow the standard QA Issue Resolution procedure, which includes the SAP mini-spec and associated test case documents.

Approvers for importing transports to production:

  • Refer to QA critical transport procedures

These transports must be tested twice, once in the production support path (SH1), then in the Support Pack upgrade path (SF2 -> SH2), before the transport(s) can be imported into production.

Development Steps:
  1. If necessary, revert each development object to be changed to the version currently in Production. In-process changes should be saved as a non-transportable copy of the object, as a downloaded text file, or as a printed listing.
  2. Change the development object(s) to implement the required fix in SF2 and SH1.
  3. Perform unit testing in SF2 & SH1.
  4. For the change in SF2:
    1. Release the transport(s) once unit tested
    2. Create a ServiceNow 'test' deployment request, making sure to select 'Comprehensive' as the 'Type', in order to trigger the approval work flow. 
    3. When executing ZUTTREQ, make sure SH2 is the 'To' environment, and include the ServiceNow request number from step b above.
    4. Include the ZUTTREQ details in the ServiceNow request as usual.
    5. Transport the fix to SH2.
  5. Since SH1 functions as both the dev and test environments, after unit testing in SH1, perform the usual regression and user-acceptance testing in SH1 also.
  6. Perform testing required to confirm the proper functioning of the fix in SH2 (as part of the SP application process).
  7. For the tested change in SH1:
    1. Release the transport(s) 
    2. Create a ServiceNow 'Prod' deployment request, as usual, including ZUTTREQ details, etc. 
    3. Obtain the required approvals.
    4. Transport the fix to Production.

Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the restricted development window.

Transport Request Procedures:

What to do in ZUTTREQ:
     Check 'Critical' and 'To' environment as SH1 -> SH1 (Prod path); SF2 -> SH2 (SP path). After approval, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SE1/PS1 and SH2.

Ongoing Projects with planned install in Production with Support Pack Go Live

Will require regression testing in SH2 to confirm proper functioning with support packs.

Resumption of normal transport cycle

On December 7, 2020, SAP system SH2 will be opened for normal testing activities to all IS&T SAP support personnel and business owners. The normal QA procedures (documents in the review folders, all business owner approvals captured, ServiceNow tickets updated) will resume at that time as well.  All changes approved on or after December 7, 2020 will be considered part of the December 9, 2020 transport cycle.

Transport Coordinator Instructions:

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

  • No labels