S4 HANA Master Data

Governance (MDG)
Vendor Master Governance
Contents/agenda slide

 Introduction
 MDG Functionalities
 Data Modelling
 UI Modelling
 Process Modelling
 Reporting

Page 2 Tuesday, May 31, 2022 Presentation title

Introduction

Standard Data Models:

 Material Master (MM)
 Business Partner (BP)
 Financials (0G)

Page 3 Tuesday, May 31, 2022 Presentation title

S4 HANA MDG Functionalities

Page 4 Tuesday, May 31, 2022 Presentation title

 “
Data Modeling

Page 5 Tuesday, May 31, 2022 Presentation title

Data Model

 A data model in Master Data Governance is comprised of various elements

(entity types, attributes, and relationships) to enable you to model master
data structures of any complexity in the system
 The system uses the data model to generate database tables for storing the
data you enter when managing the master data

Page 6 Tuesday, May 31, 2022 Presentation title

Reuse area versus Flexible option

Generated active area (flex mode): ► Re-Use active area (re-use mode): Existing
Tables as defined in the MDG data model structures of applications are used. For
are used to store active data. example, MDG for Business partner makes
use of the BUT000 table in S4 HANA.

► The BP data model is preconfigured with one reuse area called PARTNER. This reuse area
points to the access class CL_MDG_BS_BP_ACCESS_MASTER, which can handle all
fields of the pre-delivered data model

Page 7 Tuesday, May 31, 2022 Presentation title

BP Data Model

Type 1 entities:
• ADDRNO
• BP_HEADER
• BP_HRCHY
• BP_REL
• BP_SUBHRY
• FKKVK

Note: Footnotes, EY Interstate Light Italics 9pt - Lorem ipsum dolor sit amet, in quas nostrud laoreet per, ad vim minim inermis. Lorem ipsum dolor
Source: Footnotes, EY Interstate Light Italics 9pt - Lorem ipsum dolor sit amet, in quas nostrud laoreet per, ad vim minim inermis. Lorem ipsum dolor

Page 8 Tuesday, May 31, 2022 Presentation title

 “
UI Modeling

Page 9 Tuesday, May 31, 2022 Presentation title

User Interface for Supplier Master Governance

 Standard application configuration for Business partner application is BS_OVP_BP.

 Standard application configuration Supplier governance application is BS_OVP_SP.

Page 10 Tuesday, May 31, 2022 Presentation title

User Interface for Supplier Master Governance (Cont..)

 We can map the UI configuration to Business object type (OTC), Logical action and
Business Activity combination.

Standard mapping:
General Settings  Process Modelling  Business Activities  Link Logical actions
with UI Application and Business activity: Standard Definition

General Settings  Process Modelling  Business Activities  Link logical actions

with Business Activity: Custom Definition

Client specific mapping (custom):

General Settings  Process Modelling  Business Activities  Link Logical actions
with UI Application and Business activity: Standard Definition

General Settings  Process Modelling  Business Activities  Link logical actions

with Business Activity: Custom Definition

Page 11 Tuesday, May 31, 2022 Presentation title

Adapting Material Master User Interface

Options for Adaptations:

 Copy Application
 Customizing
 Enhancement
 Context Based Adaptations

Page 12 Tuesday, May 31, 2022 Presentation title

Copy Application

 With the help of the Application Hierarchy Browser for Floorplan Manager, it is quite
simple to copy the whole configuration tree of an FPM application.
 It is also possible to keep some branches of the original tree and copy only the part
you need to adapt.

Advantages:
 It is easy to understand what is happening and there is absolutely no interference
between your copied entities and later deliveries of the original application.
Drawbacks:
 Corrections and improvements of configurations delivered by SAP which affect the
original application will not reach the copied entities of your application.

Page 13 Tuesday, May 31, 2022 Presentation title

Enhancement

 All necessary entities of an application configuration can be enhanced separately.

 The enhancement is saved using workbench request and is applied across all clients of
the system

Advantages:
 It is the only option that allows you to combine both code changes and configuration
adaptations.

Drawbacks:
 The enhancement of a component configuration is technically nothing other than a
system-managed copy of the configuration. Therefore, it is not possible to enhance
only parts of a configuration.
 Enhanced configurations are separated from corrections or upgrades delivered in the
future.
 Additionally, it is not recommended to have more than one enhancement per
component configuration, as only one enhancement is ever active.

Page 14 Tuesday, May 31, 2022 Presentation title

Customizing

 Adaptations via customizing are valid for all users in the corresponding client and can
be transported using customizing request.
 The smart thing about customizing is that it only contains the changed parts of the
application (so-called delta-handling). At runtime, the original configuration is
merged with the changes in the customizing layer

Advantages:
 Only the changed parts of the configuration are stored. Therefore, later changes or
corrections will be applied even to an adapted configuration. No additional effort is
required compared to modifying the original object.

Drawbacks:
 Customizing is restricted to configurations. There is no way to customize code.
 If a configuration is deleted, the customizing delta remains in the data base. This
might lead to semantic data inconsistencies during the FPM runtime, as the delta
might contain only fragments of the information needed to render the FPM
application

Page 15 Tuesday, May 31, 2022 Presentation title

Context Based Adaptations (CBA)

 With CBA, the UI can be adapted depending on runtime parameters.

 CBA works based on adaptation schema and adaptation dimensions.
 A CBA enabled application will have an adaptation schema assigned to it.
 And each adaptation schema will have set of adaptation dimensions (nothing but
parameters which influence UI configuration)
 CBA cannot be used for the UIBB of Classification because it is implemented with
Web Dynpro bypassing FPM.
 Custom dimensions can also be added to the adaptation schema to influence UI at
runtime (but involves feeder class enhancement)

Customizing view:
Adaptation Schema :
FPM_V_ADAPT_SCHM

Adaptation Dimension:
FPM_V_ADAPT_DIM

Page 16 Tuesday, May 31, 2022 Presentation title

 “
Process
Modeling

Page 17 Tuesday, May 31, 2022 Presentation title

Define Governance Scope

 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.
 Governance scope can be defined at entity level as well as attribute level
 Ungoverned fields will not be considered during change request processing
(including validations and derivations)
 Removing the unused fields from governance scope will improve the
performance of change request processing considerably.

Page 18 Tuesday, May 31, 2022 Presentation title

Define Governance Scope (Cont…)

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.

Page 19 Tuesday, May 31, 2022 Presentation title

Change Request Types

 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.
 Change request type controls the type of changes to be executed and
workflow process
 SAP Business Workflow/Rule based workflow can be used to process
change requests in SAP Master Data Governance
 A change request type must be mapped to a business activity which
determines the usage of the change request type (ex: Create Supplier,
Process Supplier, Delete Supplier)
 In MDG, all master data changes are handled via change request
 Each change request number is associated with a change request type

Page 20 Tuesday, May 31, 2022 Presentation title

Change Request Types (Cont…)

Business Activities for BP data model (Supplier Governance):

Page 21 Tuesday, May 31, 2022 Presentation title

Change Request Types (Cont…)

While 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

Page 22 Tuesday, May 31, 2022 Presentation title

Change Request Types (Cont…)

Configure properties of change request step:

MDGIMG  General Settings  Process Modelling  Change Requests 

Configure Properties of Change Request Step

Using this configuration path, we can control,

 Whether validations and basic checks can be triggered for the change request
step or not
 Control field properties of the entities/attributes
 UI assignment for change request steps

Page 23 Tuesday, May 31, 2022 Presentation title

Rule Based Workflow

 Using the rule-based workflow, you can configure any kind of change
request process
 You can define different change request processes in decision tables of the
Business Rules Framework plus (BRFplus)
 To use the rule-based workflow for a change request type, we need to assign
workflow template WS60800086 to the CR type.

In rule-based workflow, three decision tables are available each change request
type.
• Single value decision table
• User agent decision table
• Non-user agent decision table

Page 24 Tuesday, May 31, 2022 Presentation title

Rule Based Workflow (Cont…)

Single value decision table:

 The Single Value Decision Table 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.

User agent decision table:

 The User Agent Decision Table 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.

Page 25 Tuesday, May 31, 2022 Presentation title

Rule Based Workflow (Cont…)

Non-user agent decision table:

 This decision table determines the process patterns for background steps.
 The Non-User Agent Decision Table contains the background steps that are
involved in the change request process and that do not have end user
participation.

BADI’s for rule based workflow:

USMD_SSW_RULE_CONTEXT_PREPARE:
 Used to enhance BRF+ decision tables of rule based workflow.
USMD_SSW_DYNAMIC_AGENT_SELECT:
 Used to dynamically determine the user agent for workflow step and
overwrite the agent assigned in User agent decision table.

Page 26 Tuesday, May 31, 2022 Presentation title

Validations/Derivations

 Checks/Validation raise messages. Message with severity info, warning,

error, and abort are possible.
 Derivations calculate values for attributes and can also raise messages. Only
messages with severity info are possible.

Overview of MDGM Validations and Derivations:

 Model driven checks
 Re-use of existing check logic in ERP backend system or S/4HANA backend
system
 Custom checks and validation (modelled and programmed)
 Custom derivations (modeled and programmed)

Page 27 Tuesday, May 31, 2022 Presentation title

Model driven checks

Code lists:
 The considered code list for the check comes from the Fixed Values or
Value Range Table which is assigned to the domain of the data element.
 In the customizing for the BP data model, you can use the ‘No Existence
Check’ to deactivate the standard existence check for the value of the
attribute.

Cardinality check:
 A field is mandatory if the referencing relationship has cardinality 1:1.

Format check:
 Data element is used for format check.

Required fields:
 Attributes can be defined as required fields.

Page 28 Tuesday, May 31, 2022 Presentation title

Custom checks and validation

 Rules from the Business Rules Framework (BRF+)

 Coded rules using the Badi USMD_RULE_SERVICE

Page 29 Tuesday, May 31, 2022 Presentation title

Custom derivations

 Rules from the Business Rules Framework (BRF+)

 Coded rules using BAdI USMD_RULE_SERVICE
 Coded rules using BAdI USMD_RULE_SERVICE_CROSS_ET
 Derivation with SMT-Mapping

Page 30 Tuesday, May 31, 2022 Presentation title

 “
Any Questions?

Page 31 Tuesday, May 31, 2022 Presentation title