Book 4

Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 62

Why SAP MDG?

Customer Master Data

Vendor/Supplier Master Data

Material Master Data

Finance Master Data

1. Duplicate Records

2. lack of Framework

3. Data Quality

C, C++ SAP MDM (Master Data Management)

1. Console

2. Data Manager

3. Import Manager

4. Syndicator

MDG 6.1

MDG 7.0

MDG 8.0

MDG 9.0

MDG 9.1
MDG 9.2
Source

SAP ABAP

SAP CRM

Non-SAP

SAP MDM

ECC - SAP ABAP ---- MDG

Source

SAP MDM

SAP ABAP

Non- SAP
Tx. MDGIMG

Tx. DRFIMG

Tx. ESH_COCKPIT

Tx. NWBC

Single Workflow:

REQ

VER
APP

Parallel Workflow:

(Address Verifier)

Basis

Basis

Computer Security

Basis
Basis

Data Model:

1. Custom Data Model

Storage Type:

Type 1

Changeable via CR and Generated DataBase tab

Eg: CARRID, MATERIAL, BP_HEADER

(Leading Entity type)

Relationships: (Entity type)

1. Referencing

2. Leading

3. Qualifying
4. FK

Reuse Mode

Database table

Step 1: Add the custom field in Data Model


Adjust the Stagging Area
Step 2: Add the custom field with MARA table

Step 3: Include Custom field in table T130F


Generate Data Model Specific Structure
Step 4: Structure Extensions

MDG_BS_MAT_S_<table name>

MDG_BS_MAT_S_<table_name>_UI

MDG_BS_MAT_S_<table_name>_X

Step 5: SMT mapping

MDG_BS_MAT_MAP_2PP

MDG_BS_MAT_MAP_2STA

Step 6: Activate Data Model

Customer - Vendor Integration (CVI)

Genil Model

Process Model:

Create Master Data

Change/Process Master Data

Mark for deletion of Master Data

Block & Unblock of Master Data


Mass Change

Activate Type Linkage

1. Custom Process Model

2. Standard Process Model

3. Enhancement of Standard Process Model

UI Model:

Floorplan Manager (FPM)

FPM is a Webdynpro ABAP Application which provides a certain framework for developing a new Webdynpro ABAP applic

a. Guide0G

b. ObjecCustom Object

c. OvervBP/MM/Custom Object/0G

How many different ways we can deliver the UI application?

1. Customized Configuration

2. Configured the Standard application

3. Enhance the Standard application

1. Customized Configuration - (OIF )

Custom Data Model - ZT

Business Activity - ZTB1 and Change Request Type- ZTB1A

UI Process for Custom -

UIBB - User Interface Building Block


Role Tcode - PFCG

2. Configured the Standard UI application

3. Enhance the Standard UI application

UI Field Propertities:

Field Property Activities:

1. To maCL_MDG_BS_MAT_FEEDER_FORM_MAT

2. To maCL_MDG_BS_MAT_FEEDER_FORM_MAT

3. To mak
CL_MDG_BS_MAT_FEEDER_FORM_MAT

4. To maCL_MDG_BS_MAT_FEEDER_FORM_MAT

5. To maCL_USMD_CR_GUIBB_GENERAL_DATA

6. To maCL_MDG_BS_MAT_FEEDER_FORM_MAT

7. Deriv CL_USMD_CR_GUIBB_GENERAL_DATA

Adaptation:

Workflow:

Create Master Data

Change Master Data

Mark for Deletion of Master Data

Block/Unblock Master Data

MDG RolTx. PFCG

Validation & Derivation:

1. MDG BRF Plus

2. MDG ABAP BADI


a. Service BADI

Email Notification

Rule Context Preparation

Parallel Processing

Dynamic Agent Slection

Enhancement Implementation

BADI Implementation

Class

Methods

Logic

Rule Context Preparation

1. To flow the UI field value (Which user enter in CR) to BRF table and Validate it.

2. If Match, then follow the instruction

Parallel Processing

1. Rule Based Workflow

2. ABAP BADI

Email Notification

1. Rule Basis: Link MDG System with Mail Exchange Server

2. ABAP BADI

1. To ge CR Status

2. Body of the Email


3. SubjecChange Request 1234 has been completed.

4. Whom to Send

Hi,

Your change request for creating a material has been completed.

Change Request 1234 has status: Final Check Approved.

Warm Regards,

MDG Team.

Dynamic Agent Selection

1. Rule Based Workflow

2. ABAP BADI

b. Rule BADI Name - USMD_RULE_SERVICE

Single Entity Validation

Cross Entity Derivation

MDG APIs:

Search & Duplicate:

Search is happening stagging and active area both.

Fuzzylogy Mehodology

1. DataBase Search

2. Key Search

3. Enterprise Search

4. HANA Based Search


DataBase Search:

Enterprise Search: (Embedded Search)

Step 1: Creating Connection between MDG and

Tcode: SPRO

RFC of TREX: Basis using Tx. SM59

Execute Program : ESH_ADM_SET_TREX_DESTINATION

Step 2: Assign the role SAP_ESH_LOCAL_ADMIN

Step 3: Create Connector

Tx. ESH_COCKPIT

Active - Successful

Error - Not Successful

Step 4: Perform Schedule Indexing

Step 5: If I have any custom field, then…

Append the structure "ESO_S_MARA_MAW1" with custom field.

Step 6: SMT mapping & Append the MARA.

Step 7: Update Material Node

Step 8: Repeate Schedule Indexing

Step 9: Create Search Object Connector Templ

Step 10: Assign Search object connector templa

HANA Based Search:

Step 1: Create Roles for Schema in SAP HANA studio

Step 2: Assign the roles created above to your user ID

Step 3: Create a Package in HANA studio


Step 4: Create Database connection

Tx. DBCO
Execute Program : ESH_ADM_SET_TREX_DESTINATION
Step 5: Create Search View

Step 6: Allocation of Search Help based on Search Application

Duplicate Check

Understanding on S4/HANA with MDG

1. Data Replication Process

a. Change Pointer (ALE-Idoc)


b. DRF (Data Replication Framework) (ALE-Idoc)/SOA services

Data Replication:
Client - 800 (Source)
Step1: Souce System - client 800 (SEND)

Step2: Assign those Logical systems with respective client


Target system - client 810 (RECV)
step3: Physical connections in between those 2 systems

Tx. SM59

step4: Create Idoc Type using Tcode - WE30

Step5: Message Type - MATMAS

step6: CIdoc type - MATMAS05


tcode - WE82
Segment
step7: WE81 - create the message type
Attriubutes
step8: Create Distribution Model - BD64

step9: Create PORT using Tcode - We21

step10: Execute using Tx. BD10.

Step11: Check the Idoc data uding Tx. WE02/WE05


step12: Define Replication Model

step13: define outbound implementation


CL_MDG_MAT_IDOC_DRF
step14: **

https://wiki.scn.sap.com/wiki/display/ABAP/IDoc+Statuses

Client - 810 (Destination)

Step1: Goto Distribution Model - BD64

Step 2: Create Port using Tx. WE21

Step 3: Generate Partner Profile Tx. WE20

Change Pointer: (Client - 800)

Step 1: Tx. BD50


Tx. BD87 - Reprocess the failed Idoc
Activate the Change Pointer for Message Type
Tx. WE02/WE05 - Display Idocs
Step 2: Tx. BD61
Tx. WE19 - Reprocess the success Idoc
Global Change Activation for Change Pointer

Step 3: Tx. BD21

Set the Program as Background Job i.e, RBDMIDOC

Multi-Record Processing

Mass Maintenance

DIF (Data Import Framework):

MDM - Import Manager (XML)

MDG - DIF (XML)


Application Server
Material Master Data, Classification, Customer Master Data, Vendor Master Data, Finance Data
Presentation Server
Pre-requisite for Data Transfer:

1. Export Master Data information from source system into XML/Excel file format. The XML/Excel file will be on Application

2. Copy the XML/Excel file from Application server of source system to Application server of target system.

3. Import Master Data to the target system through Data Import Framework.

Step 1: 1
Step 2: 3
Step 3: 2

Tx. AL11 use to provide the physical path name

Note: 1. Under which directory we need to store the XML file. 2. Need to define the path name.

Step 4: Using Tx. CG3Z to upload a file from the local file system to the application server.

Message Types - MATMAS (Material Basic Information)

Classification - CLFMAS

Execution through Tx. NWBC

Key Mapping & Value Mapping

https://help.sap.com/viewer/67aa93f9655e4bc88e9541b48b3dcc87/7.31.22/en-US/43d4d0e3df340d87e10000000a1553

https://blogs.sap.com/2018/03/23/how-to-read-write-the-mdg-key-mapping-informations-programmatically-aka-ukms/

https://blogs.sap.com/2018/07/17/key-mapping-in-master-data-management/

MDG Consolidation

MDG EAM Model (Enterprise Asset Management)

SAP FIORI

Case Study:

1. SLA Identification
2. Copy Template
Customer Basic Info, ERP Customer details - Sales Org, Company Code

Vendor Basic Info, ERP Supplier details - Purchase Org, Company Code

Material Basic Info, Class/Characteristcs, Plant etc.

Cost Centre, Profit Centre, Company, GL Account etc.

UI

Webdynpro

FPM - Floor Plan Manager

Architecture Overview
(RFC) MDG

1. Data Model
ALE/Idoc, Services
2. Process Model

3. UI Model
PI (Process Integration)
4. Workflow
PI (Process Integration)
5. Data Validation & Derivation
(XML) - (Idoc)
6. Search & Duplicate Check

7. Data Import & Replication

(MARA, LFA1, KNA1, BUT000)


Active Area

target

Deployment options

1. MDG as HUB

2. MDG on top of ECC (Co-deployment)

1. MDG as HUB

RFC MDG

1. Data Model
XML-Idoc (PI)
2. Process Model
ALE/Idoc
3. UI Model
XML-Idoc (PI)
4. Workflow

5. Data Validation & Derivation

6. Search & Duplicate Check

7. Data Import & Replication

Master Data (Material - MARA table)

Customer - KNA1 table

Vendor - LFA1 table

MDG 7.0

MDG 8.0

2. MDG on top of ECC (Co-deployment)

Source/MDG

MDG (7.0/8.0/9.0/9.1)
(MDG Business Function)
SAP ABAP (ECC)
MARA/LFA1/KNA1

Submit Staging Area

(Approve/Reject) Staging Area


(Approve/Reject) Staging Area

PP (Persistance Phase)

Active Area

REQ

(Submit)

VER1

(Approve/Reject)

APP

(Approve/Reject)

Final Approver

(Approve/Reject)

Active Area

Out of Box Configuration

1. Activate the Business Function Tcode: SFW5

2. Activation of Webdynpro Services Tcode: SICF

3. Activation of Authorization object of Master Data Tcode: SU21


Role Tcode: PFCG
4. Activation of BC (Business Configuration) set Tcode: SCPR20
5. Adjust profile parameter Tcode: RZ11
(Material Master Data Only)

2. Standard Data Model 3. Enhancement of Standard Data Model

Type 2 Type 3

Changeable w/o CR(MDG) Not Changeable via MDG


Generated Check/text table No generated table

Eg: CASNR (Domain Level)

Eg: CURR.

Display Run time tables: USMD_DATA_MODEL

1. Add Custom Attribute in the Data Model

2. Add Custom Entity types in the Data Model


Flex Mode

Database table (X)

Step 1: Add the custom field in Data Model


Adjust the Stagging Area

Step 2: Generate Data Model Specific Structure


Step 3: Structure Extensions

MDG_BS_MAT_S_<table_name>_UI

UI field Properties

SMT Mapping

From Stagging Area to PP Step 4: Activate Data Model

From PP to Active Area

Tx. genil_model_browser

Tx. genil_model_editor

Business Activity

Change Request Type


h provides a certain framework for developing a new Webdynpro ABAP application interface.

he UI application?

t Type- ZTB1A
b. Rule BADI (Tx. SE18 - USMD_RULE_SERVICE)

Single Entity Validation

Cross Entity Derivation

er in CR) to BRF table and Validate it.

xchange Server
has been completed.

k Approved.

ctive area both.

This search finds data in a database based on user specific seaBP/0G/Custom Data Model
It can also be used in application such as duplicate Check.
BP/0G/Custom Data Model

TREX - Search Engin for Netweaver Business Client MM/BP


Connector
All data Model
Basis

RFC Connection create in between MDG and TREX system (Basis)

TREX_DESTINATION

Security

(Page# 13 to 15)

(Page# 16 to 17)

(Page# 27 to 29)

A_MAW1" with custom field.

(Page# 10 to 12)

(Page# 20 to 25)

(Page# 18 to 19)

(Page# 18 to 19)

SAP HANA studio MDG


HANA
ve to your user ID
MDG - S/4 HANA 1909

TREX_DESTINATION

sed on Search Application

Till Now Latest Version for S/4 HANA 1909

doc)/SOA services

spective client

se 2 systems
/IDoc+Statuses

SOA services Basis configuration for MDG https://help.sap.com/doc/7ec42355c9dca20ce10000000a441


https://blogs.sap.com/2018/08/06/configuring-service-group

Outbound Impl for Supplier in SOA services


mer Master Data, Vendor Master Data, Finance Data

rce system into XML/Excel file format. The XML/Excel file will be on Application server.

server of source system to Application server of target system.

through Data Import Framework.

store the XML file. 2. Need to define the path name.

the local file system to the application server.

nformation)

4bc88e9541b48b3dcc87/7.31.22/en-US/43d4d0e3df340d87e10000000a1553f7.html

read-write-the-mdg-key-mapping-informations-programmatically-aka-ukms/

pping-in-master-data-management/
Sales Org Company Code

Purchase Org Company Code

Class/Characteristics Plant

Cost Center Profit Center

Tx. MM01

SAP MDG (Master Data Governance) SAP ABAP

1. Data Model

2. Process Model

3. UI Model

4. Workflow

5. Data Validation & Derivation

6. Search & Duplicate Check

7. Data Import & Replication

HANA database/oracle

S/4 HANA Support


(RFC) Target

ALE/Idoc, Services SAP ABAP

PI (Process Integration) Non SAP

PI (Process Integration) SAP MDM

(Idoc) - (XML)

RFC Target

ALE/Idoc SAP ABAP Data Pool

Idoc - XML (PI) SAP MDM

Idoc - XML (PI) Non-SAP


RFC Target

(Idoc) - (XML) PI SAP MDM

ALE/Idoc ECC
(Inactive Records)

(Active Records)

Staging Area

VER2 (Payment Verifier)

(Approve/Reject)

https://help.sap.com/viewer/p/SAP_MASTER_DATA_GOVERNANCE

https://help.sap.com/erp_mdg_addon70/helpdata/en/74/facb771972444eae2345e92ec829ee/frameset.htm

https://help.sap.com/viewer/e03fd31a7e094ca99e9296cf6ec80349/MDG90_SP05/en-US/60c8bc19b24f40d4a7a18c0e61
Tx: SU01
Type 4

Changeable via other entity type,


Generated Database table
Eg: VALUATION.
Formula: Type4 depends on Type 1

Material#: CRUD OIL Biscuit


MATERIAL ENTITY TYPE
Material Type

UoM

Industry Sector

CLASS: Petrol CLASSASGN ENTITY TYPE Orange Biscuit


VALUATION ENTITY TYPE
Characteristics:

Price Suger%

Density Water%

Color Price

DATA_MODEL

e Data Model
ecific Structure
2355c9dca20ce10000000a44176d/1610%20001/en-US/9baba5519178245de10000000a44176d.html
06/configuring-service-group-in-soamanager/
Supliers
/frameset.htm

8bc19b24f40d4a7a18c0e6109fbe5.html
BP Info

Company Code

Purchase Org
Create Process
Table - A

Employee Name Dept


Mr. A Computer Sc.
Mr. B Chemistry
Mr. C Phy.
SAP table

Field

Data element

domain

Bill Of Material field as Stadard field


1
2
3
4

(001) VER1 (11)


(Approve)

REQ

VER

APP
MDG

XML/Excel

Application Server

MDG

ZTEST

Material Type AEM (Sample Data)

Vendor# Company Code


1000 UK01
1000 IT01
1001 SG01
1001 IN01
1001 US01
Tx. MASS

Tx. NWBC
Supplier 1

Same

FR01
IT01
NL01

FR01
IT01
NL01

MDG Processes

Create
Change
Block/Unblock
Mark for deletion
Mass Change/Update

Change Request

REQ Submit

VER Approve

APP Approve

(Activation)

Active area

ECC (Custom Executable Program)


Material#

Industry Sector Retail (1)

Material Type AEM (Sample Material)

UoM EA (Each)

Material Group 001

Short Desc Material Create-1-AEM-EA-001

GUI

FPM (floor Plan Manager)

Webdynpro

Airline Process:

CARRID
CURR
URL
Short Description

Entity Type

MATERIAL
CLASS

VALUATION

Business Partner

BP ID/BP Group

Search Term

Name

House#/Address

City

Language

Pin

Tax details

Bank Details

ERP Supplier
Company Code

Purchase Org

MDG Data Model

ZTEST02
Material#

Material Type

Material Group

Industry Sector

UoM

Flex Mode field ZTEST01

Reuse Mode field ZTEST02

BUS2250

REQ Submit

VER Approve

APP Approve

(Activation)

/MDGMM/_S_MM_PP_MATERIAL

MDG_BS_MAT_S_MARA

MATERIAL Entity Type


ROUTINGTYPE Entity Type

BUSINESSUNIT Entity Type

Enhancement

BADI

Class

Method

Logic

Sport
Run
Run
Run
Create Master Data

Change Request

Change Request Type

Business Activity

UI (User Interface)

FPM (Floorplan Manager)

Webdynpro Component

UIBB - User Interface Building Block

FORM Based UIBB FPM_FORM_UIBB

Table Based UIBB FPM_LIST_UIBB

COMPOSIT UIBB FPM_COMPOSIT_UIBB

TABBED Based UIBB FPM_TABBED_UIBB


REQ (Submit)

(01)
VER2 (12)
(Approve)

(02)
APP (03)
(Approve)

Final Approver (90)


(Approve)

Submit Staging table

Approve Staging table

Approve Staging table

(Activation)

Access Class Conector

Active Area
Source

XML/Excel

Application Server

Target

YTEST

SAPL (Sample data)

User Interface (UI)

FIORI (UI5)

FPM (Floorplan Manager) Tx. NWBC

Webdynpro Component

Mark for deletion Block


X X

X X
Supplier 2

Same

DE01
FR01

DE01
FR01

GUI
Entity/Attribute

Material# 1234

Material Type AEM

Material Group 1001

Industry Sector Retail


Classification

Characteristics

ERP Customer
Company Code

Sales Org

Satgging Table

ZTEST02
1234 3456

AEM AEM

1001 1001

Retail Retail

EA EA

R1 R2

Z1 Z2

stagging table (Inactive Area)

stagging table

stagging table

Access Class

PP (Primary Persistance)

Active area

(Attributes)
Material# 1234

Material Type Sample

UoM Each

Industry Sector Retail

Material Group 001

Also perform as an attribute R1

B1 B2

Ownership Mr. A Mr. B

Mr. A

Mr. B

Data Model

Genil Layer BUPA

UI Model

Workflow

Replication

ECC layer

Table - B

Position Sport Meter


2 Run 400
1 Run 400
3 RUN 400
(002)

Connector Template
Basic Info

Classification

Characteristics

ECC

Create Material Tx. MM01

Create Customer Tx. XD01

Create Supplier Tx. XK01

MDG (Feeder Class)


Create Process Material#

Industry Sector Retail (1)

Material Type AEM (Sample Material)

UoM EA (Each)

Material Group 001

Short Desc MDG Material Create-1-AEM-EA-001

SLA
Material

Material Type
Material Group
Industry Sector
UoM

Class ID
Class Type
Class Name

Char ID
Char Name

MM02 MM03 MM05 MM06

XD02 XD03 XD05 XD06

XK02 XK03 XK05 XK06

You might also like