You are on page 1of 260

Master Data Governance Training Series

Week 1

MDG Training
Course Structure

Week 1:
Day 1 MDG Basics, Overview and Architecture Overview and Deployment Options (HUB , Co deployment )
Day 2 Configurations Reuse/Flex Modes , Application Components,
Day 3 MDG 7.0 Foundation First Steps into Generic, OOTB ,Data model and extensions
Day 4 Project Design Implementations, Blue print , Testing
Day 5 MDG Framework Components ,MDG (OOB) and Custom Object Frameworks

2013/06/01 MDGSAPOV v 0.1 2


Day 1

MDG Overview

2013/06/01 MDGSAPOV v 0.1 3


Day 1 MDG Overview Agenda

MDG Introduction
Utopia MDG Methodology
What is MDG and what are its capabilities?
MDG Features
Delivered Data Models
Operational Modes: Reuse vs. Flex
Process Model: Change Requests, UI Configuration, Workflow
Replication Model
MDG Installation
Deployment Models
Client Options
Configuration
Business Functions
Business Configuration (BC) Sets
Services
Utopias Master Data Governance Methodology

Strategy Design Phase Deploy Phase


Phase

Global Master
Business Rules
Data Data
Process Flows
Flow Analysis

Implement
Global
Roadmap
Vision, Roadmap

Reporting Master
Validations Approvals Data
Tracking

Operations
Data Operations
Standards
And
Sponsorship, Vision,

Creation
Process
Standards Phase Activities

Master Data
Sponsorship,
Data
Master Data
Strategy
Strategy

Master
Master

Identify & Develop Data Standards

Data Governance and Stewardship


Master Data Management Business Drivers
Increase accuracy and
Provide up-to-date information at global
completeness of Master Data
level to increase speed to market,
information
driving profitable growth
Ensure data consistency and
Gain insight through analysis and
accuracy across operational
discovery Improve Improve systems
Improve customer insight Business Data
Decisions Quality

Centralize Master Data


Master Improve responsiveness to
Information Management
Reduce Data changes in business processes
Automate error handling & Data Improved
Management Flexibility Facilitate the introduction of
other administration costs Management
Costs integrated common systems
for duplicate data entry
Improve Data Management Improved mergers and
efficiencies acquisitions infrastructure
Comply with
Regulations

Single Version of the Truth


Improve governance to meet regulations
Avoid unintentional disclosure of information
What is a Master Data Management system ?

Master
Data
Decouples master data from
individual applications Existing
Applications
Becomes a central, application Existing
independent resource Applications
Simplifies ongoing integration tasks Master
and new app development Data

Ensure consistent master Master Data


information across transactional Management
and analytical systems System
Addresses key issues such as data Existing
quality and consistency proactively Applications
Historical /
rather than after the fact in the
Master Analytical
data warehouse Data
Systems
New
Applications

Master
Data
Why integrated Master Data Governance

Different roles create/consume different Master


Data elements

Business
Users
Unified Simplify Integration
Metadata
Facilitate change mgmt
Subject Matter
Experts
and reuse
Increase trust and
confidence in
Architects
information
Design & Increase compliance to
Operational
Data Metadata standards
Analysts

Developers

DBAs
SAP MDG Solution

SAP
Master Data Governance SAP MDG provides ready-to-run
governance applications for specific
SAP master data domains.
Out-of-the-box, domain specific master
data governance applications to centrally SAP MDG applications are tailored for
create, change and distribute master data central data maintenance so that the
with a focus on SAP Business Suite data is ready for use in SAP Business
Suite environments.
SAP Master Data Governance

Native integration with SAP


Information Mgmt External
Business Suite and ERP
Data Integration & Quality Services
Re-use of SAP data model, UI and
Data Validation &
Maintenance Data Quality
Approval existing business logic and
configuration for creation and
Business Logic validation of Master Data
Local adaptations
in de-central systems

Enables governance, compliance and transparency through integrated staging,


approval and audit trail

Delivers consistent definition, authorization and replication of key master data entities
for SAP

Eliminates error prone manual maintenance process of master data in multiple


systems

Integrates with Business Objects Data Services for data quality and enrichment
SAP Master Data Governance Capabilities

6/4/2013 11
Element 1: Deliver Out-of-the-Box Functionality

6/4/2013 12
Element 2: Integrated Object Model (v 6.1)

6/4/2013 13
Element 3: Governance, Collaboration

6/4/2013 14
Element 3 and Data Quality

6/4/2013 15
Element 4: Robust Data Replication

6/4/2013 16
Element 5: Reusability & Extensibility

6/4/2013 17
Delivered Data Models (MDG Version 6.1)
Element 2: Integrated Object Model (v 7.0)

19
Internal
Need of a Master Data Solution

And other
Master data

And other Master data

Internal
SAP MDG Focus Areas

Internal
Master Data Management Solutions Business Drivers
Increase accuracy and
Provide up-to-date information at global level
completeness of Master Data
to increase speed to market, driving
information
profitable growth
Ensure data consistency and
Gain insight through analysis and discovery
accuracy across operational
Improve customer insight Improve Improve systems
Business Data
Decisions Quality

Centralize Master Data


Master Improve responsiveness to
Information Management
Reduce Data changes in business processes
Automate error handling & other Data Improved
Management Flexibility Facilitate the introduction of
administration costs for Costs Management integrated common systems
duplicate data entry
Improved mergers and
Improve Data Management
acquisitions infrastructure
efficiencies
Comply with
Regulations

Single Version of the Truth


Improve governance to meet regulations
Avoid unintentional disclosure of information

Internal
Deployment Options

Internal
Deployment Options

Internal
Deployment Options

Internal
HUB Deployment

Internal
CO-Deployment

Internal
HUB VS CO

Internal
Day 2

MDG Basic Configurations &


Application Components

2013/06/01 MDGSAPOV v 0.1 29


Key Capabilities
SAP MDG Architecture

Internal
SAP MDG Process Flow

Internal
General Flow

Internal
SAP Master Data Governance

Native integration with SAP


Information Mgmt External
Business Suite and ERP
Data Integration & Quality Services
Re-use of SAP data model, UI and
Data Validation &
Maintenance Data Quality
Approval existing business logic and
configuration for creation and
Business Logic validation of Master Data
Local adaptations
in de-central systems

Enables governance, compliance and transparency through integrated staging,


approval and audit trail

Delivers consistent definition, authorization and replication of key master data entities
for SAP

Eliminates error prone manual maintenance process of master data in multiple


systems

Integrates with Business Objects Data Services for data quality and enrichment
Internal
Storage Modes FLEX VS Re- Use

Internal
Services to be activated
Business Partner Data Model (BP)

Internal
Customer Data Model (BP)

Internal
Supplier Data Model (BP)

Internal
Finance Model

Internal
Integrated Model BP-S-C

Week1

Internal
Material Master Data Model MM
Configuration Guides

MDG overall documentation (Configuration &


Application, incl. Configuring Master Data
Governance for Custom Objects)
http://help.sap.com/erp2005_ehp_05/helpdata/en/7
c/a94fabb8274d738d994c2bc1c4cf7a/frameset.htm
Configuration Guide General Settings (incl.
enhancement)
http://help.sap.com/erp2005_ehp_05/helpdata/en/4
b/81f46cb11a41c38dd53db5b0cc6ea9/frameset.htm
Material Configuration Guide (incl. Data Model;
Extension; Rule-based Workflow)

http://help.sap.com/erp2005_ehp_05/helpdata/en/b
2/9a55fd374848a1b70679180b08514b/frameset.htm
Configuring MDG for Supplier

http://help.sap.com/erp2005_ehp_05/helpdata/en/70
/47f6938f70420f801be80a0df9fc30/frameset.htm
Configuring MDG for Financials
http://help.sap.com/erp2005_ehp_05/helpdata/en/a
d/d9b1d07d1b4aec9fd44020739e776b/frameset.htm
MDG in IMG Structure
SAP Net Weaver Portal Content:
Deploy the right Business Package

Depending on the used MDG scenario the corresponding Portal content has to
be deployed in the SAP Net Weaver Portal by the Java Support Package
Manager
(JSPM). The Portal content is part of the standard delivery of SAP Business
Suite and is delivered in several business packages for the different scenarios
as part of the SAP enhancement package 5 for SAP ERP 6.0 :
Master Data Governance for Financial
Business Package for Financial MDM 1.51 (BPERPFINMDM)
Business Package for Common Parts 1.51 (BPERP5COM)
Master Data Governance for Material
Business Package for Material Governance 1.50 (BPERPMDGM)
Business Package for Financial MDM 1.51 (BPERPFINMDM)
Business Package for Common Parts 1.51 (BPERP5COM)
Master Data Governance for Supplier
Business Package for Supplier Governance 1.50 (BPERPMDGS)
Business Package for Financial MDM 1.51 (BPERPFINMDM)
Business Package for Common Parts 1.51 (BPERP5COM)
Assign Roles in SAP NetWeaver Portal
For the portal content, you must activate the portal role of the common objects in
addition to the actual portal role of SAP Master Data Governance (Financial, Material,
Supplier). Once activated, you must assign the roles in the portal as follows:
Logon to the portal.
Choose Delegated User
Admin.
Enter your User ID.
Mark the line of your user
and click on Modify.
Select the Assigned Roles
tab.
Enter one of the following
roles, corresponding to your
scenario:
-Supplier Master Data
Manager
-Material Master Data
Manager
-Financial Master Data
Manager
and additionally the role
-ERP Common
as the search criteria.
Select the role and click Add
and Save.
SAP NetWeaver Business Client:
Personalize the Role in PFCG

Personalize a role for the use with Business Client in the SAP ERP system
In transaction PFCG choose the right role for your scenario:
For Material = SAP_MDGM, for Supplier = SAP_MDGS or for Financial = SAP_FIN_MDM.
Click on the tab Personalization and edit the personalization key SAP Master Data Governance
(R_FMDM_MODEL) by a double-click.
Define the right Data Model (Standard is Material = MM, Supplier = BP, Financial = 0G) and the right UI
Config.
Optionally, in case of MDGF, create the default values for the edition, change request type and the
entity type.
The roles ensures that the only the necessary steps can be started.
Click on the tab Authorisations and verify the settings for the authorisation objects within the role, and
restrict
them if necessary.
To assign the
necessary roles
to your user in
the SAP ERP
start transaction
SU01 and assign
one or more of
these roles
Services to be Activated for Web Dynpro Applications
for MDG
Services to be Activated for Web Dynpro Applications
for MDG
Services to be Activated for Web Dynpro Applications
for MDG 8.0

2013/06/01 MDGSAPOV v 0.1 50


Activation of the relevant MDG switches

MDG is completely switch-enabled.


You will not see it in customizing nor would
you be able to start any default processing
without the activation of the relevant
switches.
Demo Data models
Day 3

MDG 7.0 Foundation First Steps into


Generic
(Irrespective of Data Model )
Configuration Data Model Extension
The MDG Out-of-the-Box (OOTB)
solution from an End-user perspective
- CRUD

2013/06/01 MDGSAPOV v 0.1 53


Data Model Extension MM
2013/06/01 MDGSAPOV v 0.1 55
MM Data Model Entities
Demo of the Solution OOTB - CRUD

Solution Demo
Day 4

Project Design
Implementation
Blue print
Testing

MDG Practice
Day 4

Project Design
Implementation
Blue print
Testing
Data model Concepts

2013/06/01 MDGSAPOV v 0.1 59


MDG Data Modeling

Data Model Concepts


Significance of Data Modelling

A Data model organizes business data and defines how data is stored and accessed

For example: The material data model will define what constitutes a Golden Record

It will define the attributes for the golden record

It will define the structure in which the data values will be stored in MDG

Any implementation will start by using the out of the box (OOTB) data model delivered by SAP

This OOTB model can be enhanced, provided the requirements are global in nature
Master Data Governance
Data Models
Illustration with the Material Data Model Example

Entity types of the Attributes for the Data element s for


Data Model entity type
Data Model attributes
1. Material 1
1. Material Number 1. MATNR
Material Master 2. Units of Measure
2. Material type 2. MTART
(MM) 1
* 3.
4.
Material Texts
...... * 3. Base unit of Measure
* 1 3. MEINS
2

*
e.g. Material -> Units of
* measure
Handling of Active and Inactive Data
Concepts and architecture during changes
Data Modeling Entity Types and Properties
Entity-types
Overview: Storage and usage type
Data Modeling The Material Example with Storage Types
Data Modeling - Relationships
MDG Hierarchy Maintenance
Enabling of hierarchies in the data model

Hierarchies are enabled for an entity type by changing the Hierarchies attribute to
another value than - No hierarchy. As a consequence a hierarchy table will be generated
that allows storing parent-child relations between entities of this entity type (and also
between additional entity types if specified).
A hierarchy can be defined as version, name or edition dependent (see next slides).
MDG Hierarchy Maintenance
Enabling validity of a hierarchy in the data model

Hierarchies can have a validity along the edition concept by choosing the value
Hierarchy is Edition Dependent under Validity Concept for Hierarchy.
If hierarchies are edition dependent the hierarchy database table gets an additional
key field for the edition. This allows storing different validities of a hierarchy.
MDG Hierarchy Maintenance
Making a hierarchy version dependent

Hierarchies can be made version dependent.

Hierarchy versions are defined in a separate IMG activity and


have a CHAR3 key field and a description.

If hierarchies are version dependent the hierarchy database table gets an additional key field
for the version. This allows storing different versions of a hierarchy.
Hierarchy Version Parent ID Child ID
001 1000 1001
001 1001 1002
002 1000 1002
002 1000 1003

A version dependent hierarchy can be copied to another version.


MDG Hierarchy Maintenance
Making a hierarchy name dependent

Hierarchies always have a hierarchy name as root node of the hierarchy. This is true
no matter if the hierarchy is name dependent or not. The hierarchy name is
modeled as separate entity type with SUT 1 and has to be maintained under
additional entity types with Use Hierarchy Name. Each hierarchy needs exactly
one entity type as hierarchy name. This entity type has a data element but no
attributes. Hierarchy names cannot have super-ordinate entities.
Hierarchies can be made name dependent by choosing the option Not Cross-
name when enabling the hierarchy. If hierarchies are name dependent the
hierarchy database table gets an additional key field for the name. This allows
storing different versions of a hierarchy under different names. If hierarchies are
defined as Cross-name then fragments of a hierarchy are always identical under
different hierarchy names.
MDG Hierarchy Maintenance
Making a hierarchy name dependent

In cross-name hierarchies the relations may NOT differ under different names. As
soon as entity 1002 is added as child to entity 1001 in hierarchy EMEA the same
relation is also valid in hierarchy APJ. In fact it exists only once on the database.
Hierarchy Name Parent ID Child ID
EMEA 1000 1001
EMEA 1001 1002
APJ 1001 1002

In name dependent hierarchies the relations may differ under different names.
Hierarchy Name Parent ID Child ID
EMEA 1000 1001
EMEA 1001 1002
APJ 1001 1003
MDG Hierarchy Maintenance
Additional entity types

A hierarchy may contain entities of additional entity types as nodes. These


entity types are specified under Entity Types for Hierarchies (in addition to
the hierarchy name). By default, the Use has the value No Special Use. You
can also choose the value Ranges Permitted on End Nodes. This enables to
specify ranges of entities at the leaves of the hierarchy.
In the example below the entity type CCTR (Cost Center) has been specified
as allowed entity type within the Cost Center Group Hierarchy. Ranges on
end nodes have been enabled.
Another use case would be to support text nodes.
MDG Hierarchy Maintenance
Additional attributes in the hierarchy relation

Hierarchy relations can have additional attributes.


An attribute of the relation can be
specified by a data element

or by a reference to an entity
type. In this case the data element
is optional and taken from the
entity type. You can specify an
alternative data element if
technically identical.

The second example shows that if you want to add attributes to the relation of the entity type for
which the hierarchy has been defined you have to specify it again under Entity types for Hierarchies.
MDG Hierarchy Maintenance
Additional Attributes in the Hierarchy Relation

Attributes of the hierarchy relation can first be maintained during the insertion of an entity into the hierarchy.
Later they can be changed by calling Change Hierarchy Attributes or Change Range from the context menue
depending on whether a discrete entity value has been specified or a range.
MDG Hierarchy Maintenance
Single Item Maintenance

A special UIBB is available to


maintain higher-level nodes and
predecessors in the single item
maintenance.
It can be added to the UI
configuration of the entity type for
which the hierarchy has been
defined.
Depending on the configuration
the UIBB will be rendered as form
or as list (to allow only one or
multiple higher-level nodes) and
includes fields for the version
and/or predecessors.
MDG Hierarchy Maintenance
Collective Processing Capabilities

In general, hierarchies are maintained in the hierarchy view of the generic application Collective
Processing. The main features are:
You can insert new or existing nodes. You can insert several nodes in one step.
You can move nodes (incl. sub-nodes) with arrow buttons. Drag & drop is also
supported.
You can find nodes in the hierarchy.
You can expand ranges to see which entities are currently assigned.
You can trigger a mass change with selected entities from the hierarchy view. Ranges
are expanded.
MDG Hierarchy Maintenance
Collective Processing Layout

The layout of the hierarchy view is derived automatically


Columns for descriptions are included according to the text settings of all entity types
specified for the hierarchy.
Columns for attributes of the leading entity type are included (unless disabled in the
field property view by checking the flag No result list).
MDG Hierarchy Maintenance
Collective Processing Using ranges

If you have chosen the Use Ranges Permitted on End Nodes for an entity type of your hierarchy you
may specify ranges instead of discrete values for the entities that sit at the leaves of the hierarchy.
For the boundaries of the range no existence check is performed.
You can expand the range at any time from the context menu to see which entities
currently fall into the given range.
MDG Hierarchy Maintenance
File upload and download

Hierarchies can be uploaded and downloaded using the generic CSV-file based web applications
(USDM_FILE_UPLOAD & USM_FILE_DOWNLOAD).
Enhancement spots are available to do file conversions during upload and download.
Upload: USMD_DATA_TRANSFER_UPL, methods CONVERT and FINALIZE
Download: USMD_DATA_TRANSFER, method PROCESS_DOWNLOAD_HRY
MDG Hierarchy Management
Pre-delivered Models

Data Model Entity Type Version / Name Dependent Edition Dep.


0G CCTRG Not Version-dependent / Cross-name yes
0G CELEMG Not Version-dependent / Cross-name yes
0G CONSGRP Version-dependent / Not Cross-name yes
(name dependent)
0G FRSI Not Version-dependent / Not Cross- yes
name
0G FSI Version-dependent / Not Cross-name yes
(name dependent)
0G PCTRG Not Version-dependent / Cross-name yes
BP BP_HEADER Not Version-dependent / Not Cross- no
name (name dependent)
Extending Data Models

Reference How to Guide

MDG Data Model


Extensibility Options

(And Many more in SCN)

http://scn.sap.com/docs/DOC-7858
Day 5

MDG Framework Components

MDG Practice
Change Requests - Recap
Data maintenance using Change Requests the business
process view
General Change Request Processes
Determination of Workflow by Change Request Type
Configure Change Request Settings (1/3)
Status of Change Requests
Configure Change Request Settings (2/3)
Configure Change Request Settings (3/3)
Define Priorities and (Rejection) Reasons
MDG Training

Workflows OOTB and Extensions


Process Configuration
Look & Feel: SAP Business Workflow Design Tool - SWDD
Look & Feel: Rules Based Workflow
Ensure that workflow customizing is
active, complete and working
How MDG is integrated into the Business Workflow
Single Object Workflow: Steps linked to User Interaction
The links 1) configured step
Enhance the enhanced Financials workflow
Supplier Agent Determination
Set up or check the Business Rules Framework Plus
Change Request Workflow Process
Specific Process: Create Supplier
Master Data Governance for Material
Create/Change a Material Default Workflow
Master Data Governance for Material
Generic Workflow controlled by rules
Material Change Requests Types
Generic Workflow (BWF) Template
with BRF+ control
Master Data Governance Rule Based Workflow
Details on Main Branch
MDG Training

Setup of BRF+ Rule Based Worfklow


Master Data Governance for Material
Create/Change a Material: Representation in BRFplus
Set Up the Rule-Based Workflow
Maintain Content in the Single Value Decision Table
Set Up the Rule-Based Workflow (1/5)
Review and enhance the default steps
Set Up the Rule-Based Workflow (2/5)
Generate the decision tables and rules
Set Up the Rule-Based Workflow (3/5)
(Optional) Import structures from client 000
Set Up the Rule-Based Workflow (4/5)
Maintain Content in the decision tables
Set Up the Rule-Based Workflow (5/5)
Maintain Content in the decision tables
Step Types and Actions
Relationship Step TypeToolbar ButtonAction
Generic Workflow WS60800086
Example: Enhanced Change Request Workflow
BRF+ Infos

Technical Settings:

Transaction BRF+ / BRFplus

Documentation:

701: SAP NetWeaver Library -> SAP NetWeaver by Key Capability ->
Application Platform by Key Capability -> Business Services -> Business Rule
Framework plus
730: SAP NetWeaver Library -> SAP NetWeaver Library: Function-Oriented
View ->Application Server -> Application Server ABAP -> Other Services ->
Services for Application Developers -> Business Rule Framework plus
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/9a/6b67ce7c26446483
af079719edf679/frameset.htm

Start in MDG customizing

Using transaction USMD_SSW_RULE


Generating: USMD_SSW_CATA_MAT01 / USMD_SSW_CATA_<CR_TYPE>
Important variables in BRF+
Change Request & Workflow Trouble Shooting
Master Data Governance Training Series

Process Modeling : Change Requests and Workflows


Objectives

The objectives for this unit are:


Theory:
Become familiar with the configuration process for Change Requests and Simple Workflows
Understand the configuration of a rudimentary Organization Model for MDG Processing
Review the Out-of-the-Box (OOTB) Configuration Guides for all four MDG Domains
Hands On Tasks:
Define a rudimentary OM for a Data Governance Organization
Configure a new Change Request (CR) type for the Financials Data Model
Configure the corresponding workflow for the new CR type
Process several change requests using your new CR type
Process Modeling Change Requests
Change Requests
Statuses
Priorities
Reasons
Rejection Reasons
Change Request Properties
Change Request Steps
Enhancements and Checks for CR Steps
Entity Types per CR Step
Attributes per CR Step
UI per CR Step

Walkthrough in the MDG System


Process Modeling Organizational Model Configuration

Organizational Model Building Blocks


Organizational Unit
Relationships
Hierarchy
Positions
Holders
Users
T-Codes
PPOCE
PPOME
Walkthrough
Process Modeling Workflow Configuration
Workflow Configuration (Simple)
Type Linkage (one-time setup)
Configure Workflow Tasks (one-time setup)
Define Actions for CR UIs
Step Types and Action Assignment
Change Request Step Numbers
Assign Processors to CR Steps
Walkthrough in the MDG System
HARNESS
THE POWER OF DATA

UNLEASH
THE FULL POTENTIAL OF YOUR ENTERPRISE
Hands On Assignment Organization Model (OM)

Define a rudimentary Organizational Model with the following structure:


A root Organizational Unit with three subordinate Organizational Units: Financials, Business
Partner, Material
Two Positions within the Organizational Units: Requester and Approver
Assign user ID WMEINWEISER as one of the Holders of the Approver Position, assign the ID
MDG_APP_GRP as a second holder of the Approver Position
Hands On Assignment Change Request (CR)

Define a Change Request (CR) Type for the following:


Single Object Processing of a Profit Center Group
Allow both the Profit Center Group and Profit Center Hierarchy Entities to be maintained by this Change
Request type .
Associate the Change Request with an Edition that references your groups Financials Data Model
Display any error messages as warnings for this CR type
Define high priority change requests to have a two day SLA
Assign the CR Type to be processed by Workflow Template WS75700040
Hands On Assignment Workflow Configuration

Configure the WS75700040 Workflow Template


Action Assignment
Reverse the order of the buttons on Step Type 1
What did you notice about the table containing the Step Type configuration?
Change the pushbutton text for Approve to Concur
Change the quick info text for Approve to 1st level approval
Change the pushbutton text for Finalize Processing to Approve
Change the quick info text for Finalize Processing to Final Approval
Assign Processors to your CR Step Numbers
Determine how many steps need to have processors defined
Assign your Requester and Approver accordingly
Questions

HARNESS THE POWER OF DATA UNLEASH THE FULL POTENTIAL OF YOUR ENTERPRISE
Master Data Governance Training Series

MDG Training
Course Structure

Week 1:
Day 1 MDG Basics, Overview and Architecture Overview and Deployment Options (HUB , Co deployment )
Day 2 Configurations Reuse/Flex Modes , Application Components,
Day 3 MDG 7.0 Foundation First Steps into Generic, OOTB ,Data model and extensions
Day 4 Project Design Implementations, Blue print , Testing
Day 5 MDG Framework Components ,MDG (OOB) and Custom Object Frameworks

2013/06/01 MDGSAPOV v 0.1 133


Day 1

MDG Overview

2013/06/01 MDGSAPOV v 0.1 134


Day 1 MDG Overview Agenda

MDG Introduction
Utopia MDG Methodology
What is MDG and what are its capabilities?
MDG Features
Delivered Data Models
Operational Modes: Reuse vs. Flex
Process Model: Change Requests, UI Configuration, Workflow
Replication Model
MDG Installation
Deployment Models
Client Options
Configuration
Business Functions
Business Configuration (BC) Sets
Services
Utopias Master Data Governance Methodology

Strategy Design Phase Deploy Phase


Phase

Global Master
Business Rules
Data Data
Process Flows
Flow Analysis

Implement
Global
Roadmap
Vision, Roadmap

Reporting Master
Validations Approvals Data
Tracking

Operations
Data Operations
Standards
And
Sponsorship, Vision,

Creation
Process
Standards Phase Activities

Master Data
Sponsorship,
Data
Master Data
Strategy
Strategy

Master
Master

Identify & Develop Data Standards

Data Governance and Stewardship


Master Data Management Business Drivers
Increase accuracy and
Provide up-to-date information at global
completeness of Master Data
level to increase speed to market,
information
driving profitable growth
Ensure data consistency and
Gain insight through analysis and
accuracy across operational
discovery Improve Improve systems
Improve customer insight Business Data
Decisions Quality

Centralize Master Data


Master Improve responsiveness to
Information Management
Reduce Data changes in business processes
Automate error handling & Data Improved
Management Flexibility Facilitate the introduction of
other administration costs Management
Costs integrated common systems
for duplicate data entry
Improve Data Management Improved mergers and
efficiencies acquisitions infrastructure
Comply with
Regulations

Single Version of the Truth


Improve governance to meet regulations
Avoid unintentional disclosure of information
What is a Master Data Management system ?

Master
Data
Decouples master data from
individual applications Existing
Applications
Becomes a central, application Existing
independent resource Applications
Simplifies ongoing integration tasks Master
and new app development Data

Ensure consistent master Master Data


information across transactional Management
and analytical systems System
Addresses key issues such as data Existing
quality and consistency proactively Applications
Historical /
rather than after the fact in the
Master Analytical
data warehouse Data
Systems
New
Applications

Master
Data
Why integrated Master Data Governance

Different roles create/consume different Master


Data elements

Business
Users
Unified Simplify Integration
Metadata
Facilitate change mgmt
Subject Matter
Experts
and reuse
Increase trust and
confidence in
Architects information
Design & Increase compliance to
Operational
Data Metadata standards
Analysts

Developers

DBAs
SAP MDG Solution

SAP
Master Data Governance SAP MDG provides ready-to-run
governance applications for specific
SAP master data domains.
Out-of-the-box, domain specific master
data governance applications to centrally SAP MDG applications are tailored for
create, change and distribute master data central data maintenance so that the
with a focus on SAP Business Suite data is ready for use in SAP Business
Suite environments.
SAP Master Data Governance

Native integration with SAP


Information Mgmt External
Business Suite and ERP
Data Integration & Quality Services
Re-use of SAP data model, UI and
Data Validation &
Maintenance Data Quality
Approval existing business logic and
configuration for creation and
Business Logic validation of Master Data
Local adaptations
in de-central systems

Enables governance, compliance and transparency through integrated staging,


approval and audit trail

Delivers consistent definition, authorization and replication of key master data entities
for SAP

Eliminates error prone manual maintenance process of master data in multiple


systems

Integrates with Business Objects Data Services for data quality and enrichment
SAP Master Data Governance Capabilities

6/4/2013 142
Element 1: Deliver Out-of-the-Box Functionality

6/4/2013 143
Element 2: Integrated Object Model (v 6.1)

6/4/2013 144
Element 3: Governance, Collaboration

6/4/2013 145
Element 3 and Data Quality

6/4/2013 146
Element 4: Robust Data Replication

6/4/2013 147
Element 5: Reusability & Extensibility

6/4/2013 148
Delivered Data Models (MDG Version 6.1)
Element 2: Integrated Object Model (v 7.0)

150
Internal
Need of a Master Data Solution

And other
Master data

And other Master data

Internal
SAP MDG Focus Areas

Internal
Master Data Management Solutions Business Drivers
Increase accuracy and
Provide up-to-date information at global level
completeness of Master Data
to increase speed to market, driving
information
profitable growth
Ensure data consistency and
Gain insight through analysis and discovery
accuracy across operational
Improve customer insight Improve Improve systems
Business Data
Decisions Quality

Centralize Master Data


Master Improve responsiveness to
Information Management
Reduce Data changes in business processes
Automate error handling & other Data Improved
Management Flexibility Facilitate the introduction of
administration costs for Costs Management integrated common systems
duplicate data entry
Improved mergers and
Improve Data Management
acquisitions infrastructure
efficiencies
Comply with
Regulations

Single Version of the Truth


Improve governance to meet regulations
Avoid unintentional disclosure of information

Internal
Deployment Options

Internal
Deployment Options

Internal
Deployment Options

Internal
HUB Deployment

Internal
CO-Deployment

Internal
HUB VS CO

Internal
Day 2

MDG Basic Configurations &


Application Components

2013/06/01 MDGSAPOV v 0.1 160


Key Capabilities
SAP MDG Architecture

Internal
SAP MDG Process Flow

Internal
General Flow

Internal
SAP Master Data Governance

Native integration with SAP


Information Mgmt External
Business Suite and ERP
Data Integration & Quality Services
Re-use of SAP data model, UI and
Data Validation &
Maintenance Data Quality
Approval existing business logic and
configuration for creation and
Business Logic validation of Master Data
Local adaptations
in de-central systems

Enables governance, compliance and transparency through integrated staging,


approval and audit trail

Delivers consistent definition, authorization and replication of key master data entities
for SAP

Eliminates error prone manual maintenance process of master data in multiple


systems

Integrates with Business Objects Data Services for data quality and enrichment
Internal
Storage Modes FLEX VS Re- Use

Internal
Services to be activated
Business Partner Data Model (BP)

Internal
Customer Data Model (BP)

Internal
Supplier Data Model (BP)

Internal
Finance Model

Internal
Integrated Model BP-S-C

Week1

Internal
Material Master Data Model MM
Configuration Guides

MDG overall documentation (Configuration &


Application, incl. Configuring Master Data
Governance for Custom Objects)
http://help.sap.com/erp2005_ehp_05/helpdata/en/7
c/a94fabb8274d738d994c2bc1c4cf7a/frameset.htm
Configuration Guide General Settings (incl.
enhancement)
http://help.sap.com/erp2005_ehp_05/helpdata/en/4
b/81f46cb11a41c38dd53db5b0cc6ea9/frameset.htm
Material Configuration Guide (incl. Data Model;
Extension; Rule-based Workflow)

http://help.sap.com/erp2005_ehp_05/helpdata/en/b
2/9a55fd374848a1b70679180b08514b/frameset.htm
Configuring MDG for Supplier

http://help.sap.com/erp2005_ehp_05/helpdata/en/70
/47f6938f70420f801be80a0df9fc30/frameset.htm
Configuring MDG for Financials
http://help.sap.com/erp2005_ehp_05/helpdata/en/a
d/d9b1d07d1b4aec9fd44020739e776b/frameset.htm
MDG in IMG Structure
SAP Net Weaver Portal Content:
Deploy the right Business Package

Depending on the used MDG scenario the corresponding Portal content has to
be deployed in the SAP Net Weaver Portal by the Java Support Package
Manager
(JSPM). The Portal content is part of the standard delivery of SAP Business
Suite and is delivered in several business packages for the different scenarios
as part of the SAP enhancement package 5 for SAP ERP 6.0 :
Master Data Governance for Financial
Business Package for Financial MDM 1.51 (BPERPFINMDM)
Business Package for Common Parts 1.51 (BPERP5COM)
Master Data Governance for Material
Business Package for Material Governance 1.50 (BPERPMDGM)
Business Package for Financial MDM 1.51 (BPERPFINMDM)
Business Package for Common Parts 1.51 (BPERP5COM)
Master Data Governance for Supplier
Business Package for Supplier Governance 1.50 (BPERPMDGS)
Business Package for Financial MDM 1.51 (BPERPFINMDM)
Business Package for Common Parts 1.51 (BPERP5COM)
Assign Roles in SAP NetWeaver Portal
For the portal content, you must activate the portal role of the common objects in
addition to the actual portal role of SAP Master Data Governance (Financial, Material,
Supplier). Once activated, you must assign the roles in the portal as follows:
Logon to the portal.
Choose Delegated User
Admin.
Enter your User ID.
Mark the line of your user
and click on Modify.
Select the Assigned Roles
tab.
Enter one of the following
roles, corresponding to your
scenario:
-Supplier Master Data
Manager
-Material Master Data
Manager
-Financial Master Data
Manager
and additionally the role
-ERP Common
as the search criteria.
Select the role and click Add
and Save.
SAP NetWeaver Business Client:
Personalize the Role in PFCG

Personalize a role for the use with Business Client in the SAP ERP system
In transaction PFCG choose the right role for your scenario:
For Material = SAP_MDGM, for Supplier = SAP_MDGS or for Financial = SAP_FIN_MDM.
Click on the tab Personalization and edit the personalization key SAP Master Data Governance
(R_FMDM_MODEL) by a double-click.
Define the right Data Model (Standard is Material = MM, Supplier = BP, Financial = 0G) and the right UI
Config.
Optionally, in case of MDGF, create the default values for the edition, change request type and the
entity type.
The roles ensures that the only the necessary steps can be started.
Click on the tab Authorisations and verify the settings for the authorisation objects within the role, and
restrict
them if necessary.
To assign the
necessary roles
to your user in
the SAP ERP
start transaction
SU01 and assign
one or more of
these roles
Services to be Activated for Web Dynpro Applications
for MDG
Services to be Activated for Web Dynpro Applications
for MDG
Activation of the relevant MDG switches

MDG is completely switch-enabled.


You will not see it in customizing nor would
you be able to start any default processing
without the activation of the relevant
switches.
Demo Data models
Day 3

MDG 7.0 Foundation First Steps into


Generic
(Irrespective of Data Model )
Configuration Data Model Extension
The MDG Out-of-the-Box (OOTB)
solution from an End-user perspective
- CRUD

2013/06/01 MDGSAPOV v 0.1 183


Data Model Extension MM
MM Data Model Entities
Demo of the Solution OOTB - CRUD

Solution Demo
Day 4

Project Design
Implementation
Blue print
Testing

MDG Practice
Day 4

Project Design
Implementation
Blue print
Testing
Data model Concepts

2013/06/01 MDGSAPOV v 0.1 188


MDG Data Modeling

Data Model Concepts


Significance of Data Modelling

A Data model organizes business data and defines how data is stored and accessed

For example: The material data model will define what constitutes a Golden Record

It will define the attributes for the golden record

It will define the structure in which the data values will be stored in MDG

Any implementation will start by using the out of the box (OOTB) data model delivered by SAP

This OOTB model can be enhanced, provided the requirements are global in nature
Master Data Governance
Data Models
Illustration with the Material Data Model Example

Entity types of the Attributes for the Data element s for


Data Model entity type
Data Model attributes
1. Material 1
1. Material Number 1. MATNR
Material Master 2. Units of Measure
2. Material type 2. MTART
(MM) 1
* 3.
4.
Material Texts
...... * 3. Base unit of Measure
* 1 3. MEINS
2

*
e.g. Material -> Units of
* measure
Handling of Active and Inactive Data
Concepts and architecture during changes
Data Modeling Entity Types and Properties
Entity-types
Overview: Storage and usage type
Data Modeling The Material Example with Storage Types
Data Modeling - Relationships
MDG Hierarchy Maintenance
Enabling of hierarchies in the data model

Hierarchies are enabled for an entity type by changing the Hierarchies attribute to
another value than - No hierarchy. As a consequence a hierarchy table will be generated
that allows storing parent-child relations between entities of this entity type (and also
between additional entity types if specified).
A hierarchy can be defined as version, name or edition dependent (see next slides).
MDG Hierarchy Maintenance
Enabling validity of a hierarchy in the data model

Hierarchies can have a validity along the edition concept by choosing the value
Hierarchy is Edition Dependent under Validity Concept for Hierarchy.
If hierarchies are edition dependent the hierarchy database table gets an additional
key field for the edition. This allows storing different validities of a hierarchy.
MDG Hierarchy Maintenance
Making a hierarchy version dependent

Hierarchies can be made version dependent.

Hierarchy versions are defined in a separate IMG activity and


have a CHAR3 key field and a description.

If hierarchies are version dependent the hierarchy database table gets an additional key field
for the version. This allows storing different versions of a hierarchy.
Hierarchy Version Parent ID Child ID
001 1000 1001
001 1001 1002
002 1000 1002
002 1000 1003

A version dependent hierarchy can be copied to another version.


MDG Hierarchy Maintenance
Making a hierarchy name dependent

Hierarchies always have a hierarchy name as root node of the hierarchy. This is true
no matter if the hierarchy is name dependent or not. The hierarchy name is
modeled as separate entity type with SUT 1 and has to be maintained under
additional entity types with Use Hierarchy Name. Each hierarchy needs exactly
one entity type as hierarchy name. This entity type has a data element but no
attributes. Hierarchy names cannot have super-ordinate entities.
Hierarchies can be made name dependent by choosing the option Not Cross-
name when enabling the hierarchy. If hierarchies are name dependent the
hierarchy database table gets an additional key field for the name. This allows
storing different versions of a hierarchy under different names. If hierarchies are
defined as Cross-name then fragments of a hierarchy are always identical under
different hierarchy names.
MDG Hierarchy Maintenance
Making a hierarchy name dependent

In cross-name hierarchies the relations may NOT differ under different names. As
soon as entity 1002 is added as child to entity 1001 in hierarchy EMEA the same
relation is also valid in hierarchy APJ. In fact it exists only once on the database.
Hierarchy Name Parent ID Child ID
EMEA 1000 1001
EMEA 1001 1002
APJ 1001 1002

In name dependent hierarchies the relations may differ under different names.
Hierarchy Name Parent ID Child ID
EMEA 1000 1001
EMEA 1001 1002
APJ 1001 1003
MDG Hierarchy Maintenance
Additional entity types

A hierarchy may contain entities of additional entity types as nodes. These


entity types are specified under Entity Types for Hierarchies (in addition to
the hierarchy name). By default, the Use has the value No Special Use. You
can also choose the value Ranges Permitted on End Nodes. This enables to
specify ranges of entities at the leaves of the hierarchy.
In the example below the entity type CCTR (Cost Center) has been specified
as allowed entity type within the Cost Center Group Hierarchy. Ranges on
end nodes have been enabled.
Another use case would be to support text nodes.
MDG Hierarchy Maintenance
Additional attributes in the hierarchy relation

Hierarchy relations can have additional attributes.


An attribute of the relation can be
specified by a data element

or by a reference to an entity
type. In this case the data element
is optional and taken from the
entity type. You can specify an
alternative data element if
technically identical.

The second example shows that if you want to add attributes to the relation of the entity type for
which the hierarchy has been defined you have to specify it again under Entity types for Hierarchies.
MDG Hierarchy Maintenance
Additional Attributes in the Hierarchy Relation

Attributes of the hierarchy relation can first be maintained during the insertion of an entity into the hierarchy.
Later they can be changed by calling Change Hierarchy Attributes or Change Range from the context menue
depending on whether a discrete entity value has been specified or a range.
MDG Hierarchy Maintenance
Single Item Maintenance

A special UIBB is available to


maintain higher-level nodes and
predecessors in the single item
maintenance.
It can be added to the UI
configuration of the entity type for
which the hierarchy has been
defined.
Depending on the configuration
the UIBB will be rendered as form
or as list (to allow only one or
multiple higher-level nodes) and
includes fields for the version
and/or predecessors.
MDG Hierarchy Maintenance
Collective Processing Capabilities

In general, hierarchies are maintained in the hierarchy view of the generic application Collective
Processing. The main features are:
You can insert new or existing nodes. You can insert several nodes in one step.
You can move nodes (incl. sub-nodes) with arrow buttons. Drag & drop is also
supported.
You can find nodes in the hierarchy.
You can expand ranges to see which entities are currently assigned.
You can trigger a mass change with selected entities from the hierarchy view. Ranges
are expanded.
MDG Hierarchy Maintenance
Collective Processing Layout

The layout of the hierarchy view is derived automatically


Columns for descriptions are included according to the text settings of all entity types
specified for the hierarchy.
Columns for attributes of the leading entity type are included (unless disabled in the
field property view by checking the flag No result list).
MDG Hierarchy Maintenance
Collective Processing Using ranges

If you have chosen the Use Ranges Permitted on End Nodes for an entity type of your hierarchy you
may specify ranges instead of discrete values for the entities that sit at the leaves of the hierarchy.
For the boundaries of the range no existence check is performed.
You can expand the range at any time from the context menu to see which entities
currently fall into the given range.
MDG Hierarchy Maintenance
File upload and download

Hierarchies can be uploaded and downloaded using the generic CSV-file based web applications
(USDM_FILE_UPLOAD & USM_FILE_DOWNLOAD).
Enhancement spots are available to do file conversions during upload and download.
Upload: USMD_DATA_TRANSFER_UPL, methods CONVERT and FINALIZE
Download: USMD_DATA_TRANSFER, method PROCESS_DOWNLOAD_HRY
MDG Hierarchy Management
Pre-delivered Models

Data Model Entity Type Version / Name Dependent Edition Dep.


0G CCTRG Not Version-dependent / Cross-name yes
0G CELEMG Not Version-dependent / Cross-name yes
0G CONSGRP Version-dependent / Not Cross-name yes
(name dependent)
0G FRSI Not Version-dependent / Not Cross- yes
name
0G FSI Version-dependent / Not Cross-name yes
(name dependent)
0G PCTRG Not Version-dependent / Cross-name yes
BP BP_HEADER Not Version-dependent / Not Cross- no
name (name dependent)
Extending Data Models

Reference How to Guide

MDG Data Model


Extensibility Options

(And Many more in SCN)

http://scn.sap.com/docs/DOC-7858
Day 5

MDG Framework Components

MDG Practice
Change Requests - Recap
Data maintenance using Change Requests the business
process view
General Change Request Processes
Determination of Workflow by Change Request Type
Configure Change Request Settings (1/3)
Status of Change Requests
Configure Change Request Settings (2/3)
Configure Change Request Settings (3/3)
Define Priorities and (Rejection) Reasons
MDG Training

Workflows OOTB and Extensions


Process Configuration
Look & Feel: SAP Business Workflow Design Tool - SWDD
Look & Feel: Rules Based Workflow
Ensure that workflow customizing is
active, complete and working
How MDG is integrated into the Business Workflow
Single Object Workflow: Steps linked to User Interaction
The links 1) configured step
Enhance the enhanced Financials workflow
Supplier Agent Determination
Set up or check the Business Rules Framework Plus
Change Request Workflow Process
Specific Process: Create Supplier
Master Data Governance for Material
Create/Change a Material Default Workflow
Master Data Governance for Material
Generic Workflow controlled by rules
Material Change Requests Types
Generic Workflow (BWF) Template
with BRF+ control
Master Data Governance Rule Based Workflow
Details on Main Branch
MDG Training

Setup of BRF+ Rule Based Worfklow


Master Data Governance for Material
Create/Change a Material: Representation in BRFplus
Set Up the Rule-Based Workflow
Maintain Content in the Single Value Decision Table
Set Up the Rule-Based Workflow (1/5)
Review and enhance the default steps
Set Up the Rule-Based Workflow (2/5)
Generate the decision tables and rules
Set Up the Rule-Based Workflow (3/5)
(Optional) Import structures from client 000
Set Up the Rule-Based Workflow (4/5)
Maintain Content in the decision tables
Set Up the Rule-Based Workflow (5/5)
Maintain Content in the decision tables
Step Types and Actions
Relationship Step TypeToolbar ButtonAction
Generic Workflow WS60800086
Example: Enhanced Change Request Workflow
BRF+ Infos

Technical Settings:

Transaction BRF+ / BRFplus

Documentation:

701: SAP NetWeaver Library -> SAP NetWeaver by Key Capability ->
Application Platform by Key Capability -> Business Services -> Business Rule
Framework plus
730: SAP NetWeaver Library -> SAP NetWeaver Library: Function-Oriented
View ->Application Server -> Application Server ABAP -> Other Services ->
Services for Application Developers -> Business Rule Framework plus
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/9a/6b67ce7c26446483
af079719edf679/frameset.htm

Start in MDG customizing

Using transaction USMD_SSW_RULE


Generating: USMD_SSW_CATA_MAT01 / USMD_SSW_CATA_<CR_TYPE>
Important variables in BRF+
Change Request & Workflow Trouble Shooting
Master Data Governance Training Series

Process Modeling : Change Requests and Workflows


Objectives

The objectives for this unit are:


Theory:
Become familiar with the configuration process for Change Requests and Simple Workflows
Understand the configuration of a rudimentary Organization Model for MDG Processing
Review the Out-of-the-Box (OOTB) Configuration Guides for all four MDG Domains
Hands On Tasks:
Define a rudimentary OM for a Data Governance Organization
Configure a new Change Request (CR) type for the Financials Data Model
Configure the corresponding workflow for the new CR type
Process several change requests using your new CR type
Process Modeling Change Requests
Change Requests
Statuses
Priorities
Reasons
Rejection Reasons
Change Request Properties
Change Request Steps
Enhancements and Checks for CR Steps
Entity Types per CR Step
Attributes per CR Step
UI per CR Step
Walkthrough in the MDG System
Process Modeling Organizational Model Configuration

Organizational Model Building Blocks


Organizational Unit
Relationships
Hierarchy
Positions
Holders
Users
T-Codes
PPOCE
PPOME
Walkthrough
Process Modeling Workflow Configuration
Workflow Configuration (Simple)
Type Linkage (one-time setup)
Configure Workflow Tasks (one-time setup)
Define Actions for CR UIs
Step Types and Action Assignment
Change Request Step Numbers
Assign Processors to CR Steps
Walkthrough in the MDG System
OOTB Configuration Guide Review

Out-of-the-Box Configuration Guide Review:


Financials
Financials Config
Guide 6.1

Material Master Material Config


Guide 6.1

Supplier Config
Business Partner Supplier Guide 6.1

Customer Config
Guide 6.1
Business Partner Customer
Custom Object
Config 6.1

Custom Object
Hands On Assignment Organization Model (OM)

Define a rudimentary Organizational Model with the following structure:


A root Organizational Unit with three subordinate Organizational Units: Financials, Business
Partner, Material
Two Positions within the Organizational Units: Requester and Approver
Assign user ID WMEINWEISER as one of the Holders of the Approver Position, assign the ID
MDG_APP_GRP as a second holder of the Approver Position
Hands On Assignment Change Request (CR)

Define a Change Request (CR) Type for the following:


Single Object Processing of a Profit Center Group
Allow both the Profit Center Group and Profit Center Hierarchy Entities to be maintained by this Change
Request type .
Associate the Change Request with an Edition that references your groups Financials Data Model
Display any error messages as warnings for this CR type
Define high priority change requests to have a two day SLA
Assign the CR Type to be processed by Workflow Template WS75700040
Hands On Assignment Workflow Configuration

Configure the WS75700040 Workflow Template


Action Assignment
Reverse the order of the buttons on Step Type 1
What did you notice about the table containing the Step Type configuration?
Change the pushbutton text for Approve to Concur
Change the quick info text for Approve to 1st level approval
Change the pushbutton text for Finalize Processing to Approve
Change the quick info text for Finalize Processing to Final Approval
Assign Processors to your CR Step Numbers
Determine how many steps need to have processors defined
Assign your Requester and Approver accordingly
Questions

HARNESS THE POWER OF DATA UNLEASH THE FULL POTENTIAL OF YOUR ENTERPRISE