Show TOC

Process documentationDefect Correction Processing


You can only create defect corrections during the test phase of the project cycle. Since the defect correction is used in integration testing, and this testing is based on the entire project (all changes), it is not related to a specific change or request for change. A defect correction identifies an error to the responsible developer. The developer makes the required corrective change and saves the change in a transport request associated with the defect correction. Since the project scope was approved in requests for change, defect corrections do not require approval.

Defect corrections are necessary because no new normal changes can be created in the test phase, since this would change the specified and approved project scope.


  1. A tester wants to send a message about an error detected during testing, to the developer. He creates a defect correction in the WebClient UI and describes the symptoms.

  2. The tester forwards the defect correction to the developer responsible, who sets the status of the change document to In Correction.

  3. The developer creates one or more transport requests and corrects the error in the development system.

  4. To submit the change for another test, the developer sets the status to To be Retested with the action Pass to “Retest”.

  5. After importing the transport buffer into the test system again, the tester checks the functions and confirms success by setting the status to Confirmed by choosing the Confirm Defect Correction action.

More Information

Project Cycle