Consistency Check for Transport Requests

Automatic Check on Release

The system performs a consistency check immediately before a task or request is released. Here the objects are checked that are directly assigned to the task or to the request. Therefore you need to release the tasks before you release the request. This ensures that all objects belonging to the task are directly assigned to the request and checked. The following checks are performed for BW objects:

• Checks whether the corresponding TADIR entry exists

• Checks whether the request contains generated objects

  You are not allowed to transport generated objects.

• Checks whether the object exists

  If the object does not exist, the system outputs a warning that the object is transported as a deletion.

• For active versions: Checks whether the object is active and - for objects with a modified version - whether the active version corresponds to the modified version.

• Collect all objects that the current object depends on. The following checks are performed for these objects:

  • Checks whether the object exists

    If the object does not exist, the system outputs an error, because the main object is inconsistent in this case.

  • Check for a transportable package

    If the object is not assigned to a transportable package, it cannot be transported with the main object. This results in an error in the target system.

  • Checks whether the object is on the same or a different transport request (that has already been released)

    If the object is not on a request, the object will be missing in the target system and causes an error.

If an error occurs, the check log is displayed in a dialog box.

Manual Check

You can also perform the consistency check before releasing a task or a request. You can use the report RSO_TLOGO_CHECK_REQUEST to do this. If an error occurs, the log is also displayed here. However the task or request cannot be released.