MDG - Financials Config PDF

PUBLIC
2018-11-05
Master Data Governance for Financials

© 2018 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Services to be Activated for MDG Web Dynpro Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Configuring Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Activate Data Model 0G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Activate the Business Configuration Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Check or Create an Edition Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4 Check Business Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5 Check or Define a Change Request Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.6 Assign and Personalize the Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.7 Define the Validation Rules and Derivation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.8 Configure the Financials Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.9 Define Scope for Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.10 Create Hierarchy Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.11 Configure the Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.12 Define Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.13 Define Key Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.14 Define a UI Environment for Running SAP MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.15 Setting Up Initial Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.16 Display Remote Where-Used List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.17 Change Message Types for Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.18 Enable Detailed Analysis of Change Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.19 Configure Changeable IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.20 Set Up SAP HANA Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.21 Configure Business Context Viewer for MDG Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
4 Configuring the SOA Manager for MDG-F (NW 7.40 or higher). . . . . . . . . . . . . . . . . . . . . . . . . 33
5 Configuring the SOA Manager for MDG-F in MDG Client Systems (NW 7.32 or lower). . . . . . . . 48
6 Configuring ALE for Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . .54
7 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.1 Interlocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.2 Deleting Data Model 0F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8 Adapting Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8.1 Data Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

2 PUBLIC Content
Extending the MDG-F Data Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Transportation of Data Models to the Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Defining Data Models in the Configuration Workbench. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.2 UI Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Managing of UI Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Creating User Interfaces for Single Object Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
8.3 Data Quality and Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Search Providers for Master Data Governance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
8.4 Process Modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Defining a Governance Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Setting Up New Business Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuration of the Change Request Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Workflow Templates for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Scope for Hierarchy-Specific Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Enabling Detailed Analysis of Change Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
8.5 Governance Application Programming Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.6 Configuring Hierarchy Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Content PUBLIC 3
1 Master Data Governance for Financials
Master Data Governance for Financials enables you to monitor and control the creation, change, and deletion
of financial master data. This documentation provides the information you need to set up Master Data
Governance for Financials. It gives more information about the activities you need to execute in addition to
configuring Customizing settings.

4 PUBLIC Master Data Governance for Financials
2 Services to be Activated for MDG Web
Dynpro Applications
Use
For security reasons the services delivered for Web Dynpro applications initially are available in an inactive state
only. You have to activate the services you want to use.
Activities
To activate the services, proceed as described below:
1. On the Maintain Services screen (transaction SICF), make sure that the Hierarchy Type SERVICE is
selected, enter theService Name, and choose Execute.
2. Choose Service/Host Activate , to activate the service.
 Note
You have to perform the procedure for each single service you want to activate.
Once you have activated a service it cannot be reset to inactive.
The table below provides a list of the services used in the respective components of SAP MDG, Central
Governance.
Service Name MDG-C / MDG- MDG-M MDG-F MDG-CO

S / MDG-BP
APB_LAUNCHPAD Launchpad x x x x
BS_OVP_BP Web Dynpro Com x

ponent for BP OVP
BS_OVP_BP_MRP Business Partner x

Multi Objects
Processing Appli
cation
BS_OVP_CC Cleansing Case x

Application
CONFIGURE_AP Application Con x x x x

PLICATION figuration

Services to be Activated for MDG Web Dynpro Applications PUBLIC 5
S / MDG-BP
CONFIG Configure Compo x x x x

URE_COMPO nent
NENT
CUSTOM Component Con x x x x

IZE_COMPONENT figurator for the
Administrator
Layer
DRF_AD Adhoc Replication x x x x

HOC_REPLICA Model
TION
DRF_FIL Filter Criteria x x x

TER_BO_FPM
DRF_FIL Application Con x x x x

TER_POWL_AC figuration for Filter
POWL
DRF_FIL Filter Maintenance x x x x

TER_POWL_QAF_ POWL
AC
DRF_FPM_OIF_M Monitoring Web x x x x

ONITORING Dynpro Applica
tion
DRF_FPM_SEG_FL Application con x x x

TR_POPUP_AC figuration for the
popup
DRF_MAN Manual Replica x x x x

UAL_REPLICA tion
TION
FPM_CFG_HIER FPM Application x x x x

ARCHY_BROWSE Hierarchy Browser
R
IBO_WDA_INBOX Lean Workflow In x x x x

box Application
MDG_ANLY_CR_R Change Request x

EJ_REASON Rejection reason
MDG_BS_CON Master Data File x

VERTOR Convertor

6 PUBLIC Services to be Activated for MDG Web Dynpro Applications
S / MDG-BP
MDG_BS_DATA Reprocessing x x x x
LOAD_MONITOR
MDG_BS_DL_DIS Web Dynpro Appli x x x x

PLAY_LOG cation
MDG_BS_DL_DIS
PLAY_LOG
MDG_BS_DL_MO Data Load Monitor x x x x

NITOR_CONF
MDG_BS_FILE_IM Application for File x x x x

PORT Import
MDG_BS_GEN_M Generic Mass x

C_OVP Change Applica
tion
MDG_BS_MAT MDG-M: UI (entry x

point)
MDG_BS_MAT_M MDG-M: Mass x

C Change UI
MDG_BS_MAT_OV MDG-M: UI with x

P CBA
MDG_BS_MAT_SE MDG-M: UI, x

ARCH Search
MDG_BS_WD_AN Analyse ID Web x x x x

ALYSE_IDM Dynpro
MDG_BS_WD_ID_ Web Dynpro Appli x x x x

MATCH_SERVICE cation
MDG_BS_WD_ID_
MATCH_SERVICE
MDG_BS_WD_RSI Display Replica x x x x

_DISPLAY tion Status Dis
play
MDG_CRE Application for x

QUEST_GRAPH_A Flash
NALYSIS
MDG_CR_PROC Processing Time x

ESTIME_TREE

S / MDG-BP
MDG_DATA Export Master x

LOAD_EX Data and Mapping
PORT_WDA Information
MDG_DIS Cell Colors used x x x x

PLAY_COLORS for Highlighting
Changes
MDG_DQR_OVP OVP for MDG Data x x x x

Quality Remedia
tion
MDG_EXTR_FPM_ Extractor x
CMP
MDG_FILE_UP File Uploader x

LOAD_CMP
MDG_MONI Application Con x x x

TOR_CR_PROC figuration for Mon
ESTIME itoring CR Proc
essing Time
MDG_TRANS Transformer com x

FOR ponent for FPM
MER_FPM_CMP
MDGF_OVP_GEN MDG-F Applica x

tion
OIF_CFG_CENTER BCV Configuration x

Center (FPM)
POWL Personal Object x

Work List
USMD_APPLICA Web Dynpro Appli x x x

TION_LOG cation USMD_AP
PLICATION_LOG
USMD_BRFPLUS_ BRFplus Catalog x x x x

CATA Browser
LOG_BROWSER
USMD_CHANGE_ Change Docu x x x x

DOCUMENT ments

S / MDG-BP
USMD_CRE Create Change x x x x

QUEST_CREATE Request
USMD_CRE USMD_CRE x x x x
QUEST_PROCESS QUEST_PROCESS
USMD_CRE Workflow Informa x x x x

QUEST_PROTO tion
COL2
USMD_DISTRIB Web Dynpro Appli x x

UTE cation USMD_DIS
TRIBUTE / Com
ponent
FPM_OIF_COM
PONENT
USMD_EDITION Edition x
USMD_EDI Edition Compari x

TION_COMPARE son
USMD_EDI Display of Change x x x x

TION_CREQUEST Requests of an Ed
ition
USMD_EDI Edition History x

TION_HISTORY2
USMD_ENTITY Collective Proc x x x x

essing of an Entity
USMD_EN Search for Entities x x

TITY_SEARCH
USMD_EN Single Processing x x

TITY_VALUE2 of an Entity
USMD_FILE_DOW File Download x x x x

NLOAD
USMD_FILE_UP File Upload x x x x

LOAD
USMD_ISR_PROC ISR Processing of x x

ESS a Change Request

S / MDG-BP
USMD_MASS_CH Mass Change x x x x

ANGE
USMD_OVP_GEN MDG: Application x x x x

for Custom Ob
jects
USMD_RE Remote Where- x

MOTE_WHERE_U Used List
SED
USMD_RULE Rule Engine Con x x x x

figuration for Vali
dation and Deriva
tion
USMD_SEARCH MDG Generic x x x x

Search
USMD_UI_CON Manage UI Config- x x x x

FIGURATION uration
USMD_SSW_RUL Definition of Rules x x x x

E for Rule-Based
Workflow
USMD_WF_NAVI Workflow-Based x x x x
GATION Navigation
USMD_WHERE_U Where-Used List x x

SED
WDA_AUTH_OIF_ ACL Maintenance x x x x

ACL_FRAME
WDA_BS_ANLY_LI Simplified Report x x x x

ST ing: Simple List on
BI Query
WDA_BS_ANLY_LI List x x x x
ST_OVP
WDA_CFG_ENTRY Entry Sheet of x x x x

BCV Configuration
Center (POWL)
WDA_CFG_GAF_W Configuration Wiz x x x x

IZARD ard

S / MDG-BP
WDA_CFG_LAUNC Launchpad Main x x x x

HPAD tenance
WDA_CFG_OIF_U Web Dynpro Appli x x x x

GRP cation /BCV/
WDA_CFG_OIF_U
GRP / Component
FPM_OIF_COMPO
WDA_MDG_DT_C Configuration x x x x
ONF_WORK Workbench
BENCH
WDA_OIF_MAN Manage Interface x x x x

AGE Models
WDA_OIF_DIS Display OIF Model x x x x

PLAY
WDA_OIF_CREATE Create Outbound x x x x

Interface
WDA_OIF_WHERE Interface Models x x x x

USED Usage
WDA_QRM_BRF_ BRFplus Object x x x x

OBJMAN Manager
WDA_SMT Service Mapping x x x x

Tool Web Dynpro
Application
WDA_UIF_DASHB PCV Dashboard x x x x
WDA_UIF_MAIN PCV Main x x x x
WDA_UIF_SIDEPA BCV Side Panel for x x x x

NEL Standalone Mode
WDC_CFG_PAGE_ Page Builder x x x x

BUILDER
WDC_CFG_XC_ME Xcelsius Metadata x x x x

TA Extraction Stand
alone Application
WDC_UIF_CHIP BCV Chip x x x x

S / MDG-BP
WDC_UIF_COCK BCV Cockpit Start x x x x

PIT
WDR_CHIP_PAGE wdr_chip_page x x x x
WD_GLOBAL_SET Cross-Application x x x x
TING Settings for Web
Dynpro ABAP
WEBGUI SAP GUI for HTML x x x x

3 Configuring Master Data Governance for
Financials
Use
SAP Master Data Governance for Financials enables you to govern financial master data on a hub system and
to replicate the data to a number of client systems. The system centralizes and manages the master data by an
approval process. You can use this guide to help you to configure Master Data Governance for Financials (MDG-
F) 9.1.
 Note
MDG-specific Customizing is located under SAP Customizing Implementation Guide Cross-Application

Components Processes and Tools for Enterprise Applications Master Data Governance, Central
Governance .
You can also directly access all MDG-specific Customizing using transaction MDGIMG.
The Customizing settings are located under Master Data Governance, Central Governance Master Data
Governance for Financials as well as Master Data Governance, Central Governance General
Settings . For more information, see General Settings for Financials.
Prerequisites
After installing MDG-F, run the report RGZZGLUX before opening the UIs delivered with MDG-F. The report
performs several checks regarding the general ledger configuration of your MDG system.
Data Model
If data model 0F is available in your system and you want to activate the new data model 0G, delete data model
0F. Data model 0F is the predecessor of 0G and must not be used. To delete data model 0F, follow the steps
described in Deleting Data Model 0F [page 59].
Business Function
Before you activate the business functions, ensure that you have the administration authorization for MDG.
The required authorization objects are delivered with the authorization role SAP_MDG_ADMIN. In transaction
PFCG, we recommend creating a copy of this role and assigning the relevant authorization values. For the
authorization object USMD_DM, you need to assign the values for the authorization field USMD_MODEL (for
example MM, BP, or 0G) and the values for the authorization activity ACTVT (for example, 01: Create or
generate or 02: Change).
You have activated the following business functions in transaction SFW5:
● Master Data Governance, Generic Functions (MDG_FOUNDATION)

Configuring Master Data Governance for Financials PUBLIC 13
● Master Data Governance, Generic Functions 2 (MDG_FOUNDATION_2)
● Master Data Governance, Generic Functions 3 (MDG_FOUNDATION_3)
● Master Data Governance, Generic Functions 7.0 (MDG_FOUNDATION_4)
● Master Data Governance, Generic Functions 7.0 Feature Pack (MDG_FOUNDATION_5)
● Master Data Governance for Financials, Organizational Units (FIN_MDM_ORG)
● Master Data Governance for Financials 3 (MDG_FINANCIALS_3)
● Master Data Governance for Financials 7.0 (MDG_FINANCIALS_4)
● Master Data Governance for Financials 7.0 Feature Pack (MDG_FINANCIALS_5)
SAP Business Workflow
You have made your general settings for SAP Business Workflow in Customizing for SAP NetWeaver under
Application Server Business Management SAP Business Workflow . For more information, see SAP
Business Workflow.
Web Dynpro Applications
You have activated the services for Web Dynpro Applications. For a detailed list of the relevant services, see
Services to be Activated for Web Dynpro Applications [page 5].
Process
1. Activate Data Model 0G [page 15]

2. Activate the Business Configuration Set [page 15]
3. Check or Create an Edition Type [page 16]
4. Check Business Activities [page 16]
5. Check or Define a Change Request Type [page 17]
6. Assign and Personalize the Role [page 17]
7. Define the Validation Rules and Derivation Rules [page 19]
8. Configure the Financials Workflow [page 19]
9. Define Scope for Changes [page 20]
10. Create Hierarchy Versions [page 21]
11. Configure the Data Replication [page 21]
12. Define Value Mapping [page 22]
13. Define Key Mapping [page 23]
14. Define a UI Environment for Running SAP MDG [page 23]
15. Setting Up Initial Load [page 24]
16. Display Remote Where-Used List [page 26]

14 PUBLIC Configuring Master Data Governance for Financials
17. Change Message Types for Validation [page 26]
18. Enable Detailed Analysis of Change Requests [page 26]
The following configuration settings can be made for optional features:
● Configure Changeable IDs [page 27]

● Set Up HANA Search [page 28]
● Configure Business Context Viewer for MDG Financials [page 31]
Result
You have configured the system for Master Data Governance for Financials.
3.1 Activate Data Model 0G
Check whether you can use the data model 0G delivered by SAP for managing your Financials master data. For
more information about modifying the data model, see Enhancement of Master Data Governance Content.
You can activate the data model you want to use in Customizing under Master Data Governance, Central
Governance General Settings Data Modeling Edit Data Model .
Note that you should maintain usage type 3 entity types, such as the standard hierarchy name for each
controlling area, before using MDG-F.
3.2 Activate the Business Configuration Set
The Business Configuration Set CA-MDG-APP-FIN_EDITION_08 provides the default 0G_ALL edition type. We
strictly recommend using a single edition type containing all MDG-F entity types due to the cross-references
between entity types in data model 0G.
Activate the BC Set CA-MDG-APP-FIN_EDITION_08 in Customizing under Master Data Governance for
Financials Import Predefined Edition Types .
You can also activate the BC Set CA-MDG-APP-FIN_EDITION_08 using the following procedure:
1. On the SAP Easy Access screen, choose Tools Customizing Business Configuration Sets Activation
of BC Sets (transaction SCPR20).
2. Enter the BC Set CA-MDG-APP-FIN_EDITION_08, and choose the Activate BC Set button.
Leave the default settings as they are.
The Business Configuration Set CA-MDG-APP-FIN_CR_TYPES_08 contains predefined change request types
you can use for your master data governance process. You can also define your own change request types.

To activate the BC Set CA-MDG-APP-FIN_CR_TYPES_08, open the activity documentation in Customizing
under Master Data Governance for Financials Import Predefined Change Request Types , and click on the
link Change Request Types MDG-F 9.2 (CA-MDG-APP-FIN_CR_TYPES_08) in the Activities section.
You can also activate the BC Set CA-MDG-APP-FIN_CR_TYPES_08 using the following procedure:
1. On the SAP Easy Access screen, choose Tools Customizing Business Configuration Sets Activation
of BC Sets (transaction SCPR20).
2. Enter the BC Set CA-MDG-APP-FIN_CR_TYPES_08, and choose .

Leave the default settings as they are.
If you want to access the MDG-F homepage or the Business Context Viewer (BCV), activate the BC sets
MDGAF_BCV and CA-MDG-APP-FIN_BCV_PANEL_05.
If you want to use the SAP-Fiori-based request UIs, activate the BC set MDGF Change Request Types for SAP
Fiori (Financials) 7.0 FP (CA-MDG-APP-FIN_CR_ODATA_05).
This BC Set provides the predefined change request types for use in OData services and the SAP Fiori
applications Request Profit Center and Request Cost Center.
3.3 Check or Create an Edition Type
Check if the edition type 0G_ALL has been created for data model 0G after you have activated the business
functions. It should contain all entity types that are defined in the data model 0G. You can create your own
edition type in Customizing under Master Data Governance, Central Governance General Settings
Process Modeling Create Edition Type . We strictly recommend using a single edition type containing all
MDG-F entity types due to the cross-references between entity types in data model 0G.
3.4 Check Business Activities
Check if the table displayed in the "Business Activity: Definition" Overview view contains entries related to data
model 0G, for example:
Bus.Acty Description (medium text) Data Model Description (medium text)
0G Generic Business Activity for 0G Financials

DM 0G
You can display the table in Customizing under Master Data Governance, Central Governance General
Settings Process Modeling Business Activities Create Business Activity .

3.5 Check or Define a Change Request Type
If you have activated the BC set CA-MDG-APP-FIN_CR_TYPES_06, check the change request types. You can
create your own change request types in Customizing under Master Data Governance, Central Governance
General Settings Process Modeling Change Requests Create Change Request Type . You can enter
change request type keys and a short description to tag or classify your change requests. These keys can be
used later for change request analytics (process quality analysis). They can also be used to influence the
workflow-driven processes. For example, depending on the priority of a change request, you can mark it for
special processing. You can define priorities, reasons, or rejection reasons for change requests. For more
information, see Customizing for Master Data Governance, Central Governance under General Settings
Process Modeling Change Requests and work through the following activities:
● Edit Statuses of Change Requests

● Define Priorities for Change Requests
● Define Reasons for Change Requests
● Define Rejection Reasons for Change Requests
Check the predelivered print forms that are assigned to data model 0G in Customizing under UI Modeling
Assign Print Forms for Single Processing . You also have the option of defining print forms for change
requests. By default, the form USMD_EDITION_CREQUEST is used. This form is only relevant if your own print
forms or multiple print forms are required. For more information, see Customizing for Master Data Governance,
Central Governance under General Settings Process Modeling Change Requests Define Print Form for
Change Requests .
3.6 Assign and Personalize the Role
We continue using 3 work centers in financials – accounting, controlling, and consolidation. The following
authorization and menu roles are used:
Role Name Role Description Role Type
SAP_MDGF_ACC_MENU_04 Accounting Menu Menu
SAP_MDGF_ACC_DISP_04 Accounting Display Authorization
SAP_MDGF_ACC_REQ_04 Accounting Requester Authorization

SAP_MDGF_ACC_SPEC_04 Accounting Specialist Authorization
SAP_MDGF_ACC_STEW_04 Accounting Data Steward Authorization
SAP_MDGF_ACC_STEW_08 Accounting Data Steward Authorization
SAP_MDGF_CO_MENU_04 Consolidation Menu Menu
SAP_MDGF_CO_DISP_04 Consolidation Display Authorization
SAP_MDGF_CO_DISP_07 Consolidation Display Authorization
SAP_MDGF_CO_REQ_04 Consolidation Requester Authorization
SAP_MDGF_CO_SPEC_04 Consolidation Specialist Authorization
SAP_MDGF_CO_SPEC_07 Consolidation Specialist Authorization
SAP_MDGF_CO_STEW_04 Consolidation Data Steward Authorization
SAP_MDGF_CO_STEW_07 Consolidation Data Steward Authorization
SAP_MDGF_CTR_MENU_04 Controlling Menu Menu
SAP_MDGF_CTR_MENU_05 Controlling Menu Menu
SAP_MDGF_CTR_DISP_04 Controlling Display Authorization
SAP_MDGF_CTR_DISP_07 Controlling Display Authorization
SAP_MDGF_CTR_REQ_04 Controlling Requester Authorization
SAP_MDGF_CTR_SPEC_04 Controlling Specialist Authorization
SAP_MDGF_CTR_SPEC_07 Controlling Specialist Authorization
SAP_MDGF_CTR_STEW_04 Controlling Data Steward Authorization

SAP_MDGF_CTR_STEW_07 Controlling Data Steward Authorization
● On the SAP Easy Access screen, choose Tools Administration User Maintenance Role
Administration Roles (PFCG).
For example, using the role SAP_MDGF_ACC_MENU_04 on the Personalization tab page, edit the
personalization key SAP Master Data Governance (R_FMDM_MODEL). Specify 0G as the standard data
model. If applicable, assign the default values for the edition, the change request type, and the entity type.
● On the SAP Easy Access screen, choose Tools Administration User Maintenance Users (SU01).
Assign the required roles to your users, for example, SAP_MDGF_ACC_MENU_04, and at least 1
authorization role, for example, SAP_MDGF_ACC_SPEC_07.
3.7 Define the Validation Rules and Derivation Rules
Work through the Customizing activity under Data Quality and Search Validations and Enrichments
Define Validation and Derivation Rules .
3.8 Configure the Financials Workflow
Several workflow templates are available for MDG-F. For more information, see Workflow Templates for
Financials [page 98]. If the Business Configuration Set has been activated, the default SAP business workflow
template WS75700027 is assigned to change request type 0G_ALL and the workflow template WS75700040 is
assigned to all other change request types.
1. Activate type linkage

To activate the type linkage, run the following activity in Customizing for Master Data Governance, Central
Governance under General Settings Process Modeling Workflow Activate Type Linkage .
Ensure that object type BUS2250 has the following settings:
Event Receiver type Type linkage active Enable event queue
ACTIVATED ACTIVATED yes (blank)
ACTIVATED ACTIVATED_ACS yes (blank)
CREATED (blank) yes (blank)
ROLLED_BACK ROLLED_BACK yes (blank)

Event Receiver type Type linkage active Enable event queue
ROLLED_BACK ROLLED_BACK_ACS yes (blank)
The type linkage indicator must not be active for all other receiver types of object type BUS2250 and events
CREATED, ACTIVATED, and ROLLED_BACK. This receiver type is defined using the receiver type function
module USMD_WF_RECEIVER_TYPE.
 Note
To enter the receiver type function module or if you want to change the settings, mark the according
line in the table and choose Goto Details .
2. Configure workflow tasks

To ensure the general assignment of processors to the workflow, work through the Customizing activity
under General Settings Process Modeling Workflow Configure Workflow Tasks .
1. For each of the application components CA-MDG-AF and CA-MDG-APP-FIN, choose Assign Agents.
2. Tasks have the prefix TS* in their IDs. Set the tasks that are not Background Tasks to General Task.
Select the task and choose Attributes.... Then select General Task.
3. Assign agents
Depending on which workflow you selected, work through one of the following Customizing activities:
○ WS72100012, WS75700027, and WS75700040 under General Settings Process Modeling
Workflow Other MDG Workflows Assign Processor to Change Request Step Number (Simple
Workflow)
○ WS75700043 under Master Data Governance for Financials Workflow Assign Processor to
Change Request Step Number (Extended Workflow)
4. Set up rule-based workflow
Alternatively, you can use the general Workflow Template WS60800086 for the rule-based workflow.
3.9 Define Scope for Changes
You can determine the level of freedom with which users can make parallel changes to a hierarchy that belongs
to a particular hierarchy type. A change to a hierarchy can comprise adding a node, moving a node, removing a
node, changing the attributes of a node, or creating a hierarchy.
After a change to a hierarchy is saved to a change request, changes to interlocked nodes must be saved to the
same change request. The system determines which nodes are interlocked by referring to the Interlocking
[page 59] setting for the relevant hierarchy type.
You make these settings in Customizing under Master Data Governance, Central Governance General
Settings Process Modelling Hierarchies Define Scope for Changes .
Note that an Interlocking setting of Strict has a considerably greater impact on the system performance than a
setting of Loose, as the amount of data records the system locks and checks is higher with a setting of Strict.

 Note
You can only change the scope for changes to a hierarchy when no pending change requests exist for that
hierarchy. If you change the scope and then transport your changes, ensure no pending changes exist for
the affected hierarchy in the target system.
3.10 Create Hierarchy Versions
Work through the Customizing activity Master Data Governance, Central Governance General Settings
Process Modeling Hierarchies Create Hierarchy Versions .
3.11 Configure the Data Replication
Data replication in MDG can be defined, triggered, and controlled using the Data Replication Framework (DRF).
You can replicate the master data of Financials with SAP enterprise services, IDoc, or file downloads. For more
information, see File Download and Configuring Data Replication. Work through the Customizing activities for
Master Data Governance, Central Governance under General Settings Data Replication .
Replicate master data using SOA
Some additional settings are required for enterprise services. To configure the service interfaces and service
groups, see Customizing for Cross-Application Components under Processes and Tools for Enterprise
Applications Enterprise Services General Settings for Enterprise Services Manage and Test Enterprise
Services (transaction SOAMANAGER). For information on configuring the SOA Manager for NetWeaver 7.40 or
higher, see Configuring the SOA Manager for Master Data Governance for Financials (NW 7.40) [page 33].
Replicate master data using the IDoc
Alternatively, you can use Application Link Enabling (ALE) with IDoc messages. For detailed information about
how to configure the ALE for MDG-F, see Configuring ALE for Master Data Governance for Financials [page
54].
Schedule report for edition-based replication
You use the report USMD_EDITION_REPLICATE to replicate financial objects that do not support time-
dependency. The report is run once a day for all new or changed time-independent financial objects. The valid
financial objects are determined by the start date of the selected edition. You must define a variant for the
report in the MDG hub as follows:
1. Enter transaction SE38.

2. Enter the program USMD_EDITION_REPLICATE and choose the Variants button.
3. Enter a variant, for example, MDGF-0G and choose the Create button.
4. Select the data model 0G and enter 0 for the cut-off date. Choose the Attributes button.
5. Enter a description, such as Replication of 0G Editions.

6. Save your entries.
The next step is to configure and release the background job, as follows:
1. Enter transaction SM36 to define a background job.

2. Enter a job name, such as USMD_EDITION_REPLICATE. Enter the job class as C and do not enter an
execution target.
3. Choose the Start Condition button.
4. In the new window, choose Date/Time.
5. Enter the scheduled start as tomorrow’s date and the time as 00:01:00.
6. Select the Periodic job checkbox.
7. Choose the Period values button, choose Daily, and save.
9. Choose the Step button, and from the new window, choose ABAP program.
10. Enter the report USMD_EDITION_REPLICATE in the Name field.
11. Enter the variant you defined previously and save.
12. Go back to the Define Background Job screen, and check that one step has been successfully defined.
Finally, check the background job is released, as follows:
1. Enter transaction SM37.

2. Enter * for the job search, and enter your user name. Select the Released checkbox only. Check that the
Job start condition fields are empty.
3. Choose Execute. You should see your released job on the Job Overview screen.
Configuring Inbound Processing for Financial Master Data
You specify whether Internal Order master data can be changed locally in the financial controlling system after
it has been replicated from the MDG system.
You do this in Customizing under Master Data Governance, Central Governance Master Data Governance
for Financials Replication Inbound Processing for Financial Master Data Adapt the Master System Field for
Internal Order API .
3.12 Define Value Mapping
Value mapping links field values in different systems, usually based on global data types. If the Customizing
values are not harmonized in your system landscape, you must define the value mapping under Master Data
Governance, Central Governance General Settings Value Mapping . For more information, see Value
Mapping.

3.13 Define Key Mapping
If you are working with multiple connected systems and did not consolidate the financial object keys during the
initial load phase, key mapping may be required.
You can define the system-specific mappings for the key value for financials in Customizing for Master Data
Governance under Master Data Governance, Central Governance General Settings Key Mapping .
The mapping definitions of the key mappings can be conducted by any authorized user on the productive MDG
system using the business transaction from the portal or the corresponding back-end transaction.
3.14 Define a UI Environment for Running SAP MDG
You can manage the master data for financials in one of the following environments:
● SAP NetWeaver Business Client

If you want to use SAP NetWeaver Business Client for managing your master data in Financials, you can
create, define, or configure the role for the Business Client in the SAP ERP system. Perform the steps
described under Assign and personalize the role. You can now start the necessary steps without using the
SAP NetWeaver Portal. You can use the role for testing or when the portal is inactive.
Check the settings of the authorization objects within the roles and restrict them, if applicable.
● SAP NetWeaver Portal
The SAP NetWeaver portal content for MDG-F is derived directly from the menu roles. To create SAP
NetWeaver menu roles, you must log on to the portal and upload the content information from your
backend system menu roles.
 Note
You must install the Business Package for Common Parts in the SAP NetWeaver Portal before you can
upload the MDG roles.
To upload the portal content, perform the following:

1. Set up the SAP NetWeaver Portal for MDG.
2. In the Content Administration work center, choose Portal Content Managment Portal Content
and select a portal content folder to upload the portal content.
3. Right-click on the folder and choose New Role Role from Back End .
4. Select the system and client (or the connected system alias) you want to upload the role information
from. This should be your hub system.
5. From the list displayed, select the menu roles SAP_MDGF_ACC_MENU_04, SAP_MDGF_CTR_MENU_05,
and SAP_MDGF_CO_MENU_04, and begin the upload.
Once the MDG portal roles have been uploaded, you must assign them as follows:
1. Log on to the portal.
2. Choose Delegated User Administration.
3. Enter your user ID and choose Go.
4. Mark the line of your user and choose Modify.

5. Select the Assigned Roles tab.
6. Enter MDG as the search criteria.
7. Select the portal role you have previously uploaded.
8. Choose Add and save.
After assigning the user role, you need to log off and log on again to the portal. For more information on
uploading roles, see SAP Note 1685257 .
3.15 Setting Up Initial Load
Use
MDG-F supports the option to initially upload accounts, companies, cost centers, cost elements, and profit
centers from your MDG target systems into your MDG hub system.
The generic MDM extractor (MDMGX) extracts the master data in the MDG target system. The MDG data
import framework (DIF) uploads the master data in the MDG hub system. MDG-F provides content for both the
MDMGX and the DIF.
Process
● Setting up MDMGX in client systems

MDG-F uses transaction MDMGX for the extraction of master data from SAP MDG target systems. To set
up MDMGX, perform the following:
1. Apply the SAP Notes 1783851 , 1880169 , 2134044 , and 2547815 in the target systems.
2. Download the required MDMGX configuration text file from SAP Note 2707723 . The note includes a
detailed how-to document about MDMGX setup and execution.
3. Run transaction MDMGX in the client systems.
4. Choose Define Object Types. Make sure that the object types in the table below exist in your system.
The object types are predefined by SAP. If they do not exist, create the missing entries. Afterwards,
return to the main menu of the transaction.
Object Type Description
Account Chart of Account & G/L Account
Company Company
CostCenter Cost Center
CostElement Cost Element

Object Type Description
GroupAccount Group Account
ProfitCenter Profit Center
InternalOrder Internal Order
5. Choose Define Repositories and FTP Servers. Check if there is an entry with the attribute Log.
Repository Name defined as SAP_MDG_TEMPLATE. If it is available, you can use this entry as a template
for defining your own repositories. You can use the Copy button to create a new repository from the
template. Each master data object that you want to extract requires a specific repository.
6. If the template does not exist, you can create a new repository. It is mandatory that the repository
name starts with MDG_. Define the attributes of the new repository based on the master data object
that you want to extract. The table below shows the entries for the MDG-F objects. Define attributes
Clnt Code and Remote System Type according to your specific systems. Other attributes may use the
values as shown in the table.
Log. Repository Name Object Type Repository Name (Code)
(must always start with MDG_)
MDG_ACCOUNT Account MDG_Account
MDG_COMPANY Company MDG_Company
MDG_COSTCENTER CostElement MDG_CostElement
MDG_COSTELEMENT CostCenter MDG_CostCenter
MDG_GROUPACCOUNT GroupAccount MDG_GroupAccount
MDG_INTERNALORDER InternalOrder MDG_InternalOrder
MDG_PROFITCENTER ProfitCenter MDG_ProfitCenter
7. Choose Upload Ports and Check-Tables. To upload the configuration text file, do the following:
1. Define the object type as Account.
2. Select the configuration text file.
3. Select the Remove Header Line checkbox.
4. Execute the upload and go back to the main menu.
8. Define the function modules for the cost elements as follows:
1. Choose Define Function Module Parameters for Exceptional Cases and search without attributes.
2. Choose the Create button, and enter CostElement as the object type and MDM_ERP_CELEM_EXTR
as the function module. Do not provide an input parameter.
4. Repeat the procedure for the function module MDM_ERP_CELEM_DESCR_EXTR.
9. Define the function modules for internal orders as follows:
1. Choose Define Function Module Parameters for Exceptional Cases and search without attributes.

2. Choose the Create button, and enter InternalOrder as the object type and MDM_ERP_IORDER as
the function module. Do not provide an input parameter.
10. Adapt the predefined content of the configuration text file based on the master data to be extracted.
Refer to the how-to guide of SAP Note 2151430 for details.
● Setting up DIF in MDG systems

As a minimum, the DIF requires the following types of file directories on the application server:
○ One directory for each object type to store the files to be imported.
○ One directory for all object types to store the archived files that have been imported.
Perform the following:
1. Create the physical directories on the application server and map them to logical directories using
transaction FILE.
2. Run transaction MDGIMG. Configure the directories in the Customizing activity under Master Data
Governance, Central Governance General Settings Data Transfer Define File Source and Archive
Directories for Data Transfer .
3.16 Display Remote Where-Used List
You can use this BAdI to display a list of entities changed by MDG-F in a remote system. You can display the
where-used list in remote systems for entities in MDG. You can access this BAdI under Master Data
Governance, Central Governance General Settings Data Quality and Search Business Add-Ins BAdI:
Remote Where-Used List .
3.17 Change Message Types for Validation
For each message, you can define the respective message type for the different check levels (for example,
change request, edition, or single maintenance). If you do not redefine the message types for a message, the
set standard message type applies for all 3 check levels. For more information, see Customizing for Master
Data Governance, Central Governance under Master Data Governance for Financials Control of Validation
Messages Change Message Type for Validations .
3.18 Enable Detailed Analysis of Change Requests
You can apply system settings that allow you to monitor how effectively your organization processes change
requests. You can analyze the statuses and processing times of change requests in your organization, and the
types of change requests involving you. For more information, see Enabling Detailed Analysis of Change
Requests [page 108].

3.19 Configure Changeable IDs
To enable this feature, set the application parameter MDGF_ENABLE_KEY_SWITCH to X in the Web Dynpro
application configuration. SAP delivers these for each entity with SU type 1 that has its own user interface. It is
possible to enable the feature for a single entity only.
1. Create a custom Web Dynpro application configuration as a copy of a predefined SAP configuration.
1. Start the Web Dynpro application CONFIGURE_APPLICATION.
2. Define an existing Web Dynpro application configuration with component name MDGF_OVP_GEN and its
configuration ID (for example, MDGF_0G_OVP_CCTR).
3. Choose Copy. Follow the instructions of the copy window to create your custom Web Dynpro
application configuration.
4. Once the copy is finished, choose the Continue in Change Mode button to apply the application
parameter value.
5. Locate parameter MDGF_ENABLE_KEY_SWITCH in the list of application parameters and set its value to
X.
2. Create a custom MDG Communicator configuration.
1. Start the Web Dynpro application CONFIGURE_COMPONENT.
2. Define an existing MDG Communicator configuration with component name
MDG_BS_GOV_COMMUNICATOR and its configuration ID (for example, MDGF_0G_OVP_CCTR).
3. Choose the Copy button. Follow the instructions of the copy window to create your custom Web
Dynpro component configuration for the MDG Communicator.
3. Adjust MDG Customizing.
MDG consists of several customizing tables that are used for the navigation to user interfaces. You need to
add the newly created Web Dynpro application to the tables to ensure that the new user interface that
supports changeable IDs is used instead of the SAP pre-defined user interface. Carry out the steps
described below. The steps take the Cost Center as an example.
1. Start transaction MDGIMG.
2. Open General Settings Process Modeling Business Activities .
3. Open the Customizing activity Link Log. Actions with UI Application and Bus. Activity: Custom
Definition .
1. Take a look at the SAP default configuration for cost centers in the Customizing activity Link Log.
Actions with UI Application and Bus. Act.: Standard Definition, which should contain records similar
to the ones shown in the table below:
BO Type Log. Action Current UI Current UI Target UI Target UI Business Ac

App. Config. App. Config. tivity
158 CREATE * * MDGF_OVP_G MDGF_0G_OV CCT1

EN P_CCTR
158 DISPLAY * * MDGF_OVP_G MDGF_0G_OV CCT3

EN P_CCTR

2. Copy or note the lines that relate to the creation and display of cost centers using the SAP UI
configuration MDGF_0G_OVP_CCTR.
3. Navigate to the custom definition and add new entries using the previously copied or noted values
as a template. Define your new target UI configuration.
BO Type Log. Action Current UI Current UI Target UI Target UI Business Ac

App. Config. App. Config. tivity
158 CREATE * * MDGF_OVP_G ZMDGF_0G_O CCT1

EN VP_CCTR
158 DISPLAY * * MDGF_OVP_G ZMDGF_0G_O CCT3

EN VP_CCTR
4. Save your changes.
4. Open the Customizing activity Link Logical Actions with Business Activity: Custom Definition.
1. Take a look at the SAP default configuration for cost centers in the Customizing activity Link
Logical Actions with Business Activity: Standard Definition, which should contain records similar to
the ones shown in the table below:
UI Application UI Configuration Log. Action Business Activity
MDGF_OVP_GEN MDGF_0G_OVP_CCTR CREATE CCT1
MDGF_OVP_GEN MDGF_0G_OVP_CCTR DISPLAY CCT3
2. Copy or note the lines that relate to the creation and display of cost centers using the SAP UI
configuration MDGF_0G_OVP_CCTR.
3. Navigate to the custom definition and add new entries using the previously copied values as a
template:
UI Application UI Configuration Log. Action Business Activity
MDGF_OVP_GEN ZMDGF_0G_OVP_CCTR CREATE CCT1
MDGF_OVP_GEN ZMDGF_0G_OVP_CCTR DISPLAY CCT3
4. Save your changes.
3.20 Set Up SAP HANA Search

Use
You want to enable SAP HANA search for financial objects because of high volume data or advanced features
provided by the SAP HANA database such as freestyle and fuzzy search. This document explains the

configuration steps that must be applied to the MDG system to enable this feature. It describes how to connect
the search application with the SAP HANA search UIBB and generate the HANA search view.
Prerequisites
Before starting the implementation, check that SAP HANA is connected to the MDG system. If not, refer to
Configuring SAP HANA-Based Search for MDG.
Process
1. Generate SAP HANA search view in the SAP HANA database

1. Open transaction MDGIMG under Master Data Governance, Central Governance General Settings
Data Quality and Search Search and Duplicate Check Create Search View . Find the relevant
search views from the table SAP HANA Search Supported MDG-F Objects below. For the MDG-F
predelivered view for data model 0G, the name starts with MDGF_0G_*. Choose the Edit button to open
each search view.
2. Enter the name of the SAP HANA package you received from your system administrator. Save your
entries.
3. Choose Next until the last step and choose Generate. You should get a message saying the view
generation is successful.
2. Enable SAP HANA Search UIBB
This is done by adding an SAP-delivered search UIBB to the communicator configuration as follows:
1. Start the customizing configurator for the communicator configuration.
1. Start the Web Dynpro application CUSTOMIZE_COMPONENT.
2. Enter the component name MDG_BS_GOV_COMMUNICATOR. You can find the configuration ID in the
table below.
SAP HANA Search Supported MDG-F Objects
Object Name Communicator Configu HANA Search UIBB HANA Search View
ration ID
G/L Account MDGF_0G_OVP_FI_ACCO MDGF_0G_FI_ACCOUNT_ MDGF_0G_ACCOUNT

UNT DQUERY_HA
MDGF_0G_ACCCCDET
MDGF_0G_FI_ACCCCDET
_DQUERY_HA
Financial Reporting MDGF_0G_OVP_FI_REPO MDGF_0G_FI_REPORT_D MDGF_0G_FRS

Structure RT QUERY_HA
MDGF_0G_FRSI
MDGF_0G_FI_REP_ITEM
_DQUERY_HA

ration ID
Company MDGF_0G_OVP_COMPANY MDGF_0G_COMPANY_DQU MDGF_0G_COMP

ERY_HA
Cost Center MDGF_0G_OVP_CCTR MDGF_0G_CCTR_DQUERY MDGF_0G_CCTR

_HA
Cost Center Group MDGF_0G_OVP_CCTRG MDGF_0G_CCTRG_DQUER MDGF_0G_CCTRG

Y_HA
Cost Center Group Hier MDGF_0G_OVP_CCTRH MDGF_0G_CCTRH_DQUER MDGF_0G_CCTRH

archy Y_HA
Cost Element MDGF_0G_OVP_CELEM MDGF_0G_CELEM_DQUER MDGF_0G_CELEM

Y_HA
Cost Element Group MDGF_0G_OVP_CELEMG MDGF_0G_CELEMG_DQUE MDGF_0G_CELEMG

RY_HA
Cost Element Group Hier MDGF_0G_OVP_CELEMH MDGF_0G_CELEMH_DQUE MDGF_0G_CELEMH

archy RY_HA
Profit Center MDGF_0G_OVP_PCTR MDGF_0G_PCTR_DQUERY MDGF_0G_PCTR

_HA
Profit Center Group MDGF_0G_OVP_PCTRG MDGF_0G_PCTRG_DQUER MDGF_0G_PCTRG

Y_HA
Profit Center Group Hier MDGF_0G_OVP_PCTRH MDGF_0G_PCTRH_DQUER MDGF_0G_PCTRH

archy Y_HA
Internal Order MDGF_0G_OVP_IORDER MDGF_0G_IORDER_DQUE MDGF_0G_IORDER

RY_HA
Item MDGF_0G_OVP_CO_ACCO MDGF_0G_CO_ACCOUNT_ MDGF_0G_FSI

UNT DQUERY_HA
Item Hierarchy MDGF_0G_OVP_CO_REPO MDGF_0G_CO_REPORT_D MDGF_0G_FSI

RT QUERY_HA
MDGF_0G_FSIH
MDGF_0G_CO_REP_ITEM
_DQUERY_HA
Consolidation Character MDGF_0G_OVP_CONSCHA MDGF_0G_CONSCHAR_DQ MDGF_0G_CONSCHAR

istic R UERY_HA
Consolidation Unit MDGF_0G_OVP_CONSUNI MDGF_0G_CONSUNIT_DQ MDGF_0G_CONSUNIT

T UERY_HA

ration ID
Consolidation Group MDGF_0G_OVP_CONSGRP MDGF_0G_CONSGRP_DQU MDGF_0G_CONSGRP

ERY_HA
Consolidation Structure MDGF_0G_OVP_CONSGRP MDGF_0G_CONSGRPH_DQ MDGF_0G_CONSGRPH

H UERY_HA
Breakdown Category MDGF_0G_OVP_BDC MDGF_0G_BDC_DQUERY_ MDGF_0G_BDC

HA
Breakdown Category Set MDGF_0G_OVP_BDCSET MDGF_0G_BDCSET_DQUE MDGF_0G_BDCSET

RY_HA
Cause for Submission MDGF_0G_OVP_SUBMPAC MDGF_0G_SUBMPACK_DQ MDGF_0G_SUBMPACK

K UERY_HA
Transaction Type MDGF_0G_OVP_TRANSTY MDGF_0G_TRANSTYPE_D MDGF_0G_TRANSTYPE

PE QUERY_HA
3. Choose New, enter a description, and choose OK. Select a transport request if your customizing
needs to be transported to other systems.
2. Mark the Settings node, and choose New Search UIBBs . Enter all parameters for the object in
the table, for example, the following are the cost center parameters:
○ Search Mode: HA
○ Incl. Search Help: MDGF_0G_CCTR
○ Component: FPM_SEARCH_UIBB
○ Config ID: MDGF_0G_CCTR_DQUERY_HA
Result
You have completed all the necessary steps to enable HANA search.
3.21 Configure Business Context Viewer for MDG Financials
Use
You can use this function to view context-related information for your financials master data in a side panel. You
must activate the Business Context Viewer (BCV) to access the side panels for all MDG-F Web Dynpro
applications.

Prerequisites
1. To enable BCV, you must activate the following business functions:

○ FND, Business Context Viewer Main Application (/BCV/MAIN)
○ FND, Business Context Viewer Main Application 2 (/BCV/MAIN_1)
○ FND, Business Context Viewer NWBC Side Panel (/BCV/NWBC_SIDEPANEL)
2. Activate the BC Set BCV Content for MDG Framework (MDGAF_BCV) in transaction SCPR20.
3. Activate the BC Set BCV Content for MDG-F (CA-MDG-APP-FIN_BCV_PANEL_08), which contains the
business content for MDG-F.
Process
To view this content, open the BCV side panel by choosing the Side Panel link in the upper right corner of your
MDG Financials single object maintenance user interface from your current change request. From the side
panel, select one of the following overviews:
Changes Overview
Select this BCV content in the dropdown list under Overview to display a list of changes raised by the current
MDG change request.
Display Hierarchy Changes
In addition to displaying changes per change request, you can also display just the hierarchy changes for the
change request. To do so, select the display option Hierarchy Changes for Request in the section under Query
Views Query View List .
 Note
Export Hierarchy Changes
You can export the hierarchy changes for a change request to Microsoft Excel by choosing the Export
button in the BCV Main Analytics View.
More Information
For more information about BCV, see Business Context Viewer (BCV)

4 Configuring the SOA Manager for MDG-F
(NW 7.40 or higher)
Use
This document describes the configuration steps required to enable the exchange of financial data. The
configuration uses point-to-point enterprise services communication without a process integration (PI)
system. The MDG hub is installed on NetWeaver 7.40. For more information about how to use the SOA Manager
to configure a Web service-based communication, see Configuring a Consumer Proxy.
 Note
If your MDG Client system has an SAP NetWeaver version below 7.40, please refer to the configuration
steps described in Configuring the SOA Manager for MDG-F in MDG Client Systems (NW 7.32 or lower)
[page 48]
Prerequisites
The following prerequisites must be performed in both the MDG hub and target systems.
Configuration of the Web Service Runtime
Set up the technical configuration of the web service runtime using SAP Note 1043195 .
Authorizations
Assign the administrative role SAP_BC_WEBSERVICE_ADMIN_TEC for the SOA Manager.
Authorize the following transactions:
● SU01
● SUIM
● PFCG
Service Users in ABAP Stack
To create a service user, carry out the following steps:
1. Choose transaction SU01, choose Create, and enter a user.

2. On the Roles tab, assign the role SAP_BC_WEBSERVICE_ADMIN_TEC.
Business Functions
Check if the business function FND_SOA_REUSE_1 is active.

Configuring the SOA Manager for MDG-F (NW 7.40 or higher) PUBLIC 33
 Note
Activate the business function from transaction SFW5. By activating the business function, you can use the
following cross-application tool improvements that facilitate the use of services:
● SOA mapping tool

● Error handling
● Point-to-point enablement for asynchronous enterprise services
For replication to an ERP system, activate the business function FIN_MDM_SOA_ORG in the MDG target system.
For replication to an ERP system with SEM-BCS installed, activate the business function FIN_MDM_SOA_CU in
the MDG target system.
Maintain Transport Request for Inbound Service
1. Assign a transport request for an inbound service by running the Customizing activity in the MDG target
system under Cross-Application Components Processes and Tools for Enterprise Applications Master
Data Governance, Central Governance Master Data Governance for Financials Replication Enterprise
Services Inbound Services for Financials Master Data Manage Transport Requests . If the Customizing
activity is not available in the client, open transaction SM34 and enter the view cluster VC_TRN_REG_RQST.
Choose Maintain.
2. Enter the application FINMDM_DATA_REPLICATION and choose Continue.
3. Enter the groups FINMDM_DATA_COMPANY_RPLCTN and FINMDM_DATA_REPLICATION_GRP and mark
both as automatic.
4. Afterwards, add a Customizing transport to each group. If necessary, create a transport with transaction
SE09 beforehand.
In an ERP system with SEM-BCS installed, perform the same steps, but use the application SEM_BW_INBOUND
and the groups SEM_BW_INBOUND_ITEM and SEM_BW_INBOUND_REPUNIT_EHP6.
Support for Point-to-Point Communication
To activate the support for point-to-point communication, run the Customizing activity under Cross-
Application Components Processes and Tools for Enterprise Applications Enterprise Services Point-to-
Point Enablement for Asynchronous Enterprise Services Activate Support for Point2Point Communication .
Connection to System Landscape Directory
Check whether the hub and target systems are connected to the system landscape directory (SLD) or the BAdI
MDG_IDM_GET_LCL_SYSTEM is implemented to determine the local system ID. For more information, see
Customizing for Master Data Governance, Central Governance under General Settings Data Replication
Define Custom Settings for Data Replication Define Technical Settings BAdI: Determination of Local System
Name .
Error and Conflict Handler
To activate the error and conflict handler, run the Customizing activity under Cross-Application Components
General Application Functions Error and Conflict Handler Activate Error and Conflict Handler .

34 PUBLIC Configuring the SOA Manager for MDG-F (NW 7.40 or higher)
Procedure
The following steps are required to configure the SOA Manager for MDG-F (transaction SOAMANAGER) and must
be performed in both the MDG hub and MDG target systems.
Configure a Profile For Point-To-Point Communication
1. On the Technical Administration tab, choose Profiles.

2. Choose Create Profiles, enter the name MDG and description and choose Next.
 Note
The profile names should be identical in the SOA manager settings for both MDG hub and target
systems.
3. Mark User ID/Password and verify that in section Identifiable Business Context, the field IBC Determination
has the value No IBC Determination. Choose Next.
4. If necessary, enter the proxy settings and choose Finish to save the settings and activate the profile.
Retrieve Business Application ID
1. On the Technical Administration tab, choose SAP Client Settings and then choose Edit.
2. Enter a business system and a business system ID in the form: XYZ_001, where XYZ is the system ID and
001 is the client.
3. To receive the business application ID from the system landscape directory (SLD), choose Get from SLD.
The business application ID should now be displayed in the corresponding field.
Configure a Provider System for the Business Scenario Configuration
1. On the Technical Administration tab, choose Provider Systems, then choose Create. Enter the system ID of
the client system as the name, for example XYZ_001, select the profile name defined in step 1, and choose
Next.
2. Enter the SLD identifier in the following form:
<Client>.SystemName.<ABC>.SystemNumber.<InstallationNumber>.SystemHome.<Host>, for
example, 416.SystemName.QV6.SystemNumber.0020270862.SystemHome.uxdbqv6.
 Note
The system number can be found under System Status SAP System Data Installation
Number .
Similarly, the system home can be found under System Status Database Data Host .
3. Enter the access URL for WSIL and logon information under WSIL Services.
 Note
To identify the host name and port for the access URL, call transaction SMICM and choose Goto
Services . Use the HTTPS host name and port displayed in the list. We recommend that you use the
message server host.
4. Enter the user for WSDL and a password for the WSDL documents.

5. Enter the service user that you have created in the backend system.
6. Maintain the business application ID. The business application ID can be found in the counterpart system
in the transaction SOAMANAGER under Technical Administration SAP Client Settings
1. Choose Create to maintain a business application ID in the MDG hub system.
2. Enter an application name and description, for example sap.com/BusinessApplicationABAP.
3. Enter the business application ID.
4. Choose Finish to save and activate the system connection.
As a result, the Identifiable Business Context (IBC) reference for the counterpart system is automatically
generated. To verify this, perform the following:
1. From the Service Administration tab, choose the link Identifiable Business Context Reference.
2. Choose the Search button. The IBC reference for the counterpart system should display in the list in the
form of XYZ_001, where XYZ_001 is the system ID and client of the counterpart system.
Edit Logon Data for Business Scenario
 Note
The backend user should exist in both systems.
1. On the Service Administration tab, choose Logon Data Management.

2. On the Maintenance tab, choose Create, enter your data, and choose Next.
3. Select User/Password or X.509 as the authentication method.
4. Enter the user name that you created earlier in the backend system and choose Finish.
Assign Logon Data to Provider IBC Reference

2. Under the Assignments tab, choose Create.
3. Use the input help to search for Provider IBC Reference. Select the IBC reference of the counterpart system
from the search result list and choose Next.
4. Select the user name you entered in the previous step as logon data from the dropdown list and choose
Finish.
Create Integration Scenario for Point-To-Point Communication
Service definitions and service groups that you configure to run SOA communications with SEM-BCS are
shown in separate tables.
1. Create an integration scenario configuration in the MDG hub system.

1. On the Service Administration tab, choose Local Integration Scenario Configuration.
2. Choose Create, provide a name and a description for the integration scenario, and choose Next.
2. Select service definitions and assign a profile.
1. Choose Add to search for the service definition.
2. In the dialog box, search for the service definition CHARTOFACCOUNTSREPLICATIONCONF, select it in
the result list and choose Add to Worklist.
3. Similarly, search for all required service definitions and add them to the worklist:

Service Definition (Internal Name) Description
CHARTOFACCOUNTSREPLICATIONCONF Confirmation of Chart of Accounts Replication
FINANCIALREPORTINGSTRUCTUREREP Confirmation of Financial Reporting Structure Replication
GENERALLEDGERACCOUNTMASTERREPL Bulk Confirmation of General Ledger Account Master Rep

lication
COMPANYREPLICATIONBULKCONFIRMA Bulk Confirmation for Company Replication
COSTCENTREREPLICATIONBULKCONFI Bulk Confirmation for Cost Center Replication
PROFITCENTREREPLICATIONBULKCON Bulk Confirmation for Profit Center Replication
COSTCENTREGROUPHIERARCHYREPLIC Confirmation for Cost Center Group Hierarchy Replication
PROFITCENTREGROUPHIERARCHYREPL Confirmation for Profit Center Group Hierarchy Replica

tion
COSTELEMENTREPLICATIONBULKCONF Bulk confirmation for cost element replication
COSTELEMENTGROUPHIERARCHYREPL1 Confirmation for cost element group hierarchy replication
Service definitions for replication to a SEM-BCS system:
CHARTOFACCOUNTSREPLICATIONCONF Confirmation of Chart of Accounts Replication
FINANCIALREPORTINGSTRUCTUREREP Confirmation of Financial Reporting Structure Replication
FINANCIALCONSOLIDATIONELEMENTR Bulk confirmation for replication of Financial Consolida

tion Element
FINANCIALCONSOLIDATIONSTRUCTUR Confirmation for replication of Financial Consolidation

Structure
3. Assign profile to service definitions:

1. Select all service definitions from the list and choose Assign Profile.
2. Select the profile MDG, choose Assign Profile and choose Next.
4. Select service groups and assign the provider IBC reference:
1. Choose Add to search for the service group.
2. Enter the service group USMD_CHARTOFACCRPLCTNRQ_V1, select it in the result list and choose Add to
Worklist.
3. Repeat the procedure for all required service groups:

Service Group (Internal Name) Description
USMD_CHARTOFACCRPLCTNRQ_V1 Chart of Account Replication for Version 1
USMD_FINREPSTRUCTRPLCTNRQ Service Group for Outbound FinancialReportingStructur

eReplicationRequest
USMD_GENLEDACCMRPLCTNRQ Service Group for Outbound GeneralLedgerAccountMas

terReplicationBulkRequest
USMD_COMPANYRPLCTNBRQ Service Group for Outbound CompanyReplicationBulkRe

quest
USMD_COSTCTRRPLCTNBRQ Service Group for Outbound CostCentreReplicationBulk

Request
USMD_PROFITCTRRPLCTNBRQ Service Group for Outbound ProfitCentreReplicationBulk-

Request
USMD_COSTCTRGRPHIRPLCTNRQ Service Group for Outbound CostCentreGroupHierarch

yReplicationRequest
USMD_PRFTCTRGRPHIRPLCTNRQ Service Group for Outbound ProfitCentreGroupHierarch-

yReplicationRequest
USMD_COSTELMTRPLCTNBRQ Service Group for Outbound CostElementReplicationBulk

Request
USMD_COSTELMNTGRPHIRPLCTNRQ Service Group for CostCentreGroupHierarchyReplication

Request
Service groups for replication to an SEM-BCS system:
USMD_CHARTOFACCRPLCTNRQ_V1 Chart of Account Replication for Version 1
USMD_FINREPSTRUCTRPLCTNRQ Service Group for Outbound FinancialReportingStructur

eReplicationRequest
USMD_FINCNSELMNTRPLCTNBRQ Service Group for Outbound FinancialConsolidationEle

mentReplicationBulkReq
USMD_FINCNSSTRUCTRPLCTNRQ Service Group for Outbound FinancialConsolidationStruc

tureReplicationReq
5. Assign the provider IBC reference:

1. Select all service groups from the list and assign them to the provider IBC reference by choosing
Assign IBC Reference.
2. In the dialog box search for the IBC reference of the counterpart system, mark the entry in the search
results list and choose Assign to Service Group.

3. Choose Finish.
6. Do not activate the business scenario immediately, as you first need to define the integration scenario
configuration in the target system.
To create an integration scenario configuration in the MDG target system, carry out the following steps:
1. Create an integration scenario configuration in the MDG target system.

1. On the Service Administration tab, choose Local Integration Scenario Configuration.
2. Choose Create, provide a name and a description for the integration scenario and choose Next.
2. Select the service definitions and assign the provider IBC reference.
1. Choose Add to search for a service definition.
2. In the dialog box, search for the service definition CHARTOFACCOUNTSREPLICATIONREQ1, select it in
the result list and choose Add to Worklist.
3. Similarly, search for all service definitions and add them to the worklist:
CHARTOFACCOUNTSREPLICATIONREQ1 Replication request for chart of accounts – version 1
FINANCIALREPORTINGSTRUCTURERE1 Replication request for financial reporting structure
GENERALLEDGERACCOUNTMASTERREP1 Replication bulk request for general ledger account mas

ter data
COMPANYREPLICATIONBULKREQUEST_ Bulk replication request for company
COSTCENTREREPLICATIONBULKRQ Bulk replication request for cost center
PROFITCENTREREPLICATIONBULKREQ Bulk replication request for profit center
COSTCENTREGROUPHIERARCHYREPLRQ Replication request for cost center group hierarchy
PROFITCENTREGROUPHIERARCHYREP1 Replication request for profit center group hierarchy
COSTELEMENTREPLICATIONBULKREQU Bulk replication request for cost element
COSTELEMENTGROUPHRYREPLRQ Replication request for cost element group hierarchy
Service definitions for replication to an SEM-BCS system:
CHARTOFACCOUNTSREPLICATIONV1RQ Replication request for chart of accounts
FINREPORTINGSTRUCREPLICATIONRQ Replication request for financial reporting structure
FINANCIALCONSOLIDATIONELMNTBRQ Bulk replication request for Financial Consolidation Ele

ment
FINANCIALCONSOLIDATIONSTRUCTRQ Replication request for Financial Consolidation Structure

3. To assign a profile to the service definitions in the MDG target system, carry out the previous steps for the
MDG hub.
4. Select Service Groups and assign the provider IBC reference as follows:
2. Enter the service group FBS_CHTACCTSRPLCTNCO, select it in the result list, and choose Add to
Worklist.
3. Repeat the procedure for all required service groups.
FBS_CHTACCTSRPLCTNCO Confirmation of chart of accounts replication
FBS_FINRPTGSTRUCCO Confirmation about replication of financial reporting

structure
FBS_GLACCTMSTRRPLCTNRCO Bulk confirmation of general ledger account master repli

cation
FBS_COMPANYRPLCTNBCO Bulk confirmation for company replication
KBAS_CO_COST_CENTRE_RPLCN Bulk confirmation for cost center replication
KE1_PRCTRRPLCTN_SG Bulk confirmation for profit center replication
KBAS_CO_CCGROUP_RPLCN Confirmation for cost center group hierarchy replication
KE1_PRCTRGRP_SG Confirmation for profit center group hierarchy replication
KBAS_CO_COSTELEMNT_RPLCN Bulk confirmation for cost element replication
KBAS_CO_CELGROUP_RPLCN Confirmation for cost element group hierarchy replication
UC0_CHARTOFACCRPLCTNCO Confirmation about Replication of Chart of Accounts
UC0_FINREPSTRUCTRPLCTNCO Confirmation about Replication of Financial Reporting

Structure
UC0_FINCNSELMNTRPLCTNBCO UC0_FINCNSELMNTRPLCTNBCO
UC0_FINCNSSTRUCTRPLCTNCO UC0_FINCNSSTRUCTRPLCTNCO
5. To assign a provider IBC reference in the MDG target system, carry out the previous steps for the MDG hub.
6. Activate the integration scenario in the target system:
1. Choose Yes to activate the integration scenario immediately.
2. Click on the link Click here to open shown at the top to display all pending tasks.
3. Choose the pushbutton Rebuild List to refresh the list of all pending tasks.

4. Choose the pushbutton Process List to execute all pending tasks.
To activate the logical ports in the MDG target system, you must first process any pending tasks in the MDG
hub. This activates the integration scenario in the MDG hub. You must then process all pending tasks in the
target system that failed the activation again.
Define Business Systems
In the MDG hub client, create a business system for each target system:
1. Enter transaction MDGIMG.

2. Navigate to General Settings Data Replication Define Custom Settings for Data Replication Define
Technical Settings Define Technical Settings for Business Systems .
3. Choose the pushbutton New Entries.
4. Set the values for business system, logical system, and RFC destination for each client of the target
system, for example, QM8_410; QM8CLNT410; QM8CLNT410.
5. Mark the line of the newly defined business system and select the folder Define Bus. Systems, Bos. Enter all
required business object types:
Business Object Type Description
154 Company
158 Cost Center
229 Profit Center
892 General Ledger Account Master
897 Cost Center Group Hierarchy
898 Profit Center Group Hierarchy
899 Financial Accounting Chart of Accounts
900 Financial Consolidation Chart of Accounts
901 Financial Accounting Financial Reporting Structure
983 Cost Element
985 Cost Element Group Hierarchy
The following are the business object types for replication to an SEM-BCS system:
893 Financial Consolidation Element
894 Financial Consolidation Structure

900 Financial Consolidation Chart of Accounts
902 Financial Consolidation Financial Reporting Structure
904 Financial Consolidation Group
905 Financial Consolidation Unit
Repeat this step for all business systems defined for SOA replication in step 4.
6. For each business system with a defined business object, choose the folder Define Bus. Systems, BOs,
Communication Channel. Choose the pushbutton New Entries and select the communication channel 1
Replication via Services. Repeat this for all defined business object types.
Create Replication Models
After the point-to-point communication has been defined in SOAMANAGER, create the replication models as
follows:
1. Enter transaction MDGIMG.

Replication Models .
3. Choose the pushbutton New Entries and enter a replication model for each object type as described in the
following table:
Replication Model Description Log Days Data Model
SOA_ACC Replication model for Account (SOA) 1 0G
SOA_CCTRH Replication model for Cost Center Group 1 0G

Hierarchy (SOA)
SOA_CELE Replication model for Cost Element 1 0G

(SOA)
SOA_CELEH Replication model for Cost Element 1 0G

Group Hierarchy (SOA)
SOA_COA Replication model for Chart of Account 1 0G

(SOA)
SOA_COMP Replication model for Company (SOA) 1 0G
SOA_COST Replication model for Cost Centre (SOA) 1 0G
SOA_FRS Replication model for Financial Reporting 1 0G

Structure (SOA)

SOA_ITEM Replication model for Item as Group Ac 1 0G

count (SOA)
SOA_PCTH Replication model for Profit Center Group 1 0G

Hierarchy (SOA)
SOA_PCTR Replication model for Profit Center (SOA) 1 0G
Replication models for replication to a SEM-BCS system:
SOA_FSI Replication model for Fin. Cons. Struc 1 0G

ture Item (SOA)
SOA_FCFRS Replication model for Fin. Cons. Fin. Rep. 1 0G

Structure (SOA)
SOA_CONSGU Replication model for Financial Cons. 1 0G

Group & Unit (SOA)
SOA_FCS Replication model for Fin. Consolidation 1 0G

Structure (SOA)
4. For each defined replication model, mark the line of the replication model and select folder Assign
Outbound Implementation. Choose the pushbutton New Entries. Assign one outbound implementation to
each replication model as described in the following table:
Replication Model Outbound Implementation Description
SOA_ACC 1010 General Ledger Account Master
SOA_CCTRH 1110 Cost Centre Group Hierarchy
SOA_CELE 1180 Cost Element
SOA_CELEH 1190 Cost Element Group Hierarchy
SOA_COA 1000_V1 Financial Accounting Chart of Ac

counts
SOA_COMP 1140 Company
SOA_COST 1100 Cost Centre
SOA_FRS 1020 Financial Accounting Reporting Struc

ture

SOA_ITEM 1001_V1 Financial Consolidation Chart of Ac

counts
SOA_PCTH 1130 Profit Centre Group Hierarchy
SOA_PCTR 1120 Profit Centre
Outbound implementations for replication to a SEM-BCS system:
SOA_FSI 1001_V1 Financial Consolidation Chart of Ac

counts
SOA_FCFRS 1021 Financial Consolidation Reporting

Structure
SOA_CONSGU 1160 Financial Consolidation Group
1150 Financial Consolidation Unit
SOA_FCS 1170 Financial Consolidation Structure
5. For each outbound implementation you have described in step 4 ,mark the line of the implementation and
select the folder Assign Target Systems for Repl. Model /Outb.Impl. Choose the pushbutton New Entries.
Assign all business systems with the ERP clients of the target systems.
Define Package Size for Bulk Messages
To improve performance, an outbound parameter can be set to bundle outgoing messages. You can add the
outbound parameter PACK_SIZE_BULK, e.g. with the value 500, for SOA replication for the objects account,
company, consolidation group, and unit.
Activate Replication Models
You activate the defined replication models as follows:
1. Call transaction MDGIMG.

3. In the table of replication models, mark all previously defined replication models.
4. Choose Activate and check the log for error messages. Successful activation is indicated with a checkmark
in the Active column.
Check the log and make sure that all selected replication models have been activated successfully.
OPTIONAL: Set Consumer Proxy to Default Port (Transaction SOAMANAGER)

 Caution
In case the replication is triggered for PI service instead of P2P communication in the hub or the client, and
the SOA message is displayed in SXMB_MONI instead of SRT_MONI, you have to set the logical port for the
consumer proxy to default in SOAMANAGER.
In the client of the MDG hub, you have to set the logical port to default for the consumer proxies:
1. On the Service Administration tab, choose Web Service Configuration.

2. Search for object name CO_USMD_COMPANYRPLCTNBRQ, and click on the internal name to display the
consumer proxy details.
3. On the Configurations tab, mark the entry with the desired target system, and choose Set Log. Port Default.
4. Repeat the steps above for all entries mentioned in the table below.
Consumer Proxy External Name
CO_USMD_COMPANYRPLCTNBRQ CompanyReplicationBulkRequest_Out
CO_USMD_CHARTOFACCRPLCTNRQ_V1 ChartOfAccountsReplicationRequest_Out_V1
CO_USMD_GENLEDACCMRPLCTNRQ GeneralLedgerAccountMasterReplicationBulkRequest_Out
CO_USMD_FINREPSTRUCTRPLCTNRQ FinancialReportingStructureReplicationRequest_Out
CO_USMD_COSTCTRRPLCTNBRQ CostCentreReplicationBulkRequest_Out
CO_USMD_COSTCTRGRPHIRPLCTNRQ CostCentreGroupHierarchyReplicationRequest_Out
CO_USMD_PROFITCTRRPLCTNBRQ ProfitCentreReplicationBulkRequest_Out
CO_USMD_PRFTCTRGRPHIRPLCTNRQ ProfitCentreGroupHierarchyReplicationRequest_Out
CO_USMD_COSTELMNTRPLCTNBRQ CostElementReplicationBulkRequest_Out
CO_USMD_COSTELMNTGRPHIRPLCTNRQ CostElementGroupHierarchyReplicationRequest_Out
Consumer proxies for replication to a SEM-BCS system:
CO_USMD_CHARTOFACCRPLCTNRQ_V1 ChartOfAccountsReplicationRequest_Out_V1
CO_USMD_FINREPSTRUCTRPLCTNRQ FinancialReportingStructureReplicationRequest_Out
CO_USMD_FINCNSELMNTRPLCTNBRQ FinancialConsolidationElementReplicationBulkRequest_Out
CO_USMD_FINCNSSTRUCTRPLCTNRQ FinancialConsolidationStructureReplicationRequest_Out
In the client of the MDG client system, you have to set the logical port to default for the consumer proxies:
1. On the Service Administration tab, choose Web Service Configuration.

2. Search for object name CO_USMD_COMPANYRPLCTNBCO, and click on the internal name to display the
consumer proxy details.
3. On the Configurations tab, mark the entry with the desired target system, and choose Set Log. Port Default.
4. Repeat the steps above for all entries mentioned in the table below.
CO_FBS_COMPANYRPLCTNBCO CompanyReplicationBulkConfirmation_Out
CO_FBS_CHTACCTSRPLCTNCO ChartOfAccountsReplicationConfirmation_Out
CO_FBS_FINRPTGSTRUCCO FinancialReportingStructureReplicationConfirmation_Out
CO_FBS_GLACCTMSTRRPLCTNRCO GeneralLedgerAccountMasterReplicationBulkConfirma-
tion_Out
CO_KBAS_COSTCTRGRPHRYRPLCO CostCentreGroupHierarchyReplicationConfirmation_Out
CO_KBAS_COSTCTRRPLCTNCO CostCentreReplicationBulkConfirmation_Out
CO_KBAS_COSTELMNTGRPHRYRPLCO CostElementGroupHierarchyReplicationConfirmation_Out
CO_KBAS_COST_ELEMENT_REPLICATI CostElementReplicationBulkConfirmation_Out
CO_KE1_PRCTRGRPRPLCTNCO ProfitCentreGroupHierarchyReplicationConfirmation_Out
CO_KE1_PRCTRRPLCTNBULKCO ProfitCentreReplicationBulkConfirmation_Out
Consumer proxies for replication to a SEM-BCS system:
CO_UC0_CHARTOFACCRPLCTNCO ChartOfAccountsReplicationConfirmation_Out
CO_UC0_FINCNSELMNTRPLCTNBCO FinancialConsolidationElementReplicationBulkConfirma-
tion_Out
CO_UC0_FINCNSSTRUCTRPLCTNCO FinancialConsolidationStructureReplicationConfirma-
tion_Out
CO_UC0_FINREPSTRUCTRPLCTNCO FinancialReportingStructureReplicationConfirmation_Out
Result
You have configured the financial data for SOA manager using enterprise services on NetWeaver 7.40.

More Information
Configuring Master Data Governance for Financials [page 13]

5 Configuring the SOA Manager for MDG-F
in MDG Client Systems (NW 7.32 or lower)
Use
This document describes the configuration steps required to enable the exchange of financial data using point-
to-point enterprise services communication without a process integration (PI) system.
 Note
This document is relevant only for MDG client systems with SAP NetWeaver Basis release 7.32 or lower. For
systems with NetWeaver Basis release 7.40 or higher, follow the steps for the common MDG (hub) setup.
This document is not valid for the configuration of the MDG hub system.
Prerequisites
The following prerequisites must be performed in both the MDG hub and target systems.
Authorizations
Assign the administrative role SAP_BC_WEBSERVICE_ADMIN_TEC for the SOA Manager.
Authorize the following transactions:
● SU01
● SUIM
● PFCG
Service Users in ABAP Stack
To create a service user, carry out the following steps:
1. Choose transaction SU01, choose Create, and enter a user.

2. On the Roles tab, assign the role SAP_BC_WEBSERVICE_ADMIN_TEC.
Business Functions
Check if the business function FND_SOA_REUSE_1 is active.

48 PUBLIC Configuring the SOA Manager for MDG-F in MDG Client Systems (NW 7.32 or lower)
 Note
Activate the business function from transaction SFW5. By activating the business function, you can use the
following cross-application tool improvements that facilitate the use of services:
● SOA mapping tool

● Error handling
● Point-to-point enablement for asynchronous enterprise services
For replication to an ERP system, activate the business function FIN_MDM_SOA_ORG in the MDG client system.
For replication to an ERP system with SEM-BCS installed, activate the business function FIN_MDM_SOA_CU in
the MDG client system.
Maintain Transport Request for Inbound Service
1. Assign a transport request for an inbound service by running the Customizing activity in the MDG client
system under Cross-Application Components Processes and Tools for Enterprise Applications Master
Data Governance Central Governance Master Data Governance for Financials Replication
Enterprise Services Inbound Services for Financials Master Data Manage Transport Requests . If the
Customizing activity is not available in the client, open transaction SM34 and enter the view cluster
VC_TRN_REG_RQST. Choose Maintain.
2. Enter the application FINMDM_DATA_REPLICATION, and choose Continue.
3. Enter the groups FINMDM_DATA_COMPANY_RPLCTN and FINMDM_DATA_REPLICATION_GRP, and mark
both as automatic.
4. Afterwards, add a Customizing transport to each group. If necessary, create a transport with transaction
SE09 beforehand.
In an ERP system with SEM-BCS installed, perform the same steps, but use the application SEM_BW_INBOUND,
and the groups SEM_BW_INBOUND_ITEM and SEM_BW_INBOUND_REPUNIT_EHP6.
Support for Point-to-Point Communication
To activate the support for point-to-point communication, run the Customizing activity under Cross-
Application Components Processes and Tools for Enterprise Applications Enterprise Services Point-to-
Point Enablement for Asynchronous Enterprise Services Activate Support for Point2Point Communication .
Connection to System Landscape Directory
Check whether the client system is connected to the system landscape directory (SLD) or the BAdI
MDG_IDM_GET_LCL_SYSTEM is implemented to determine the local system ID. For more information, see
Customizing for Master Data Governance, Central Governance under General Settings Data Replication
Define Custom Settings for Data Replication Define Technical Settings BAdI: Determination of Local System
Name .
Error and Conflict Handler
To activate the error and conflict handler, run the Customizing activity under Cross-Application Components
General Application Functions Error and Conflict Handler Activate Error and Conflict Handler .

Configuring the SOA Manager for MDG-F in MDG Client Systems (NW 7.32 or lower) PUBLIC 49
Procedure
The following steps are required to configure the SOA Manager for MDG-F (transaction SOAMANAGER). Carry
out the following steps in the MDG client system.
Configure a Profile For Point-To-Point Communication
1. On the Technical Administration tab, choose Profiles.

2. Choose Create Profiles, enter the name MDG and description, and choose Next.
 Note
The profile names should be identical in the SOA manager settings for both MDG hub and client
systems. Reuse the corresponding name of the MDG hub.
3. Select User ID/Password, and choose Next.

4. If necessary, enter the proxy settings, and choose Finish to save the settings and activate the profile.
Configure the Client Settings
1. On theTechnical Administration tab, choose SAP Client Settings, and choose Edit.
2. Enter a business system and a business system ID in the following format: XYZ_001, where XYZ is the
system ID and 001 is the client.
3. To receive the business application ID from the system landscape directory (SLD), choose Get from SLD.
Configure a Provider System for the Business Scenario Configuration
1. On the Technical Administration tab, choose Provider Systems, then choose Create. Enter the system ID of
the client system as the name, for example XYZ_001, select the profile name defined in step 1, and choose
Next.
2. Enter the SLD identifier in the following format:
<Client>.SystemName.<ABC>.SystemNumber.<InstallationNumber>.SystemHome.<Host>, for
example, 416.SystemName.QV6.SystemNumber.0020270862.SystemHome.uxdbqv6.
 Note
You can find the system number under System Status SAP System Data Installation Number
in the main menu.
You can find the system home under System Status Database Data Host in the main menu.
3. Enter the access URL for WSIL and logon information under WSIL Services.
 Note
To identify the host name and port for the access URL, call transaction SMICM, and choose Goto
Services . Use the HTTPS host name and port displayed in the list. We recommend using the message
server host.
4. Enter the user for WSDL and a password for the WSDL documents.
5. Enter the service user you created in the backend system.
6. Enter the business application ID.

 Note
To determine the business application ID, run transaction SOAMANAGER in the counterpart system
(MDG hub), and navigate to Technical Administration SAP Client Settings .
7. Choose Finish to save and activate the system connection.
Edit Logon Data for Business Scenario
 Note
The backend user has to exist in both systems.

2. On the Maintenance tab, choose Create, enter your data, and choose Next.
3. Select User/Password or X.509 as the authentication method.
4. Enter the user name that you created earlier in the backend system, and choose Finish.
Assign Logon Data to Business Operation

2. On the Assignments tab, choose Create.
3. Use the input help to select a provider system/business application, and choose Next.
4. Select the user name you entered in step 4 as logon data from the dropdown list, and choose Finish.
Configure System for Point-To-Point Communication Using Service Groups
Service definitions and service groups that you configure to run SOA communications with SEM-BCS are
shown in separate tables.
1. Select service definitions and assign a profile.

1. Choose Add to search for the service definition.
2. In the dialog box, search for the service definition CHARTOFACCOUNTSREPLICATIONREQ1, select it in
the result list, and choose Add to Worklist.
3. Similarly, search for all required service definitions and add them to the worklist:
CHARTOFACCOUNTSREPLICATIONREQ1 Replication request for chart of accounts – version 1
FINANCIALREPORTINGSTRUCTURERE1 Replication request for financial reporting structure
GENERALLEDGERACCOUNTMASTERREP1 Replication bulk request for general ledger account mas

ter data
COMPANYREPLICATIONBULKREQUEST_ Bulk replication request for company
COSTCENTREREPLICATIONBULKRQ Bulk replication request for cost center
PROFITCENTREREPLICATIONBULKREQ Bulk replication request for profit center
COSTCENTREGROUPHIERARCHYREPLRQ Replication request for cost center group hierarchy

PROFITCENTREGROUPHIERARCHYREP1 Replication request for profit center group hierarchy
COSTELEMENTREPLICATIONBULKREQU Bulk replication request for cost element
COSTELEMENTGROUPHRYREPLRQ Replication request for cost element group hierarchy
Service definitions for replication to an SEM-BCS system:
CHARTOFACCOUNTSREPLICATIONV1RQ Replication request for chart of accounts
FINREPORTINGSTRUCREPLICATIONRQ Replication request for financial reporting structure
FINANCIALCONSOLIDATIONELMNTBRQ Bulk replication request for Financial Consolidation Ele

ment
FINANCIALCONSOLIDATIONSTRUCTRQ Replication request for Financial Consolidation Structure
2. Assign profile to service definitions:

1. Select all service definitions from the list and choose Assign Profile.
2. Select the profile MDG, choose Assign Profile, and choose Next.
3. Select Service Groups and Assign Business Applications in the provider system service group:
2. Enter the service group FBS_CHTACCTSRPLCTNCO, select it in the result list, and choose Add to
Worklist.
3. Repeat the procedure for all required service groups:
FBS_CHTACCTSRPLCTNCO Confirmation of chart of accounts replication
FBS_FINRPTGSTRUCCO Confirmation about replication of financial reporting

structure
FBS_GLACCTMSTRRPLCTNRCO Bulk confirmation of general ledger account master repli

cation
FBS_COMPANYRPLCTNBCO Bulk confirmation for company replication
KBAS_CO_COST_CENTRE_RPLCN Bulk confirmation for cost center replication
KE1_PRCTRRPLCTN_SG Bulk confirmation for profit center replication
KBAS_CO_CCGROUP_RPLCN Confirmation for cost center group hierarchy replication
KE1_PRCTRGRP_SG Confirmation for profit center group hierarchy replication

KBAS_CO_COSTELEMNT_RPLCN Bulk confirmation for cost element replication
KBAS_CO_CELGROUP_RPLCN Confirmation for cost element group hierarchy replication
UC0_CHARTOFACCRPLCTNCO Confirmation about Replication of Chart of Accounts
UC0_FINREPSTRUCTRPLCTNCO Confirmation about Replication of Financial Reporting

Structure
UC0_FINCNSELMNTRPLCTNBCO UC0_FINCNSELMNTRPLCTNBCO
UC0_FINCNSSTRUCTRPLCTNCO UC0_FINCNSSTRUCTRPLCTNCO
4. Assign a business application to the service groups:

1. Select all service groups from the list and assign them to the business application by choosing Assign
Business Application.
2. Select the provider system and the assigned business application name from the list and choose
Assign to Service Group.
3. Choose Finish.
5. Activate the business scenario in the target:
1. Choose Yes to activate the business scenario immediately.
2. Choose Process List to execute all pending tasks.
6. To activate the logical ports in the MDG client system, you must first process any pending tasks in the MDG
hub. This activates the business scenario in the MDG hub. You must then process all pending tasks in the
client system. This activates the logical ports.
Result
You have configured the financial data for SOA manager using enterprise services.
More Information
Configuring Master Data Governance for Financials [page 13]

6 Configuring ALE for Master Data
Governance for Financials
Use
This document describes the configuration steps that are required to enable the exchange of financial data
using Application Link Enabling (ALE) for MDG-F.
Prerequisites
Set Up RFC Connections
Set up RFC connections in the MDG hub and MDG target systems:
1. Run transaction SM59 (configuration of RFC connections), and provide the required RFC destination
details.
2. Define the logical systems in Customizing for SAP NetWeaver. Run transaction SALE, and choose Basic
Settings Logical Systems Define Logical System . Enter all target systems as logical systems.
3. Run transaction SALE, and assign the logical system to a client under Basic Settings Logical Systems
Assign Logical System to Client .
Define Global Company Codes
If the company code is required for your data, you must define the global organizational units for company
code. Run this activity in Customizing for SAP NetWeaver under Application Server IDoc Interface/
Application Link Enabling (ALE) Modelling and Implementing Business Processes Global Organizational
Units Cross-System Company Codes . Create cross-system company codes and map all company codes in
use to the defined global company codes.
Define Global Business Areas
If the business area is required for your data, you must define the global organizational units for business areas.
Run this activity in Customizing for SAP NetWeaver under Application Server IDoc Interface/Application
Link Enabling (ALE) Modelling and Implementing Business Processes Global Organizational Units Cross-
System Business Areas . Create cross-system business areas and map all business areas in use to the defined
global business areas.
Procedure
The following steps are required to configure ALE for MDG-F (transaction SALE) in the MDG hub and MDG
target system.

54 PUBLIC Configuring ALE for Master Data Governance for Financials
Create a Distribution Model
To create a new distribution model in the MDG hub, carry out the following steps in both systems:
1. Run transaction SALE (Display ALE Customizing), and choose Modelling and Implementing Business
Processes Maintain Distribution Model and Distribute Views . Alternatively, run transaction BD64
(Display Distribution Model).
2. In editing mode, create a new model. Choose Create Model View. Enter a short text and a technical name.
3. Choose Add Message Type for the newly created model. Enter the logical sender system and receiver
system, and add a message type from the following table. Repeat this step for all required IDoc message
types.
IDoc Message Type Description
GLMAST Master data G/L accounts (Master IDoc)
COSMAS Master cost center
COGRP1 Cost center groups
COELEM Cost element master data
COGRP2 Cost element groups
PRCMAS Profit center master record
COGRP6 Profit center groups
For Internal Order, choose Add BAPI, and make the following entries:
Obj. name/interface: InternalOrder
Method: SaveReplica.
Save your entries.
4. After you have saved your settings, you need to generate a partner profile. Choose Environment
Generate Partner Profiles . Select the model view you just have saved and enter the target system. Select
immediate processing for the output mode and inbound parameter. Choose the Execute button.
5. After you have generated the necessary partner profile, choose Edit Model view Distribute to
distribute this model view to your target system.
6. Enter the target system, and repeat step 4 to generate partner profiles on the MDG client.
Enhance Distribution Model for Confirmation Message
The configured distribution model needs to be enhanced to send a confirmation message back from the target
client to the client of the MDG hub:
1. Enter the client of the MDG hub and call transaction SALE.
2. Goto Modelling and Implementing Business Processes Maintain Distribution Model and Distribute
Views . Select the distribution model you have generated previously.
3. Select Environment: Change Partner Profile from the dropdown list.
4. Open Partner Type LS, and select the profile of the target system.
5. Choose the Create inbound parameter button.

Configuring ALE for Master Data Governance for Financials PUBLIC 55
6. Chose the message type ALEAUD and enter the process code AUD2. Save your entries.
In the client of the target system, the distribution model also needs to be enhanced:
1. Enter the client of the target system and call transaction SALE.
2. Goto Communication Maintain Distribution Model and Distribute Views . Select the distribution
model you have generated previously.
3. Select Environment: Change Partner Profile from the dropdown list.
4. Open Partner Type LS and select the profile of the source system.
5. Choose the Create outbound parameter button.
6. Chose the message type ALEAUD, select the receiver port from the selection list, and enter the value
ALEAUD01 as the basic type.
7. Select Transfer Idoc Immed. as the output mode and save your entries.
Define Business Systems
In the client of the MDG hub, a business system for the target client needs to be created as follows:

2. Goto General Settings Data Replication Define Custom Settings for Data Replication Define
Technical Settings Define Technical Settings for Business Systems .
3. Choose the New Entries button.
4. Enter the business system, logical system, and RFC destination for the target client.
5. Select the line of the newly defined business system and select the folder Define Bus. Systems, Bos. Enter
all desired business object types:
158 Cost Center
229 Profit Center
892 General Ledger Account Master
983 Cost Element
984 Cost Element Group
895 Cost Center Group
896 Profit Center Group
DRF_0019 Internal Order
6. Select each business object type, and choose the folder Define Bus. Systems, BOs, Communication
Channel. Choose the New Entries button, and select the communication channel 2 Replication via IDoc.
Repeat this for all defined business object types.
Create Replication Models

Once the distribution model and the business system are defined in the client of the MDG hub, it is possible to
create a replication model for each IDoc type:

3. Choose the New Entries button, and define a replication model with name, description, and data model 0G
for each IDoc type listed.
4. For each defined replication model, select the line of the replication model, and select the folder Assign
Outbound Implementation. Choose the pushbutton New Entries. Assign the corresponding outbound
implementation to each replication model you have defined:
Outbound Implementation Description
1012 General Ledger Account Master IDoc
1102 Cost Centre IDoc
1112 Cost Centre Group Hierarchy IDoc
1182 Cost Element IDoc
1192 Cost Element Group Hierarchy IDoc
1122 Profit Centre IDoc
1132 Profit Centre Group Hierarchy IDoc
1200 MDG-F Internal Order IDoc
5. For each outbound implementation you have described in step 4, select the line of the implementation, and
select the folder Assign Target Systems for Repl. Model /Outb.Impl. Choose the New Entries button. Assign
the business system with the ERP client of the target system.
6. Save your entries
Activate Replication Models
Activate the previously defined replication models as follows:

3. In the table of replication models, select all replication models you have previously defined.
4. Choose the Activate button, and check the log for error messages. Successful activation is indicated with a
checkmark in the Active column.
5. Check the log and make sure that all selected replication models have been activated successfully.

Configuring ALE for Master Data Governance for Financials PUBLIC 57
Result
You have successfully set up ALE for MDG-F.
More Information
● Configuring Master Data Governance for Financials [page 13]

● Configuring the SOA Manager for MDG-F (NW 7.40 or higher) [page 33]
● Configuring the SOA Manager for MDG-F in MDG Client Systems (NW 7.32 or lower) [page 48]

7 Appendix
7.1 Interlocking
Definition
Interlocking specifies which nodes are interlocked with a pending change request while a change to a hierarchy
is made. A change to a hierarchy can comprise adding a node, moving a node, removing a node, changing the
attributes of a node, or creating a hierarchy. After a change to a hierarchy is saved to a change request,
changes to interlocked nodes must be saved to the same change request. If a node is not interlocked, you can
use any change request to make a hierarchy-specific change.
Use
With a setting of Loose, nodes assigned to the parent node of the node being changed are interlocked.
With a setting of Strict, interlocking propagates upwards and downwards from the parent node of the node
being changed as follows:
● Upwards interlocking interlocks the parent node and its assigned nodes, the parent node of the parent
node and its assigned nodes, and so on up to the root node.
● Downwards interlocking interlocks child nodes of the parent node, their child nodes, and so on down to
the end nodes. This comprises a subhierarchy of interlocked nodes with the parent node at its root.
For a full description of what interlocking means that includes a graphical representation of the Loose and
Strict settings, see Scope for Hierarchy-Specific Changes [page 104].
7.2 Deleting Data Model 0F
Prerequisites
Make sure that data model 0F is not activated in your productive system.

Appendix PUBLIC 59
Activities
1. If the data model 0F has an active version, run transaction MDG_DELETE_MODEL (Delete Active Version of
Data Model) first.
 Caution
Running transaction MDG_DELETE_MODEL will irrevocably delete the active version of the data model,
including all dependent data.
2. Open the Customizing activity Master Data Governance, Central Governance General Settings Data
Modeling Edit Data Model , and confirm the dialog box.
3. In the data model list, select the row that contains data model 0F.
4. Choose .
5. In the Specify objects to be deleted dialog box, select all entries.
6. Confirm all information and warning messages by pressing Enter.
7. Choose to confirm the deletion of the data model. If required, create a workbench request.

60 PUBLIC Appendix
8 Adapting Master Data Governance for
Financials
This documentation provides the information you require to change and enhance settings for Master Data
Governance for Financials. It supplements the information provided in the section Configuring Master Data
Governance for Financials.
8.1 Data Modeling
The purpose of data modeling is to define the structure of the data storage. During the master data processing,
a change request is used that stores the master data changes in a staging area. The data model can define a
reuse area that is used for data storage after the change request processing has been completed and the
related data has been activated. In this case, the system moves data from the staging area to a storage location
that is connected by the access class of the reuse area. This storage location is called active area.
If there is no reuse area defined, the same database tables that are used for the staging area, are also used to
store active data. Then, no access class is involved, the system does not move data from one location to
another, and MDG is used as the active area.
8.1.1 Extending the MDG-F Data Model
For information on how to extend the MDG-F data model, see Extend Data Model by New Fields (https://
scn.sap.com/docs/DOC-55226 ).
8.1.2 Transportation of Data Models to the Target System
Use
You can transfer data models for Master Data Governance from your test system to your target system by
means of transport requests.

Adapting Master Data Governance for Financials PUBLIC 61
Process
To transport an active version of a data model to the target system, proceed as follows:
1. In Customizing for Master Data Governance, choose General Settings Data Modeling and then the
Edit Data Model activity.
2. To activate the data model again, select it and choose .

A dialog box appears.
3. Specify the transport request that you want to use to transport the active data model and save your
entries.
The active data model is transported to the target system. Once in the target system, the data model is
activated automatically. This can have the following effects on the generated database tables in which the
entities are saved:
○ The generated database tables are generated again.
○ The generated database tables are adjusted.
○ If the entity type was removed from the current data model, the generated database tables are
deleted.
 Note
If a deletion of the active data model is transported, the generated database tables are not deleted –
with the exception of the hierarchy tables.
To transport an inactive version of a data model to the target system, proceed as follows:
1. In Customizing for Master Data Governance, choose General Settings Data Modeling and then the
Edit Data Model activity.
2. Choose Table View Transport and specify the transport request with which you want to transport the
inactive data model.
3. Select the data model and choose Process Transport Include in Request .
In the dialog box that appears, specify that all lower-level entries are to be transported and save your
entries.
 Note
You can activate the transported inactive data model in the target system.
To do this, in Customizing for Master Data Governance in the target system, choose General Settings
Data Modeling and then the Edit Data Model activity.
Select the data model and choose .

62 PUBLIC Adapting Master Data Governance for Financials
8.1.3 Defining Data Models in the Configuration Workbench
Use
You can use this Web Dynpro application to define and activate a data model to map master data in the system,
along with its properties and relationships. The system uses this data model to generate database tables in
which the master data can be stored.
You can assign a reuse active area to a data model or to individual entity types of a data model. Then the
inactive portion of master data for this data model is stored in the generated tables and the active portion is
stored in the database tables specified in the reuse active area.
 Note
You can also assign a reuse active area on the level of an entity type.
Prerequisites
You have created any customer-specific data elements you want to use for the entity types in the data model or
for their attributes.
If you use entity types with internal key assignments, you can define prefixes for internal key assignment. You
do this in Customizing for Master Data Governance under General Settings Define Prefixes for Internal Key
Assignment .
Features
Selecting Data Models or Creating New Ones
In the Configuration Workbench screen, you can select a data model for editing or you can create a new data
model. By default, the system displays all data models that are available for processing.
For each data model you can see whether an inactive version of the data model exists alongside the active
version and whether that version differs from the active version. .
Working with Data Models and their Entity Types
After you select a data model for editing or create a new data model in the Configuration Workbench screen,
the Data Model screen opens.
In the Data Model screen, you can complete the following tasks:
● Edit data model details

● Create and customize entity types that belong to a data model.
● Check the validity of your settings using the Check button.
● Activate changes using the Activate button.

● Enable and disable entity types, attributes, and relationships
For more information, see Adapting Standard MDG Content to Your Business Needs
Data Model Details Panel
In the Data Model Details panel, you can edit the data model description and view details such as version, and
activation status
Entity Types Panel
You can select an entity type or create a new one in the Entity Types panel. You can edit settings for a selected
or newly created entity type using the tab pages.
Entity Details Tab
Entity Details is divided into the following sections:
● General Details
You must define a Storage and Use Type for the entity type. In addition, you can provide other data, such as
a description and a data element.
● Hierarchies
You can indicate whether hierarchies are allowed and what properties they are allowed to have. You can
only allow a hierarchy to be set up for entity types with storage and use type 1.
● Key Assignment
You can indicate how keys are assigned to the entity type.
● Enablement Status
You can enable entity types that are relevant to your business and disable entity types that are irrelevant to
your business.
● Reuse
You can specify a reuse active area and references to elements of the data dictionary.
● Texts
You can specify the fields of the check tables that contain the texts for an entity type. This is only possible
for entity types of storage and use type 3.
Attributes Tab
Here you define the attributes of each entity type in the data model. Attributes are mapped as non-key fields in
the generated database tables of the entity type. You also need to assign an existing data element to each
attribute. The data element determines the technical properties of the attribute as well as the field labels and
the input help texts on the user interface. Attributes can be defined as required entry fields or as optional fields.
You use a currency-supplying attribute or a unit-supplying attribute to assign a currency or unit of measure to
the attribute.
Incoming Relationships and Outgoing Relationships Tabs
Relationships can be viewed from the perspective of each of the entity types that are involved. For example, the
HAS_ADRE relationship between BP_HEADER and ADDRESS can be viewed from the perspective of both entity
types.
You can view the relationship in the following ways:
● If you select the BP_HEADER entity type, you can view the relationship in the Outgoing Relationships tab
page.
● If you select the ADDRESS entity type, you can view the relationship in the Incoming Relationships tab
page.

For all relationships, you can define properties such as:
● Relationship Type (leading, referencing, qualifying, or foreign key)

● Cardinality
● Fields of foreign key relationships
You can assign the key fields of the from-entity type to the attributes and key fields of the to-entity type.
 Example
In the PFLI entity type of the SF data model, you model flight scheduling data. For example, you can specify
the cities CITYFROM and CITYTO. The GEOCITY entity type has a storage and use type of 3. It acts as a
check table for valid cities. If you want to ensure only valid cities are selectable, you create a foreign key
relationships between CITYFROM and GEOCITY, and between CITYTO and GEOCITY.
To maintain the foreign key attributes for PFLI, you can open the Incoming Relationships tab, select the
relationships CITYFROM and CITYTO, and choose the foreign keys button. You want to define foreign key
relationships so that the fields PARTNER_1 and PARTNER_2 at entity type BPREL contain only the values of
the field BP_HEADER at entity type BP_HEADER.
Business Object Types Tab
You have to assign business object types only for entity types of storage and use type 1 that you want to
replicate, or for which you want to generate their own Enterprise Search template.
If you have assigned the same business object type to multiple entity types, then you have to specify the entity
type to be used for each business object type.
You can do this in Customizing for Master Data Governance under Data Modelling Specify the Entity Type to
Be Used for Each Business Object Type
Hierarchies Tab
If you want it to be possible to set up a hierarchy for the entity type, you must specify at least the root node
(hierarchy name) for the hierarchy here. To do this, choose one of the available entity types and assign
Hierarchy Name as the usage type. You also can specify all entity types that are to be allowed in the hierarchy of
the entity type (No Special Use or Ranges Permitted on End Nodes)
8.2 UI Modeling
The purpose of UI modeling is to define and customize user interfaces with which users process master data.
8.2.1 Managing of UI Configurations
Use
You use the Manage UI Configurations (USMD_UI_CONFIGURATION) Web Dynpro application to manage user
interfaces in SAP Master Data Governance. Each table row represents a separate user interface and consists of

the user interface application and its configuration. You can create a new user interface configuration by
copying an existing one. You can also edit the configurations for existing user interfaces. Each link you click
opens the relevant screen in the Floorplan Manager (FPM).
 Note
You can only use this function if Business Function Master Data Governance, Generic Functions 7.0 Feature
Pack (MDG_FOUNDATION_5) is active.
The previous version of this application only allows management of UI configurations for specific types of
single-object processing UIs.
If the relevant business function is not active, you can edit the relevant technical elements using
transaction SE80. For more information, see the links in this document under Activities Working with a
UI Configuration . The documents listed cover editing using transaction SE80 as well as editing using this
Web Dynpro application.
The most common types of user interface that you can manage are as follows:
● Single-Object Processing
● Multiple-Record Processing
● Search
There are many options to change a user interface including customizing, enhancement, context-based
adaptation (CBA), and personalization. Some options affect all clients of a system. Other options are client
specific. It is even possible to restrict changes to only one user. For more information, see Floorplan Manager
for Web Dynpro ABAP.
Prerequisites
● An active data model exists.

● You have basic knowledge of how to use the FPM and of the configuration of applications and components
with Web Dynpro ABAP.
● To create a new user interface by copying an existing one, the following criteria must be met:
○ You can use an active MDG data model with at least one entity type with storage and use type 1.
○ You have assigned a business object type code (OTC) to this entity type.
○ Before starting the configuration you need to carry out the following steps to ensure the default data
model as the data model for which the UI is configured in the following way:
1. Run transaction SPERS_MAINT.
2. Select Edit Objects
3. From the displayed list, choose SAP Master Data Governance - R_FMDM_MODEL.
4. In the pop-up, set the value of the field Standard Data Model to the model that you want to use for
UI processing.
5. Confirm and save.

Activities
Opening the Web Dynpro Activity in Customizing
Path in Customizing for Master Data Governance, Central Governance (transaction MDGIMG): General
Settings UI Modeling Manage UI Configurations
Copying a User Interface Configuration
1. Select the UI configuration you want to copy and choose the Copy button.
2. To expand configurable components, choose the Configurable Components button.
3. In the Copy column, select the technical elements you want to copy, and enter appropriate names for the
target configurations.
4. Choose the Start Deep-Copy button.
5. Return to the Manage UI Configurations screen and refresh the table content. The system displays an
additional row in the table with the configurations you just created.
6. If the user interface is compatible with the MDG Communicator, the MDG Communicator Status is set to
Configuration missing. To make the MDG Communicator available, you must configure it by choosing the
Details link.
Subsequent steps depend on the type of user interface you are configuring and the type of configuration you
want.
Working with a UI Configuration
The following documents provide detailed information on the concept behind the particular types of user
interfaces, and instructions on how to create new user interfaces either using the Web Dynpro application
USMD_UI_CONFIGURATION or using transaction SE80:
Single-Object Processing
● Concept: Creating User Interfaces for Single Object Processing [page 67]
● Instructions: Creating a Basic Configuration for the Single-Object Processing UI
Search
● Concept: Configuration of the Generic Search

● Instructions: Configuring the Generic Search for a Particular Business Object Type
8.2.2 Creating User Interfaces for Single Object Processing
In a complete UI configuration for single object processing, several components work together and need to be
configured accordingly as shown in the figure MDG UI Configuration for Single-Object Processing below.
Two of these components are the MDG Web Dynpro application USMD_OVP_GEN and MDGF_OVP_GEN with
their application configurations. Each application configuration is specific for an object type and this object
type is defined with the parameter USMD_OTC.
This Web Dynpro application implements an adaptable overview page (OVP) component of the Floorplan
Manager (FPM): FPM_ADAPTABLE_OVP. This OVP component is a wrapper that contains an FPM overview
page component (FPM_OVP_COMPONENT). The configuration of the adaptable OVP references the

adaptation scheme for creating context based adaptations (CBA) of the included OVP component and of its
sub-components.
For more information, see Generic Context-Based Adaptation Scheme.
The configuration of the OVP contains at least one page. At least one section of the page contains user
interface building blocks (UIBBs). Most UIBBs enable the processing of business object data on the UI. The
UIBBs are configured for all entity types that belong to the business object. Usually, there’s more than one
entity type.
The MDG framework provides the following UIBBs:
● The change request UIBB (CRUIBB) displaying the change request properties, such as description, due
date, notes, and attachments
● The validity UIBB displaying the time validity for edition-based entities
These UIBBs are no explicit parts of the configuration of the Web Dynpro application, but are added at runtime
by the MDG communicator, which has overall responsibility for the change request process. The MDG
communicator controls the availability of change request actions, which are represented as buttons in the
global toolbar. The settings that the MDG communicator uses are stored in its component configuration.
 Note
You can also include the CRUIBB explicitly in the OVP configuration.
If you want to have an object-specific search, the OVP can include an initial screen with an FPM search UIBB to
enter search criteria and a list UIBB to display search results.

MDG UI Configuration for Single-Object Processing
MDG Data Model
The UI configuration is based on the active version of an MDG data model. At design-time, when you create the
configuration of a UI or customize a UI, the relevant data model is determined by the standard data model from
your user profile. You set the standard data model in the following way:
1. Run transaction SPERS_MAINT.

2. Select Edit Objects.
3. From the displayed list, choose SAP Master Data Governance - R_FMDM_MODEL.

4. In the pop-up set the value of the field Standard Data Model to the model that you want to use for UI
processing.
5. Confirm and save.
At run-time, when the UI is used to process data, the MDG data model is determined by the business object
type code given in the parameter USMD_OTC of the configuration of the Web Dynpro application
USMD_OVP_GEN or MDGF_OVP_GEN.
genIL Components
When you activate an MDG data model that is in the customer namespace, the system creates the following
genIL components as local objects. The names of the components are as follows:
● ZSP_<ID of MDG data model>

This component is responsible for all user interfaces related to the single object processing of the entity
types from your custom data model. If your data model ID, for example, is ZT, the genIL component is
named ZSP_ZT.
● ZMP<ID of MDG data model>
This component is responsible for all user interfaces related to the multi-record processing of the entity
types from your custom data model. If your data model ID, for example, is ZT, the genIL component is
named ZMP_ZT.
● ZHP<ID of MDG data model>
This component is responsible for all user interfaces related to the hierarchy processing of the entity types
from your custom data model. If your data model ID, for example, is ZT, the genIL component is named
ZHP_ZT.
You can check the successful creation of the genIL components by calling transaction
GENIL_MODEL_BROWSER.
 Note
If you work with a data model that is in the SAP namespace, you have to create the related genIL
components and a transaction handler class manually. For more information, see Creating genIL
Components and Transaction Handler Manually.
Business Object Type Code
Every configuration of the Web Dynpro applications USMD_OVP_GEN and MDGF_OVP_GEN contains the
parameter USMD_OTC that must be set to the business object type code (OTC) of the object that the UI should
be used for. The OTC is defined in Customizing for Master Data Governance under General Settings Data
Modeling Define Business Object Type Codes . You need to assign the OTC to the data model and the entity
type in the view Business Object Type in the Customizing activity Edit Data Model under General Settings
Data Modeling . You also need to set the indicator Root in the same view. Additionally, you need to assign the
data model and the entity type to the OTC in the Customizing activity Define Entity Type to Be Used by Business
Object Type under General Settings Data Modeling .
Data ModelSpecific Structures
The UI components of MDG require several DDIC structures that are specific to the data model used for the UI
configuration. Initially and also after every change to the data model, these structures need to be generated. If
you follow the recommendation and enter the required information for your data model in Customizing activity
Edit Data Model under General Settings Data Modeling , this generation is performed automatically.

Mandatory Naming Convention for the MDG Communicator
The application configuration ID must be the same as the configuration ID for the MDG communicator settings.
Otherwise, the application cannot determine which settings to use and the integration with the MDG
framework will not work.
Possible symptoms of a mismatch between configuration IDs at runtime are as follows:
● No CRUIBB is displayed after choosing Edit in one of the UIBBs.

● No change request ID is generated.
● No change request action buttons are displayed in the main toolbar.
Recommended Naming Conventions for Other Configurations
● Application Configuration <Prefix>_<Data Model>_OVP_<Main Entity Type or Business

Object Type>
Example: USMD_SF_OVP_CARR
● Component Configurations <Prefix>_<Data Model>_<Main Entity Type or Business Object
Type>_<Component Type>
Examples:
○ USMD_SF_CARR_OVP for the configuration of the OVP component for the entity type CARR in data
model SF
○ USMD_SF_CARR_FORM for the configuration of a form component for the entity type CARR in data
model SF
Highlight Changes
You can set the colors and the activation of the highlight changes function in the configuration of the used MDG
Web Dynpro application, for example USMD_OVP_GEN or MDGF_OVP_GEN, using the parameters
MDG_HC_DISABLE, MDG_HC_COLOR_SAVED, and MDG_HC_COLOR_UNSAVED. For more information, see
Highlight Changes.
8.3 Data Quality and Search
The data quality functions of MDG allow you to enrich and validate master data, as well as to prevent the
creation of duplicates. The various search capabilities are not only used to find master data that can be
processed, but are also used for matching data to prevent the creation of duplicate information. Correct and
complete data can be achieved with automatic derivation of attributes and enrichment from external data
sources.
8.3.1 Search Providers for Master Data Governance
In SAP Master Data Governance you can use the following search providers to search for master data:
● Enterprise Search
● Database Search [page 72]
● Business Address Services (BAS)-Based Search

● Searching with Customer-Specific Search Providers [page 72]
● SAP HANA Search
 Note
To configure SAP HANA Search see Configuring SAP HANA-Based Search for MDG and Configuring
Drill-Down Search (Optional).
8.3.1.1 Database Search
In SAP Master Data Governance you can use the database search to find master data for changing or
verification. It is an exact search method that is based on exact values or value ranges like identification
numbers or names that are stored in databases.
8.3.1.2 Searching with Customer-Specific Search Providers
Use
In SAP Master Data Governance you can also implement your own search providers. If you want to do this, you
have to do the following:
Procedure
Mandatory settings for search processing
1. In Customizing for Master Data Governance, enter your specific settings under SAP Customizing
Implementation Guide Cross-Application Components Master Data Governance General Settings
Data Quality and Search Define Search Applications :
○ Define your search application.
○ Define your access class.
 Note
Your access class must use the standard search interface IF_USMD_SEARCH_DATA (Search for
Entities).
2. User interface: Use the generic WebDynpro application USMD_ENTITY_SEARCH and launch it with the
parameter SEARCH_MODE = your new search application (as defined in step 1).
Optional search indexing
1. Initial load of index: Use the class CL_USMD_MODEL_EXT to read or extract data from the Master Data
Governance data models.

2. Delta load of index: Use the enhancement spot USMD_TRANSACTION_EVENTS to update the index with the
changes made in the records of a Master Data Governance data model.
8.4 Process Modeling
The configuration of governance scope, change requests, and workflow offers you flexible ways to model the
desired governance process.
8.4.1 Defining a Governance Scope
Prerequisites
You have identified the data models whose governance scope you want to change, as well as the content within
each data model that you want to govern.
You are aware of the consequences of changing the governance scope. See the help document in Customizing
for Master Data Governance under General Settings Process Modeling Define Governance Scope
Context
You can determine a governance scope based on your business needs. Ungoverned fields are read-only in
change requests, unless you remove them from the user interface.
 Example
In the material application, you can for example, remove sales grouping data from the governance scope.
Procedure
1. In Customizing for Master Data Governance under General Settings Process Modeling , choose Define
Governance Scope.
2. In the Data Models view, select the data model whose governance scope you want to define.
3. Make necessary changes to the Governed settings of entity types, attributes, and referencing relationships.

If there are dependencies, a pop-up informs you of these dependencies and proposes required changes.
You can apply required changes or cancel. The following changes to governance scope are not possible:
○ Changes to the Governed setting for entity types with a storage and use type of 1.
These entity types are shown in the Customizing activity, to enable navigation to attributes.
○ Changes the Governed setting of attributes that are key fields.
These attributes are not shown in the Customizing activity.
○ Changes to attributes for which the Required Field setting is set to Yes in the data model.
These attributes are not shown in the Customizing activity.
Results
You have defined a governance scope for the data model. You can keep ungoverned data model elements on
the user interface for information purposes. If the elements are not informative to your users, we recommend
that you remove them. For more information, see Managing of UI Configurations [page 65].
8.4.2 Setting Up New Business Activities
Context
You need to carry out the following steps if you want to enable users to create a single entity without having to
create a change request beforehand in a separate step. As a result, the user also no longer needs to select the
data model, the entity type, or the change request type. These are predefined automatically as part of the
configuration settings described in this documentation.
Procedure
1. Create a new business activity in the customer namespace.
In Customizing for Master Data Governance, Central Governance, choose General Settings Process
Modeling Change Requests Create Business Activity .
2. Assign the new business activity to a change request type for single objects.
In Customizing for Master Data Governance, Central Governance, choose General Settings Process
Modeling Change Requests Create Change Request Type .

8.4.3 Configuration of the Change Request Process
When configuring the change request process you need to define the following:
● Processing steps and their processors

● Possible actions of processors
● Process flow between steps
● Change request status in each step
Additionally, you can use editions to schedule changes and you can define when the data replication should
happen. For more information, see Using Editions to Schedule Changes.
You must configure the following elements:
● Change Request Type

The change request type defines which data can be processed. The change request type is assigned to one
MDG data model and lists the possible entity types that the change request can contain.
SAP Business Workflow is used to process change requests in SAP Master Data Governance. To define the
process flow of the change request you can use standard workflow templates or custom workflow
templates when defining a change request type. For more information on SAP Business Workflow, see the
Customizing activities under SAP NetWeaver Application Server Business Management SAP
Business Workflow .
Alternatively, you can use the MDG rule-based workflow template when defining a change request type. In
this case, the content of Business Rule Framework plus (BRFplus) decision tables defines the process flow
of the change request.
For more information, see the Customizing activity Create Change Request Type under General Settings
Process Modeling Change Requests .
● Change Request Step
Each change request process consists of a number of change request steps that can be either dialog steps
or background steps. For each dialog change request step, you can do the following:
○ Assign processors
○ Configure validations and data enrichments
○ Assign UIs
The processing sequence of the steps is based on the processors' decision and other criteria that are
evaluated by the workflow assigned to the change request type.
If you are not using the rule-based workflow, the workflow template defines the available change request
steps. Every change request type using this workflow template can only have the available steps. For more
information, see Customizing activity Define Change Request Step Types and Assign Actions under
General Settings Process Modeling Workflow .
If you are using the rule-based workflow, the Customizing settings and the content of the BRFplus decision
tables define the available steps. Every change request type using the rule-based workflow can have
different change request steps although all change request types are using the same rule-based workflow
template. For more information, see Customizing activity Define Change Request Steps for Rule-Based
Workflow under General Settings Process Modeling Workflow Rule-Based Workflow .
● Change Request Step Type and Change Request Action
The change request step type defines the possible actions that a processor of a change request step can
use. We deliver a number of change request step types, for example Approve Change Request with the
possible actions Approve and Reject.

The change request step type of each change request step is determined at runtime. You can configure a
change request step that allows the actions Approve and Reject in one case, while allowing Finalize
Processing and Send for Revision in another case.
For more information, see Customizing activity Define Change Request Step Types and Assign Actions
under General Settings Process Modeling Workflow .
● Change Request Status
The change request status informs the user about the processing status and determines the possible
changes to the change request and the contained data. We deliver a set of status control attributes:
○ no processing
○ objects can be added or removed
○ data changes are allowed
The following statuses that finalize the change request and stop further processing: Final Check Approved
and Final Check Rejected. In all other statuses, including any custom statuses, the change request is still
open and interlocks the contained data to protect it from processing with other change requests. For more
information, see Customizing activity Edit Statuses of Change Requests under General Settings
Process Modeling Change Requests .
The change request status is set by the workflow. Either the task Set Status of Change Request is used to
set the status or, if the rule-based workflow is used, the decision tables are used. For more information, see
Customizing activity Configure Workflow Tasks under General Settings Process Modeling
Workflow .
8.4.3.1 Designing the Change Request Process
Use
For the design of the change request process and its configuration, it is useful to create a diagram that
comprises all change request steps and their connections. The recommended process is as follows:
Process
1. Start with step 00 and an appropriate description, for example Request. Provide a name for the group of
users that are allowed to create change requests of this type, for example Requester.
Change Request Step: 00/Request. Change Request Type: Requester

 Note
You control which users can create change requests of a certain type with the authorization object
USMD_CREQ. For further information on authorizations, see Authorization Objects and Roles Used by
Master Data Governance.
Also, add a step 99 to represent the end of the process.
Change Request Step: 99/Complete

2. Add a step for each task that a user needs to perform. Assign a step number that is unique for the process
and choose an appropriate description. Name the group of users that shall perform the task. Select a step
type in Customizing activity Define Change Request Step Types and Assign Actions under General
Settings Process Modeling Workflow that fits to the task and includes the actions the processor
should be able to choose. Add the step type and the possible actions as outcomes to the diagram like
shown below.
Dialog Step 90/Approve: With Expert as Processor, Approve Change Request as Step Type, and Approve and Reject as
Possible Actions
3. Add a step for each background task. Assign a step number and a description. Add this information
together with the description of the background task to the diagram. Also, include all possible outcomes of
the task on which you want to react in the process. Some important standard tasks of MDG to work with
the change request are the following:
○ ACTIVATE CHANGE REQUEST (TS60808002)
○ DISCARD CHANGE REQUEST (TS75707936)
○ CHANGE REQUEST REPLICATION (TS60807976)

Background Step 91/Activate: To Activate All Data of the Change Request with Task Activate Change Request and Two
Outcomes to Handle Successful and Unsuccessful Completion of the Task
4. Connect each step with an arrow that originates from the respective outcome of the previous step and
ends at the step that should follow. For each arrow, add the new status that the change request shall have,
when the process proceeds from one step to the next.
If the expert chooses to approve the change request, the status shall be set to 02/Changes to be Executed, and the
system shall activate the change request.
More Information
For more information, see Creating a Basic Change Request Process [page 89] and Add User-Agent Steps
[page 92] for examples to configure the rule-based workflow.

8.4.3.2 Configuration of the Workflow
Use
SAP Business Workflow is used to process change requests in Master Data Governance (MDG). You have the
option to use standard or custom workflow templates when defining a change request type. If you choose
standard templates you can customize predefined change request process flows. If you choose custom
templates you can create your own process with the workflow builder of SAP Business Workflow.
Alternatively, you can use the MDG rule-based workflow, which is based on one generic workflow template. You
can configure your particular change request process with BRFplus decision tables. Using the rule-based
workflow you can add or remove a change request step or change the order of the steps without the need to
change anything in the workflow template by adapting the BRFplus decision tables.
Prerequisites
You have performed the basic workflow setup as described in the document Workflow Set-Up.
Activities
Standard Workflow Template
1. Choose an appropriate template by examining its documentation.

2. Create the change request type and enter the chosen workflow template.
3. Perform further configuration according to the requirements of the template, for example, assign
processors to the change request steps.
Custom Workflow Template
1. Create the workflow template.

2. Define the change request steps in the MDG Customizing.
3. Create the change request type and enter your custom workflow template.
4. Perform further configuration, according to the requirements of the template, for example assign
processors to the change request steps.
Rule-based workflow
1. Create the change request type.

2. Define change request steps in MDG Customizing.
3. Create decision tables.

8.4.3.2.1 Workflow Set-Up
Use
You use this process to define the mandatory Customizing settings that are needed to enable SAP Business
Workflow for the change request process in Master Data Governance.
Prerequisites
You have defined the necessary settings for SAP Business Workflow and defined the organizational plan in
Customizing under SAP NetWeaver Application Server Business Management SAP Business
Workflow .
Process
1. The workflow system user (typically WF-BATCH) processes background tasks of MDG. Therefore, this user
needs to have the required MDG authorizations. Assign the PFCG role SAP_MDG_WF_ADM to the workflow
system user in transaction SU01. For more information, see SAP Note 1650993 .
2. Create event type linkages for the business object BUS2250 (MDG Change Request) as described in
Customizing activity Activate Event Type Linkage under General Settings Process Modeling
Workflow .
3. To assign processors to change request types and change request steps, decide on the possible agents of
the MDG workflow tasks in general. In Customizing activity Configure Workflow Tasks under General
Settings Process Modeling Workflow assign specific agents from your organizational plan to each
dialog task. In the attributes pop-up of each dialog task, select to whom processors may forward a
respective work item. Instead of assigning specific possible agents to a dialog task, you can also classify a
dialog task as general task, so that a work item can be executed by any user. All users in the list of possible
agents that are also assigned as processors of a change request step, are selected as the agents at runtime
and will receive the work item. Make the settings for all dialog tasks of the application component CA-MDG-
AF and the respective components of the MDG application that you use.
 Note
If you assign a processor to a change request step that is not assigned as possible agent, the workflow
will end in an error at runtime unless you have classified the task as general task.

8.4.3.2.2 Rule-Based Workflow
Definition
Instead of building your own workflow template, you can use the MDG rule-based workflow. Using the rule-
based workflow, you can configure any kind of change request process without the need to create and adapt a
workflow template. You can define different change request processes in decision tables of the Business Rules
Framework plus (BRFplus), which are maintained in Customizing for each change request type. At runtime, the
current step, the user interactions, and other parameters in the decision tables determine the process flow of
the change request. When you adapt the decision tables in BRFplus, you can add or remove a change request
step or change the order of the steps without changes in the workflow template.
The rule-based workflow uses BRFplus to determine the change request status, the next change request step,
and expected agent(s). To make this information available, the system uses the current step, the last action,
the priority of the change request, and, where appropriate, the reason of rejection as input parameters. You
access the BRFplus application to determine how change requests are processed for a particular change
request type in Customizing activity Configure Rule-Based Workflow under General Settings Process
Modeling Change Requests Workflow Rule-Based Workflow . If you process this Customizing activity for
a change request type for the first time the system generates a BRFplus application for each change request
type. Each application contains functions, rule-sets, and decision tables. The content of the decision tables
defines the change request process.
Three decision tables are available for each change request type:
● Single Value Decision Table

The Single Value Decision Table DT_SINGLE_VAL_<change request type> defines the process flow
between the change request steps. Based on the previous step, the action, and other parameters, this
table returns the next step and other result parameters. The most important result parameter is the
condition alias that links to the other decision tables. This decision table has the following condition
columns:
○ CR Previous Step
This parameter contains the previously processed change request step.
○ Previous Action
This parameter contains the result of the previous system or previous user action.
○ Chng. Req. Priority
This parameter contains the current priority of the change request.
○ Chng. Req. Reason
This parameter contains the reason for this change request.
○ CR Rejection Reason
This parameter contains the reason for rejection of this change request.
○ CR Parent Step and Parallel Agt Grp No.
These columns are used for parallel processing and are considered by the rule-based workflow to find
the next step in the relevant subprocess. The system identifies the relevant subprocess by referring to
the values in CR Parent Step and Parallel Agt Grp No.. For more information, see Parallel Processing
[page 95].
Based on the data from these condition columns, the system takes the actions and sets the statuses
outlined in the result columns. This decision table has the following result columns:
○ Condition Alias
The condition alias references the other decision tables. Each condition alias must be handled using at
least one row in either the User Agent Decision Table or the Non-User Agent Decision Table.

○ New Chng. Req. Step
This parameter contains the next step in the process.
○ New CR Status
This parameter contains the new status for the change request.
○ Hours to Completion
After the expected completion time in hours has passed, without any of the agents having processed
the work item, the system automatically sends a notification.
○ Merge Type and Merge Parameter
In parallel processing, the merge type and the merge parameter define how the results of the
subprocesses are merged back into the higher-level process. The system only supports the merge type
B calling a BAdI method. The filter value for the BAdI is determined by the merge parameter. For more
information, see Parallel Processing [page 95].
○ Dyn Agt Sel Service
The service name is used so select an implementation of BAdI: Dynamic Selection of Agent in Rule-
Based Workflow in MDG Customizing under General Settings Process Modeling Workflow Rule-
Based Workflow Business Add-Ins . The implementation can overwrite various result values and
determine the user agent groups. You can use this BadI, for example, to determine the processors at
runtime based on data in the change request. For more information, see the documentation of BAdI:
Dynamic Selection of Agent in Rule-Based Workflow.
● User Agent Decision Table
The User Agent Decision Table DT_USER_AGT_GRP_<change request type> determines the
processors of the change request step that was returned as the next step by the Single Value Decision
Table. It also determines the change request step type that defines the possible actions the processors can
execute.
This table has the following condition column:
○ Condition Alias
The condition alias links the row in this table with corresponding rows in the Single Value Decision
Table.
This decision table has the following result columns:
○ User Agt Grp No.
Enter an arbitrary value in the column User Agt Grp No. and enter the processors in the column User
Agent Value. If you need more than one entry for User Agent Value to define the processors, enter the
same value for User Agent Group and Condition Alias in each row to create one user agent group.
You configure parallel processing of the change request step by entering different values for User Agent
Grp No. and the same condition alias. For each value in User Agent Grp No., a separate subprocess is
started. For more information, see Parallel Processing [page 95].
○ Step Type
The step type defines the possible actions for the processor in the change request step.
○ User Agent Type and User Agent Value
Identifies what kind of agent receives the work item in a change request. It can be a single user, an
organizational unit, a role, a job, a position, or a special user. The user agent value defines the agents a
work item can be sent to. It can be a user ID, or a user group ID. It can also point to rather than directly
identify the user agent – for example, with user agent type SU (single user), user agent value LAST
specifies the last processor and user agent value INIT specifies the requester of the change request.
● Non-User Agent Decision Table
This decision table determines the process patterns for background steps.

The Non-User Agent Decision Table DT_NON_USER_AGT_GRP_<change request type> contains the
background steps that are involved in the change request process and that do not have end user
participation.
This table has the following condition column:
○ Condition Alias
The condition alias links the row in this table with corresponding rows in the Single Value Decision
Table.
This decision table has the following result columns:
○ Agent Group
Enter an arbitrary value in this column to execute the operation in column Process Pattern in the
background.
If you are using parallel processing, create a row for each process pattern that should be executed in a
separate subprocess. Choose a different value in this column for each row. For more information, see
Parallel Processing [page 95].
○ Process Pattern
The Process Pattern controls the flow of the process and to define what the system shall perform in
this change request step. Frequently used values are:
○ 05 Activation (do not bypass snapshot)
Activates the change request, for example, after final approval.
○ 08 Roll Back Change Request
Removes all inactive data, for example, after the change request was rejected.
○ 99 Complete (Sub-)Workflow
Completes a workflow or a subworkflow. This process pattern is used, for example, in the last step
to end the change request process.
See Process Pattern [page 88] for a complete list of available process patterns.
○ Service Name
The meaning of this parameter depends on the process pattern. For example, it contains the workflow
template when creating a sub-workflow with process pattern 03 Call Sub-Workflow.
More Information
For information on how to create and enhance your rule-based workflow, see Creating a Basic Change Request
Process [page 89] and Add User-Agent Steps [page 92].
Application specific information on rule-based workflow is available in Rule-Based Workflows for Material.
8.4.3.2.2.1 Configuring the Rule-Based Workflow
Use
This document explains how to configure the rule-based workflow for a change request process that you have
described using a process diagram as explained in Designing the Change Request Process [page 76].

Prerequisites
● You have completed the Customizing settings as described in Workflow Set-Up [page 80].
● You have created a diagram of the change request process that you want to configure as described in
Designing the Change Request Process [page 76].
Process
● Enhance Process Diagram

Enhance the process diagram with further information required by the rule-based workflow. For each non-
user agent change request step, determine the appropriate Process Pattern [page 88] and add the
information to the diagram.
To activate the change request, you need to use the process pattern 06/Activation.
For each arrow pointing to a change request step, choose a 3 digit identifier for the condition alias. It is
common to use abbreviations of the step’s meaning for better readability, for example APP for an approval
step.

The arrow pointing to the change request step Activate is labeled with the condition alias ACT.
For information about an example of a process diagram that is enhanced for the rule-based workflow, see
Add User-Agent Steps [page 92].
● Create Change Request Type
In Customizing activity Create Change Request Type under General Settings Process Modeling
Change Requests , create the change request type for which you want to define the process flow. Assign
the rule-based workflow template WS60800086 to the change request type.
● Define Change Request Steps
In Customizing activity Define Change Request Steps for Rule-Based Workflow under General Settings
Process Modeling Workflow Rule-Based Workflow , define the process steps that are used in the
process diagram of your change request type.
● Service Names
In the case of a complex workflow scenario, for example, when using a handler to merge the results of
parallel processing, you need to define service names for the BAdI implementations that you need to use.
For more information, see the documentation of Customizing activity Define Service Names for Rule-Based
Workflow under General Settings Process Modeling Workflow Rule-Based Workflow .
● Build Decision Tables
Start Customizing activity Configure Rule-Based Workflow under General Settings Process Modeling
Workflow Rule-Based Workflow and enter your change request type to open the BRFplus workbench
and to enter the values for the decision tables.
 Note
If you perform this activity the first time for this change request type, the BRFplus application is
generated. Depending on the settings of the client, you are asked to assign a transport request and a
software component.
1. For each arrow in your process diagram, enter a row in the Single Value Decision Table
DT_SINGLE_VAL_<change request type>. Use the step numbers on each end of the arrow as the
values for CR Previous Step and New Chng. Req. Step. The action code of the previous step that

triggers this connection is the value for Previous Action. The labels on the arrow provide the values for
Condition Alias and New CR Status.
The arrow of this diagram leads to the following values in the decision table: CR Previous Step = 90. New Chng. Req.
Step. = 91. Previous Action = 03. Condition Alias = ACT. New CR Status = 02.
 Note
You can use the condition columns Chng. Req. Priority, Chng. Req. Reason, CR Rejection Reason,
CR Parent Step, and Parallel Agt Grp No. as additional parameters to make the process flow more
specific.
You can enter a time limit for the processors of the next change request step in Hours to Completion.
This uses the feature of the requested end deadline monitoring of the SAP Business Workflow. The
rule-based workflow will send a notification to all processors of this change request step as a reminder
to complete this task.
The result columns Merge Type and Merge Parameter are used for parallel processing. For further
information, see Parallel Processing [page 95].
Instead of providing values for the result columns in the decision table, you can provide a service name
in Dyn Agt Sel Service to link to an implementation of BAdI: Dynamic Selection of Agent in Rule-Based
Workflow. For more information, see the documentation of BAdI: Dynamic Selection of Agent in Rule-
Based Workflow in MDG Customizing under General Settings Process Modeling Workflow Rule-
Based Workflow Business Add-Ins .
2. For each user agent step in your process diagram, enter a row in the User Agent Decision Table
DT_USER_AGT_GRP_<change request type>. If you followed the recommendation in Designing the
Change Request Process [page 76] to use the same condition alias for all arrows that point to a change
request step, use this value for the column Condition Alias. If you use different aliases, you need to
create multiple rows, one for each alias.
Transfer the values for Step Type, User Agent Type, and User Agent Value from the diagram into the
table. The valid values for User Agent Type and User Agent Value are defined by your organizational
structure (for example, see Customizing activity Edit Organizational Plan) and identify an
organizational object, for example, the purchasing department. If you use SU for User Agent Type you
can use INIT (Initiator) as User Agent Value to select the requester of the change request as
processor. Furthermore, the value LAST for User Agent Value selects the processor of the previous step
as the processor.
If the overall group of processors for the change request step consists of multiple organizational
objects, create a row for each object. In this case and unless you want to configure parallel processing
of the change request step, use the same value for User Agt Grp No. for this condition alias.

You configure parallel processing of the change request step by using different values for User Agt Grp
No. for the same condition alias. For further information, see Parallel Processing [page 95].
The information from this diagram leads to the following values in the decision table: Condition Alias = APP. User
Agt Grp No. = 001 (arbitrary value). Step Type = 02. User Agent Type = AG. User Agent Value = MD Experts
(assuming there is a PFCG role named MD Experts and all users assigned to this role should be processors).
3. For each background step in your process diagram, enter a row in the Non-User Agent Decision Table
DT_NON_USER_AGT_GRP_<change request type>.
If you followed the recommendation in Designing the Change Request Process [page 76] to use the
same condition alias for all arrows that point to a change request step, use this value for the column
Condition Alias. If you use different aliases, you need to create multiple rows, one for each alias.
Transfer the value for Process Pattern from the diagram into the table. If required by the chosen
process pattern, specify the Service Name. Unless you want to configure parallel processing in this
change request step, choose any value for Agent Group, for example 001. For more information, see
Parallel Processing [page 95].
The information from this diagram leads to the following values in the decision table: Condition Alias = ACT. Process
Pattern = 06. Service Name = <not required>. Agent Group = 001 (arbitrary value).
 Caution
The decision tables are processed in sequence Therefore, the table entries should be arranged starting
with the most specific ones, followed by more general ones.

More Information
For information about examples of process diagrams related to the rule-based workflow, see Creating a Basic
Change Request Process [page 89] and Add User-Agent Steps [page 92].
8.4.3.2.2.2 Process Pattern

The rule-based workflow groups several workflow steps together to form basic operations that are called
Process Patterns. These patterns are used to control the flow of the change request process or to define which
background task the system will perform in a change request step.
Technically, the rule-based workflow runs in a loop. In each repetition of the loop, one out of several process
patterns is executed. The workflow continues to run in this loop until the change request process is ended with
the process pattern 99 Complete (Sub-)Workflow .
If the current change request step is a user-agent step, the used process pattern is 01 UI Dialog. For non-user
agent steps, the column Process Pattern in the Non-User Agent Decision Table
DT_NON_USER_AGT_GRP_<change request type> is used to determine the pattern.
The possible process patterns are:
● 01 UI Dialog
This process pattern is used by the system for user-agent change request steps and should not be entered
by you in the Non-User Agent Decision Table. It is a special process pattern that is always automatically
selected if a user agent has been found in the user agent decision table. This process pattern uses the
dialog task Dialog Processing TS60807954.
● 02 Call Synchronous Method
You can use this process pattern to include operations that are not provided from SAP. This process
pattern uses the background task Synch. System Method TS60807949. For more information, see BAdI:
Calling of System Method for Rule-Based Workflow in MDG Customizing under General Settings
Process Modeling Workflow Rule-Based Workflow Business Add-Ins .
● 03 Call Sub-Workflow
You can use this process pattern to start a sub-workflow. The background task Subworkflow for Single Step
Workflow TS60807994 starts a sub-workflow with the workflow template ID that is read from the column
Service Name of the non-user agent decision table.
● 04 Call Data Replication
You can use this process pattern to start the replication of the master data after the change request has
been activated. This process pattern uses the background task Change Request Replication TS60807976
and the method DISTRIBUTE of the object type MDG Change Request BUS2250 to replicate the object
using the data replication framework (DRF).
● 05 Activation (do not bypass snapshot)
You can use this process pattern to activate the data in the change request. This process pattern uses the
background task Activate Change Request TS60808002 with the indicator IGNORE_SNAPSHOT_DIFF not
set. The value of Previous Action is updated with the result of the operation enabling you to handle error
situations. If there have been conflicting changes to the data in the standard master data tables while the
change request was in process the activation fails. In this case, Previous Action is set to 33 Activation failed
for Snapshot. If the activation was successful Previous Action is set to 31 Activation Successful. In all other
cases, Previous Action is set to 32 Activation failed.

● 06 Activation (bypass snapshot)
You can use this process pattern to activate the data in the change request, even if the data has been
changed in the backend since the change request was created. The system ignores these potential
changes and overwrites them. This process pattern uses the background task Activate Change Request
TS60808002 with the indicator IGNORE_SNAPSHOT_DIFF set.
● 07 Validate Change Request
You can use this process pattern to validate the change request data. The results are written to the
application log. The process pattern uses the background task Check Change Request TS75707952.
● 08 Roll Back Change Request
You can use this process pattern to remove the inactive data of the change request from the staging area if
the change request should not be activated. This process pattern also provides the information when and
by whom the change request was released and sets the change request status to 06 Final Check Rejected.
The process pattern uses the background task Discard Change Request TS75707936.
● 98 Error
You can use this process pattern to handle errors and exceptions. The process pattern uses the
background task Error Handler TS60807951.
● 99 Complete (Sub-)Workflow
You can use this process pattern to end the rule-based workflow instead of looping back.
8.4.3.2.2.3 Creating a Basic Change Request Process
Use
This document describes how to enable a basic change request process using the MDG rule-based workflow.
This basic change request process only activates the change request after it was submitted. The process does
not include any dialog step. To provide data governance capabilities, you need to enhance the process adding
further change request steps such as approving the change request.
The figure in this document shows a complete process.

Basic MDG Change Request Process
The process starts with step 00 when the requester submits the change request. The next step 91 is the
activation of the change request. If the change request is successfully activated, its status is set to Final Check
Approved and the process ends with step 99. If the activation fails, the change request is rolled back in step 92,
the change request status is set to Final Check Rejected, and the process ends.
Prerequisites
You have created a change request type and you have entered the template for rule-based workflow
WS60800086 in Customizing activity Create Change Request Type under General Settings Process
Modeling Change Requests . In the following example configuration, the change request type CR_TYPE is
used.

Process
You need to perform the following steps in order to configure the rule-based workflow for the basic change
request process:
1. Create necessary change request steps.

Define the change request steps 00, 91, 92, and 99 as shown in the figure in Customizing activity Define
Change Request Steps for Rule-Based Workflow under General Settings Process Modeling Workflow
Rule-Based Workflow .
Change Request Type Change Request Step Description of Change Request Step
CR_TYPE 00 Request
CR_TYPE 91 Activation
CR_TYPE 92 Roll Back
CR_TYPE 99 Complete
2. Define decision tables.

For every change request type, there is a separate set of BRFplus decision tables that contain the
configuration of the change request process. You can start the configuration of the rule-based workflow in
Customizing activity Configure Rule-Based Workflow under General Settings Process Modeling
Workflow Rule-Based Workflow .
In the Single Value table of change request type CR_TYPE, you define the sequence of the steps. If a column
is not mentioned in the tables below it is not relevant for this process configuration. You have to add a row
in the Single Value table for each arrow in the figure to connect two change request steps and use the
following information from the figure:
○ Previous Change Request Step
○ New Change Request Step
○ Change Request Status
○ Change Request Action
○ Condition Alias
The first row of the Single Value table corresponds to the arrow from step 00 to step 91 in the figure: The
column CR Previous Step contains 00 and the column New CR Step contains 91. Since the first change
request step is the request step that produces no action result, the column CR Previous Action is left
empty. The column New CR Status contains 02 as the status of the change request in step 91. Finally, the
column Condition Alias contains the identifier ACT that you need to assign and that is used to connect this
row with rows in the other decision tables.
Single Value table
CR Previous Step CR Previous Action Condition Alias New CR Step New CR Status
00 n.a. ACT 91 02
91 =31 END 99 05

91 <>31 RB 92 02
92 n.a. END 99 06
The basic process contains only steps with background steps. Therefore, you only have to configure the
Non User Agent table and the User Agent table is left empty. In the figure all arrows pointing to the same
change request step have identical condition aliases. These condition aliases have been chosen to match
the process pattern of this step.
You have to add a row in the Non User Agent table for each change request step and use the following
information from the figure:
○ Condition Alias
○ Process Pattern
 Note
The column Agent Group is only relevant for parallel processing. Use the value 001 to create one work
item for a change request step.
If you look at the arrow with condition alias ACT from step 00 to step 91 with process pattern 05, the first
row in the Non User Agent table contains the condition alias ACT, agent group 001 and process pattern 05.
The following rows are needed in the Non User Agent table for the configuration of the complete basic
process:
Condition Alias Agent Group Process Pattern
ACT 001 05
RB 001 08
END 001 99
After you have saved and activated the new entries for the Single Value table and the Non User Agent table,
you can use the new change request type.
8.4.3.2.2.4 Add User-Agent Steps
Use
This document describes how to enhance the basic change request process with a user agent step. In the basic
process, a change request is immediately activated after the requester submits the change request without
further involvement of another user. In this enhanced process, a second user checks the change request in an
additional user-agent step. If this user decides to approve the change request, the activation is started with
change request step 91. Otherwise, the roll back of the change request is started with change request step 92.
The other change request steps are not changed.
 Note
The terms dialog step and user agent step are used as synonyms in MDG.

To enhance the basic process from the document Creating a Basic Change Request Process [page 89] to the
enhanced process described in this document, the new step 90 Final Check with step type 2 Approve Change
Request is added. The user symbol next to the step type indicates that this is a user-agent step. The arrow from
change request step 00 now points to the new change request step 90. The condition alias of this arrow was
chosen as FC to abbreviate Final Check. The arrow, depicting that the user has accepted the change request
with action 03, points to the change request step 91. The condition alias ACT for the change request step 91 is
added to the arrow. The arrow, depicting that the user has rejected the change request with action 04, points to
the change request step 92. The condition alias RB for the change request step 92 is added to the arrow.
Change Request Process Including a User Agent Step
Prerequisites
You have configured the rule-based workflow for the basic change request process, as described in Creating a
Basic Change Request Process [page 89]. In the following example process, the change request type CR_TYPE
and the user FINAL_CHECK_USER are used.

Process
You need to process the following steps in order to extend the basic workflow with a user step:
1. Create the new change request step.

The new change request step for the user dialog is defined in Customizing activity Define Change Request
Steps for Ruled-Based Workflow under General Settings Process Modeling Workflow Ruled-Based
Workflow .
Workflow Step Numbers
Type of Chg. Request CR Step Keys Validation Description
CR_TYPE 90 n.a. n.a. Final Check
2. Adapt and add lines to decision tables.

Comparing the figure Change Request Process Including Dialog Tasks with the figure Basic MDG Change
Request Process of the basic rule-based workflow you can see that you have to add new rows to the
decision table and also change existing rows of the decision table, because the first arrow from change
request step 00 to step 91 in figure Basic MDG Change Request Process has changed. In the figure Change
Request Process Including Dialog Tasks, the arrow points to the new change request step 90. The Single
Value table row with the previous change request step 00 has changed to the following:
00 n.a. FC 90 02
After this change, you have to add a new row to the Singe Value table for every arrow that is depicted in the
figure Change Request Process Including Dialog Tasks and not depicted in the figure Basic MDG Change
Request Process. You have to add the following rows to configure the new sequence of steps:
90 03 ACT 91 02
90 04 RB 92 02
In the basic rule-based workflow, only background tasks are used. In the enhanced workflow described in
this document, a dialog task is used. In the User Agent table, you have to configure the user agent group,
the change request step type, the user agent and the user agent value for the new change request step 90.
The following line with the condition alias FC for the new change request step is required:
Condition Alias User Agt Group Step Type User Agent Type User Agent Value
FC 001 02 US (User) FINAL_CHECK_USER

8.4.3.2.2.5 Parallel Processing
Use
The rule-based workflow allows the parallel processing of a change request for processors belonging to more
than one agent group. For example, you can define an approval step in which both one processor of the
controlling department and one processor of the purchasing department need to approve the change request.
Both groups of users will receive a work item for the processing of the change request at the same time and
can complete their work independent of each other.
Parent Step
The step from which parallel processing starts is called parent step. In contrast to regular change request
steps, you assign multiple agent groups to a parent step. For each assigned agent group, a subprocess is
started that is executed in parallel. The first step of each subprocess has the same step number as the parent
step. Therefore, the step number of the parent step and the agent group number of the subprocess are
additionally used to uniquely identify each step in subprocesses. The process that is started initially after the
change request was submitted is called root process.
Process Flow in Sub-Processes
Each subprocess is an instance of the rule-based workflow. Subprocesses provide the information of their
parent step and the agent group for which they were started. This information is used during the evaluation of
the single value decision table for determining the next change request step. Using these parameters in the
single value decision table, you separate the configuration of the process flow in the initial process from the
process flow in the subprocesses.
Ending of SubProcesses
Subprocesses have to be ended by using a change request step with the process pattern 99 Complete
(Sub-)Process.
When all subprocesses have ended, processing continues in the parent step by evaluating the action results of
the subprocesses. This is done by a result handler. For example, if any user of the two departments chooses to
reject the change request in a subprocess that the overall result of the parent step rejects the change request.
Result handlers are implementations of BAdI: Handling of Parallel Results in Rule-Based Workflow in MDG
Customizing under General Settings Process Modeling Workflow Rule-Based Workflow Business
Add-Ins and referenced by their service name.
For more information, see the documentation of BAdI: Handling of Parallel Results in Rule-Based Workflow.
Using the actions and steps returned by the subprocesses, the result handler returns a merge step and merge
action that are used in the next loop of the rule-based workflow to evaluate the single value decision table.
You need to specify the result handler in the row of the single value decision table that leads to the parent step
of the subprocesses. This is done by providing the value B in column Merge Type and the service name of the
result handler in column Merge Parameter.
Agent Groups
Agent groups are assigned to change request steps through the condition alias of the single value decision
table. User agent groups are defined in the user agent decision table for dialog steps. Non-user agent groups
are defined in the non-user agent decision table for background steps. Both types of groups are uniquely
identified by their group number and the condition alias.

User Agent Groups
A user agent group specifies the assigned processors of a change request step and the step type of the dialog
step. All users assigned to a user agent group will receive a workitem to process the change request step. You
can use multiple organizational objects to specify the members of the user agent group. In this case, you need
to create a row for each organizational object in the user agent decision table and use the same value in the
columns Condition Alias and User Agent Grp No.. This defines a user agent group with multiple rows.
You configure the parallel processing of a change request step by entering different values for User Agent Grp
No. and the same condition alias. For each value in User Agent Grp No., a separate subprocess is started.
It is not allowed to have rows with the same condition alias and the same user agent group, but different step
type, because a change request step can only have one change request step type. However, it is possible to
configure parallel steps that have different change request step types.
Non-User Agent Groups
A non-user agent group specifies the process pattern that should be executed in the background in a change
request step. A non-user agent group is defined by entering the condition alias, the agent group, and the
process pattern in the non-user agent group decision table.
You configure parallel processing of a change request step by entering different values for the agent group and
the same condition alias. For each value in the agent group, a separate subprocess is started to execute the
respective process pattern.
It is not allowed to have more than one row with the same values for the condition alias and the agent group,
because only one process pattern can be executed in each change request step. However, you can define
parallel background steps, in which process patterns are executed in parallel.
It is not allowed to have a row in the non-user agent decision table that has the same values for condition alias
and agent group as a row on the user agent decision table, because a change request step can only be either a
dialog or a background step. However, you can define two parallel steps, one as a dialog step and the other as a
background step.
Phases of Parallel Processing
The phases in which the rule-based workflow handles parallel processing are as follows:
1. After having evaluated the decision tables, it is checked whether there is more than one agent group
assigned to the change request step.
2. For each agent group, a new instance of the rule-based workflow is started. The already determined agent
group and the step number of the parent step are passed to the instance. In the parent step, the processing
is suspended until every subprocess has ended.
3. In the initial loop of the rule-based workflow, the agent group is already known and processing can directly
continue by creating the workitem for the dialog step or executing the process pattern in case of a
background step. After that, a new loop is started.
4. In the second loop, the action result of the previous step, the information of the parent step, and the agent
group of this sub-process are used to find a matching row in the single value decision table and to find the
assigned condition alias in the user agent decision tables and non-user Agent decision tables.
5. If a step with process pattern 99 End (Sub-)Process is found, the workflow ends and control returns to the
parent step. If there are further steps defined for the subprocess they are processed in further loops of the
subworkflow.
6. After all subprocesses have ended, the result handler is called. It uses the action results' return and the
change request step numbers' return by the subprocesses to determine a merge step and merge action.

Both values are used in the next loop of the rule-based workflow to query the decision tables and
processing continues until the root process is ended as well.
More Information
Rule-Based Workflow: Technical Details [page 97]
8.4.3.2.2.6 Rule-Based Workflow: Technical Details

This document explains how the rule-based workflow works by describing the workflow template of the rule-
based workflow and how this workflow template of the rule-based workflow uses the BRFplus application of a
particular change request type.
We deliver the standard workflow template WS60800086 for the rule-based workflow. This workflow template
consists of the following steps:
1. Start Workflow
An instance of the rule-based workflow template is started when a user submits a change request of a type
that has the rule-based workflow template assigned. The same workflow template is also used to create
sub-workflow instances for parallel processing.
2. Determine Change Request Type
The system determines the change request type; for example, Create Material or Change Material and
stores the change request type in the workflow container.
3. Check Assignment of Processor to Workflow
The system checks whether a processor is already assigned to the workflow, for example, the current
workflow instance is a sub-workflow that was started for parallel processing.
If a processor is not yet assigned, the system launches BRFplus. The BRFplus decision tables for the
change request type are used to find the next step, the process pattern, and the agents, based on the
previous step and action. If the current workflow instance is the main workflow, the system also refreshes
the status of the change request.
4. Determine Whether Single Processing or Parallel Processing is Configured
The system determines the number of configured agent groups of the current change request step. An
agent group can consist of a single user or multiple users. For example, it might be necessary that users in
the purchasing department and users in the accounting department should able to approve the change
request in parallel.
If more than one agent group is found, parallel processing is configured and the system proceeds as
follows:
1. The system creates multiple workflow instances of the WS60800086 template: one for each agent
group. These sub-workflows run in parallel.
2. As soon as all subworkflows are completed, the BAdI: Handling of Parallel Results in Rule-Based
Workflow in MDG Customizing under General Settings Process Modeling Workflow Rule-Based
Workflow Business Add-Ins is called in order to merge the results of the parallel subworkflows into
one result and, based on those results, determines the next step of the change request process.
5. Branch by Process Pattern
Based on the determined process pattern, the workflow branches into one out of several basic operations
of the rule-based workflow.

For more information, see Process Pattern [page 88]
6. Check Workflow Completion
The system checks whether the process pattern was 99 Complete (Sub-)Workflow.
○ If this is the case the system completes the workflow.
○ If this is not the case the system returns to step 3 and starts again.
8.4.4 Workflow Templates for Financials
The following workflow templates are available for Master Data Governance for Financials:
● Workflow Template WS72100012 [page 98]

Related Information
Configure the Financials Workflow [page 19]
8.4.4.1 Workflow Template WS72100012
SAP delivers the standard workflow template WS72100012 for the approval process. This enables you to
forward the change request as a work item to the appropriate processors. The status of the change request is
automatically updated in the background. The template is mandatory for cost center hierarchy or profit center
hierarchy maintenance if the objects are distributed using IDocs to the MDG client systems.
This workflow template consists of the following steps:
1. Start workflow
The workflow is started when a change request is created, for example, by a corporate accountant.
2. Get number of parallel steps
The system determines the number of users or user groups to which the change request needs to be sent.
3. Evaluate change request
A work item is sent to all responsible master data specialists. Each specialist independently evaluates the
change request and either agrees or disagrees with it:
○ If one or more specialists disagree with the change request, the work item with the change request is
sent back for revision to the corporate accountant ( → Step 4).
○ If all master data specialists agree with the change request, a work item with the change request is
sent to the master data manager for consideration and approval ( → Step 5).
4. Revision after rejection

The person responsible for processing the change request when it is rejected, such as the corporate
accountant, decides whether to revise the change request:
○ If he or she revises the change request, a work item with the change request is again sent to the master
data specialists for evaluation ( → Step 3).
○ If he or she withdraws the change request, the status of the change request is set to Final Check
Rejected. If changes have already been made to the master data, these are reset and the workflow is
ended ( → Step 10).
5. Consider and approve
The master data manager gets a work item to approve or reject the change request:
○ If he or she rejects the change request, a work item with the change request is sent back for revision to
the corporate accountant ( → Step 4).
○ If he or she approves the change request, a work item with the change request is sent to the master
data processor to execute the changes ( → Step 6).
6. Execute changes
The master data processor receives a work item to execute the changes:
○ If he or she is unable to execute the changes, he or she can send the change request back to the
corporate accountant. In this case, a work item with the change request is sent to the corporate
accountant for revision ( → Step 4).
○ If he or she is able to successfully execute the changes, the changes made to the master data are then
checked ( → Step 7).
7. Validate
The system checks the change request using validation rules for consistency, and saves the check results
in a log. Afterwards, the log is available in the change request.
8. Perform final check
The master data manager gets a work item to do a final check of the change request. He or she checks the
validation results in the log and then either approves or rejects the final check:
○ If he or she approves the change request, the system activates the changes. ( → Step 9).
9. Activate changes
The system activates the master data in the database tables of the modified objects according to the
changes entered in step 6.
 Note
The changes are then activated in the central system. When the workflow has been completed, the
changes still need to be distributed to the local systems. If a cost center hierarchy or profit center
hierarchy has been changed, the system creates MDG change pointers for the affected cost centers or
profit centers. After activation, the system triggers the distribution based upon the previously created
MDG change pointers. This ensures that both the hierarchies and master data is synchronized in the
MDG client system.
10. End workflow

The system ends the workflow.

automatically updated in the background.
1. Start workflow
The workflow is started when a change request is created, for example, by a corporate accountant.
2. Get number of parallel steps
The system determines the number of users or user groups to which the change request needs to be sent.
A work item is sent to all responsible master data specialists. Each specialist independently evaluates the
change request and either agrees or disagrees with it:
○ If one or more specialists disagree with the change request, the work item with the change request is
sent back for revision to the corporate accountant ( → Step 4).
○ If all master data specialists agree with the change request, a work item with the change request is
sent to the master data manager for consideration and approval ( → Step 5).
○ If he or she revises the change request, a work item with the change request is again sent to the master
data specialists for evaluation ( → Step 3).
○ If he or she withdraws the change request, the status of the change request is set to Final Check
ended ( → Step 10).
The master data manager gets a work item to approve or reject the change request:
○ If he or she approves the change request, a work item with the change request is sent to the master
data processor to execute the changes ( → Step 6).
6. Execute changes
The master data processor receives a work item to execute the changes:
○ If he or she is unable to execute the changes, he or she can send the change request back to the
corporate accountant. In this case, a work item with the change request is sent to the corporate
accountant for revision ( → Step 4).
○ If he or she is able to successfully execute the changes, the changes made to the master data are then
checked ( → Step 7).
7. Validate
The system checks the change request using validation rules for consistency, and saves the check results
in a log. Afterwards, the log is available in the change request.
The master data manager gets a work item to do a final check of the change request. He or she checks the
validation results in the log and then either approves or rejects the final check:

○ If he or she approves the change request, the system activates the changes. ( → Step 9).
9. Activate changes
 Note
The changes are then activate in the central system. When the workflow has been completed, the
changes still need to be distributed to the local systems.
10. End workflow

automatically updated in the background.
1. Start workflow
The workflow is started when a change request is created by the user, for example, a corporate accountant.
2. Execute changes
The master data specialist receives a work item to execute the changes:
○ If they do not want to execute the changes, they can send the change request back to the corporate
accountant. In this case, a work item with the change request is sent to the corporate accountant for
revision ( → Step 3).
○ If they want to execute the changes, the changes made to the master data are then checked ( → Step
4).
○ If he they revise the change request, a work item with the change request is again sent to the master
data specialist for processing ( → Step 2).
○ If they withdraw the change request, the status of the change request is set to Final Check Rejected. If
changes have already been made to the master data, these are reset and the workflow ends ( → Step
6).
The system checks the change request, using validation rules for consistency, and saves the check results
in a log. The master data steward receives a work item to do a final check of the change request. They
check the validation results in the log and either approve or reject the final check:
○ If they reject the change request, a work item with the change request is sent back for revision to the
corporate accountant ( → Step 3).
○ If they approve the change request, the system activates the changes ( → Step 5).
5. Activate changes

 Note
The changes are then activated in the central system. When the workflow has been completed, the
changes still need to be distributed to the local systems.
6. End workflow

SAP delivers the standard workflow template WS75700043 for the approval process.
This enables you to forward the change request as a work item to the appropriate processors. The status of the
change request is automatically updated in the background.
 Note
You define in the Customizing for Financial Master Data Management, under Workflow/Process Modeling
Assign Processor to Workflow Step (Advanced Workflow) , whether one or more responsible processors
receive a work item in their worklists for the workflow steps, dependent on the entity type (for example,
entity type Account).
1. Start workflow
The workflow is started when a requester creates a change request in the universal worklist in the portal.
2. Determine number of processors for parallel steps
In the next workflow step, the system determines the number of users or user groups to which the change
request needs to be sent.
The Customizing for Financial Master Data Management lets you configure the system to do so dependent
on the entity type of the objects contained in the object list of the change request, under Workflow/
Process Modeling Assign Processor to Workflow Step (Advanced Workflow) .
The respective processors automatically receive a work item in their universal worklist and evaluate the
change request independently of one another. The system then determines the number of approvals and
objections:
○ If one or more processors objects to the change request, the requester receives an information SAP
express mail as soon as all the processors have evaluated the change request (→ step 4).
○ If all the processors approve the change request, the processors responsible for the consideration and
approval receive a work item in their worklists (→ step 5).
4. (Optional) SAP express mail after objection
The requester receives an SAP express mail in his or her Business Workplace indicating that one or more
processors objected to the change request. The employees responsible for the consideration and approval
also receive a work item in their worklists (→ step 5).
The respective processors have received a work item in their worklists and consider the change request
independently of one another. The system then determines the number of approvals and rejections:
○ If one or more processors reject the change request the requester automatically receives an SAP
express mail for each rejection (→ step 6).

The change request is then also submitted to a consideration committee, which meets regularly (→
step 7).
○ If all the processors approve the change request, the processors responsible for changing the master
data receive a work item in their worklists (→ step 9).
6. (Optional) SAP express mail after rejection
The requester receives an SAP express mail in his or her Business Workplace indicating that one or more
processors rejected the change request (→ step 7).
7. (Optional) Consider in committee
A committee that meets regularly discusses and considers the change request.
The responsible employee has also received a work item in his or her worklist, documenting the
committee's decision in the workflow process:
○ If the committee decides that the change request should be deleted, the processor rejects the change
request. The requester then receives the work item in his or her universal worklist to cancel the change
request (→ step 8).
○ If the committee decides that the change request has to be revised, the processor rejects the change
request. The requester then receives the work item in his or her universal worklist to revise the change
request (→ step 8).
○ If the committee approves the change request, the processor approves the change request. The
processors responsible for changing the master data then receive a work item in their universal
worklists (→ step 9).
8. (Optional) Revision after rejection
The requester has received a work item to process the change request further:
○ If the requester revises the change request, a work item with the change request is sent to the
processors again for evaluation (→ step 3).
○ If the requester withdraws the change request, the status of the change request is set to Final Check
over (→ step 13).
9. Execute changes
All the relevant processors from the responsible organizational units have received a work item in their
worklists independently of one another. They execute the changes as described in the change request. To
do so, they change the master data for every object in the object list and then confirm the change manually
in their universal worklists.
Once all the changes have been executed, the system validates the change request (→ step 10).
 Note
The responsible processors cannot add any new objects to the object list.
10. Validate
The system checks the change request using validation rules for consistency, and saves the check results.
The relevant employees from the responsible organizational units also receive a work item in their universal
worklists to perform the final check of the change request.
The relevant employees from the responsible organizational units have received a work item in their
universal worklists to perform the final check of the change request.
They check the validation results and make the following decision:
○ If a processor decides that the change request should be deleted, he or she rejects the change request.
The responsible organizational unit then receives the work item in their universal worklist to cancel the
change request (→ step 8). The requester also receives an SAP express mail for information.

○ If a processor decides that the change request needs to be revised, he or she rejects the change
request. The responsible organizational unit then receives a work item and revises the change request
(→ step 8).
○ If a processor approves the change request, he or she approves the change request. The system then
activates the changes (→ step 12).
12. Activate changes
 Note
The changes are then activated in the central system. When the workflow is over, the changes still need
to be distributed to the local systems.
13. End workflow

8.4.5 Scope for Hierarchy-Specific Changes
Definition
You can determine the extent to which users can make parallel changes to a hierarchy that belongs to a
particular hierarchy type. A change to a hierarchy can comprise adding a node, moving a node, removing a
node, changing the attributes of a node, or creating a hierarchy. After a change to a hierarchy is saved to a
change request, changes to interlocked nodes must be saved to the same change request. The system
determines which nodes are interlocked by referring to the Interlocking setting in Customizing for the relevant
hierarchy type.
Hierarchy nodes that represent business objects are technically distinct from the business objects themselves.
Interlocking affects the parallel processing of hierarchy nodes only.
Concept
The Interlocking Setting
You can define the scope of interlocking in Customizing for Master Data Governance under Process Modeling
Hierarchies Define Scope for Changes
The Interlocking setting applies to a Hierarchy Type and specifies which nodes besides the node being changed
are interlocked while a hierarchy-specific change is in process. The setting is described in the table below:
Interlocking Setting Interlocked Nodes
Loose Nodes assigned to the parent node of the node being

changed.

Interlocking Setting Interlocked Nodes
Strict Interlocking propagates upwards and downwards from the

parent node of the node being changed:
● Upwards interlocking interlocks the parent node and

its assigned nodes, the parent node of the parent node
and its assigned nodes, and so on up to the root node.
● Downwards interlocking interlocks child nodes of the
parent node, their child nodes, and so on down to the
end nodes. This comprises a subhierarchy of inter
locked nodes with the parent node at its root.
When applying the Interlocking setting, be aware of the following:
● Choosing the scope for hierarchy-specific changes involves striking a balance between centralized control
and process efficiency.
● The Interlocking setting also defines the locking of nodes to avoid competing changes by multiple users
who work on the hierarchy at the same time.
Prerequisites
To minimize business disruption, we recommend that you define the scope for changes to a hierarchy type
when you define the hierarchy type within a data model. You can only change the scope for changes to a
hierarchy type when no pending change requests exist for any hierarchy of this type. If you must change the
scope after you have defined the hierarchy type and you must then transport your changes, ensure that no
pending changes exist for the affected hierarchies in the target system.
Example
The hierarchy called Global consists of continents, countries, cities, and teams. A change request to add Rome
as a child node to Italy as the parent node is pending. No other hierarchy-relevant change requests are
pending. If you want to change nodes that are specified as Interlocked in the figures and descriptions below,
you must use the pending change request that assigns Rome to Italy. For changes to other nodes, you can use
separate change requests.
Interlocking – Loose
The figure below shows how the Interlocking setting of Loose affects a hierarchy in the scenario where Rome is
added to Italy.

Interlocking – Loose
Loose interlocking affects all nodes that are assigned to the parent node of the node being changed. The
node being changed is Rome and its parent node is Italy. Only the direct child nodes of Italy - Rome and Milan -
are interlocked with the pending change request.
Interlocking – Strict
The figure below shows how the Interlocking setting of Strict affects a hierarchy in the scenario where Rome is
assigned to Italy in a pending change request.

Interlocking - Strict
Upwards Interlocking
All nodes in the path from Italy to Global are interlocked. The child nodes of these nodes are also interlocked.
Affected nodes include the following:
● Italy (parent node), Rome and Milan (child nodes)

● Europe (parent node of parent node), France and Italy (child nodes)
● Global (root node), Asia and Europe (child nodes)
Downwards Interlocking
All nodes in the subhierarchy below Italy are interlocked. Affected nodes include the following:
● Cities Rome and Milan, which are below country Italy (Also covered by upwards interlocking)
● Teams I and J, which are below city Rome
● Teams K and L, which are below city Milan
● Any other nodes that might be added in the future to any nodes descending from Italy

8.4.6 Enabling Detailed Analysis of Change Requests
Use
You can apply system settings that allow you to monitor in detail how effectively your organization processes
change requests. You can analyze the statuses of change requests in your organization, the processing times of
change requests in your organization, and the nature of change requests involving you. For more information,
see Analysis of Change Requests.
Procedure
Enabling the detailed analysis of change requests involves completing the following tasks:
1. Configuring Operational Data Provisioning

2. Activating Business Information (BI) Content in Master Data Governance
3. Setting up the business context viewer
4. Assigning roles to your user
5. Changing authorization objects
6. Integrating SAP BusinessObjects Dashboards
7. (Optional) Defining a service-level agreement
Configuring Operational Data Provisioning
For more information, see Operational Data Provisioning.
Activating BI Content in Master Data Governance
You use Business Information (BI) content to analyze change requests.
To activate the content, proceed as follows:
1. Run transaction BSANLY_BI_ACTIVATION.

2. Choose the 0MDG_ANLY_CR_PROCESS content bundle.
3. Optional Step: If you want to identify and fix the errors that would occur if you activated the content
bundle, choose the Simulate Activation button.
4. To activate the content bundle, choose the Activate button.
Setting Up the Business Context Viewer
You must activate the business context viewer to be able to access side panels for the following Web Dynpro
applications that are used in the analysis of change requests:
● Processing Time (List View)(MDG_MONITOR_CR_PROCESTIME).

● My Change Requests(USMD_EDITION_CREQUEST)
You can refer to the following documents:
● For instructions on how to activate the business context viewer, see Business Context Viewer in Single
Processing.
● For more information about the business context viewer, see Business Context Viewer (BCV).

● For more information about side panels, see Side Panel
.
You can only access the side panels after you change the authorization object Business Context Viewer
Execute Side Panel (BCV_SPANEL). Instructions on how to do this are provided in the Changing Authorization
Objects section of this document.
 Note
After you activate the business context viewer, you can configure a side panel for any Web Dynpro
application.
Assigning Roles to Your User
You need to assign roles to your user. For more information, see .Authorization Concept in Business Context
Viewer (BCV)
Roles to Access Web Dynpro Applications
Investigate if the role or roles you already have allow you to access the following Web Dynpro applications:
Web Dynpro Application Description
MDG_MONITOR_CR_PROCESTIME Used for the analysis of the status of change requests or the
processing time of change requests.
MDG_ANLY_CR_REJ_REASON Used to display the reasons why change requests were re
jected.
USMD_EDITION_CREQUEST Used to display change requests involving you.
 Note
You can view and edit roles using transaction PFCG. The Menu tabbed page shows Web Dynpro
applications. Often, existing roles that use the required Web Dynpro applications have technical names with
suffixes of *_MENU.
If you do not have the required roles, consider the following options:
● Assign the Master Data Governance: Analytics (SAP_MDGA_MENU) role to your user.
This role only contains the relevant Web Dynpro applications.
● Create your own role and add the Web Dynpro applications to that role.
If you do this, you can control the placement of Web Dynpro applications on the menu in the user interface.
Changing Authorization Objects
You must modify authorization objects to accomplish the following:
● Specify the change request types to be analyzed and the level of access required
● Specify the Web Dynpro applications requiring a side panel.
For every role associated with the relevant Web Dynpro applications, proceed as follows:
1. Call up transaction PFCG.

2. Enter the name of the role and choose the icon.
3. Open the Authorizations tab page and, in Maintain Authorization Data and Generate Profiles section, choose
the icon.
4. Change the relevant authorization objects as shown in the following table:
Authorization Object Purpose Parameter Settings
SAP Master Data Specify the types of change Change Request Type Specify the level of the ac
Governance Type of requests users are allowed cess allowed to each the
to analyze and the level of change request types speci
Change Request
access allowed. fied under Activities. As a
(USMD_CREQ)
minimum, choose Display.
Choose other options, if re
quired.
Activities Specify which change re

quest types can be ac
cessed. You can use the *
symbol as a wildcard for the
entire technical name or for
part of the technical name
of the change request type.
 Caution
Be careful when using
wildcards; you do not
want to accidentally
provide access to incor
rect change request
types.

Authorization Object Purpose Parameter Settings
Business Context Viewer Specify the Web Dynpro ap Context Key Enter the following context
Execute Side Panel plications requiring a side keys:
(BCV_SPANEL) panel. ○ MDGAF_MYCR

The application is the
Application Framework
(MDGAF) and the object
is My Change Requests
(MYCR). Specifying this
context key enables a
side panel for the My
Change Request
screen.
○ MDGAF_ANLY
The application is the
Application Framework
(MDGAF) and the object
is (ANLY). Specifying
this context key ena
bles a side panel for the
Status (Graphic View)
screen, which is used
to analyze the status of
change requests.
Activity Specify an activity of 16,

which allows you to execute
the side panel.
Front End Integration Xcel Authorization for working RSXCLSID Specify the technical name
sius Dashboard with SAP BusinessObjects of the dashboard:
(S_RS_XCLS) Dashboards. 0XC_MDG_MONITOR_CR.
Activities Specify the level of the ac

cess allowed to dashboards.
As a minimum, choose
Display. Choose other op
tions, if required.
RSZOWNER Specify the owner of the

dashboard for a reporting
comment. We recommend a
value of “*” to provide uni
versal ownership.
5. Save the authorization profile and choose the icon.
Integrating Dashboards

For an overview of how to integrate dashboards, see SAP Help Portal Business Intelligence Xcelsius
Enterprise Integration .
SAP Business Objects dashboards only work if a BI Java server is enabled. For more information, see SAP Note
1450981
(Optional) Defining a Service-Level Agreement
A change request is late if it exceeds its due date (an optional field of the change request) or if it violates a
Service Level Agreement (SLA). You can define the SLA in Customizing for priorities of change request types.
To define a service level agreement for each priority of a change request type, proceed as follows:
1. In Customizing for Master Data Governance, Central Governance, choose General Settings Process
Modeling Change Requests Create Change Request Type
2. In the Type of Change Request view, choose a Change Request Type
3. In the Service Level Agreement view, define a target number of days and hours for each Priority.
When specifying hours, you can only specify 4 hours, which is a half day.
Result
After completing this procedure, it is possible to access meaningful analytical information about change
requests.
8.5 Governance Application Programming Interface
Use
For greater flexibility you want to be able to develop new UIs that enhance your Master Data Governance
applications and are consistent with the existing software. A number of developments in the Master Data
Governance Application Framework (MDGAF) allow you greater freedom to build UIs for applications.
● Governance API
● Convenience API
● Application Context API
● Communicator
● Change Request UI Building Block (CRUIBB)

The configuration of components is shown below:
All interactions between applications and MDGAF are now handled by either the Governance API or the
Convenience API. It is not possible to use the Convenience API and the Governance API at the same time for
the same model. This restriction is introduced to prevent misuse of the both APIs.
Features
Governance API
The Governance API covers the entire governance process, handling processes that are not UI-related, and
background services such as master data load and data replication.
The Governance API is designed to handle multiple change requests simultaneously. At any time, one instance
of the Governance API can exist in the system per data model.
The Governance API also provides services to the convenience API. There is less grouping of functions than in
the Convenience API so that you can combine a greater range of individual methods to meet the needs of the
application. The Governance API also provides services for UI issues, but the applications access these
services through the Convenience API, which then calls the Governance API.
The Governance API Class ID is CL_USMD_GOV_API (IF_USMD_GOV_API).

Convenience API
The Convenience API provides the functionality needed for an application to work with a change request. It can
handle one change request for a single data model at a given time. The Convenience API takes over all
governance-relevant logic such as managing change request data, handling change requests, and routing
change requests to the Governance API. The Convenience API groups together some of the methods of the
Governance API ensuring tighter control of the change request-handling capability available to the applications,
and simplifying the use of UI services for applications. The application manages only the application data.
The Convenience API Class ID is CL_USMD_CONV_SOM_GOV_API (IF_USMD_CONV_SOM_GOV_API).
Application Context API
The Application Context API stores context-specific runtime information at a central point so that this
information is accessible for other parts of the application and can be used to control the program-flow.
Previously the system did not provide application context information such as what change request is being
processed and whether the master data object is to be created or updated. The Application Context API
provides a consistent, reliable solution to this problem.
The following context information is available:
● Data model
● Business activity
● Workflow information
○ Change request
○ Change request type
○ Change request step
○ Change request index (relevant for parallel processing)
○ Workflow item
● Application parameter data (stored in the Workflow Container, not accessed by MDG)
The Application Context API offers the following advantages:
● Allows existing UIs to access the application context without using the complete Governance API
● Keeps existing interfaces stable
● Increases flexibility.
While, for example, the Governance API or Convenience API can only be instantiated for a data model, the
Context API is directly available to MDGAF components such as a UI application or background process.
● Manages application-specific context data
Application-specific context data is stored within the workflow container. This enables you to provide
application-specific context data throughout the workflow.
The Application Context API Class ID is CL_USMD_APP_CONTEXT.
Communicator
The Communicator allows the user to work with the change request and ensures consistency of change
request handling prerequisites, such as change request type, change request ID, and work item ID. When a user
begins working with a change request, the Communicator recognizes missing parameters and initiates user
interaction accordingly, for example, requesting the user to specify a change request type if none has yet been
specified.
Change Request UI Building Block (CRUIBB)

This UI component is included in application-specific UIs and handles the presentation of change request data
in Web Dynpro applications, ensuring a consistent UI layout for change request data across all applications.
The CRUIBB contains data such as CR description, priority, reason for CR, notes, and attachments.
Applications need to manage the application data only.
8.6 Configuring Hierarchy Types
Use
A hierarchy is tree-like structure consisting of hierarchy nodes that is identified by its hierarchy name. The
hierarchy type defines which objects can be used as nodes. The configuration of hierarchies is centered around
the hierarchy type. You use entity types in the MDG Data Model to create a hierarchy type.
 Example
An airline hierarchy has a hierarchy type based on entity type Airline (CARR) and a hierarchy name based on
entity type Names of Hierarchies of Airlines (CARR_HIER)
Integration
● You can start processing hierarchies from the results list of the Generic Search application, if it is
configured for use with hierarchies. For more information, see Search Business Object.
● Collective Processing (USMD_ENTITY) allows users to structure and restructure a hierarchy. For more
information, see Collective Processing.
● You can open single-object processing for individual business objects displayed in the List View and in the
Hierarchy view of the Collective Processing application. For more information, see Single-Object Processing
● (Applicable to selected business object types in SAP Master Data for Custom Objects and SAP Master Data
Governance for Financials only) You can assign individual business objects to hierarchies in the Hierarchy
Assignment block of Single-Object Processing, if the appropriate change request type is configured. For
more information about the end user process, see Hierarchy Assignments in Single-Object Processing
 Note
After working with a hierarchy assignment, users must finalize the change request before the system
allows them to add, delete, remove, or change the hierarchy properties of other hierarchy nodes that
have the same parent node.
● You can upload and download hierarchies in the relevant applications. For more information, see the
following:
○ File Upload (USMD_FILE_UPLOAD)
○ File Download (USMD_FILE_DOWNLOAD)
● You can change multiple master data objects at the same time through integration with the Mass Change
process.

● When you change data in Collective Processing, the process of either creating a new change request or
assigning an existing change request to your changes is supported.
Procedure
 Note
All paths to Customizing mentioned in this document are in Customizing for Master Data Governance,
Central Governance under General Settings.
When configuring hierarchy types, you need to answer the following questions, which are grouped based on
their corresponding settings:
● Data Modeling: Which entity type is a used as a hierarchy type? Is the hierarchy type synchronized? Is the
hierarchy type version-dependent?
● Data Modeling: Is the hierarchy type edition dependent?
You can use editions to schedule changes to business objects and hierarchies. For more information, see
Using Editions to Schedule Changes.
● Data Modeling: Which other entity types can be represented as nodes in hierarchies of this hierarchy type?
Which entity type defines the root node (Hierarchy Name)? For which entity types in the hierarchy are
ranges permitted on end nodes?
● Data Modeling: How do you define the relationships between nodes in a hierarchy of this hierarchy type?
For example, you can set credit / debit balances indicators on the account assignment in a financial
reporting structure.
● Data Modeling: What authorizations on the various levels of the hierarchy should the nodes have?
● UI Modeling: Do you want to create a user interface for single-object processing that allows assignment of
single objects to hierarchies?
● Process Modeling: If the hierarchy type is version-dependent, which versions are defined?
● Process Modeling: Which change request types are defined for the creation and processing of hierarchy
types?
● Process Modeling: When a user creates a change request for a hierarchy assignment, which nodes does
the system interlock with the pending change request?
● Data Quality and Search: Which validations apply to the relationships between hierarchy nodes?
● When a hierarchy node is expanded in the Collective Processing user interface, how many nodes should
display?
Data Modeling: Which entity type is a used as a hierarchy type? Is the hierarchy type synchronized? Is it
version-dependent?
The Is Hierarchy Type setting specifies which entity types are used as hierarchy types (described in the table
below), and whether the relevant hierarchies have versions and are synchronized. Hierarchy types define which
business objects can be used as nodes in the hierarchy. Synchronized hierarchies are useful if you want to
reuse subhierarchies in multiple hierarchies. Version-dependent hierarchies are useful if alternative views of
data are required for planning purposes.
Customizing Activity: Data Modeling Edit Data Model

View: Inactive Data Models Entity Types
Setting: Is Hierarchy Type
Values: ● If the entity type is used as a hierarchy type, the field

starts with Yes.
Requirement:
Assign the storage and use type 1 (Changeable via
Change Request) to this entity type.
Example:
A profit center group is the hierarchy type of a profit
center hierarchy.
● If versions of hierarchies can exist, the field starts with
Yes and states that the hierarchy type is Version
Dependent.
Example:
The hierarchy can have a planning version and a current
version.
● If subhierarchies must be synchronized in all hierarchies
they belong to, the field starts with Yes and states that
the hierarchy type is Synchronized
Example:
The structure of the synchronized subhierarchy Oyster
Airline Allianceis mirrored in hierarchy Airline Alliances -
Regional and hierarchy Airline Alliances - Tiered.
Version-Dependent Hierarchies
If the Oyster Airline Alliance hierarchy is version dependent, it can have a planning version and a current
version. If it is not version dependent it can only have one version (see figure below).

Is Hierarchy Type Setting With and Without Version Dependency
Synchronized Hierarchies: Example
You have indicated in Customizing that Hierarchy type Airline (CARR) is synchronized. Airlines are the main
building block within airline alliances. As a result of airlines being synchronized across airline alliances, the
addition of a new airline to subhierarchy Alliances Regional EU Oyster Airline Alliance is mirrored in
subhierarchy Alliances - Tiers Tier 1 Oyster Airline Alliance . If the hierarchy type Airline is not
synchronized, no mirroring occurs (see figure below).

Is Hierarchy Type Setting With and Without Synchronization
Data Modeling: Is the hierarchy type edition dependent?
View: Inactive Data Models Entity Types
Setting: Validity Concept for Hierarchy

Values: ● Edition.
Hierarchies can use Editions. For more information, see
Using Editions to Schedule Changes.
 Note
If you create an edition-dependent hierarchy, all
business objects that belong to that hierarchy and
for which you have created user interface building
blocks (UIBBs) in single-object processing, must
also be edition-dependent.
● No Edition
Hierarchies cannot use editions.
Data Modeling: Which other entity types can be represented as nodes in hierarchies of this hierarchy
type? Which entity type defines the root node (Hierarchy Name)? For which entity types in the hierarchy
are ranges permitted on end nodes?
You specify the entity types that can be represented as nodes in a hierarchy. Each Entity Type has a designated
use.
View: Inactive Data Models Entity Types Entity Types for
Hierarchies
Setting: Use
Values: ● Hierarchy Name

The root node of the hierarchy. This defines that this hier
archy can be processed using change requests and
therefore this entity type has to be defined with storage
and use type 1 (Changeable via Change Request). Each
hierarchy type must have just one hierarchy name.
● No Special Use
Default setting for all entity types you add to the hierar
chy. You can define master data objects such as profit
centers as hierarchy nodes. You can also add text nodes.
The entity types for added nodes can be of storage and
use type 1, 2, and 3.
● Ranges Permitted on End Nodes
You can allow the definition and the adjustment of ranges
for the leaf nodes of the hierarchy by changing the de
fault setting of No Special Use to this setting. For the
boundaries of the range no existence check is performed
Data Modeling: How do you define the relationships between nodes in a hierarchy of this hierarchy type?

Views: ● Inactive Data Models Entity Types Entity Types
for Hierarchies Hierarchy Attributes

For example, you can set credit/debit balances indica
tors on the account assignment in a financial reporting
structure. You can specify a hierarchy attribute for a re
lationship using a data element. You can specify an al
ternative data element if it is technically identical. .
● Inactive Data Models Entity Types Entity Types
for Hierarchies Hierarchy Attributes from
References
For example, you can set credit/debit balances indica
tors on the account assignment in a financial reporting
structure. You can specify a hierarchy attribute for a re
lationship using a reference to an entity type. If you
want to add hierarchy attributes to the relation of the
entity type for which the hierarchy has been defined you
have to specify it in the Entity Types for Hierarchies view
Data Modeling: What authorizations at the various levels of the hierarchy should hierarchy nodes have?
In the Customizing activity Define Authorization Relevance per Entity Type, you can determine whether
authorization is relevant for objects on every level of the hierarchy (see table below).
Customizing Activity: Data Modeling Define Authorization Relevance per
Entity Type
This activity indicates which parts of the hierarchy are au

thorization relevant, but does not define the authorizations
themselves.
More Information The authorization object for master data is USMD_MDAT and
the authorization object for hierarchies is USMD_MDATH. The
standard role for a Master Data Governance Administrator is
SAP_MDG-ADMIN
For more information, see Authorization Objects and Roles

Used by SAP MDG, Central Governance
UI Modeling: Do you want to create a user interface for single-object processing that allows assignment of
single objects to hierarchies?
You can adapt the single-object processing user interface so that it includes a Hierarchy Assignment block (see
link in table below.)

More Information For general information about creating a single-object proc
essing user interface, see Creating User Interfaces for Single
Object Processing [page 67].
For hierarchy-specific information, see Creating a UI for Hier

archies.
Process Modeling: If the hierarchy type is version-dependent, where are the versions defined?
You can define hierarchy versions in Customizing.
Customizing Activity: Process Modeling Create Hierarchy Versions
Hierarchy versions are valid for all data models in your MDG
system landscape.
Process Modeling: Which change request types are defined for the creation and processing of hierarchies?
You can create change requests that are relevant both to single-object processing and collective processing of
hierarchies. The initial settings are described in the table below.
Customizing Activity: Process Modeling Change Requests
Before You Start Identify which entity type is used as the hierarchy type, by
referring to the following section of this document:
Data Modeling: Which entity type is a used as a hierarchy

type? Is the hierarchy type synchronized? Is the hierarchy
type version-dependent?

Views and Settings: ● Type of Change Request
○ Main Entity Type
○ If you are creating a change request type for
an entire hierarchy, the main entity type you
specify is the hierarchy type.
○ If you are creating a change request type for
single-object processing with hierarchy as
signment, the main entity type is the business
object type being changed. You specify the hi
erarchy type later as one of the entity types in
Type of Change Request Entity Type

○ Edition Type:
Specify an edition type if the main entity type is ed
ition dependent.
○ Single-Object:
○ Select this checkbox if change requests are
relevant to single-object processing with hier
archy assignments. For more information, see
Hierarchy Assignments in Single-Object Proc
essing.
○ Deselect this checkbox if change requests are
relevant to hierarchy processing. For more in
formation, see Hierarchy Assignments in Col
lective Processing.
● Type of Change Request Entity Type

Include all the entity types that are involved in the
change request type. Ensure that one of the entity types
listed matches the Hierarchy Type.
 Example
This example is for change request type CCT2P2 that
can be used to create a cost center and that allows hier
archy assignments in the creation of the cost center.
● Type of Change Request

○ Type of Change Request: CCT2P2
○ Description: Create Cost Center with
Hry. Assignments
○ Main Entity Type: CCTR. This is the entity type
for a cost center, on which the change request
type is based.
○ Edition Type: OG_ALL.
○ Single-Object: Checkbox selected as this is a
change request type to create individual cost
centers.

○ Type of Change Request Entity Type
○ CCTR
○ CCTRG. This entity type represents the
cost center group, which is the hierarchy
type.
○ CCTRH
More Information: Configuration of the Change Request Process [page 75]
Process Modeling: When a user creates a change request for a hierarchy assignment, which nodes does
the system interlock with the pending change request?
Customizing Activity: Process Modeling Hierarchies Define Scope for
Changes
View: Scope for Changes
Setting: Interlocking
Values: Loose interlocking interlocks nodes assigned to the parent

node of the node being changed.
Strict interlocking propagates upwards and downwards from

the parent node of the node being changed.
● Upwards interlocking interlocks the parent node and its

assigned nodes, the parent node of the parent node and
its assigned nodes, and so on, up to the root node.
● Downwards interlocking interlocks child nodes of the
parent node, their child nodes, and so on, down to the
end nodes. This comprises a subhierarchy of inter
locked nodes with the parent node at its root.
More Information Define Scope for Changes [page 20]
Data Quality and Search: Which validations apply to the relationships between hierarchy nodes?
You can add validations for relationships between hierarchy nodes using the BRFplus or using BAdI: Define
Validations/Derivations in Customizing. For example, you can define specific cardinalities such as single higher-
level nodes.
Examples of validations that you can create include the following:
● Do not allow the same business objects in the same hierarchy twice.
● Generate an error message if a business object is not assigned to a hierarchy.
● Do not repeat a business object in the same subhierarchy.
Tool BRFplus

Complimentary Coding Data Quality and Search Business Add-Ins BAdI:
Define Validations/Derivations
More Information Definition of Validations and Derivations in BRFplus
User Parameter: When a hierarchy node is expanded in the Collective Processing user interface, how many
subnodes should display?
For faster screen load and a reduction in user scrolling, you can control the number of subnodes that display
when a node is expanded. The user can click <Number> More to expand the collapsed nodes.
User Parameter Max. Number of Child Nodes Displayed in Hierarchy

Processing (MDG_HRYUI_NODE_LIMIT)
Example
The following example shows how to display the configuration settings of a profit center group hierarchy and its
profit center group.
1. Process the Customizing activity Edit Data Model under General Settings Data Modeling . Mark the
data model SF on the Inactive Data Models view. Then double-click the Entity Types view.
In the column Entity Type, double-click the entity type CARR (Airline). In the group frame Entity Types you
can see the following configuration settings:
○ Is Hierarchy Type: Yes - Not Version-dependent / Not Synchronized
○ Validity / Hierarchy: No Edition. The complete name of this field is Validity Concept for Hierarchy.
2. In the column Entity Type, double-click the entity type CARR_HIER (Names for Hierarchies of Airlines). In
the group frame Entity Types, you can see the following configuration setting:
Storage and Use Type: Changeable via Change Request
 Note
Assigning the Names for Hierarchies of Airlines hierarchy CARR_HIER to the storage and use type 1
(Changeable via Change Request) defines that this hierarchy can be processed using change requests.
This assignment enables the entity type CARR_HIER to become a root node for the hierarchy.
3. Double-click the Entity Types view and mark the row of the entity type CARR. Then double-click the Entity
Types for Hierarchies view. In the group frame Entity Types for Hierarchies you can see the following
configuration settings:
○ The Entity Type of Node CARR_HIER (Names for Hierarchies of Airlines) has the Use: Hierarchy Name.
○ The Entity Type of Node CARR (Airline) has the Use: No Special Use.

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

126 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 127
www.sap.com/contactsap
© 2018 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

MDG - Financials Config PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MDG - Financials Config PDF

Hochgeladen von

Copyright:

Verfügbare Formate

PUBLIC

Master Data Governance for Financials

THE BEST RUN

1 Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Services to be Activated for MDG Web Dynpro Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Configuring Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Configuring the SOA Manager for MDG-F (NW 7.40 or higher). . . . . . . . . . . . . . . . . . . . . . . . . 33

6 Configuring ALE for Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . .54

8 Adapting Master Data Governance for Financials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Master Data Governance for Financials

Master Data Governance for Financials

Master Data Governance for Financials

To activate the services, proceed as described below:

Once you have activated a service it cannot be reset to inactive.

Service Name MDG-C / MDG- MDG-M MDG-F MDG-CO

BS_OVP_BP Web Dynpro Com­ x

BS_OVP_BP_MRP Business Partner x

BS_OVP_CC Cleansing Case x

CONFIGURE_AP­ Application Con­ x x x x

Master Data Governance for Financials

CONFIG­ Configure Compo­ x x x x

CUSTOM­ Component Con­ x x x x

DRF_AD­ Adhoc Replication x x x x

DRF_FIL­ Filter Criteria x x x

DRF_FIL­ Application Con­ x x x x

DRF_FIL­ Filter Maintenance x x x x

DRF_FPM_OIF_M Monitoring Web x x x x

DRF_FPM_SEG_FL Application con­ x x x

DRF_MAN­ Manual Replica­ x x x x

FPM_CFG_HIER­ FPM Application x x x x

IBO_WDA_INBOX Lean Workflow In­ x x x x

MDG_ANLY_CR_R Change Request x

MDG_BS_CON­ Master Data File x

Master Data Governance for Financials

MDG_BS_DL_DIS­ Web Dynpro Appli­ x x x x

MDG_BS_DL_MO Data Load Monitor x x x x

MDG_BS_FILE_IM Application for File x x x x

MDG_BS_GEN_M Generic Mass x

MDG_BS_MAT MDG-M: UI (entry x

MDG_BS_MAT_M MDG-M: Mass x

MDG_BS_MAT_OV MDG-M: UI with x

MDG_BS_MAT_SE MDG-M: UI, x

MDG_BS_WD_AN­ Analyse ID Web x x x x

MDG_BS_WD_ID_ Web Dynpro Appli­ x x x x

MDG_BS_WD_RSI Display Replica­ x x x x

MDG_CRE­ Application for x

MDG_CR_PROC­ Processing Time x

Master Data Governance for Financials

MDG_DATA­ Export Master x

MDG_DIS­ Cell Colors used x x x x

MDG_DQR_OVP OVP for MDG Data x x x x

MDG_FILE_UP­ File Uploader x

MDG_MONI­ Application Con­ x x x

MDG_TRANS­ Transformer com­ x

MDGF_OVP_GEN MDG-F Applica­ x

OIF_CFG_CENTER BCV Configuration x

POWL Personal Object x

USMD_APPLICA­ Web Dynpro Appli­ x x x

USMD_BRFPLUS_ BRFplus Catalog x x x x

USMD_CHANGE_ Change Docu­ x x x x

Master Data Governance for Financials

USMD_CRE­ Create Change x x x x

USMD_CRE­ Workflow Informa­ x x x x

BS_OVP_BP Web Dynpro Com x

CONFIGURE_AP Application Con x x x x

CONFIG Configure Compo x x x x

CUSTOM Component Con x x x x

DRF_AD Adhoc Replication x x x x

DRF_FIL Filter Criteria x x x

DRF_FIL Application Con x x x x

DRF_FIL Filter Maintenance x x x x

DRF_FPM_SEG_FL Application con x x x

DRF_MAN Manual Replica x x x x

FPM_CFG_HIER FPM Application x x x x

IBO_WDA_INBOX Lean Workflow In x x x x

MDG_BS_CON Master Data File x

MDG_BS_DL_DIS Web Dynpro Appli x x x x

MDG_BS_WD_AN Analyse ID Web x x x x

MDG_BS_WD_ID_ Web Dynpro Appli x x x x

MDG_BS_WD_RSI Display Replica x x x x

MDG_CRE Application for x

MDG_CR_PROC Processing Time x

MDG_DATA Export Master x

MDG_DIS Cell Colors used x x x x

MDG_FILE_UP File Uploader x

MDG_MONI Application Con x x x

MDG_TRANS Transformer com x

MDGF_OVP_GEN MDG-F Applica x

USMD_APPLICA Web Dynpro Appli x x x

USMD_CHANGE_ Change Docu x x x x

USMD_CRE Create Change x x x x

USMD_CRE Workflow Informa x x x x

USMD_DISTRIB Web Dynpro Appli x x

USMD_EDI Edition Compari x

USMD_EDI Display of Change x x x x

USMD_EDI Edition History x

USMD_ENTITY Collective Proc x x x x

USMD_EN Search for Entities x x

USMD_EN Single Processing x x

USMD_FILE_UP File Upload x x x x

USMD_ISR_PROC ISR Processing of x x

USMD_RE Remote Where- x

USMD_RULE Rule Engine Con x x x x

USMD_UI_CON Manage UI Config- x x x x

WDA_BS_ANLY_LI Simplified Report x x x x

WDA_CFG_GAF_W Configuration Wiz x x x x

WDA_CFG_LAUNC Launchpad Main x x x x

WDA_CFG_OIF_U Web Dynpro Appli x x x x

WDA_OIF_MAN Manage Interface x x x x

WDA_OIF_DIS Display OIF Model x x x x

WDA_UIF_SIDEPA BCV Side Panel for x x x x

WDC_UIF_COCK BCV Cockpit Start x x x x