Attaching Check for Non-ABAP Objects

When attaching non-ABAP objects directly in the application, you can use the Attaching Check to adhere to the correct export sequence of non-ABAP objects and to prevent potential downgrades.

Use

The Attaching Check is available as an optional function in SAP systems as of a specific Support Package level. For more information on the availability, see SAP Note 2392088 Information published on SAP site. Before you can use the check, you must enable it for each non-ABAP system as described under Enabling the Attaching Check for Non-ABAP Objects.

When you attach a non-ABAP object to a transport request directly in the non-ABAP application, the Attaching Check analyzes whether transport requests with status Modifiable exist that were created in the same non-ABAP source system, and whether these requests contain the same objects that you want to attach to the transport request.

The check identifies an object as identical in the following cases:

  • The object belongs to the same application type.
  • The object has the same object type.
  • The object has the same object ID.

The Attaching Check assumes that content attached to a transport request at a later point in time is newer than content attached at an earlier point in time. To prevent downgrades of objects, the check does not allow identical objects to be attached to more than one modifiable transport request.

Note that the analysis of objects causes the overall attaching process to take longer.

Prerequisites

The prerequisites as described under Prerequisites for the Attaching Check must be fulfilled.

Process

At the time of the attachment of non-ABAP objects in the closely coupled non-ABAP application, the Attaching Check is performed.

If the check finds one or more identical objects in any modifiable transport request of the same system and application type, the attach process is stopped. The non-ABAP objects that you wanted to attach to the transport request are not attached.

Check the error message in the non-ABAP application to find out which transport requests contain identical objects.

If the non-ABAP application does not provide sufficient details, you can check the logs of the Attaching Check in the ABAP communication system of the non-ABAP system. For more information, see Checking the Logs of the Attaching Check.

To resolve issues, in many cases, it makes sense to release the transport request that already contains the same object before attaching the object to the current transport request. For more information, see Evaluating Check Results.