Ansicht
Dokumentation

/AIN/ARC_OBJECT_CHEC - BAdI: Check object data for archiving

/AIN/ARC_OBJECT_CHEC - BAdI: Check object data for archiving

Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

When you archive using program /AIN/DM_ARCH_WRITE and you select the run time parameter Actions without document, the program selects allobjects from table /AIN/DM_OBJECT for archiving. This may cause a problem because some of the archived objects may be linked to documents containing actions that were performed on the archived objects. If the related objects are archived, it would result in those documents remaining in the system without their corresponding objects.

Similarly, when you archive using program /AIN/DM_ARCH_WRITE and you select the run time parameter Documents with Actions, the program selects all objects from table /AIN/DM_OBJECT for archiving. This may cause a problem because some of the archived objects may be linked to actions that still point to those same objects. If the related objects are archived, it would result in those actions remaining in the system without their corresponding objects.

The BAdI /AIN/ARC_OBJECT_CHECK solves these problems by allowing you to write code and to perform the checks necessary to prevent this inconsistency. You implement the BADI method CHECK for any evaluations that you want to make before the system archives an object. The method CHECK has one import parameter (I_OBJECT) and two changing parameters (CH_VETO and CH_DETAIL_TEXT).

This BADI is called for each object to be archived. The import parameter I_OBJECT will contain the object details. If you wish to have the archiving process skip certain entries, for example, based on other active references, you specify CH_VETO = 'X'. You may use CH_DETAIL_TEXT to document the reason for skipping an entry during the archiving process.

Before the BAdI can be called you must create and activate an implementation of the BADI by using transaction SE19.

You include your custom code in the CHECK method of your implementation.






ROGBILLS - Synchronize billing plans   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2109 Date: 20240328 Time: 135829     sap01-206 ( 58 ms )