...
Transport path SF2 -> SF5/SH1
Approver: see above
The functional team must follow the standard QA Issue Resolution procedure, which includes the PEC and associated test cases or an SAP mini-spec.
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 2010'. These transports must be double tested, once in the production support path (SF2-> SF5/SH1) and then again in the Support Pack path (SF2-> SH3), before the transport(s) can be imported into production.
...
...
Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.
...
...
What to do in ZUTTREQ:
Check 'Critical' and 'To' environment as SF5. After approval, Ron will move the transport(s) to SF5/SH1, and SH3.
None planned during this year's project.
On December 15, 2010 SAP system SH3 will be opened for normal testing activities to all IS&T SAP support personnel and business owners. The normal QA rules (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 15, 2009 will be considered part of the December 23, 2010 transport cycle.