Ansicht
Dokumentation

PLM_AUDIT_AUO_UPDATE - Create, Change, and Delete Audit

TXBHW - Original Tax Base Amount in Local Currency   ABAP Short Reference  
This documentation is copyright by SAP AG.

This Business Add-In is used in the Audit Management component (CA-AUD).

You can use this BAdI to enter all changes to an audit (create, change, delete) and the associated audit objects. You can then use it to replicate the changes in another system.

You can process changes at the following points in time:

• AT_SAVE
  The user has called the function 'Save' in the dialog. At this point in time, you can implement another check of the data to be saved. If errors are found during this check, this information can be returned. The data is not saved, and the user is informed.

• BEFORE_UPDATE
  The call is performed immediately before the data is transferred to the update. No messages can be output at this point. The save cannot be stopped.

• IN_UPDATE
  The call takes place in the update. No messages can be output at this point.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

To display sample code, choose Goto → Sample Code → Display.

The following methods are available:

• Create Audit When Saving

• Create Audit Before Update Task Is Called

• Create Audit in Update Task

• Create Audit Question When Saving

• Create Audit Question Before Update Task Is Called

• Create Audit Question in Update Task

• Create Audit Object When Saving

• Create Audit Object Before Update Task Is Called

• Create Audit Object in Update Task

• Change Audit When Saving

• Change Audit Before Update Task Is Called

• Change Audit in Update Task

• Change Audit Question When Saving

• Change Audit Question Before Update Task Is Called

• Change Audit Question in Update Task

• Change Audit Object When Saving

• Change Audit Object Before Update Task Is Called

• Change Audit Object in Update Task

• Delete Audit When Saving

• Delete Audit Before Update Task Is Called

• Delete Audit in Update Task

• Delete Audit Question When Saving

• Delete Audit Question Before update Task Is Called

• Delete Audit Question in Update Task

• Delete Audit Object When Saving

Note

This method is currently not in use. If necessary, use the methods DELETE_OBJECT_BEFORE_UPDATE, DELETE_OBJECT_IN_UPDATE, or another method called at the AT_SAVE point in time.

• Delete Audit Object Before Update Task Is Called

• Delete Audit Object in Update Task

General Data in Customer Master   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 8102 Date: 20240607 Time: 032811     sap01-206 ( 84 ms )