Ansicht
Dokumentation

PLM_AUDIT_QUN_UPDATE - Create, Change, and Delete Question Lists

TXBHW - Original Tax Base Amount in Local Currency   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

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

You can use this BAdI or the corresponding methods to record all changes made to a question list and the related items (create, change, delete). 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.

This Business Add-In is not active in the standard system.

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.

See also:

Methods:

• Create Header When Saving

• Create Header Before Update Task Is Called

• Create Header in Update Task

• Create Item When Saving

• Create Item Before Update Task Is Called

• Create Item in Update Task

• Change Header When Saving

• Change Header Before Update Task Is Called

• Change Header in Update Task

• Change Item When Saving

• Change Item Before Update Task Is Called

• Change Item in Update Task

• Delete Header When Saving

• Delete Header Before Update Task Is Called

• Delete Header in Update Task

• Delete Item When Saving

• Delete Item Before Update Task Is Called

• Delete Item in Update Task

#########################################################################################################################

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.

Length: 6617 Date: 20240523 Time: 214537     sap01-206 ( 71 ms )