Ansicht
Dokumentation

FDT_DDIC_BINDING_UP_TO_DATE - BRFplus: Check or update DDIC binding for data objects

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Purpose

With this report, you can analyze the binding relationships between data objects defined in BRFplus and the dictionary objects (DDIC) that have been used as a reference for the object definition. If the report detects any inconsistencies or errors, you can decide which actions shall be taken to restore a consistent system status.

Integration

Prerequisites

Features

In addition to the detection and analysis of data binding issues, the report allows for various counteractivities to either correct the observed issues, to restore the affected objects, or to remove objects that cannot be restored from the system. Which measures the report takes depends on the selections that you make.

Selection

Selection

In the Selection section, you define the scope of data objects to be processed. You can either define a list of individual objects (Object Scope) or define the scope with the help of a superordinate object (Application Scope).

• Object Scope

• Data Object ID: One or more IDs of the objects to be processed.

• Application Scope

• Application ID: One or more IDs of the BRFplus applications to which the data objects to be processed belong.

• Application Name, Package, Software Component: Technical name of the BRFplus application, package, or software component to which the data objects to be processed belong. In these fields, only one entry is possible. However, you can use wildcards to extend the scope.

• Data Object Types: Choose the category of data objects to be processed. It is recommendable to choose all three categories so that the system can proceed in case of errors where different object types are involved.

Action

In the Action section, you define what the report shall do with the selected data objects.

• Check DDIC Binding: Checks the data objects in the selection scope for errors or inconsistencies. The results are presented in the report list. This option is read-only, there is no write access to the database.

• Update DDIC Binding: Performs the same checks as with the Check DDIC Binding option, but corrects the errors detected according to the following settings.

• Test Mode: Indicates whether the report carries out changes to the affected objects, or if the changes are only simulated without actually writing to the database.

• Storage Type: Choose the storage type a data object must have in order to be processed. For each update run, all objects to be processed must have the same storage type. This is because objects with different storage types cannot be written to the same transport request.

• Object Status: Decide whether objects that are currently marked as obsolete or marked for deletion shall also be processed. If you activate this option, the system temporarily unmarks the affected objects because otherwise, no changes would be possible. After having applied the necessary changes, the affected objects are automatically reverted to their original state.

• Action for Invalid Bindings: Decide what the system should do with objects that have an invalid data binding. A typical example is an element data object that has been bound to a data element in the ABAP Dictionary, and the data element has been deleted afterwards. You have the following options:

• Clear Binding: The binding relationship is removed. The unbound data object is kept alive in the system and can still be used. The object settings that were originally inherited from the DDIC element remain in effect for the unbound data object.

• Mark for Deletion: Like Clear Binding. In addition, the object is marked for deletion.

• Delete if not used: Like Mark for Deletion. In addition, the object is logically deleted. Deleting an object, however, is only possible if the object is not used by any other objects.

• Action for Dereferenced Objects: Decide what the system should do with partially dereferenced objects. A typical example is the situation where one or more components have been removed from a structure in the ABAP Dictionary that has been previously bound to a BRFplus structure. You have the following options:

• Check and Update Binding: Adjusts the data object to the current state of the object in the ABAP Dictionary to which it is bound.

• Mark for Deletion: Like Clear Binding. In addition, objects that have lost their counterpart in the ABAP Dictionary are marked for deletion.

• Delete if not used: Like Mark for Deletion. In addition, objects that have been marked for deletion are logically deleted. Deleting an object, however, is only possible if the object is not used by any other objects.

Standard Variants

Output

Activities

Example

ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5828 Date: 20240531 Time: 233534     sap01-206 ( 106 ms )