SAP ABAP IMG Activity GRRMSCUSTAGGR (Automatic Risk Aggregation Settings)
Hierarchy
GRCFND_A (Software Component) GRC Foundation ABAP
   GRC-RM (Application Component) GRC Risk Management
     GRRM_CUSTOMIZING (Package) Customizing related obejcts
IMG Activity
ID GRRMSCUSTAGGR Automatic Risk Aggregation Settings  
Transaction Code S_GM1_71000010   (empty) 
Created on 20110928    
Customizing Attributes GRRMSCUSTAGGR   Automatic Risk Aggregation Settings 
Customizing Activity GRRMSCUSTAGGR   Automatic Risk Aggregation Settings 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GRRMSCUSTAGGR    

Use

In this Customizing activity, you create custom aggregation modes to enable Automatic Risk Analysis Aggregation.

In automatic risk aggregation, the software calculates an aggregated risk from multiple input risks. Any change in one of the input risks automatically updates this calculation. In this way, you can set up a hierarchy of risks, typically with different granularity, where the higher risks are automatically synchronized with changes happening on the lower levels.

Automatic aggregation only covers the analysis part of the risk. Analyses of the input risks are combined using defined calculation rules to generate an updated analysis of the aggregate risk.

The way in which the calculation of aggregate risks is performed depends on customizing settings. There are the following possibilities:

  • The standard (default) calculation mechanism provided by SAP

    This mechanism can only aggregate corporate risks with a forecasting horizon based analysis into a target corporate risk. For each forecasting horizon the impact of the target analysis is calculated by combining all underlying analyses in one of the following ways:

    • Sum: the aggregated impact is the sum of all underlying impacts
    • Average: the aggregated impact is the average of all underlying impacts
    • Maximum: the aggregated impact is the highest of all underlying impacts
    • Minimum: the aggregated impact is the lowest of all underlying impacts

      Similarly, the probability is calculated for each forecasting horizon by combining the underlying analyses in one of the following ways:

    • Sum: the aggregated probability is the sum of all underlying probabilities
    • Average: the aggregated probability is the average of all underlying probabilities
    • Maximum: the aggregated probability is the highest of all underlying probabilities
    • Minimum: the aggregated probability is the lowest of all underlying probabilities
    • Product: the aggregated probability is the product of all underlying probabilities (interpreted as fractions of 1)
  • A custom calculation mechanism implemented individually.

    Such a custom logic requires the implementation of an ABAP class implementing the ABAP interface IF_GRRM_ANALYSIS_AGGREGATION. The standard logic, described above, is also implemented as such a class (CL_GRRM_ANA_AGGR_DEFAULT) and can be used as an example when implementing a custom logic.

Requirements

To enable e-mail notifications to notify about failed aggregations or changes in underlying risks, you should complete the following customizing activities:

  • Users, who receive notifications are determined by the standard agent determination mechanism of GRC and the business event for this is 0RM_RISK_AGGREGATION. It can be customized in IMG activity Governance, Risk and Compliance -> General Settings -> Workflow -> Maintain Custom Agent Determination Rules.
  • The notification messages are customized in IMG activity Governance, Risk and Compliance -> General Settings -> Workflow -> Maintain Custom Notification Messages. Here, you use the message class 0RM_RISK_AGGREGATION and message numbers 01 (for aggregation failure notification) and 02 (for change update notification).

Standard settings

Activities

In this Customizing activity, you can define multiple aggregation modes. You define each mode in terms of the following parameters:

  • Cust. aggr

    Identifying key

  • Imp aggr

    Impact aggregation, mandatory for the default aggregation mode.

  • Prob aggr

    Probability aggregation, mandatory for the default aggregation mode.

  • Reference to

    The name of an ABAP class which implements a custom logic, mandatory for the custom aggregation mode.

    If an ABAP class is in the Reference to field, the custom logic implemented in that class is applied. If the field is blank, the standard calculation is applied using the specified settings for impact and probability aggregation.

  • Customized aggregation

    A descriptive name to appear on the user interface.

Example

Use

In this Customizing activity, you create custom aggregation modes to enable Automatic Risk Analysis Aggregation.

In automatic risk aggregation, the software calculates an aggregated risk from multiple input risks. Any change in one of the input risks automatically updates this calculation. In this way, you can set up a hierarchy of risks, typically with different granularity, where the higher risks are automatically synchronized with changes happening on the lower levels.

Automatic aggregation only covers the analysis part of the risk. Analyses of the input risks are combined using defined calculation rules to generate an updated analysis of the aggregate risk.

The way in which the calculation of aggregate risks is performed depends on customizing settings. There are the following possibilities:

o    The standard (default) calculation mechanism provided by SAP

This mechanism can only aggregate corporate risks with a forecasting horizon based analysis into a target corporate risk. For each forecasting horizon the impact of the target analysis is calculated by combining all underlying analyses in one of the following ways:

-    Sum: the aggregated impact is the sum of all underlying impacts

-    Average: the aggregated impact is the average of all underlying impacts

-    Maximum: the aggregated impact is the highest of all underlying impacts

-    Minimum: the aggregated impact is the lowest of all underlying impacts

Similarly, the probability is calculated for each forecasting horizon by combining the underlying analyses in one of the following ways:

-    Sum: the aggregated probability is the sum of all underlying probabilities

-    Average: the aggregated probability is the average of all underlying probabilities

-    Maximum: the aggregated probability is the highest of all underlying probabilities

-    Minimum: the aggregated probability is the lowest of all underlying probabilities

-    Product: the aggregated probability is the product of all underlying probabilities (interpreted as fractions of 1)

o    A custom calculation mechanism implemented individually.

Such a custom logic requires the implementation of an ABAP class implementing the ABAP interface IF_GRRM_ANALYSIS_AGGREGATION. The standard logic, described above, is also implemented as such a class (CL_GRRM_ANA_AGGR_DEFAULT) and can be used as an example when implementing a custom logic.

Requirements

To enable e-mail notifications to notify about failed aggregations or changes in underlying risks, you should complete the following customizing activities:

o    Users, who receive notifications are determined by the standard agent determination mechanism of GRC and the business event for this is 0RM_RISK_AGGREGATION. It can be customized in IMG activity Governance, Risk and Compliance -> General Settings -> Workflow -> Maintain Custom Agent Determination Rules.

o    The notification messages are customized in IMG activity Governance, Risk and Compliance -> General Settings -> Workflow -> Maintain Custom Notification Messages. Here, you use the message class 0RM_RISK_AGGREGATION and message numbers 01 (for aggregation failure notification) and 02 (for change update notification).

Standard settings

Activities

In this Customizing activity, you can define multiple aggregation modes. You define each mode in terms of the following parameters:

o    Cust. aggr

Identifying key

o    Imp aggr

Impact aggregation, mandatory for the default aggregation mode.

o    Prob aggr

Probability aggregation, mandatory for the default aggregation mode.

o    Reference to

The name of an ABAP class which implements a custom logic, mandatory for the custom aggregation mode.

If an ABAP class is in the Reference to field, the custom logic implemented in that class is applied. If the field is blank, the standard calculation is applied using the specified settings for impact and probability aggregation.

o    Customized aggregation

A descriptive name to appear on the user interface.

Example

Use

In this Customizing activity, you create custom aggregation modes to enable Automatic Risk Analysis Aggregation.

In automatic risk aggregation, the software calculates an aggregated risk from multiple input risks. Any change in one of the input risks automatically updates this calculation. In this way, you can set up a hierarchy of risks, typically with different granularity, where the higher risks are automatically synchronized with changes happening on the lower levels.

Automatic aggregation only covers the analysis part of the risk. Analyses of the input risks are combined using defined calculation rules to generate an updated analysis of the aggregate risk.

The way in which the calculation of aggregate risks is performed depends on customizing settings. There are the following possibilities:

  • The standard (default) calculation mechanism provided by SAP

    This mechanism can only aggregate corporate risks with a forecasting horizon based analysis into a target corporate risk. For each forecasting horizon the impact of the target analysis is&#x

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 GRRMSCUSTAGGR 0 /ORM/GR10000003 GRC Risk Management 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
GRRMAGGRCUSTV V - View SM30  
History
Last changed by/on SAP  20111102 
SAP Release Created in V1100