Page History

...

Fixes for issues found during Unit Testing in SF2 or SIT in SH3

Transport path = SF2 -> SH3

Approver: Frank Quern

Transports will be imported into SH3 during SIT twice daily (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.

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 2010'.  

...

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. During SIT, transport the fix to SH3 and test to confirm the efficacy of the fix.

...

Transport request procedures:

...

Transport path = SF2 -> SH3

Approver: Frank Quern

Transports will be imported into SH3 during SIT twice daily (shortly after 12 noon and then again after 5pm). Requests must be received by 11:30am and 4:30pm, respectively.

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 2010'.  

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

...