Page History

...

The following are the steps in the special development process. Questions about this process should be directed to Eping (Lucia) Wei, Transport Coordinator, at lma@mit.edu or 617-253-0231.

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. Execute ZUTTREQ making sure SH2 is the 'To' environment
6. Enter the transport(s) into the Transport # Sequence field within the SP 2015 2016 ticket 
7. During SIT, transport the fix to SH2 and test to confirm the efficacy of the fix.

...

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, SF8 SH1 will be used for development.

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

...

• One of the business members of the Steering Committee
• Frank Quern (PO), Siobhan Cunningham Garry Zacheiss (backup)

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

...

All transports must be associated with a Request Tracker (RT) ticket recorded in the Functional Team's Support queue and within the  RT SAP::Test Issue queue under the project name 'SAP Support Pack 2015Packs 2016'. These transports must be triple tested twice, once in the production support path (SF8-> SH1), then in HANA upgrade path (SF2/HANA -> SH2/HANA) and then again in the Support Pack upgrade path (SF2 -> SH2), before the transport(s) can be imported into production.

...

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 , SF2/HANA & SF8SH1.
4. Transport the fix to SH1, SH2/HANA & SH2 (as part of the SP application process).
5. Perform the usual regression and user-acceptance testing in SH1.
6. Perform testing required to confirm the proper functioning of the fix in SH2 /HANA & SH2(as part of the SP application process).
7. Obtain the required approvals.
8. Transport the fix to Production.

...

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 SH1 SE1/PS1 and SH2 and SH2/HANA.

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

TBD (Will require regression testing in SH2 & SH2/HANA to confirm proper functioning with support packs.)

Resumption of normal transport cycle

On December 167, 2015 2016 SAP system SH2 /HANA 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, RT tickets updated) will resume at that time as well.  All changes approved on or after December 167, 2015 2016 will be considered part of the December 178, 2015 2016 transport cycle.

Transport Coordinator Instructions:

...