Start of Content Area

Function documentation TMS Quality Assurance  Locate the document in its SAP Library structure


TMS Quality Assurance increases the quality and the availability of the production systems by letting you check requests in the QA system before they are delivered to subsequent systems.

The system for which the QA approval procedure is activated is called the QA system. When the QA approval procedure is activated, transport requests are only forwarded to the delivery systems if all the QA approval steps are processed for each request in the QA system and each request has been approved. (When you configure the QA system, you determine how many QA approval steps have to be processed for each request.) If a check for an approval step is not successful, the entire request cannot be approved.


Rejected requests are not imported into the delivery systems of the QA system.


If you reject requests, there is the risk that errors may occur when they are imported into the delivery systems. This is a result of the requests containing objects that are referenced from other requests. It is safer to correct an error using a subsequent transport (see Transport Strategy in the CTS).


In the TMS transport route configuration, you determine which system is the QA system, and which approval steps should apply to this system. You configure the QA approval procedure by performing these two steps. All the requests that are then imported into the QA system are included in the QA worklist.

You can go from the TMS Import Overview to the QA Worklist where you have to check the requests for each approval step.

You can only import all requests into the delivery systems if all the requests ready for import have been checked (which means approved or rejected).

If all the requests for a project and target clients are checked, you can import them even if requests for other projects and target clients have not been checked yet.


Your system landscape contains at least one QA system from which there are configured delivery routes into other systems.


In a 3-system landscape, the requests from the development system are imported into the QA system. There, the requests are checked and the approved requests are forwarded to the production system.


You determine which system is the QA system, switch on the option Forward after confirmation for this system, and define which approval steps are valid for this system.

After a system has been configured as the QA system, the QA worklist is built. You then have to check the requests in these views for the individual approval steps.

Using this history you can display the QA activities for a specific period.


  1. When you configure the QA approval procedure, you determine the QA system, switch on the option Forward after confirmation, and define the approval steps for that system.
  2. You approve or reject requests.
  3. You display the QA history for a selected period.