Versions Compared

Old Version 5

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.

...

The last regularly scheduled transport release to Production will take place on Thursday, October 10, 2019. Development in SF2 will be allowed through FridayWednesday, October 1116, 2019 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 Thursdayon Wednesday, November 27, 2019. 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 1116 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. Questions about this process should be directed to Elda Prudden, Transport Coordinator, at  eprudden@mit.edu or 617-253-5153.

...

For the duration of the restricted development window  (10/1116/2019-11/27/2019), 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).

...

  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.  Fill out the ZUTTREQ fields described below, and include the details in the ServiceNow request as usual.
  6. Execute ZUTTREQ making sure SH2 is the 'To' environment, and include the ServiceNow request number from above
  7. Enter the transport(s) into the Transport # Sequence field within the SP 2019 ticket 
  8. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

...

Transport request procedures:

What to do in ZUTTREQ:
Select SH2 as the 'To' environment. The ZUTTREQ program The ServiceNow approval workflow process will send the request to Lori Singer and others for approval.
After he has given his approvalthe necessary approvals have been given, the R3 Admin team (r3-chmgt@mit.edu) will move the transport(s) to SH2 twice a day (shortly after 12 noon and then again after 5pm).

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 into SH2 twice a day (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.
These transports must be associated with RT tickets recorded in the Request Tracker SAP::Test Issues queue under project name "SAP Support Packs 2019".

...