Data Replication Framework Overview

 Use:

You can use this function to replicate data from the source system to one or more target systems.
There are two modes of Deployment in SAP MDG
1.       Co-deployment
-          In this the MDG and Business Processes, both resides in same system.
-          In this, after activating CR, the data will be stored in standard table of same system.


1.       Hub deployment
-          In this MDG and Business Processes, both resides in two different system.
-          After activating CR, first it stored in MDG standard tables like KNA1, LFA1 then it will get replicate into other systems.



Two types of Data Models


Reuse Mode:

- After Activation of CR the data will directly go active area which w which is SAP Business Running Tables e.g. KNA1, LFA1, MARA.


- To use this, we must create active area and assign access class to it.


- The access class act as bridge between MDGAF (Application framework) and the reuse area.


- No need of DRF

Flex Mode:

-          After activation of CR, the data will be storing in Staging area only. We need to Replicate data using DRF to pass data in Active area.


When DRF Needed:

1.       In Hub Model (Both Reuse mode/Flex mode).

2.       In Co-deployed mode (Only for Flex mode).

Communication Channel: -

              In general Communication Channel is the is the medium through which we can send the message to the target system. For Example, Phone call, text message, emails, radio, social media.

The following communication channels are available for data replication purposes:

  • RFC

  • IDoc

  • Enterprise Services

  • File download

Business Objects

·       Business Object is Real time entity which represent Objects in Business System.

·       It’s having Attributes and Operations.

·       In MDG we having Business Object like BP, Customer, Supplier, Material.

·       BP is one Business Object. Which can have multiple Roles.

·       BP can have Customer Role that comes under another Business Object.

·       The Business Object have some set of operation like some BO can only be Creation of Customer.

·       BP will have relationships like two persons can open a software company in partnership. So, they don’t hold any other roles apart form BP. So, they will have some set of attributes which will common for all BP roles.

Business System

·       System is a set of services.

·       Example Creating Customer is Service.

·       This all Business Systems will be stored in System Landscape Directory.

·       Landscape is nothing but the Overview of something.

·       System Landscape is the Collection of Systems which is using Business Process.

·       SLD is a place where we bring all Systems.

Key Mapping



So here we have 3 system. First is Salesforce system, second is MDG system and third one is S4/Hana system.

·       Salesforce will create customer first with the name XYZ123 suppose.

·       Then it needs to replicate to MDG system for governance like Checking Data Quality, Validations and all.

·       After that it should replicate from MDG Hub system to S4/HANA System.

·       When the customer XYZ123 will come into MDG Hub system the MDG will generate its own Customer ID as per the number range.

·       Salesforce having internal number generation so after creation of customer in salesforce, the system gave this customer number as XYZ123.

·       MDG also having Internal number generation so MDG will generate a separate number of same Customer suppose here 1700129.

·       After that S4/HANA will have External number generation so that same customer which is created in MDG Hub should seat inside Business Processing System here, S4/HANA with same Customer ID i.e. 1700129.

·       Here the problem comes, the two different system having two different customer ID’s for same Customer.

·       So, if someone change something in Customer form SFDC system then that same customer should get change which is having different ID in MDG.

·       To solve this, we having key mapping framework in DRF. In SAP we having some table where we save all this mapping.      


Value Mapping



·       Take an example of Payment term, In SAP system we have payment terms in format like 10, 20, 50, NT30, NT60. But in Salesforce system it can be in Roman like X, XX, XV, etc.

·       Now End user creating Customer Master in Salesforce system with Payment term = XX (Payment term should get convert into ‘20’ in SAP). So, this same customer should get replicate into MDG system and SAP system. But SAP and MDG don’t understand this payment term ‘XX’ so, it should get converted into ‘20’ in SAP system while replicating.

·       For this Value Mapping is used. 

Business System:
-          It is a logical system which function as sender or receiver within Exchange Infrastructure.
-          It is local representation of physical or virtual system. It uses to group together some SAP systems and its processes and define communication between them. It also defines the control of data between SAP system and third-party systems.
-          It is defined in System Landscape Directory (SLD) which is a central repository of information about all of the SAP systems in our landscape. Once a business system has been defined in the SLD, it can be imported into your SAP systems.
-          ERP system, PI system, CRM system are the examples of Business Systems.

Logical System:
-          A logical system is a system containing applications that are coordinated to work with one set of data
-          A logical system can be a specific client on a specific SAP system.
-          We can define the logical system in SALE transaction.

Define Filtering Criteria
T-code = DRFF 

Log Information
 
·       SLG1 is the T-code by which we can see the log of any objects.
·       FMDM is the Object name for MDG objects.
·       DRFLOG is Replication related Log data.
 
Next step is to define Replication Model

Configuration of DRF for Outbound Implementation

DRFIMG -> Define Custom Setting for Data Replication -> Define Technical Setting -> Define Technical Setting for Business Systems.


Next step is to define Replication Model

   

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