SAP ABAP IMG Activity GRRMOBORXDWNL (BAdI: Loss Download to ORX Format)
Hierarchy
☛ GRCFND_A (Software Component) GRC Foundation ABAP
   ⤷ GRC-RM (Application Component) GRC Risk Management
     ⤷ GRRM_OB_DDIC (Package) Operational Risk Management for Banks: Dictionary Objects
IMG Activity
ID GRRMOBORXDWNL BAdI: Loss Download to ORX Format  
Transaction Code S_GFR_11000013   (empty) 
Created on 20110519    
Customizing Attributes GRRMOBORXDWNL   BAdI: Loss Download to ORX Format 
Customizing Activity GRRMOBORXDWNL   BAdI: Loss Download to ORX Format 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GRRMOBORXDWNL    

Use

In this Business Add-In (BAdI), you can specify the implementation to use to download reports compliant with the Operational Riskdata eXchange Association (ORX). After specifying and activating the implementation, you can download the ORX report using the Loss Event Management application (Assessments > Loss Event Assessment > Loss Event Management).

Requirements

There can be only one active implementation of this BAdI at any given time.

Standard settings

Activities

To activate an implementation:

  1. In the Active (IMG) column, select the check box for the implementation that you want to activate.
  2. Choose the Enter pushbutton.

To display an implementation:

  1. Select the implementation that you want to view, and choose the Display Implementation pushbutton. The Enhancement Implementation Display screen appears.
  2. Review the implementation, as appropriate.
  3. To return to the BAdI Implementations screen, choose the Back (F3) pushbutton.

To specify a new implementation:

  1. Choose the Create Implementation pushbutton.
  2. In the Enhancement Implementation field, type the name of enhancement implementation.
  3. In the Short Text field, type a short description of the implementation. Leave the Composite Enhancement Implementation field blank.
  4. Choose the Enter pushbutton. The Create Object Directory Entry dialog appears.
  5. In the Package field, select or type the name of the package to which you want to assign the implementation.
  6. Choose the Save pushbutton. The Create Enhancement Implementation appears.
  7. Choose the Enter pushbutton. A dialog appears allowing you to confirm the creation of the enhancement implementation.
  8. Choose the Cont. pushbutton. The Enhancement Implementation dialog appears.
  9. In the BAdI Implementation column, enter the name of the implementation.
  10. In the Implementation Class column, enter the name of the class that implements the Business Add-In.
  11. Choose the Enter pushbutton. The Create Implementation Class screen appears.
  12. Select the example class, CL_GRRM_OB_ORX_DWNL_DATA_EXM, and choose the Copy Sample Class pushbutton.
  13. Save the class, and assign it to a package. The Enhancement Implementation Change screen appears.
  14. Press Ctrl-F3 to activate the enhancement implementation.
  15. If required, change the implementation code in the implementing class between the method <Interface Name>~<Name of Method> and endmethod statements.
  16. Save and activate the code.
  17. Navigate to the Change Implementation screen.
  18. To activate the implementation, choose the Activate pushbutton. Note that you can choose to activate the Business Add-In implementation at a later time.

The system executes the code in the method you specified when the application is run.

For more information about implementing Business Add-Ins (as an enhancement), refer to BAdIs - Embedding in the Enhancement Framework in the SAP Library.

Example

A sample Business Add-In implementation (GRRM_OB_ORX_DWNL_DATA,) and a sample class (CL_GRRM_OB_ORX_DWNL_DATA_EXM) provides an example of how to implement the ORX report logic.

The sample implementation retrieves and downloads the following loss attributes:

  • Reference ID Number, which is the loss event identifier
  • Business Line Code, which is the organization unit from the ORX secondary hierarchy to which the loss event is mapped using Static Data Management
  • Event Category, which is the risk category from the ORX secondary hierarchy to which the loss event is mapped using Static Data Management
  • Country (ISO Code)
  • Credit Related, C if the credit risk share of the loss is more than 0%, N if the credit risk share of the loss is 0%
  • Related Event Reference ID, which is the ID of the grouped loss (if the loss event is grouped)
  • Date of Occurrence
  • Date of Discovery
  • Date of Recognition
  • Gross Loss Amount
  • Direct Recovery
  • Indirect Recovery
  • Gross Income

Business Attributes
ASAP Roadmap ID 201   Make global settings 
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 GRRMOBORXDWNL 0 /ORM/GR10000003 GRC Risk Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20110520 
SAP Release Created in V1000