What is modeling?

Identifying all the business parameters and then implementing them in a way that it integrates with the code and workflow design.

Normally the business policies that are referred for making a business decision are converted to rules.

SAP NetWeaver BRM Modeling is helpful in formatting rules for business policies.

Policies can lead to two kinds of rules one set refers to adherence to the business policies and another is non-adherence. The process of Formatting rules out of business policies and decision making parameters (most of them are auto meaning non-manual) is referred as modeling.

There are no hard and fast rules in modeling, with logic and experience the modeling can be visualized in simple and effective ways.

Consider below examples, these demonstrate simple and complex modeling. The second example will also demonstrate “Negative validation approach”.

  • Example 1 – simple rule. Check for minor, in most of financial process the age criteria is very basic calculation which is normally hard coded or configured in configuration file. Normally this file access and setup is handled by an IT person. In BRM the condition becomes a very basic rule. If ( < condition > ) { < action > } If (age < 18) {Tag the person as a Minor}
  • Example 2 – complex Rule Grouping multiple conditions together to reach a common valid reason can be achieved by either creating a Rule-set encompassing all simple Rules Or by creating a decision table and a single rule to trigger actions. The selection of either approach above will depend upon the business policies and relationship among them, here we are considering a special case.

Consider following multiple conditions referring to age criteria for a particular eligibility in processing:

  • the age should not be more than 45
  • the person should not be minor.
  • the person should have completed 10 years in current job.
  • the history performance should not be “red”
  • the govt employee has relaxation of 5 years for age.
  • the history performance with “green” will have 2 year relaxation.

In normal the above requirements can be implemented with 5 independent rules with simple if condition each, or with a decision table as below. Initial Parameters: Age, isValidAge = true, maxAgeLmt = -1

Govt Employee
performance yes No
red maxAgeLmt = -1 maxAgeLmt = -1
Green maxAgeLmt = 50 maxAgeLmt = 47

Rule If (18 < age < maxAgeLmt) {The person is not eligible} The factors (parameters) affecting and there possible value: &nbsp&nbsp&nbsp Direct age limit 18 to 45 &nbsp&nbsp&nbsp Performance history red / green &nbsp&nbsp&nbsp Govt. Employee yes/ NO With increasing number of factors the decision table would grow big, but it provides a one time view for multiple policies catered to. This approach is to look at the invalidation criteria than validity check. This is “Negative validation approach”. Here rules are modeled to check for the non-adherence of the criteria opposite to normal approach. This is first simple example which gives a different way of considering requirement while implementing and modeling the requirements for the BRM.


  • Rule modeling is important activity in BPM/BRM process implementation.
  • this activity needs clear and crisp understanding of the business practices and business policies.
  • the rules modeling should align with aim and purpose of automation of business process.

Need Help:
In case you need assistance in SAP SOA BRM Modeling, please contact us. Please send us your questions, comments or assistance request, and our team would be glad to assist you.

By Nikhil Joshi (on behalf of SAP Consulting Team)

SAP :: Streamlined

We offer variety of services including SAP ECC ,SAP HR,SAP BW,SAP CRM, SAP SCM,SAP BPM, Business Objects, SAP ABAP DevelopmentSAP BASIS and SAP NetWeaver consulting. We have expertise in providing implementation,development, SAP Migration and SAP support services to SAP customers across diverse industries at a global level.
Have a question on SAP? Write to our SAP Architect.

(We promise a no-obligation consulting reply)