...
All transports must be associated with a Request Tracker (RT) ticket recorded in the RT SAP::Test Issue queue under the project name 'SAP Support Pack 20122013'. Note: Any in-process changes saved during step 1 will need to be manually merged into the corrected objects after the development freeze.
...
Transports generated during Unit Testing will be accumulated and moved as a group as part of the Support Pack application process in 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 Pack 20122013".
Transport path = SF2 -> SH2
Approver: Frank Quern
...
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 20122013'. These transports must be double tested, once in the production support path (SF2-> SH1) and then again in the Support Pack path (SF2-> SH2), before the transport(s) can be imported into production.
...
On December 612, 2012 2013 SAP system SH2 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 511, 2012 2013 will be considered part of the December 612, 2012 2013 transport cycle.