Ansicht
Dokumentation

ECATT_CUST_LOCAL_OBJ - Configure CTS/TADIR Handling

Addresses (Business Address Services)   CPI1466 during Backup  
This documentation is copyright by SAP AG.

eCATT objects are normally subject to the settings for the system change option. This means that they can only be created, changed, or deleted in the following cases:

• You are allowed to change repository objects in the client.

• The namespace in which an eCATT object is located is open for changes.

• The software component that the package assigned to the eCATT object belongs to is open for changes.

Changes to eCATT objects are recorded in the same way as other development objects (for example, classes, programs, DDIC objects) in transport requests (CTS connection). Each object has an object catalog entry (table TADIR or GTADIR), which contains the corresponding metadata for the object (for example, package, person responsible) and ensures that an object name is not assigned twice in a system landscape.

This default behavior can be deactivated for individual namespaces in the table ECCUST_LOCAL_OBJ. The result of this is that no object catalog entries are written in the respective name range, and changes are no longer recorded in transport requests.

In this case, the system change option settings are no longer relevant, and you are free to make any changes you want to eCATT objects in the namespace in question. There is no longer a check that the name is unique in the system landscape, and changes are no longer recorded in transport requests.

This configuration makes it possible to use eCATT in a non-development environment, but it does have some disadvantages, as mentioned above.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 1781 Date: 20240523 Time: 175259     sap01-206 ( 41 ms )