BRF+ Framework Overview

 

BRF+ (Business Rule Framework)

-          BRF+ is based on the Business Rule Management System offered by SAP. It is a part of SAP NetWeaver.  Therefore, whatever the applications in term of SAP which are based on SAP NetWeaver can be access through BRF+ within the boundary of SAP system.

-          BRF+ provides the comprehensive programming interface or the user interface for defining and processing of our business rules.

 

For any Organization, for any operation, they need three things. 1. Data 2. Business Process 3. Rules We have separated all these three segments in different systems. Because the rule is more prone to change and it is not a good practice to change our program/software or Data very frequently. So, the rules are maintained in different system called as Business Rules Management Systems.

BRMS is a general term which is used by all software’s like Oracle, PeopleSoft, workday, sap, salesforce which they use to maintaining the business rules.

In terms of SAP we called it as a BRF+. 

BRF+ is the BRMS system specific to SAP to maintain the business rule for SAP environment.

It’s a BRMS system which allow us to define, maintain and edit rules specific to our businesses.

We can keep track of a version of rules. We can track changing of rules. We can maintain in the central repository. Where everybody has an access to change it or define it.

Difference between BRF and BRF+.

-          BRF is an old version of BRF+.

-          It was purely Dialogue Based. It was developed using Module Pool Programming in Core ABAP. Dialogue dyne-pros.

-          BRF+ is an advance version of BRF+. It’s a rule management framework system and it is Webdynpro based UI to maintain and design the rules.

History of BRF+

-          The whole story started at 2005.

-          When they wanted to design the system called FDT system. (Formula and Derivation tool).

-          FDT started and they understood that they need to separate the business rules from the code because it is not practical to change the code every day.

-          So they came with the first project FDT. Later they came with BRF and after they migrate it to the BRF+.

Steps to Define the Rules

1.       Modelling

2.       Defining

3.       Automate

4.       Maintain

*** T-code = BRF+, BRFPLUS, FDT_WORKBENCH

*** BRF+ Application

i.                     It is like a web-dynpro component which encapsulate the other entities.

ii.                   It is a container for all the objects related to BRF.

Whenever we need to define the business rules. We need to define lot of other entities. Something called Data Objects, Functions, Expressions, Rules and Rule sets.

Role need to access BRF+ = SAP_BC_FDT_ADMINISTRATOR.

 

T-CODE BRF+ => Two tabs 1. Repository 2. Catalogue

1.       Repository: Can create application.

2.       Catalogue: Business can have application related to different modules like MM, SD, MDG. So that they can collect into one catalogue. That will be useful for end user to maintain the rule.

 

Creation of Application

Create Application => General data => Application

Storage Type: Once we create and save, we cannot change it.

1.       System: Client Independent, it will be accessible to all the client. We can only use the element and variable available in the system. We cant use the customizing one. We can transport it throughout the systems.

2.       Customizing: We can use our own customizing elements. We can transport it too.

3.       Master Data: We cannot transport this one. Can use locally.

Mark for Deletion: After 15 days it will delete from the system.

Every Application object will have some unique ID, which will help to transport that application to other systems.

We having versioning option here so, whenever any changes made in application, we can save that version and use it later. So, we can maintain multiple version in the application and according we can activate and deactivate the versions to use it.

After creating application, we have to activate it and after that only we can create other objects.

Data Object:

** It is like global variable which we can use throughout the application.

Inside this we can create Element, structure and tables. Element is nothing but the field. We can create the structure and table inside this.

Functions:

·       Function are entry point of BRF+ Application from ABAP

·       This is the point of contact between BRF and ABAP code

·       It can be called from ABAP code

1.       Directly via ABAP code using BRF API’s

2.       Using FM

3.       Using webservices

It is like Function Module. Having some input output values.

Function can be operated in 3 modes.

1.       Event mode(using this, we can trigger a rule set(collection of rules)).

2.       Functional mode(directly call an expression)

3.        

In Functions => Details section

Generates: if we want to use this function in any other function module in abap code then we can convert this function module in general function module or web services to call it.

Create code template: system will generate code for that function and we can use this code in our program.

Context: whatever variables, structure or table which we have defined which is import parameters.

Result Data Object: This is like export parameters.

Assigned Rulesets: in this we can define multiples rules.

Expressions: Conditions, Decision Tables, Loops and all.

 

 

 

Comments

Post a Comment

Popular posts from this blog

SAP MDG Process Modelling

Image
Overview In SAP MDG, every change to master data is initiated using a change request. After a change request is initiated, it needs to be processed before activation or rollback by applying governance rules and collaborations. The process model provides the required input (metadata) for change request creation and processing, e.g., workflow, CR steps, and objects that can be processes. Submit and activate/rollback are mandatory steps in a change request. MDG reuses the SAP Business Workflow component of an underlying SAP business suite. SAP MDG workflow is an instance of SAP Business Object BUS2250. If the request has parallel processing, then each parallel step of the change request will have one BUS2250 instance. Define Governance Scope: Here we can define governance scope on the entity as well as the attribute level. For example, we have kept ‘NO’ to the below custom entity. As a result of MDG UI, the UIBB for this entity will only be in read-only mode. Business Object An ...
Read more

MDG Derivation (BADI)

Image
In this blog, we will see how to derive MDG attributes using BADI. Derivations can be divided into two types.  Single-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from same entity. For this, we use 'USMD_RULE_SERVICE' BADI definition. Cross-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from another entity. For this, we use 'USMD_RULE_SERVICE_CROSS_ET' BADI definition. First, we will see a single entity derivation. Scenario:  We are going to make language English as the default if the user gives the country as India. Steps: 1. Go to SE18. 2. In 'USMD_RULE_SERVICE' BADI defination, create BADI Implementation.  3. For creating BADI Implementation, first we need to create Enhancement Implementation.  4. Give the properties as below. 5. Now, create BADI Implmentation and give following properties. 6. Maintain the filter values. H...
Read more

MDG Validation (Using BADI)

Image
In this blog, we will see how to validate the MDG attributes using the BADI implementation. So, we are taking the example of the 'BP Grouping' field to make it mandatory on the UI. For this, we should know the technical attribute name for the respective field. In our case, 'BU_GROUP' is the technical name for the BP grouping field. Steps for the Implementation of Validation BADI. 1.   Open T-code ‘MDGIMG’ –> General Setting -> Data Quality and Search -> Business Add-Ins -> Execute BADI: Define Validation/Derivation OR SE18 -> BADI name: 'USMD_RULE_SERVICE' -> Create BADI Implementation.  2. After execution, the following screen will appear. Go down, and there you will find the option to create enhancement implementation. Click on that button. 3. Provide the name and short description of the implementation, as follows:   4.  After that, we have to create the BADI Implementation and Implementation class. 5.  You will be directed to the Enha...
Read more