MDG88 Login Configuration Guide
MDG88 Login Configuration Guide
for S/4HANA
Release 2021
Retail and Fashion Management by Utopia for S/4HANA
Document History
The following tables provide an overview of the most important document changes and approvals.
Version Date Description Author/Reviewer
Approval History
Version Date Description Name
1.0 25-03-2022 Final version Ramesha Kalammanavar
Table of Contents
1. Introduction ......................................................................................................................................6
4. Configuration Process....................................................................................................................10
4.4.1. Link Log. Actions with UI Application and Bus. Act.: Standard Definition ........................... 27
4.8.1. Optional................................................................................................................................ 39
7. Configuration Process....................................................................................................................67
7.2.3. Configure MDG Check flag for RMP Schema (Optional) .................................................... 76
7.2.4. Configure Number Range Check flag for RMP Schema (Optional) .................................... 77
7.2.5. Configure Variant No. Validation for RMP Schema (Optional) ............................................ 77
7.2.6. Configure Highlight Changes Indicator / Saved Colr / UnSaved Colr for RMP Schema
(Optional) ....................................................................................................................................... 78
7.4.1. Link Log. Actions with UI Application and Bus. Act.: Standard Definition ........................... 81
1. Introduction
This document provides the information you require to configure SAP Master Data Governance
(MDG) for Utopia RFM Solutions and the optional RMP Mass Processing solution.
1.1. Purpose
This Configuration guide provides the information you require to set up SAP Master Data Governance
(MDG) for Utopia Retail and Fashion Management (RFM) extension Solutions for MDG for S/4HANA
2021 solution and the optional RMP Mass Processing solution.
• System Administrators
• Technical Consultants
• Functional Consultants
1.3. Organization
This guide primarily consists of the following sections.
• Business Function
• Set Up Workflow
• Set Up Search
• Import MDG Content for RFM
• Adjust Profile Parameters
• User Roles
• Web Dynpro Applications
• Number Ranges
Note
The required authorization objects are delivered with the authorization role SAP_MDG_ADMIN.
With t-code PFCG, Utopia recommends you to create a copy of SAP_MDG_ADMIN role and
assigning the relevant authorization values. For the authorization object USMD_DM Data Model
you need to assign the values for the authorization field USMD_MODEL Data Model (here AR)
and the values for the authorization activity ACTVT Activity.
Example:
01: Create or Generate
02: Change
2. Make sure that you have activated the following business functions:
• Business Function Set SAP Retail (ISR_RETAILSYSTEM)
• Master Data Governance, Generic Functions (MDG_FOUNDATION)
• 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 Feat. Pack (MDG_FOUNDATION_5)
• Master Data Governance, Generic Functions 8.0 (MDG_FOUNDATION_6)
• Master Data Governance, Generic Functions 9.0 (MDG_FOUNDATION_7)
• Master Data Governance, Generic Functions 9.1 (MDG_FOUNDATION_8)
• Master Data Governance, Generic Functions 9.2 (MDG_FOUNDATION_9)
• Master Data Governance, Generic Functions 1909 (MDG_FOUNDATION_10)
• Master Data Governance, Generic Functions 2020 (MDG_FOUNDATION_11)
• Master Data Governance, Generic Functions 2021 (MDG_FOUNDATION_12)
For additional BCV Content, activate business function /BCV/NWBC_SIDEPANEL. If you want to
use the MDG for Utopia RFM homepage or the Business Context Viewer, activate the business
functions /BCV/MAIN and /BCV/MAIN_1.
For more information on the Business Context Viewer, see Business Context Viewer in Single
Processing [External].
Note
Regenerate the authorization profile of SAP_ALL or include USMD* authorization objects into
the authorization for the user SAP_WFRT.
2. To activate the workflow features, use the semi-automated configuration in transaction code (t-
code) SWU3. Alternately, you can access these settings in Customizing under SAP NetWeaver
> Application Server > Business Management > SAP Business Workflow > Maintain Standard
Settings.
When you are configuring the RFC destination, superuser authorization is required to create the
default SAP_WFRT user.
• Refer to the note for aligning the authorizations for SAP_WFRT user for MDG-RFM -
2746880 - S/4 HANA MDG RFM - SAP_WFRT Authorization Issues
• Regenerate the authorization profile for SAP_ALL or include the USMD* authorization objects
into the authorizations of the user SAP_WFRT.
a. For the Check Entries from HR Control Tables section, execute report RHSOBJCH in t-
code SE38 and keep the default settings.
c. It is not required to maintain the Web Server node and Guided Procedures section.
If you want to use the SAP NetWeaver Business Client with the single sign-on, ensure that the
parameters login/create_sso2_ticket and login/accept_sso2_ticket are set correctly.
Run t-code RZ11 to check that the host name is fully qualified for parameter icm/host_name_full
Assign the following MDG-RFM for FMS standard roles to the users, depending on their
responsibilities in the company:
Assign the following Fiori role to the users to access MDG RFM via Fiori Launchpad( The UGIRUI02
940 component should be installed)
/UGIRUI02/BCR_MDG_RFM - Article Governance - Fiori Role for MDG Apps
Ensure that you have the following user roles assigned correctly in the PFCG t-code:
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 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.
Note
Refer to the Fiori Implementation guide for Fiori roles. This document can be found on the SAP Help
Portal for RFM 2021 [External]
Note
For the security reasons, services delivered for Web Dynpro applications are in an inactive state. You
must activate the required service. Once service is activated, it cannot be reset to the inactive state.
Refer to the web services for MDG-CO (for example Custom Objects) that needs to be activated.
4. Configuration Process
This process describes the minimal set of customizing steps and recommended check activities
required to do the following:
New Mandatory(M)
SI No BC Set Name Installation Upgrade Optional(O)
1 MDGAF_BCV Yes No M
2 /UGI4/MDG_RFM_DATAMODEL_910 Yes No M
3 /UGI4/MDG_RFM_DATAMODEL_920 Yes No M
4 /UGI4/MDG_RFM_DATAMODEL_1909 Yes No M
5 /UGI4/MDG_RFM_DATAMODEL_2020 Yes No M
6 /UGI4/MDG_RFM_DATAMODEL_2021 Yes Yes M
7 /UGI4/MDG_RFM_DATA_STRUCTURE_910 Yes No M
8 /UGI4/MDG_RFM_910 Yes No M
9 /UGI4/MDG_RFM_DATA_STRUCT_1909 Yes No M
10 /UGI4/MDG_RFM_DATA_STRUCT_2020 Yes No M
11 /UGI4/MDG_RFM_DATA_STRUCT_2021 Yes Yes M
12 /UGI4/MDG_RFM_FMS_900 Yes No M
13 /UGI4/MDG_RFM_1909 Yes No M
14 /UGI4/MDG_RFM_BCV_900 Yes No M
15 /UGI4/MDG_RFM_OTC_900 Yes No M
16 /UGI4/MDG_RFM_OTC_910 Yes No M
17 /UGI4/MDG_RFM_DIF_2020 Yes No M
18 /UGI4/MDG_RFM_DIF_900 Yes No M
19 /UGI4/MDG_RFM_DIF_910 Yes No M
20 /UGI4/MDG_RFM_FMS_DIF_1709 Yes No M
21 /UGI4/MDG_RFM_DIF_1909 Yes No M
22 /UGI4/MDG_RFM_DATA_IMP_2020 Yes No M
23 /UGI4/MDG_RFM_VC_HDB_PP_FMAP_900 Yes No M
24 /UGI4/MDG_RFM_VC_MDGHDB001_900 Yes No M
25 /UGI4/MDG_RFM_VC_HA_DQ_SEARCH Yes No M
26 /UGI4/MDG_RFM_HANA_SEARCHVW_1909 Yes No M
27 /UGI4/MDG_RFM_VC_HDB_PP_FMAP1909 Yes No M
28 /UGI4/MDG_RFM_VC_MDGHDB001_2020 Yes No M
29 /UGI4/MDG_RFM_VC_HA_SHALLOC_2020 Yes No M
30 /UGI4/MDG_RFM_VC_HDB_PP_FMAP2020 Yes No M
31 /UGI8/MDG_RFM_IDOC_INB_PCODE_900 Yes No M
32 /UGI8/MDG_RFM_IDOC_INB_PCODE_910 Yes No M
33 /UGI8/MDG_RFM_IDOC_INB_PCODE1709 Yes No M
34 /UGI8/MDG_RFM_IDOC_INB_PCODE1909 Yes No M
35 /UGI4/MDG_RFM_OTC_1709 Yes No M
36 /UGI4/MDG_RFM_OTC_1909 Yes No M
37 /UGI4/MDG_RFM_LOG_PROD_CONFIG Yes No M
38 /UGI4/MDG_RFM_IDOC_MSGTYP_CP Yes No O
39 /UGI4/MDG_RFM_MSGTYP_FIELDS_CP Yes No O
40 /UGI4/MDG_RFM_IDOC_MSGTY_CP_2020 Yes No O
41 /UGI4/MDG_RFM_MSGTYP_FLD_CP_2020 Yes No O
42 /UGI4/MDG_RFM_DRF_2020 Yes No O
43 /UGI8/MDG_RFM_IDOC_FM_MAP_2020 Yes No M
44 POC_BC_SIDE_PANEL Yes No M
To enable the MDG-RFM pre-delivered content, some BC Sets need to be activated in the following
sequence:
Note
Select the Activation Mode as “Expert Mode” when prompted during the activation of each BC Set.
Once the above BC sets are activated, you need to activate the Data Model AR.
Use the following steps to activate the Data Model AR:
o Check (or enhance) and activate the AR Data Model.
o Check whether you can use the Data Model delivered by SAP for managing your
Article master data with MDG-RFM solution.
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
By deactivating or reactivating an entity, a relationship, or an attribute you are not changing any
dictionary or database object, you are only changing the ability of MDG to edit the chosen object.
When you take a field out of governance scope it becomes read-only on the MDG UI and you
can remove it if you want.
o Adjust Staging Area of Linked Change Requests(Required only for upgrade scenario)
After the activation, you must set any existing user in the system as the owner of the overview
IDs of the delivered BCV.
16. /UGI4/MDG_RFM_OTC_910: BC Set for MDG-RFM 9.0 SP01 Business Object Type Code
19. /UGI4/MDG_RFM_DIF_910: RFM - Define Object Types for Data Transfer 910
21. /UGI4/MDG_RFM_DIF_1909 – Define Data Transfer Business Activities for RFM/FMS 1909.
Ensure that the following 4 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.
Note
Mandatory: All temporary IDs must be prefixed with @@. Use the following values:
• Data Model: AR
• Entity Type: MARA
• Prefix: @@
Note
The following list of entries must be configured for one application at any system (either RFM or
FMS):
BO Type Log, Current UI Application Current UI Configuration Target UI
Action Name Application
DRF_001 USMD_OVP_GE
7 * * * N
DRF_001 USMD_OVP_GE
7 CREATE * * N
DRF_001 CHANG USMD_OVP_GE
7 E * * N
DRF_001 DISPLA USMD_OVP_GE
7 Y * * N
DRF_001 USMD_OVP_GE
7 MASS * * N
DRF_001 USMD_OVP_GE
7 LOAD * * N
Note
Go to MDGIMG General Settings Process Modelling Business Activities Link Log. Actions with
UI Application and Bus. Act. Custom Definition .
4.4.1. 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 .
Note
The following list of entries must be configured for one application at any system (either RFM or FMS):
BO Type Log, Action Current UI Application Name Current UI Configuration Target UI Application
DRF_0017 * * * USMD_OVP_GEN
DRF_0017 CREATE * * USMD_OVP_GEN
DRF_0017 CHANGE * * USMD_OVP_GEN
DRF_0017 DISPLAY * * USMD_OVP_GEN
DRF_0017 MASS * * USMD_OVP_GEN
DRF_0017 LOAD * * USMD_OVP_GEN
DRF_0017 CHANGE USMD_CHANGE_DOCUMENT USMD_CHANGE_DOCUMENT USMD_OVP_GEN
DRF_0017 CHANGE USMD_EDITION_CREQUEST USMD_EDITION_CREQUEST USMD_OVP_GEN
DRF_0017 CREATE USMD_CHANGE_DOCUMENT USMD_CHANGE_DOCUMENT USMD_OVP_GEN
DRF_0017 CREATE USMD_EDITION_CREQUEST USMD_EDITION_CREQUEST USMD_OVP_GEN
Note
Go to MDGIMG General Settings Process Modelling Business Activities Link Log. Actions with UI Application and Bus. Act. Custom Definition .
General Settings Process Modeling Business Activities Link Logical Actions with 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.
[Link]. Table 4: RFM Objects Logical Actions with Business Activity Linkage – Manual Entry Required
For RFM
UI Application Name UI Configuration Log. Action Description Business Activity Description
USMD_OVP_GEN /UGI4/_AR_OVP_MARA CHANGE Change AR02 Article Master Change
USMD_OVP_GEN /UGI4/_AR_OVP_MARA CREATE Create AR01 Article Master Create
USMD_OVP_GEN /UGI4/_AR_OVP_MARA DISPLAY Display AR03 Article Master Display
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
USMD_SEARCH /UGI4/_AR_SEARCH CHANGE Change AR02 Article Master Change
USMD_SEARCH /UGI4/_AR_SEARCH CREATE Create AR01 Article Master Create
For FMS
UI Application Name UI Configuration Log. Action Description Business Activity Description
USMD_OVP_GEN /UGI4/_AR_OVP_MARA_FMS CHANGE Change FMS2 Article Master Process (FMS)
USMD_OVP_GEN /UGI4/_AR_OVP_MARA_FMS CREATE Create FMS1 Article Master Create (FMS)
USMD_OVP_GEN /UGI4/_AR_OVP_MARA_FMS DISPLAY Display FMS3 Article Master Display (FMS)
USMD_OVP_GEN /UGI4/_AR_OVP_MARA_FMS LOAD Data Exchange FMSB Article Master Load DIF (FMS)
USMD_OVP_GEN /UGI4/_AR_OVP_MARA_FMS MASS Mass Processing FMSA Article Master Mass Change (FMS)
USMD_SEARCH /UGI4/_AR_SEARCH_FMS CHANGE Change FMS2 Article Master Process (FMS)
USMD_SEARCH /UGI4/_AR_SEARCH_FMS CREATE Create FMS1 Article Master Create (FMS)
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:
Web Dynpro Application Application Configuration UI
USMD_OVP_GEN /UGI4/_AR_OVP_MARA /UGI4/_AR_MARA_OVP
USMD_SEARCH /UGI4/_AR_SEARCH /UGI4/_AR_SEARCH_OVP
In case of FMS the following Web Dynpro application configurations shall be verified:
Web Dynpro Application Application Configuration UI
USMD_OVP_GEN /UGI4/_AR_OVP_MARA_FMS /UGI4/_AR_MARA_OVP_FMS
USMD_SEARCH /UGI4/_AR_SEARCH_FMS /UGI4/_AR_SEARCH_OVP_FMS
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 t-code 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.
This loads the following long text types:
4. 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’
Description Article HANA Search
Business Object Name DRF_0017
HANA Package ZMDG (Customer Namespace)
Note
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 Ruleset is for saving your manual changes in the HANA studio. Next
time when you generate the view the manual changes are not overwritten.
a. Click “Next” and continue with the next guided step “Select Entities and Attribute”.
i. Select the required entity and attribute at the HANA database. The system, by
default, selects few attributes and entity.
ii. Click “Next” to continue with the step as “Review and Generate”.
iii. Review the already selected (in the previous step) Entity and Attribute.
Note
MDG-RFM 2021 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.
The system displays the HANA Search UI as displayed in the following screen.
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
BAdI:Search For Data in Reuse Active Area
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:
BAdl Description
/UGI4/ENH_SEARCH_REUSE Implementation: Search for Data in Reuse Active Area
Furthermore, you need to check if the old search object connector template had been removed:
Master Data Governance General Settings Data Quality and 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
b. Search help ‘/UGI4/RFM_HA_SEARCH’ allocation to Search Application for HANA
Search.
You can verify the setting in Customizing by navigating to Master Data Governance General
Settings Data Quality and Search Search and Duplicate Check Define Search Application
Allocation of Search help to Search Application
c. As part of Standard, Main Entity is allocated to the Search Help, use the following
screen for verifying the same.
Field Description
Search mode HA
Data Model AR
Incl. Search Help /UGI4/RFM_HA_SEARCH
Entity type MARA
1. Select the Search Mode ‘HA’ by Navigating to Master Data Governance General Settings
Data Quality and Search Search and Duplicate Check Define Search Application
2. Select the Search Mode ‘HA’ and click the Match Profile.
3. 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
4. Duplicate Check relevant fields are added as per the standard delivery. Use the following table
and screen for verifying the same.
Field Value
Search mode HA
Data Model AR
Match Profile Id MATCH_AR_ARTICLE
Entity type MARA
5. 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
The following information describes the minimal settings for a basic governance process.
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 [Link] the below BC sets are activated in section 4.1 for the CR types
/UGI4/MDG_RFM_FMS_900 – SOP/ MOP CR types
/UGI4/MDG_RFM_DIF_900 – Data Load CR 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.
For RFM
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:
For RFM
AR01
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: Standard
4. Business Activity: Article Master Create (AR01)
5. Service Level Agreement for Change Request Types: <leave empty>
AR02
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: Standard
4. Business Activity: Article Master Change (AR02)
5. Service Level Agreement for Change Request Types: <leave empty>
AR0A
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: W Issue Error Messages as Warnings
4. Business Activity: Article Master Mass Change (AR0A)
5. Service Level Agreement for Change Request Types: <leave empty>
AR0B
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: W Issue Error Messages as Warnings
4. Business Activity: Article Master Load DIF (AR0B)
5. Service Level Agreement for Change Request Types: <leave empty>
For FMS
FMS1
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: Standard
4. Business Activity: Article Master Create (FMS1)
5. Service Level Agreement for Change Request Types: <leave empty>
FMS2
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: Standard
4. Business Activity: Article Master Change (FMS2)
5. Service Level Agreement for Change Request Types: <leave empty>
FMSA
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: W Issue Error Messages as Warnings
4. Business Activity: Article Master Mass Change (FMSA)
5. Service Level Agreement for Change Request Types: <leave empty>
FMSB
1. Entity type: MARA
2. UI Configuration ID:
3. Msg. output: W Issue Error Messages as Warnings
4. Business Activity: Article Master Load DIF (FMSB)
5. Service Level Agreement for Change Request Types: <leave empty>
4.8.1. 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 .
Optionally, 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 .
After the installation of the PAT file, activate the SICF service: WDA_MDG_RFM_CFG
Note
All the Change Requests should be activated and there should not be any staging data while
maintaining the Splitter by the t-code /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
3. When no Splitter is maintained, the following error is populated on the MDG screen.
4. When the staging data is not cleared or activated, below error shall be populated on Activation
of Splitter by the t-code “/N/UGI4/MDG_RFM_CFG”.
Note
In case open transactions (e.g.; Sales Order, Purchase Order) exists for an Article, the user will
not be able to change the Segmentation Structure and Strategy.
The RFC destinations of the client systems where we need to check for the open transactions
need to be maintained in the following configuration using the t-code
“/N/UGI4/MDG_RFM_CFG”.
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 the 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 .
You can use an alternative procedure with the generic workflow maintenance transaction as
described in the following steps:
b. In the Navigation area go to step 000073 Dialog Processing and select it.
c. In the Task Properties area, choose Agent Assignment for Task. Choose the Agent
Assignment for Task button.
d. On the next screen select Dialog Processing and choose the “Attributes” button.
f. Return to the Task Properties list and verify that the status icon beside Agent
Assignment is green or yellow.
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:
For RFM
Change Request Change Request Keys Successful Validation Description
Type Step Required
AR01 0 Empty Empty Processing
AR01 80 Empty Empty Approver
AR01 90 Empty Checked Final Check
AR01 91 Empty Empty Activation
AR01 92 Empty Empty Revision/Cancel BG
AR01 93 Empty Empty Validation
AR01 95 Empty Empty Revision Processing
AR01 99 Empty Empty Complete
Due to technical restrictions, further settings cannot be included in the BC Sets. Perform the following
checks and act as required:
Run the following activity in Customizing: General Settings Process Modeling Workflow Rule-
based Workflow Configure Rule-Based Workflow .
Alternatively, you can run t-code USMD_SSW_RULE for Process Definition of Rule-Based Workflow.
DT_SINGLE_VAL_AR
[Link]
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.
DT_USER_AGT_GRP_
[Link]
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.
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 (1-4) for all relevant Change Request Types AR02, AR0A, and AR0B
Maintain your content in the Decision Tables, reflecting your governance process. You can use
the pre-delivered SAP content as a starting point.
2 AR0A
DT_SINGLE_VAL_AR DT_USER_AGT_GRP_ DT_NON_USER_AGT
[Link] [Link] _GRP_AR0A.xlsx
3 AR0B
DT_SINGLE_VAL_AR DT_USER_AGT_GRP_ DT_NON_USER_AGT
[Link] [Link] _GRP_AR0B.xlsx
Note
If you extend the BRF+ 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 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 in Rule-Based Workflows for Material [External]. The following Change
Request Types appear in the standard delivery: AR01, AR02, and AR0A.
DT_SINGLE_VAL_AR01/2/A
Previous Step Previous Action Condition New Step New Change
Alias Request Status
00 (Create Change No value 1 80 (Approver) 02 (Changes to be
Request) executed)
90 (Final Check) 09 (Activate) 2 91 (Final Approval) 04 (Final Check to Be
Performed)
90 (Final Check) 04 (Reject) 3 95 (Revision 10 (To Revise:
Processing) Perform Changes)
91 (Final Approval) 31 (Activation 4 99 (Complete) 05 (Final Check
Successful) Approved)
Note
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:
1. /UGI4/MDGRFM_SPEC (The MDG-RFM Specialist role of PFCG/SU01)
2. /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 SAP_WFRT.
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.
For FMS
MDG-RFM uses advanced workflow capabilities by combining the SAP Business Workflow with the
SAP Business Rules Framework plus (BRF+) tool. This section describes how to activate and load
the necessary settings for BRF+.
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:
Change Request Change Request Keys Successful Validation Description
Type Step Required
FMS1 0 Empty Empty Processing
FMS1 80 Empty Empty Approver
FMS1 90 Empty Checked Final Check
FMS1 91 Empty Empty Activation
FMS1 92 Empty Empty Revision/Cancel BG
Due to technical restrictions, further settings cannot be included in the BC-sets. Perform the following
checks and act as required:
Run the following activity in Customizing: General Settings Process Modeling Workflow Rule-
based Workflow Configure Rule-Based Workflow .
i. From the displayed Additional Actions list, click “Import from Excel”.
DT_SINGLE_VAL_FM
[Link]
Note
Do not change this file manually, upload the file as it is, and after the upload, you can change
data in your table.
b. Activate the table as displayed in the following screen:
c. From the left pane, select the “User Agent Decision Table”
i. Click “Edit”, then in Additional Actions and click “Import from Excel” and activate
the table.
ii. Upload the enclosed Excel file DT_USER_AGT_GRP_FMS1 and click OK.
DT_USER_AGT_GRP_
[Link]
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.
d. From the left pane, select the “Non-User Agent Decision Table”
i. Click “Edit”, then in Additional Actions and click “Import from Excel” and activate
the table.
DT_NON_USER_AGT
_GRP_FMS1.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.
iii. Repeat these steps for all relevant Change Request Types FMS2, FMSA, and
FMSB.
Maintain your content in the Decision Tables, reflecting your governance process.
You can use the pre-delivered SAP content as a starting point.
2 FMSA
DT_SINGLE_VAL_FM DT_USER_AGT_GRP_ DT_NON_USER_AGT
[Link] [Link] _GRP_FMSA.xlsx
3 FMSB
DT_SINGLE_VAL_FM DT_USER_AGT_GRP_ DT_NON_USER_AGT
[Link] [Link] _GRP_FMSB.xlsx
Note
If you extend the BRF+ 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_FMS1
DT_NON_USER_AGT_GRP_FMS1
DT_USER_AGT_GRP_FMS1
DT_NON_USER_AGT_GRP_FMS1 and DT_SINGLE_VAL_FMS1 contain the automated steps and
follow-up logic used by the BRF+. The follow-up logic can result in an automated step or in a user
task that will be visible as a workflow.
Users involved in the Master Data Governance (MDG) process need to be included in table
DT_USER_AGT_GRP_FMS1. This action enables 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_FMS1 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_FMS1.
Conduct this maintenance for all relevant Change Request Types. Further details on the workflow
concepts can be found in Rule-Based Workflows for Material [External]. The following Change
Request Types appear in the standard delivery: FMS1, FMS2, FMSA, and FMSB.
DT_SINGLE_VAL_FMS1/2/A/B
DT_USER_AGT_GRP_FMS1/2/A/B
COND_ALIAS AGENT_GROUP STEP_TYPE USER_TYPE USER_VALUE
1 001 2 (Approve Change AG /UGI4/MDGRFM_FMS_STEW
Request)
5;7,9 001 8 (Activate Change AG /UGI4/MDGRFM_FMS_SPEC
Request)
3; 10 001 4 (Revise) SU INIT
DT_NON_USER_AGT_GRP_AR01/2/A
Note
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:
1. /UGI4/MDGRFM_FMS_SPEC (The MDG-RFM for FMS Specialist role of PFCG/SU01)
2. /UGI4/MDGRFM_FMS_STEW (The MDG-RFM for FMS 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 SAP_WFRT.
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.
1. ARTMAS
2. INFREC
3. BOMMAT
4. LIKOND
5. SERDAT
6. CLFMAS
7. /UGI8/ARTHIER_ASST
8. /UGI8/SUBSTITUTION
9. /UGI8/LAYMOD
10. RPLMAS
If you want to replicate change states or revision levels using IDoc ECMREV, you must also activate
the ALE Change Pointers using t-code SALE. In t-code SALE navigate to IDoc Interface/Application
Link Enabling (ALE) Modeling and Implementing Business Processes Master Data Distribution
Activate Change Pointers for Message Types or use t-code BD50.
2. Check communication
Run t-code SALE and choose > Communication > Created RFC Connections .
The target partner system must be defined here as an ABAP connection with a connection type
of 3 and with the same name as the target Logical System. Perform a connection test.
3. Use bgRFC
a. Run t-code SBGRFCCONF and on the tab, Define Inbound Destination and choose
“Create Inbound Destination”.
d. Choose “Save”.
e. Go to the “Scheduler: Destination” tab and choose “Create and Create Scheduler
Settings for Inbound Destination”.
f. Select the new destination and check the default setting. Choose “Save”.
i. In change mode, create a new model. Choose the Create Model View
pushbutton. Enter a short text and a technical name.
ii. Choose the Add Message Type pushbutton for the newly created model.
iii. Enter names for the logical source and destination systems and choose Message
Type INFREC.
iv. Repeat points 3 and 4 for Message Types BOMMAT, LIKOND, SERDAT,
CLFMAS, /UGI8/ARTHIER_ASST, /UGI8/SUBSTITUTION, /UGI8/LAYMOD
vi. Optional: Use the Message Type SERDAT to prevent errors during inbound
processing. With serialized message distribution, IDocs are created, sent, and
posted in a specific order.
Set up sending and receiving systems using t-code SALE in sender and target
systems. Choose Modeling and Implementing Business Processes > Master Data
Distribution > Serialization for Sending and Receiving Data.
5. Create Partner Profile
a. Run t-code SALE and choose Modeling and Implementing Business Processes >
Partner Profiles > Generate Partner Profiles. Alternatively, run t-code BD82 (Generate
Partner Profiles).
i. Select the newly created model and in the Partner System field, enter the logical
destination system.
ii. Enter the ALE-User (the default value is ALEREMOTE) and the following values
and execute.
Field Value
Version 3
PackSize 100
Output Mode Transfer IDoc immediately
Inb. Parameters: Processing Trigger Immediately
iii. To verify your settings, run t-code WE20 and from the Partner Profiles menu,
choose Partner Type LS. Verify that Partner type LS is the logical destination
system.
iv. In the detail screen, the chosen Message Types should appear.
i. Select the new model and choose Edit > Model view Distribute.
ii. Verify that the correct receiving system is marked and choose Enter.
Utopia RFM Solution Configuration Guide
© 2022 Utopia Global, Inc. Page 52 of 91
Retail and Fashion Management by Utopia for S/4HANA
iii. Verify within the receiving system that the model view was created.
Note
If the protocol contains the error “Port could not be created”, can be ignored.
d. Check that the correct Process Code is being used. To do this go to the details for the
Inbound Parameter Message Types and in Inbound Options check that the parameter
Process Code as follows:
Message Type Process Code Process Processing by Function Module
Type
ARTMAS /UGI8/ARTMAS Processing /UGI8/MDG_AR_IDOC_INPUT_ARTMAS
by
Function
Module
BOMMAT BOMM Processing IDOC_INPUT_BOMMAT
by
Function
Module
INFREC INFR Processing IDOC_INPUT_INFREC
by
Function
Module
LIKOND LIKO Processing IDOC_INPUT_LIKOND
by
Function
Module
MMADDI /UGI8/ADDI Processing /UGI8/MDG_AR_IDOC_INPUT_MMADDI
by
Function
Module
VCHARVAL BAPI Processing BAPI_IDOC_INPUT1
by
Function
Module
/UGI8/ARTHIER_ASST /UGI8/ARTHIER_01 Processing /UGI8/MDG_AR_IDOC_INPUT_ARTHIE
by
Function
Module
CLFMAS CLFM Processing IDOC_INPUT_CLFMAS
by
Function
Module
/UGI8/LAYMOD /UGI8/LAYMOD Processing /UGI8/MDG_AR_IDOC_INPUT_LAYMOD
by
Function
Module
/UGI8/SUBSTITUTION /UGI8/SUBS Processing /UGI8/MDG_AR_IDOC_INPUT_SUBST
by
Function
Module
RPLMAS /UGI8/RP Processing /UGI8/MDG_AR_IDOC_INPUT_RPLMAS
by
Function
Module
You can test the distribution using t-code BD10. Verify the results in the receiving client using t-code
BD87.
1. Run t-code DRFIMG and navigate to Enhance Default Settings for Outbound Implementation
Define Parameters to check if the outbound parameter PACK_SIZE_BULK is available.
The following information should be available for this parameter:
Outbound Parameter Description Data Type Value Length
PACK_SIZE_BULK Package size for Bulk Messages Integer 10
2. Select the parameter and open the Outbound Parameter Value view. Check that the parameter
value is 1000.
3. Run t-code DRFIMG to check if the Filter Objects below have been defined. Select Enhance
Default Settings for Outbound Implementation Define Filter Objects to view the Filter Object
definitions. Check that the main Filter Object /UGI4/0017 (Article) is available.
5. Run t-code DRFIMG to check if the Outbound Implementation /UGI4/AR has been defined.
Select Enhance Default Settings for Outbound Implementation Define Outbound
Implementations . Choose Assign Segment Filter Objects and confirm that the following
settings are made.
i. In the Business System field specify the receiver system. In the Logical System
field, enter the Logical System used for IDoc communication. In the RFC
Destination field enter the RFC destination to be used for RFC communication
with the receiver system.
ii. Select the entry and open the Define Bus. Systems, BOs view,
iii. In the BO Type field enter the Business Object Type DRF_0017. In the Output
Mode field, Object-Dependent Default is the default entry. You can optionally use,
Direct Output, where changes are directly transferred to a target system.
iv. Select the entry and double-click on Define Bus. Systems, BOs, Communication
Channel. In the Communication Channel field enter the means you want to use to
transmit data to the applications. In the Key Harm. field specify if you want your
keys harmonized between the hub and the client systems,
b. Create the Replication Model and assign it to the Outbound Implementation as follows:
ii. Navigate to Data Replication Define Custom Settings for Data Replication >
Define Replication Models.
iii. Select Define Replication Model and then select New Entries.
iv. Enter a Replication Model (/UGI_AR) and a description. In the Log Days field, you
may enter the number of days after which you want an Application Log to expire.
In the Data Model field, enter AR.
v. Select the newly defined Replication Model and choose Assign Outbound
Implementation.
c. Create the Replication Model and assign it to the Outbound Implementation for change
pointers(optional)as follows:
ii. Navigate to Data Replication Define Custom Settings for Data Replication >
Define Replication Models.
iii. Select Define Replication Model and then select New Entries.
iv. Enter a Replication Model (/UGI_AR_C) and a description. In the Log Days field,
you may enter the number of days after which you want an Application Log to
expire. In the Data Model field, enter AR.
v. Select the newly defined Replication Model and choose Assign Outbound
Implementation.
Note
"The incorrect entries for UGI4 in table IBO_C_WF_TAS" needs to be deleted before adding the
following entries.
Note
If customers want to use the standard MDG POWL Inbox, use the following steps to configure the
same.
4. In the hierarchy menu, select folder Role Master Data Governance for FMSChange
RequestsChange Requests and Documents.
5. In the toolbar bar, click on “Transaction” button menu Select Web Dynpro Application.
Note
Repeat the above steps for all other relevant /UGI4/ Roles.
To upload your portal content to the portal, perform the following actions:
Utopia RFM Solution Configuration Guide
© 2022 Utopia Global, Inc. Page 59 of 91
Retail and Fashion Management by Utopia for S/4HANA
b. Right-click the folder and choose New Role Role from Back End .
c. Select the system and client (or the connected system alias) you want to upload the role
information from. This should be your MDG system.
d. From the displayed list, select the MARA roles you want to upload the content from and
begin the upload.
e. After the roles are uploaded, perform the following actions to assign and personalize the
MDG portal roles as follows:
f. After assigning the user role you need to log off and log on to the portal. For more
information on uploading role information see SAP Note 1685257 [External].
There are four roles containing authorization and navigation information and one role
(/UGI4/MDGRFM_MENU) OR (/UGI4/MDGRFM_FMS_MENU) containing only navigation information.
To assign and personalize the roles of 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 t-code PFCG (Role Maintenance). Choose role
/UGI4/MDGRFM_MENU.
a. 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.
b. Verify the setting of the authorization objects within the roles and restrict them if
required.
c. On the SAP Easy Access screen, choose Tools > Administration > User Maintenance >
Users. Run t-code SU01 (User Maintenance) and assign the Master Data Governance
for Material: Menu role (/UGI4/MDGRFM_MENU) for application to the MDG user.
4.14.1. Prerequisites
A browser with Flash plug-in
MDG Analytics is based on operational analytics in ECC. The Info provider is an ODP (Operation
Data Provider) and it is in the ECC system and not in BW.
Note
Ensure that the following services are activated:
MDG_MONITOR_CR_PROCESTIME - Application Configuration for Monitoring CR Processing Time
MDG_CR_PROCESTIME_TREE – Processing Time
MDG_ANLY_CR_REJ_REASON - Change Request Rejection reason
1. If the MDG version used is lower than MDG 9.0 on S/4HANA, ensure the following parameters
mentioned in the screen below are set to the values as displayed.
If not perform the following instructions:
a. Go to the package ‘USMD_GENERIC_BOLUI’ that contains the Web Dynpro application
using t-code SE80.
2. 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).
3. The SAP_BLUECRYSTAL theme also exists, and the theme has a FIORI 1.0 as displayed
below.
4. If you are running MDG for RFM S/4HANA 2021, SAP_BELIZE theme is available with a FIORI
2.0 as displayed below.
To choose and run the required theme, perform the following actions.
1. Run t-code SE11 and access to table NWBC_CFG and click “Display”.
4. If you want to change the Theme in the future, perform the following.
a. Access the table
d. Click Save.
f. Path filter: *
7. Configuration Process
This process describes the minimal set of customizing steps and recommended check activities
required to do the following:
New Mandatory(M)/
SI No BC Set Name Installation Upgrade Optional(O)
1 /UGIRMP/DM_MASS_100 Yes No Yes
2 /UGIRMP/DM_MASS_2020 Yes No Yes
3 /UGIRMP/DM_MASS_STRUC_100 Yes No Yes
4 /UGIRMP/DM_MASS_CRTYPE_100 Yes No Yes
5 /UGIRMP/DM_MASS_DRF_100 Yes No Yes
6 /UGIRMP/DM_MASS_DRF_2020 Yes No Yes
7 /UGIRMP/DM_MASS_OTC_100 Yes No Yes
8 /UGIRMP/DM_MASS_SCOPE_100 Yes No Yes
9 /UGIRMP/DM_MASS_SCOPE_1909 Yes No Yes
10 /UGIRMP/DM_MASS_SCOPE_2020 Yes No Yes
11 /UGIRMP/DM_MASS_SCHEMA_100 Yes No Yes
12 /UGIRMP/DM_MASS_SCHEMA_1909 Yes No Yes
13 /UGIRMP/DM_MASS_SCHEMA_2020 Yes No Yes
14 /UGIRMP/DM_MASS_SCHEMA_2021 Yes Yes Yes
15 /UGIRMP/RMP_1909 Yes No Yes
To enable the Retail Mass Processing (RMP) pre-delivered content, navigate to transaction code (t-
code) SCPR20 and activate the following BC Sets in sequence:
Once this BC set activated, you need to activate the data model. You can activate the data
model using the following steps.
b. Activate the delivered data model AR in Customizing for Master Data Governance under
General Settings Data Modelling Edit Data Model .
c. Adjust Staging Area of Linked Change Requests General Settings Data Modelling
Edit Data Model .
Note
Make sure that the mentioned standard schemas and related details (schema tables, fields to be
modified and Change Request types) are available in the schema definition.
Use the following steps to validate the RMP schemas.
BOM 32
EINA 8
EINE 9
EINSGT 34
FSH_SEASONS_MAT 6
MAKT 5
MALG 21
MARA 1
MARC 2
MARM 4
MAW1 3
MBEW 11
MEAN 12
MLAN 7
MLEA 13
MLGN 14
MLGT 15
MPOP 16
MVKE 17
RESTRICT 20
SGT_MADKA 30
SGT_MARM 24
SGT_MLGN 26
SGT_MLGT 25
SGT_MRP 28
SGT_MRP_GN 29
SGT_MVKE 27
TXCOMP 22
TXFIBR 23
URL 37
VARIANT 10
WLK2 18
WRPL 36
WTADDI 35
CONFIGMAT 36
EORD 37
PROPUNIT 38
As an example, screens from UGIRMP_CHANGE schema tables and order are displayed:
Note
• If you need to add any new tables, you need to add the table names in the respective schema
and provide the respective fields in the table.
• If you want to enhance table with additional fields, add the fields directly under a specific
schema specific table.
• If you want to add any custom fields which are available in the above standard tables or
added tables through this schema, API should support the updating of custom fields data.
then only this Mass change solution will be supported.
Note
Refer the following documents for custom field addition.
• UGI_RFM_RMP_HowToGuide_Extend_RMP
Use the following steps to add a standard field from the standard table.
1. Navigate to Customizing for Master Data Governance under Retail Mass Processing by
Utopia Process Modeling Schema Definition .
The following screen is displayed with the available schemas.
5. Add the “Field Name” and the “Field Display order” and save.
The field is added to the “Fields to be modified” as displayed in the following screen.
b. Active by Default – Cannot be changed (if this is set, the MDG Check option will be
enabled by default for the change request once the relevant schema type is selected
and the UI field will be read-only.
c. Inactive by Default – Can be changed (if this is set, the MDG Check option will not be
enabled by default for the change request once the relevant schema type is selected
and can be changed by the user in the change request UI
7.2.4. Configure Number Range Check flag for RMP Schema (Optional)
1. Navigate to Master Data Governance, Central Governance Retail Mass Processing by
Utopia Process Modeling Schema Definition .
2. Select the option for Number Range Check for the Schema to one of the below values based
on the requirement
a. Internal Number Range Type Validation - if this is set, the article creation will perform a
number range validation against internal number range and throw an error if not a valid
internal number.
b. External Number Range Type Validation - if this is set, the article creation will perform a
number range validation against external number range and throw an error if not a valid
external number.
c. Validate both for Internal and External Number Ranges - if this is set, the article creation
will perform a number range validation against internal/external number ranges based
on article type and throw an error if not in a valid number range
b. Not Checked – If the checkbox is not checked, then the variant number validation will
not be performed. This is the default value for this field for any schema.
b. Not Checked – If the checkbox is not checked, then the changes are not highlighted in
change request schema
3. Select value for “Saved Change Color”. The selected color value will be used to highlight the
saved changes in the CR for the schema. The default value(83) is handled in the application
level and it is not mandatory to select the value here
4. Select value for “UnSaved Change Color”. The selected color value will be used to highlight the
Unsaved changes in the CR for the schema. The default value(65) is handled in the application
level and it is not mandatory to select the value here
Note
• In case of any table addition supported by API (maintained in the schema tables), you need to
create staging table and staging history table. The table details should be maintained in the
above configuration as listed in the section on Validate RMP Scope Tables.
7.4.1. Link Log. Actions with UI Application and Bus. Act.: Standard Definition
The logical actions shown in the tables in section UI navigation for RMP Change needs to be manually entered.
Navigate to Customizing for Master Data Governance under General Settings Process Modeling Business Activities Link Log. Actions with UI Application and Bus.
Act. Standard Definition .
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:
Web Dynpro Application Application Configuration UI
USMD_OVP_GEN /UGIRMP/_AR_MASS /UGIRMP/_AR_MASS_OVP
USMD_SEARCH /UGIRMP/_AR_SEARCH_FMS /UGIRMP/_AR_SEARCH_OVP_FMS
Note:
• UI configuration/adaptation and step dependent properties are done using the RMP
configuration. CBA or MDGIMG configurations are not used in RMP
3. 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.
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 type: UGIRMP1
o Entity type: MASS
o UI Configuration ID
o Msg. output: Standard
o Business Activity: RFM Mass Create (MAS1)
o Service Level Agreement for Change Request Types: <leave empty>
Run the following activity in Customizing: General Settings Process Modeling Workflow Rule-
based Workflow Configure Rule-Based Workflow .
DT_SINGLE_VAL_UGI
[Link]
Note
Do not change this file manually, upload the file as it is, and after the upload, you can change
data in your table.
8. From the left pane, select the User Agent Decision Table
a. Click Edit.
b. In Additional Actions, click “Import from Excel” and activate the table.
c. Upload the enclosed Excel File DT_USER_AGT_GRP_ UGIRMP1 and click OK.
DT_USER_AGT_GRP_
[Link]
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.
9. From the left pane, select the Non-User Agent Decision Table
a. Click “Edit”.
b. From Additional Actions, click “Import from Excel” and activate the table.
DT_NON_USER_AGT
_GRP_UGIRMP1.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.
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.
• DT_SINGLE_VAL_UGIRMP1
• DT_NON_USER_AGT_GRP_UGIRMP1
• DT_USER_AGT_GRP_UGIRMP1
Users involved in the Master Data Governance (MDG) process need to be included in table
DT_USER_AGT_GRP_UGIRMP1. This action enables 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_UGIRMP1 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_UGIRMP1.
Conduct this maintenance for all relevant Change Request types. Further details on the workflow
concepts can be found here. The following Change Request types appear in the standard delivery:
UGIRMP1.
DT_USER_AGT_GRP_UGIRMP1
Note
• 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_STEW
o /UGI4/MDGRFM_SPEC
• 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.
Run t-code DRFIMG to check if the outbound implementation /UGIRMP/AR has been defined. Select
Enhance Default Settings for Outbound Implementation Define Outbound Implementations
. Choose Assign Segment Filter Objects and confirm that the following settings are made.
b. In the Business System field specify the receiver system. In the Logical System field,
enter the Logical System used for IDoc communication. In the RFC Destination field
enter the RFC destination to be used for RFC communication with the receiver system.
c. Select the entry and open the Define Bus. Systems, BOs view
d. In the BO Type field enter the business object type /UGIRMP/MA. In the Output Mode
field, Object-Dependent Default is the default entry. You can optionally use, Direct
Output, where changes are directly transferred to a target system.
e. Select the entry and double-click on Define Bus. Systems, BOs, Communication
Channel. In the Communication Channel field enter the means you want to use to
transmit data to the applications. In the Key Harm. field specify if you want your keys
harmonized between the hub and the client systems.
Create the replication model and assign it to the outbound implementation as follows:
a. Run t-code DRFIMG.
b. Navigate to Data Replication Define Custom Settings for Data Replication Define
Replication Models .
d. Enter a replication model (/UGIRMP/AR) and a description. In the Log Days field, you
may enter the number of days after which you want an Application Log to expire. In the
Data Model field, enter AR.
e. Select the newly defined replication model and choose Assign Outbound
Implementation.
To upload your portal content to the portal, perform the following actions:
4. Select the system and client (or the connected system alias) you want to upload the role
information from. This should be your MDG system.
5. From the displayed list, select the MARA roles you want to upload the content from and begin
the upload.
6. After the roles are uploaded, perform the following actions to assign and personalize the MDG
portal roles as follows:
a. Log on to the portal.
7. After assigning the user role you need to log off and log on to the portal. For more information
on uploading role information see SAP Note 1685257.
To assign and personalize the roles Master Data Governance for RFM perform the following actions:
8. On the SAP Easy Access screen, choose Tools Administration User Maintenance Role
Administration Roles or alternatively, run t-code PFCG (Role Maintenance). Choose role
/UGIRMP/RFM_MASS_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.
9. Verify the setting of the authorization objects within the roles and restrict them if required.
10. On the SAP Easy Access screen, choose Tools Administration User Maintenance Users
Run t-code SU01 (User Maintenance) and assign the Master Data Governance for Material:
Menu role (/UGIRMP/RFM_MASS_MENU) for application to the MDG user.
3. Enter the enhancement name starting with Z / Y and click on “Create” button
4. Enter the following details in the dialog window and Click on . Save it as local object. Click
b. Component: /UGI/4
Note
In case, a Z Customer Enhancement of the /UGI/4 GenIL component exist, then a Super
Enhancement needs to be created to the current Existing Z Enhancement with the same
settings above.
/ugirmp/ enhancement needs to be a super enhancement of customer enhancement or vice
versa.