SAP ABAP IMG Activity PLM_AUDIT_OBJECT (Definition and Structure of an Audit Object)
Hierarchy
☛ SAP_ABA (Software Component) Cross-Application Component
   ⤷ CA-AUD (Application Component) Audit Management
     ⤷ PLM_AUDIT (Package) Audit Management: Other Components
IMG Activity
ID PLM_AUDIT_OBJECT Definition and Structure of an Audit Object  
Transaction Code S_ABA_72000218   (empty) 
Created on 20041213    
Customizing Attributes PLM_AUDIT_OBJECT   Definition and Structure of an Audit Object 
Customizing Activity PLM_AUDIT_OBJECT   Definition and Structure of an Audit Object 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PLM_AUDIT_OBJECT    

Use

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

This BAdI contains the methods for the check, selection, and display of the audit object.

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.

Standard settings

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

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

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.

Recommendation

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.

Further notes

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

Methods

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG PLM_AUDIT_OBJECT 0 AEC0000474 Audit Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050209 
SAP Release Created in 700