Kontakt

Ansicht
Dokumentation

PLM_AUDIT_OBJECT_A - Definition of an Object for Investigation (Audit,...)

PLM_AUDIT_OBJECT_A - Definition of an Object for Investigation (Audit,...)

rdisp/max_wprun_time - Maximum work process run time   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In Business Add-In(BAdI) is used in the Audit Management, Failure Mode and Effects Analysis (FMEA) and other components.

This BAdI contains the methods for checking, selecting and displaying the object for an investigation, depending on the investigation type. In Audit Management, we use the terms Audit Objects and Audit Types. The information below relates specifically to use in Audit Management but the description applies to investigations in general.

Since it is not possible to plan all possible audit objects in a standard software, and external data may have to be accessed, the audit object is connected using this interface. As a result, you can create your own implementations (in addition to those supplied by SAP) without having to make modifications.

Within this interface, you can access the detailed information about the audit object that was defined in Customizing for the audit type.

A filter type must be specified when this BAdI is implemented. This filter type is assigned in the field Input Values for Audit Object (BAdI) (technical field name PLMV_AUDIT_TYPE-FILTER) in Customizing for the audit type.

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.

Audit type: External product audit of product 4711 for the vendor IDES.

The audit object "Product 4711 for vendor IDES" is described by the two attributes Product (attribute type 01) and Vendor (attribute type 02). You define the associated data elements for the entry fields in Customizing. During the BAdI implementation, the system then accesses the data for the business partner and the product master record that exists in the system.

Audit type: Internal system audit in development AREA1 according to ISO 9000.

The audit object is described by the two attributes QM System and Area. The auditor therefore sees two entry fields for the audit object with those field labels that were defined in Customizing for the audit type.
You define the input values for the possible QM systems in a separate value table in Customizing for the audit type. No value table exists for the individual areas in the system yet. During BAdI implementation, you access an external system.

To display sample code, choose Goto-> Sample Code -> Display.

The implementation must be in line with the Customizing entries for the audit type. The technical properties of the entry fields are defined in Customizing. This allows you to cover different audit types during an implementation.

You can find technical details about the individual methods in the interface documentation for the interface: IF_EX_PLM_AUDIT_OBJECT.

Methods






RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 6354 Date: 20240523 Time: 191353     sap01-206 ( 97 ms )