SAP ABAP IMG Activity EHSI_IA_RPHDFLG_COMP (BAdI: Determination of Reportable Event Indicator in Inc./Acc. Log Header)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-IHS (Application Component) Industrial Hygiene and Safety
     ⤷ CBIH (Package) EH&S: Industrial Hygiene and Safety
IMG Activity
ID EHSI_IA_RPHDFLG_COMP BAdI: Determination of Reportable Event Indicator in Inc./Acc. Log Header  
Transaction Code S_ALN_01002342   (empty) 
Created on 20030416    
Customizing Attributes EHSI_IA_RPHDFLG_COMP   BAdI: Determination of Reportable Event Indicator in Inc./Acc. Log Header 
Customizing Activity EHSI_IA_RPHDFLG_COMP   BAdI: Determination of Reportable Event Indicator in Inc./Acc. Log Header 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHSI_IA_RPHDFLG_COMP    

Use

This Business-Add In (BAdI) is used in the component Industrial Hygiene and Safety (EHS-IHS).

With this BAdI you can check whether the Reportable Event indicator was set in the header data of an incident/accident log entry and have the system set the indicator if necessary.

The BAdI is called when a user saves a newly created incident/accident log entry and changes the header data.

Requirements

Standard settings

The BAdI is active in the standard system. The default coding is supplied empty.

The BAdI is not filter-dependent and not for multiple usage.

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.

If you replace the function module with your own implementation, you avoid the following actions and/or ABAP statements in your own implementation:

  • Triggers messages of any type (statement: MESSAGE)
  • Changes the roll area (statement: COMMIT, SUBMIT, CALL TRANSACTION)
  • Calls dialogs (statement: CALL SCREEN)

Avoiding these actions and/or ABAP statements allows correct subsequent processing of the APIs that call this user exit and or BAdI.

See also:

Methods

Determine Reportable Event Indicator in Incident/Accident Log Header

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 EHSI_IA_RPHDFLG_COMP 0 SH10000009 Incident/Accident Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030528 
SAP Release Created in 200