Understanding SAP MDG in a Traditional way
According to SAP Insights Digital transformation is a business-wide initiative to integrate intelligent technology into all areas of the business to achieve better outcomes and optimized performance and business processes.
In my previous blog post, I have briefly explained the Role and Capabilities of SAP MDG in SAP’s futuristic plan for digital transformation.
In order to have a full utilization of SAP MDG in this era of digital transformation, it is important to understand the traditional approach of SAP MDG.
In this blog post, I will try to give a holistic view of the of the traditional approach and technologies used in SAP MDG. I have added the links for some related blog posts published and available in the SAP MDG community in this regard.
- A data model in MDG is comprised of various elements (entity types, attributes, and relationships) to enable the modelling of master data structures of any complexity.
- Once the data model is implemented in MDG and activated, the system automatically generates the underlying tables and structures.
- When the end users create or change data from the UI, the data is persisted in these generated tables
Data Model: BP
Data Model: MM
Data Model: 0F
Blog posts for Data Modelling:
Data Loading Options in the SAP MDG Staging Area
Some of the available options capable of loading data in the staging area of SAP MDG are as follows:
- Data Import Framework
- File Upload Framework
The Data Import Framework requires at least two file directories on the application server to facilitate loads:
- One directory to store the files to be imported
- One directory to store the archived files that have been imported
The Data import framework supports load files only in certain defined file formats (XML). Standard Business Add-In (BAdI) BADI_MDG_FILECONVERTER is used to perform any conversion activities, including formatting the load files in the desired XML formats.
Data Import Framework is a cross-entity type application. It supports importing various entity types for various data models.
File Upload Framework is another popular option in the SAP MDG framework that is used for initial loads by uploading a file in the SAP MDG staging area. SAP MDG delivers Web Dynpro application USMD_FILE_UPLOAD which is used for loading master data from the load file to the SAP MDG staging area.
Blog posts for Data Import:
Workflow and Business Rules
SAP delivers a rule-based workflow template (WS60800086), which is configurable using a BRFplus decision tables and can be used for any change request process where SAP-delivered workflow templates do not suit the project-specific requirements.
For the purpose of Create Material, SAP delivers for Change Request Type MAT01, the BRFplus application
- DT_SINGLE_VAL_MAT01: Single-value decision table
- DT_USER_AGT_GRP_MAT01: User agent decision table
- DT_NON_USER_AGT_GRP_MAT01: Nonuser agent decision table
The condition alias defined for each row in a single-value decision table becomes a link between the single value decision table and the user agent or nonuser agent decision tables.
Blog posts for Rule-Based Workflow:
User Interface Modelling
SAP MDG UI leverages both Web Dynpro technology and SAP Fiori design.
Web Dynpro ABAP screens are used by SAP MDG Central Governance.
SAP Fiori screens are used in SAP MDG Consolidation.
The Key components include SAP predefined Floorplans, UI building blocks (UIBBs), and Floorplan Manager configuration editor.
The floorplan applications are linked and grouped under pre-delivered SAP MDG roles for each domain. These standard applications cater to each master data activity create, change, block, delete, mass processing.
Blog posts for UI Modelling:
The outbound implementation defines how the replication of business object is executed. Outbound implementation defines the communication channel.
The communication channel denotes the means of transmitting data to target systems of the SAP MDG system. The communication channels are:
- Replication via web services
- Replication via IDoc
- Replication via file
- Replication via RFC
A business object should be assigned to an SAP MDG entity type..
A business system in the context of the data replication framework is used to represent the physical system in an enterprise landscape to which master data are replicated. A business system can represent both the source system and target system.
Replication models define what data (through outbound implementation) are sent to
which system (through the business system) under what conditions (through outbound parameters).
An Outbound Implementation must be assigned to a Replication Model.
Blog posts for Data Replication:
SAP MDG provides Prebuilt data models, business rules, workflows, and user interfaces which can be extended and customized according to business needs. ABAP WebDynpro, Floor Plan Manager, BRFplus, SAP workflows, Idoc and ALE are the main technologies (technology components) used to achieve smooth master data creation, updation, deletion experience in SAP MDG for multiple domains and systems.
Please provide your feedback or thoughts in the comment section.