SAP ABAP IMG Activity SIMG_ICL_BRF_RL (Define Rules)
Hierarchy
INSURANCE (Software Component) SAP Insurance
   FS-CM (Application Component) Claims Management
     ICL_BASIS (Package) FS-CM: General Functionality
IMG Activity
ID SIMG_ICL_BRF_RL Define Rules  
Transaction Code S_KK4_08000608   (empty) 
Created on 20030730    
Customizing Attributes SIMG_ICL_BRF_RL   Define Rules 
Customizing Activity SIMG_ICL_BRF_RL   Define Rules 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _ICL_BRF_RL    

Use

In this IMG activity you define rules for an event of the Business Rule Framework (BRF). You can use these rules to provide BRF events with business content.

The starting point is a BRF event for which you want to define rules. This BRF event might be

  • an event provided by SAP
  • an event that you have created yourself in IMG activity Enhance Events

Rules

Normally a rule consists of a Boolean expression and an action (this is the so-called "real rule"). In this context an action stands for any number of concrete actions.

However, there are also adaptations of the "real" rule. Here is a list of all the rules supported by the BRF:

  • The common rule, consisting of an expression and action ("real rule")

    Appearance: if <Expression> = TRUE then <Action>
    In other words, if a condition defined by <expression> delivers the result TRUE, the assigned <action> is executed.

  • The rule does not contain an expression but an action ("false rule")

    If you do not define an expression, the action is always executed as soon as the event is triggered.

  • The rule contains an expression, but no action ("false rule")

    The expression is always calculated, but no action is executed.
    This rule only makes sense in the following cases:

    • When the event expects a result to be returned
    • When the expression in the rule is a control predicate that already executes a special action implicitly.

You can define any number of rules for an event. If two rules use the same expression and the same action, the system considers them to be the same and rejects them.

Insurance line of business

For every event you define rules that depend on the insurance line of business. For example, the same event in a P&C claim should call other rules than is the case in health insurance. You must specify the insurance line of business. This is obligatory. Cross-line rules are not available.

Internal claim type

In addition, you can define rules depending on the internal claim type. Specifying the internal claim type is optional. The version and generation of the internal claim type are not considered.

Gate Expression

You can use a gate expression to control whether a rule is applied.

  • If you do not enter a gate expression, the rule is always applied if the insurance line specified in the rule and the internal claim type (if specified) are valid.
  • If you enter a gate expression (and this must be a Boolean expression), the rule is only applied if the insurance line and the internal claim type (if specified) are valid and the gate expression delivers the value TRUE. If this is not the case, the rule is ignored.

Notes

  • The BRF does not have any independent object called "Rule". Basically, a rule is merely a triple consisting of an event, a Boolean expression, and an action.
  • When you create a rule, make sure that both the Single Instance Mode and Multi-Instance Mode flags are set. If this is not the case, the rule will not be processed.

Requirements

The event for which you want to define one or several rules already exists.

The rule that you want to realize has not already been entered in this event.

Standard settings

Rules are only provided in the form of sample customizing, if at all. If rules have already been entered, check their usability and remove them if necessary.

Activities

If you want to define a real rule in an event, you must make the following decisions:

  • In which event do you want to enter the rule?
  • In which insurance line is the rule required?
  • For which internal claim type is the rule required and/or does the required rule perhaps depend on the internal claim?
  • What should the rule be called?
  • Do you want to assign the rule to a rule set?
  • Which Boolean expression is required?
  • Which action is required / which actions are required?
  • Should the rule only be used under certain circumstances (gate expression)?
  • Should the rule be used in dialog mode (single instance mode) and/or in batch mode (multi-instance mode)?

To define rules for an event, perform the following activities:

  1. Call this IMG activity.
  2. On the Change Rules screen, select the event for which you want to define rules.
  3. Confirm using the @2K@ icon (Enter).
  4. Make the required settings on the screen that follows.
  5. Save your entries.

Example

You could define the following rule for event LOLCH (Loss Location Changed) in the Claims Management system: A claim handler task is created if the loss location is incomplete.

What is important here is that you can use the expression to define yourself what an incomplete address is, without having to change the code of the application.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
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
ICL_BRF_RL T - Individual transaction object ICL_BRF_RL  
History
Last changed by/on SAP  20030730 
SAP Release Created in 472