Key Fields of a Rule 

Rules always have at least the following key fields:

·        Event

·        Expression

·        Action

In some applications it is necessary to add other key fields. This means that right from the start you can prevent rules that make no sense in a certain context from being executed.

For example, the SAP Claims Management industry solution for insurance has the insurance line of business as an additional key field (such as life insurance, health insurance, property & casualty insurance). This means that an event in a claim related to P&C insurance calls up different rules from the same event in a claim related to health insurance.

The BRF therefore supports the possibility of setting any number of parameters for rules.

However, if you want to add your own parameters, you must consider the following:

·        You are no longer able to use the corresponding BRF standard table (TBRF210).

You therefore have to define a corresponding table yourself in the application.

The following applies for this table:

¡        You must define the table in a package of your application.

¡        The table contains at least the key fields of the standard table TBRF210 as well as the other key fields that you define yourself.

¡        Usually the table contains all the attributes of table TBRF210.

Practice has shown that a cross-application rule table contains all fields of TBRF210 plus other key fields (such as the insurance line of business).

·        In your application, create a class that implements interface IF_DETERMINE_ASSIGNMENT_BRF.

This class contains method DETERMINE_ASSIGNMENT.

The method has the following effect:

¡        It reads the rules from your application-specific table

¡        It converts the rules to the format of standard table TBRF210

 When you implement your DETERMINE_ASSIGNMENT class, we recommend that you orient yourself on the delivered classes CL_DET_ASSIGNMNT_RL_BRF and CL_DET_ASSIGNMNT_RS_BRF.