IMG MDG -3

Central Governance for Material

• Data Model Mapping
  •  you use this report to display the mapping between the entities from the ERP database tables and the entities in the Master Data Governance(MDG) hub.  this information can be used to determine if all customer created fields are mapped correctly. ths report lists all relevant entities, attributes, and keys, this includes;
    • fully mapped entities and their mapped fields
    • partially mapped entities with their mapped and unmapped fields
    • flexible entities which are not mapped since they appear only in the MDG hub
• Clear UI Metadata Buffers
  • use
    • this report clears the following buffers in this sequence;
      • text buffer
      • search help buffer
      • SMT-Mapping Data Buffer
      • SPI Metadata Buffer
      • you shoud use this report after extending the data model to make sure that the metadata is consistent with the MDG customizing and UI Configuratoin.
• Import Predefined Change Request Types
  • use
    • in this customizing activity, you can activate as BC set containing the predefined change request types created by SAP. This BC set is made up of other BC sets. you can use these change request types for your master data governance process or define your own. this activity must be carried out independently for each client. the change request types each have a rule-based workflow  defined for them and a link to BRF+* applications.
      • the change request types are;
        •  create material
        • process material
        • mark material for deletion
        • process multiple materials
• Import Predefined Change Request Types for Multi-Record Processing
• Import Predefined Chnage Request Types for SAP Fiori
• Import Predefined Change Request Types for Lean Classification
• Import Predefined Change Request Types for SOAP Product Inbound
• Import BS Set to Reset Governance Scope
• Maintain Fields for iDoc Key Mapping
• Maintain Fields for iDoc Value Mapping
• Business Add-Ins
  • BAdI : Change Request Data Enrichment
  • BAdI : Extension of the API with Customer-Specific Segments
  • BAdI : Define Alternate DRF Filter Provider

 

What is BRF+?

Introduction

BRF+ stands for 'Business Rule Framework Plus which provides a comprehensive application programming interface and user interface for defining business rules.

it enables you to define business rules without the need of writing ABAP code.

the generated business rules can be incorporated into other SAP programs or subsititution/validation rules.

BRF+ is not new and even not directly related to SAP S/4 HANA, but with the release of SAP S/4 HANA 1610, BRF+gained more attention since it is launched as the go-to solution for some business processes.  the mose importana ones are the changes in output management for billing and purchasing.

it is a part of SAP NetWeaver ABAP stack

the t-code used is BRF+ or BRF+

 

what is the significance of BRF+?

before BRF+ came into existence, still the business was running right?

so , it is very much important to understand how it was handler earlier,  before we get into SAP BFR+/BFRplus.

the following below are the approaches follwed when SAP BRF+ was not into exsitence or when the developer was not aware of SAP BRF+/BFRplus.

    Lets say you want to add a condition based on the particular companay code(BUKRS) & Sales Organization(VKORG) and execute some functionality, this was achieved by simply doing the hardcoding in IF ELSE condition & achive the functionality to work for a particular company code & sales organization - &this was handled in program itself, which is the traditional approach.

the above approach was little bit difficult - if any changes come in future, as it was time comsuming for the developer to do analysis first & do the changes - if the change was done at multiple places.so the second approach & the little bit better approach which was used to follow is to maintain the company code & sales organization in the cutomized table and fetch the corresponding value maintained from the customized table.

the third approach what SAP suggested is to maintain the hardcoded values using table TVARVC and the associated transation to store parameter data and baed on parameter data stored in TVARVC validation was done for a particular company code & sales organization and corresponding value was fetched.

at lease with evolution of SAP S/4HANA, BRF+ has got more prominence and SAP has already started using BRF+in some standard applications for decision making purpose.

so even in some standard application or program SAP is still following the above approahces. but, not SAP is thinking to overcome the approaches mentioned above ,by the framework which is known as SAP BRF+/BRFplus.

=components of BRF+

Application

Data Object Creation

Functions

Rule Set

Rules

Decision Tables

Decision Tree

=Note

All SAP applications that are based on SAP NetWeaver can access BRFplus withing the boundaries of the SAP system.

In BRF+ terminology, the imput is called Context & the Output is called the Result.

this is available from SAP(ECC) ERP 6.0 onwards.

 

How do we create  BRF+ & its procedure?

1. create an application using t-code BRF+

2. inside the application, we will create all the other object like Data Object Creation, function, rule set and so on.

3. Data Object Creation consists of all the variables used, which will be used for processing. these variables are basically input data to the BRF+ to process and to generate the output/result.

4. next step, is to create functions which is the core componenet - where the actual processing of the functionality gets executed.

5. inside the functions we have a Rule Set, which is basically a container which holds all set of ruls and these rules are processed based on the decision tables.

6. here, rules will be assigned to Rule Set and Rule Set in assigned to Functions and the Function will be tagged to a application.

7. Decision tables are going to hold the data which consists of all possible inputs & corresponding Output values.

8. Basically, the data objects import parameters validate against the decision tables and these decision table will generage the outcome/result.

9. decision tree can also be used instead of Decision tables but these would be used when you have very simple - yes of no type of validation.

note: this is just a high level steps for creating BRF+ - as its just an overview & step by step creation of BRF+ will be covered in another blog post.

 

 

 

 

Introduction to SAP BRF+/BRFplus & why is it so popular in SAP World !! | SAP Blogs