SAP ABAP IMG Activity BADI_MPD_REPORTING (BAdI: Compliance Reporting)
Hierarchy
☛ ECC-DIMP (Software Component) DIMP
   ⤷ IS-AD-MPD (Application Component) Maintenance Program Definition
     ⤷ AD_MPD (Package) Maintenance Program Definition
IMG Activity
ID BADI_MPD_REPORTING BAdI: Compliance Reporting  
Transaction Code S_ALI_97000016   (empty) 
Created on 20040308    
Customizing Attributes BADI_MPD_REPORTING   BAdI: Compliance Reporting 
Customizing Activity BADI_MPD_REPORTING   BAdI: Compliance Reporting 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_MPD_REPORTING    

Use

This Business Add-In (BAdI) is used in the component Maintenance Program Definition (IS-AD-MPD).

This BAdI enables you to handle the three reporting modes of the MPD program and is called when you run one of these reportings. This BAdI interprets data from the Product Structure Browser (PSB) and database tables and can present it in three different reporting modes, assisting the user in maintenance plan creation, update and status reporting. The COMPLIANCE_REPORTING method of the BAdI is called when one of these reporting modes is triggered and it, in turn, passes the data on to the respective reporting mode.

Requirements

There are no prerequisites if you use the default implementation.The planning and scheduling for each document should be up-to-date and correctly maintained, as the data will be passed on from the reporting BAdI to the BAdI responsible for maintenance plan creation and up-date (BAdI_MPD_MP_GENER). The maintenance plans cannot be automatically created without planning and scheduling data.

Standard settings

  • The Business Add-In is active in the standard system.
  • The Business Add-In is not filter-dependent.
  • The Business Add-In is not reusable.
  • The default code is executed when there is no active customer implementation.

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.

See also:

Methods:

Data Processing for Total Compliance Reporting

Data Processing for Consistency Reporting

Data Processing for Change Implementation Reporting

Data Processing for Work Status Reporting

Example

To display the default code, choose Goto -> Default Code -> Display.

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 BADI_MPD_REPORTING 0 ALI0000001 Maintenance Program Definition 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20080730 
SAP Release Created in 500