Configuring Master Data Governance For U
Configuring Master Data Governance For U
Document History
The following table provides an overview of the most important document changes and approvals.
Table of Contents
1. Introduction ...................................................................................................................................... 5
3. Configuration Process...................................................................................................................... 9
3.4.2. Link Log. Actions with UI Application and Bus. Act.: Standard Definition ........................... 17
3.4.3. Link Logical Actions with Business Activity: Standard Definition ......................................... 18
3.6. Verify Data Quality, Search Settings and Duplicate Check ........................................................ 24
3.10. Deploying MDG RFM 9.0 when MDG RFM 8.0 is already present .......................................... 31
Appendix ...............................................................................................................................................46
1. Introduction
This document provides the information you require to set up SAP Master Data Governance (MDG)
for Utopia RFM Solutions for MDG™.
1.1. Purpose
This Configuration Guide provides the information you require to set up SAP Master Data Governance,
retail and fashion management extension by Utopia for S/4 HANA version 9.0 on S/4HANA 1610
(Utopia Retail and Fashion Management (RFM) Solutions for MDG™ v9.0 for S/4HANA 1610).
.
System Administrators
Technical Consultants
Functional Consultants
.
1.3. Organization
This is an optional section.
Prerequisites
Before You Start
Business Function
Setup Workflow
This Chapter describes the sequence of configuration
process steps as provided below.
Title Description
02: Change.
Note:
These business functions are available with MDG 9.0
objects into the authorization for the user WF-Batch.
To activate the workflow features, use the semi-automated configuration in transaction SWU3. Or
Alternately, you can access these settings in Customizing under SAP NetWeaver Application
Server Business Management SAP Business Workflow Maintain Standard Settings
For further information, see the documentation for the Configuration activity. Note the following while
maintaining the settings:
When you are configuring the RFC destination, super user authorization is required to create
the default WF-BATCH user.
Regenerate the authorization profile for SAP_ALL or include the USMD* authorization objects
into the authorizations of the user WF-Batch.
o For the Check Entries from HR Control Tables section, execute report RHSOBJCH in
transaction SE38 and keep the default settings.
o Maintain the prefix numbers for the standard objects.
o You do not require to maintain the Web Server node and Guided Procedures section.
/UGI4/MDGRFM_MENU - Master Data Governance for RFM: Menu (Only Menu)
/UGI4/MDGRFM_REQ - Master Data Governance for RFM: Requester
/UGI4/MDGRFM_SPEC - Master Data Governance for RFM: Specialist
/UGI4/MDGRFM_STEW - Master Data Governance for RFM: Data Steward
/UGI4/MDGRFM_DISP - Master Data Governance for RFM: Display
Ensure that you must have the following user roles assigned correctly in the PFCG transaction:
This role contains authorizations for basic tasks relevant to the configuration and
administration of SAP Master Data Governance (MDG) for all domains. Some authorizations
allow critical activities. If you have multiple users involved in the configuration and
administration of MDG content, Utopia recommends you to split this role into several new
roles and assign each new role a subset of the authorizations for this role. Such an approach
ensures users only complete tasks they are responsible for and reduces the risk of critical
errors. Authorizations for the MDG transactions are not included in this role.
SAP_PAGEBUILDER_DISPLAY role is required to use the Page Builder tool for accessing
homepages created using Page Builder.
Use transaction SICF to activate the services. For a detailed list of the relevant services, see Services
to be activated for Web Dynpro Applications [External File].
Note:
For the security reasons, services delivered for Web Dynpro applications are in an inactive state. You
must activate the required service. Once a service is activated, it cannot be reset to inactive state.
Refer to the Web Services for MDG-CO (for example Custom Objects) that need to be activated.
3. Configuration Process
This configuration process describes the minimum set of customizing steps and the recommended
check activities to perform the following:
Create article
Change article
Multiple-record processing
Run the settings for this process in Customizing under Cross-Application Components Processes
and Tools for Enterprise Applications Master Data Governance .
a. Link Log. Actions with UI Application and Bus. Act.: Standard Definition
b. Link Logical Actions with Business Activity: Standard Definition
5. Setting Up Search
9. Deploying MDG RFM 9.0 when MDG RFM 8.0 exists in your system
a. Check whether you can use the data model delivered by SAP for managing your
Article master data with MDG-RFM solution.
b. Activate the delivered data model AR in Customizing for Master Data Governance
under General Settings Data Modelling Edit Data Model .
Note:
You can select the governance scope at any point after you activate the Data Model.
The governance scope determines which fields from the data model can be edited by
the Master Data Governance application. Use this customizing activity to narrow the
governance scope Master Data Governance General Settings Process Modeling
Define Governance Scope
To support internal key assignment, run the activity in Customizing for Master Data
Governance under General Settings Data Modelling Define Prefixes for Internal Key
Assignment .
Note:
Mandatory: All temporary IDs must be prefixed with @@. Use the following values:
Data Model: AR
Entity Type: MARA
Prefix: @@
After the activation, you must set any existing User in the system as the owner of the
Overview IDs of the delivered BCV.
9. /UGI4/MDG_RFM_OTC_910: BC Set for MDG-RFM 9.0 SP01 Business Object Type Code
11. /UGI4/MDG_RFM_DIF_910: RFM - Define Object Types for Data Transfer 910
Make sure that the 2 BC-Sets for the Inbound Process Codes are also processed in any SAP ECC-
based target client and where the UGI8 software component is installed.
In this Customizing activity, you can specify if the system can hide the entity types for the data model
AR, and where it can hide.
Verify the pre-delivered field properties for the data model AR in Customizing under General
Settings UI Modeling Manage UI Configurations .
The Web Dynpro application and the application configuration in the PFCG role combine with settings
made in Customizing to determine the UI displayed.
You need to verify the UI modeling for the following Web Dynpro application configurations:
Link Log. Actions with UI Application and Bus. Act.: Standard Definition
Link Logical Actions with Business Activity: Standard Definition
3.4.2. Link Log. Actions with UI Application and Bus. Act.: Standard Definition
The Logical actions shown in the following tables need to be entered manually.
For more information, see Customizing for Master Data Governance under General Settings Process Modeling Business Activities Link Log. Actions with UI
Application and Bus. Act. Standard Definition .
3.4.2.1. Table 1: RFM Objects Logical Actions UI Application and Bus Act. Linkage - Manual Entry Required
Log. Business
BO Type Current UI Application Name Current UI Configuration Target UI Application Target UI Configuration
Action Activity
Log. Business
BO Type Current UI Application Name Current UI Configuration Target UI Application Target UI Configuration
Action Activity
General Settings Process Modeling Business Activities Link Actions with UI Application and Bus. Act. Standard Definition .
For each UI application and action, you can assign a business activity. At runtime, you can then use the available change request types.
3.4.3.1. Table 1: Link Logical Actions with Business Activity: Standard Definition
Description Business
UI Application Name UI Configuration Logical Action Description
Activity
Description Business
UI Application Name UI Configuration Logical Action Description
Activity
USMD_OVP_GEN /UGI4/_AR_OVP_MARA LOAD Data Exchange AR0B Article Master Load DIF
USMD_OVP_GEN /UGI4/_AR_OVP_MARA MASS Mass Processing AR0A Article Master Mass Change
2. Long Text Table Creation and Initial Load: As the Long Text is used in the Search, first you
must execute a report, and perform the initial load of this Texts the format of the HANA views.
a. In transaction SA38, execute the report MDG_HDB_MAT_MIGRATE_LONGTEXT as a
background job.
b. Select the Overwrite target table records checkbox, to perform the initial load of Article
long texts to the database table MDGHDB_LONGTEXT.
Sales Text
Purchase Order Text
Inspection Text
3. Active the Search View
a. To activate the already delivered in the product Hana Search View
/UGI4/RFM_HA_SEARCH, navigate to Master Data Governance General Settings
Data Quality and Search Search and Duplicate Check Create Search View
b. Click Edit to activate the Hana Search View and provide the following details for the first
guided step Enter General Data.
Field Value
Search View /UGI4/RFM_HA_SEARCH’
IMPORTANT:
Choose the HANA package only from customer namespace and ensure that the package also
exists in the ABAP Development environment. Currently this existence is not checked by the
system.
Note:
You can activate the Rule Set if you want to adjust your Hana Search later in the HANA
Studio. With this you can go attribute by attribute and give your choice of attribute
characteristics like fuzziness and so on. The Rule set is for saving your manual changes in
the HANA studio. Next time when you generate the view the manual changes are not
overwritten.
c. Click Next and continue with the next guided step Select Entities and Attribute.
Select the required entity and attribute at the Hana database. The system, by default
selects few attributes and entity.
d. Click Next to continue with the Review and Generate step.
Review the already selected (in the previous step) Entity and Attribute.
e. Click Save twice.
Note:
MDG-RFM 9.0 delivers a set of SAP HANA Search templates segregated in different Article
functionalities and processes. These Search types are optional to activate and generate
depending on your Data Model needs.
For generating each view, perform the same steps of the SAP HANA Main View activation
and generation explained in this chapter
You can find those and the related usage description via the customizing path
Master Data Governance General Settings Data Quality and Search Business Add-Ins
Note:
If you upgrade from a previous release and especially leveraging TREX / Enterprise search, make
sure you disable the old BAdIs for MDG-RFM and eventually for MDG-M:
Furthermore, you need to check if the old search object connector template had been removed:
Master Data Governance General Settings Data Quality and Search Search and Duplicate
Check Assign Search Object Connector Templates to Object Types
Remove any entry for the Business Object Type DRF_0017 MDG_Article!
1. In the Delivered Standard, HANA Search Setting, you can verify the following.
a. Existence of entry HA and Freeform settings are activated if this feature is planned to
be used.
Note:
This entry cannot be removed or deactivated (E-class entry delivered by SAP). You
can verify these settings in Customizing by navigating to Master Data Governance
General Settings Data Quality and Search Search and Duplicate Check Define
Search Application
c. As part of Standard, Main Entity is allocated to the Search help, Follow the below
Mentioned Screen shot for verifying the same.
Field Description
Search mode HA
Data Model AR
d. As part of Standard Main Entity is allocated to the Search Application, Follow the
below given table and screenshot for verifying the same.
Field Description
Search mode HA
Data Model AR
Entity Type MARA
a. Select the Search Mode ‘HA’ by Navigating to Master Data Governance General
Settings Data Quality and Search Search and Duplicate Check Define Search
Application
b. Select the Search mode ‘HA’ and click the Match Profile
c. If you want to run a duplicate check, assign the pre-delivered match profile
MATCH_AR_ARTICLE or your own match profile to the data model AR and the MARA
entity type. Navigate to General Settings Data Quality and Search Search and
Duplicate Check Match Profile .
d. Duplicate Check relevant fields are added as per the standard delivery. Follow the
below given table and screenshot for verifying the same.
Field Value
Search mode HA
Data Model AR
Match Profile Id MATCH_AR_ARTICLE
Entity type MARA
Attribute(Fuzziness) ATTYP (1,00), MATKL, MTART (1,00), TXTMI
3. For activating the Duplicate Check in RFM done with HANA Search provider do the following:
Navigate to General Settings Data Quality and Search Search and Duplicate Check
Configure Duplicate Check for Entity Types .
Field Value
Data Model AR
Entity type MARA
Search Mode HA
Low Thres 60(Any)
High Thres 85(Any)
Match Profile ID for Duplicate MATCH_AR_ARTICLE
Check
Include search help /UGI4/RFM_HA_SEARCH
MPbased UI To be checked [X]
The following information describes the minimal settings for a basic governance process. For more
information about each customizing activity, see the relevant documentation for that customizing
activity.
1. Review and/or define which statuses the change requests can have, and which processing
options are enabled for those statuses. Optionally, you can add new statuses to be used in the
change request types.
For more information, see Customizing for Master Data Governance under General
Settings Process Modeling Change Requests Edit Statuses of Change Requests ..
The following statuses are delivered for the SAP standard processes.
2. Check that the following business activities are in your system and that they are assigned to
the default data model AR.
AR01 Article Master Create
AR02 Article Master Change
AR03 Article Master Display
AR0A Article Master Mass Change
AR0B Article Master Load (DIF)
For more information, see Customizing for Master Data Governance under General
Settings Process Modeling Business Activities Create Business Activity .
3. Create new change request types for data model AR, or validate after import MDG for RFM.
For more information, see Customizing for Master Data Governance under General
Settings Process Modeling Change Requests Create Change Request .
The following table shows the change request types for data model AR. Only the relevant
columns are included.
The standard workflow template used by Master Data Governance for article is
WS60800086. This template is a rule-based workflow which uses BRF+ decision tables.
There is also a workflow template without BRF+, which covers the same processes. If you want to
use this template, replace template WS60800086 with template WS46000057 in the relevant
Change Request type.
The following settings should exist in the substructures of the change request types:
AR01
o Entity type: MARA
o UI Configuration ID:
o Msg. output: Standard
o Business Activity: Article Master Create (AR01)
o Service Level Agreement for Change Request Types: <leave empty>
AR02
o Entity type: MARA
o UI Configuration ID:
o Msg. output: Standard
o Business Activity: Article Master Change (AR02)
o Service Level Agreement for Change Request Types: <leave empty>
AR0A
o Entity type: MARA
o UI Configuration ID:
o Msg. output: W Issue Error Messages as Warnings
o Business Activity: Article Master Mass Change (AR0A)
o Service Level Agreement for Change Request Types: <leave empty>
AR0B
o Entity type: MARA
o UI Configuration ID:
Optional
Optionally, you can define priorities, reasons, or rejection reasons for change requests. You can enter
codes and a short description to tag or classify your change requests. These codes can be used later
for change request analytics (process quality analysis). They also can 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.
Perform the following activity in Customizing for Master Data Governance under General Settings
Process Modeling Change Requests Define Priorities / Reasons / Rejection Reasons for Change
Requests .
Optional
you can define print forms for change requests. By default, the form USMD_EDITION_CREQUEST is
used. This is relevant only if your own or multiple print forms are required.
For more information, see Customizing for Master Data Governance under General Settings
Process Modeling Change Requests Define Print Form for Change Requests . text
After the installation of PAT file, activate the SICF service: WDA_MDG_RFM_CFG
Note:
All the CRs should be activated and there should not be any staging data while maintaining the
Splitter by the transaction /UGI4/MDG_RFM_CFG
1. After the installation of PAT file, activate the SICF service: WDA_MDG_RFM_CFG
a. Activation Path: SICF -> Services -> SAP-> BC-> Webdynpro-> UGI4 ->
WDA_MDG_RFM_CFG
i. Right click, select “Activate Service”
ii. In the popup, select “Yes to all”.
3. When no splitter maintained, below error shall be populated on the MDG screens.
4. When the staging data is not cleared or activated, below error shall be populated on activation
of splitter by the transaction code “/UGI4/MDG_RFM_CFG”.
a. Maintain the IDOC variant count by using the transaction code “/UGI4/MDG_RFM_CFG”.
This count is to specify how many variant articles need to be sent in one IDOC if the generic
article is outbound via DRF. This is an optional step as if no count is maintained, all the
variant articles of the generic article will be sent in the same IDOC to the target system
3.10. Deploying MDG RFM 9.0 when MDG RFM 8.0 is already
present
b. Make sure before deploying the new add-on (MDGRFM900), no CRs related to AR Data
Model exist. If you have any open Article CRs you will lose Staging Data in your current
CRs.
c. After MDGRFM900 is deployed, proceed to delete CRTYPE AR03 under customizing
MDGIMG->General Settings->Process Modelling->Change Requests->Create Change
Request Type:
i. Select AR03
ii. Click Delete button,
iii. Select All Entries (which deletes all dependent entries too).
d. After Activating the Data Model, proceed to adjust staging data with the new data model.
Necessary general settings for workflows are defined.
The organizational plan is defined in Customizing for SAP NetWeaver under Application
Server Business Management SAP Business Workflow .
The active type linkages for Article (BUS2250) are set correctly.
Follow the instructions in Customizing for MDG under General Settings Process Modeling
Workflow Activate Type Linkage .
For object type BUS2250 check that the Type Linkage Active indicator is active for the
events CREATED, ACTIVATED, and ROLLED_BACK.
In addition, check that the Enable Event Queue indicator is active for the events
ACTIVATED, and ROLLED_BACK, but not for the event CREATED.
Note:
The standard workflow template used by Master Data Governance for article is WS60800086.
To ensure the general assignment of processors using the rule-based workflow, run the following
activity in Customizing for Master Data Governance under General Settings Process Modeling
Workflow Configure Workflow Tasks .
Check that the steps for Rule-Based Workflow are correctly imported by running the following activity
in Customizing: General Settings Process Modeling Workflow Rule-based Workflow Define
Change Request Steps for Rule-Based Workflow .
The following are the default steps required for all change request types:
Due to technical restrictions, further settings cannot be included in the BC-sets. Perform the following
checks and take action as required:
Run the following activity in Customizing: General Settings Process Modeling Workflow Rule-
based Workflow Configure Rule-Based Workflow .
DT_SINGLE_VAL_AR
01.xlsx
Note:
Do not change this file manually, upload the file as it is, and after the upload you can
change data in your table.
3. From the left pane, select the User Agent Decision Table
a. Click Edit, then in Additional Actions and click Import from Excel and activate the
Table.
b. Upload below excel File DT_USER_AGT_GRP_AR01 and click OK.
DT_USER_AGT_GRP_
AR01.xlsx
Note:
Do not change this file manually, and upload the file as it is. After uploading the file,
you can change data in your Table.
4. From the left pane, select the User Agent Decision Table
a. Click Edit, then in Additional Actions and click Import from Excel and activate the
Table.
b. Upload Excel File DT_NON_USER_AGT_GRP_AR01 and click OK.
DT_NON_USER_AGT
_GRP_AR01.xlsx
Note:
Do not change this file manually, and upload the file as it is. After uploading the file, you
can change data in your Table.
5. Repeat these steps for all relevant change request types AR02 and AR0A.
Maintain your content in the decision tables, reflecting your governance process. You can use
the pre-delivered SAP content as a starting point.
Note:
If you extend the BRF plus decision tables, make sure that the status of the final step is set to
05 Final Check Approved or 06 Final Check Rejected.
The following are the minimal settings for the relevant change request types.
DT_SINGLE_VAL_AR01
DT_NON_USER_AGT_GRP_AR01
DT_USER_AGT_GRP_AR01
Users involved in the Master Data Governance (MDG) process need to be included in table
DT_USER_AGT_GRP_AR01. This action enables the users to receive and execute the
workflow tasks. Maintain agents (for example the users or organizations in the Portal Content
and Portal Role Assignment sections of this guide) for all change request types and their
associated workflow steps. Each condition alias that appears in the DT_SINGLE_VAL_AR01
table needs at least one processor, automatic or user (group). For all non-automated steps, at
least one entry needs to exist in DT_USER_AGT_GRP_AR01.
Conduct this maintenance for all relevant change request types. Further details on the
workflow concepts can be found here [External].The following change request types appear in
the standard delivery: AR01, AR02 and AR0A.
DT_SINGLE_VAL_AR01/2/A
DT_USER_AGT_GRP_AR01/2/A
DT_NON_USER_AGT_GRP_AR01/2/A
Notes:
It is necessary to activate your new entries for each of the three decision tables.
The quickest way to allow users to participate in any workflow step for testing purposes is
assigning the following roles to their user ID in SU01:
o /UGI4/MDGRFM_SPEC (The MDG-RFM Specialist role of PFCG/SU01)
o /UGI4/MDGRFM_STEW (The MDG-RFM Steward role of PFCG/SU01)
If the system cannot find a processor for your change requests check the background steps of
the change requests workflow log to see if a work item with the description Set Status x for
Change Request y is in process or in error. If this is the case regenerate the authorization profile
of SAP_ALL or include USMD* authorization objects into the authorization for the user WF-
Batch.
Choosing the process pattern 06 Activation (Bypass Snapshot) means that the article will be
activated, even if the article record was changed in the backend system since the change
request was created. Any backend changes are lost upon activation.
Prerequisites:
BI Java Server
A browser with flash plug-in
MDG Analytics is based on operational analytics in ECC. The Infoprovider is an ODP
(Operation Data Provider) and it is located in the ECC system and not in BW.
Note:
Processing Time
MDG_CR_PROCESTIME_TREE – Processing Time
MDG_ANLY_CR_REJ_REASON - Change Request Rejection reason
Note:
"The Incorrect entries for UGI4 in table IBO_C_WF_TAS" need to be deleted before adding
the below entries.
SAP NetWeaver Portal
SAP NetWeaver Business Client
The SAP NetWeaver Portal content for MDG for material is derived directly from the system PFCG
roles. To create SAP NetWeaver Portal roles for your users, you must log on to your portal and
upload the content information from your back-end system PFCG roles.
To upload your portal content to the portal, perform the following actions:
If you are running SAP Master Data Governance on the SAP NetWeaver Business
Client (and not on the SAP NetWeaver Portal), you need to create, define, and configure the roles for
the Business Client in the SAP ERP system.
There are four roles containing authorization and navigation information and one role
(/UGI4/MDGRFM_MENU) containing only navigation information.
To assign and personalize the roles Master Data Governance for RFM perform the following actions:
1. On the SAP Easy Access screen, choose Tools Administration User Maintenance Role
Administration Roles or alternatively, run transaction PFCG (Role Maintenance). Choose
role /UGI4/MDGRFM_MENU.
This role ensures that the necessary steps can be started without using the SAP NetWeaver
Portal. This can be used for testing or if the portal is inactive.
2. Verify the setting of the authorization objects within the roles and restrict them if required.
3. On the SAP Easy Access screen, choose Tools Administration User Maintenance Users
. Run transaction SU01 (User Maintenance) and assign the Master Data Governance for
Material: Menu role (/UGI4/MDGRFM_MENU) for application to the MDG user.
If you want to use the delivered FIORI User Interfaces, follow the complementary guide.
<<<< name of the guide >>>>>
In SAP MDG you can choose different User Interface (UI) Themes to display the UI.
The UI theme for default is SAP_CORBU theme (that is the theme displayed below).
The SAP_BLUECRYSTAL theme also exists, and the theme has a FIORI 1.0 as displayed below.
If you are running MDG for RFM 900 in S/4 HANA, SAP_BELIZE theme is available with a FIORI 2.0
as displayed below.
To choose and run the required Theme, perform the following actions.
Appendix
This Chapter provides the details of other relevant Configuration Guide links