Configuring Master Data Governance for Utopia EAM Solutions for MDG™ Service Master

Prerequisites

Business Function

Ensure the following business functions are activated:

• 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 Feature Set (MDG_FOUNDATION_5)

Ensure you have administration authorization for MDG. The SAP_MDG_ADMIN role is recommended. For the USMD_DM Data Model authorization object, assign values for the USMD_MODEL field (e.g., U2) and the activity (e.g., 01: Create or 02: Change).

Set Up Workflow

To use workflow processes, define general settings for SAP Business Workflow in Customizing for SAP NetWeaver under Application Server → Business Management → SAP Business Workflow. Activate workflow features using transaction SWU3 or via Customizing under SAP NetWeaver → Application Server → Business Management → SAP Business Workflow → Maintain Standard Settings.

Notes for settings:

• Superuser authorization is needed for RFC destination configuration to create the default WF-BATCH user.
• Regenerate the authorization profile for SAP_ALL or include USMD* authorization objects into the WF-Batch user's authorizations.
• Execute report RHSOBJCH (transaction SE38) for the Check Entries from HR Control Tables section.
• Maintain prefix numbers for standard objects.
• The Web Server node and Guided Procedures section do not require maintenance.

Set Up Search

MDG uses the standard MDG database search. No further setup is required.

Adjust Profile Parameters

Ensure the profile parameter abap/shared_objects_size_MB is at least 300 megabytes. Check using transaction RZ11.

For Single Sign On (SSO) with SAP NetWeaver Business Client, ensure login/create_sso2_ticket is set to 2 and login/accept_sso2_ticket is set to 1.

Verify that the host name is fully qualified for parameter icm/host_name_full using transaction RZ11.

User Roles

Assign the following user roles in PFCG transaction:

• SAP_MDGA_MENU – Master Data Governance: Analytics
• SAP_MDG_ADMIN – Master Data Governance: Administrator

The SAP_MDG_ADMIN role contains authorizations for basic configuration and administration tasks. It is recommended to split this role for users involved in configuration and administration to limit access to specific tasks and reduce risks.

Additional roles include:

• /UGI1/_MDGPROC_ALLUSR – Standard User Authorizations
• /UGI1/_MDGPROC_REQ – Master Data Governance for Service Master: Requestor
• /UGI1/_MDGPROC_SPEC – Master Data Governance for Service Master: Specialist
• /UGI1/_MDGPROC_STEW – Master Data Governance for Service Master: Steward

Web Dynpro Applications

Activate inactive services using transaction SICF. Refer to the documentation for a list of relevant services.

Process

This section describes the minimal customizing steps and check activities for:

• Create Service Master
• Change Service Master
• Process multiple Service Masters
• File Upload
• File Download

Run settings in Customizing under Cross-Application Components → Processes and Tools for Enterprise Applications → Master Data Governance, or use transaction code MDGIMG.

Key configuration steps include:

1. Activate the Data Model U2 [Page 8]
2. Activate Change Request Types (BC-Set) [Page 10]
3. Link Log. Actions with UI Application and Bus. Act.: Standard Definition [Page 10]
4. Verify Remaining Process Modeling Settings [Page 13]
5. Verify UI Modeling (Optional) [Page 15]
6. Set Up Search [Page 15]
7. Configure Process Quality Metrics (Optional) [Page 16]
8. Data Model U2 BRF+ objects [Page Error! Bookmark not defined.]
9. Configure Workflow Tasks [Page 17]
10. Set Up Data Replication [Page 19]
11. Customizing for ALE Audit (Optional) [Page 24]
12. Choose where you want to run SAP Master Data Governance [Page 26]
13. Final Steps [Page 27]
14. Workflow Templates for Utopia SERVICE MASTER Solutions for MDG™ [Page 28]

Result

The system is configured for SERVICE MASTER. Mass changes and distribution to other systems can be executed if data load has been done.

More Information

• Functional restrictions: See SAP Note 2284041
• Master Data Governance Security Guide [Extern]
• Master and Master Update Guide [Extern]

1 Activate the Data Model U2

Check if the data model delivered by SAP and Utopia can be used for managing SERVICE MASTER data with MDG for SERVICE MASTER.

Activate the data model U2 in Customizing for Master Data Governance under General Settings → Data Modeling → Edit Data Model.

Note: When upgrading to MDG 7.0 or MDG 8.0, check that active and inactive versions of data models are the same. Activate all models after the upgrade if there are differences.

After activation, trigger the job to adjust the data model.

Assign an internal key

Run the activity in Customizing for Master Data Governance under General Settings → Data Modeling → Define Prefixes for Internal Key Assignment.

Note: Authorizations cannot be defined here; existing back-end authorizations are reused.

Check or Generate Data Model-Specific Structures

Activate the SERVICE MASTER Data Model-Specific structures. Run the activity in Customizing for Master Data Governance under General Settings → Data Modeling → Generate Data Model-Specific Structures. Select the U2 data model and double-click on Data Models → Structures.

If structures do not exist or after data model changes, regenerate them. Choose a package in the customer namespace (beginning with Y or Z) if prompted.

If a dialog box appears stating that "Customer object TABL CI* cannot be assigned to package /UGI1/MDG_PROC_GLOBAL," select the check mark (✔) and enter your chosen package ID in the dev class field.

Other customizing activities in data modeling are relevant if your data model needs enhancement. See Enhancement of Master Data Governance Content.

2. Activate Change Request Types (BC-Set)

For create, change, mark for deletion, and process SERVICE MASTER Objects, example change request types are available. Run the BC-Set activation process (transaction code SCPR20) for the BC-Sets:

• /UGI/MDG_PROC_CREQUEST_01 – Utopia PROC Solutions for MDG Change Request Types - Service Master
• /UGI1/MDG_PROC_OTC_CODE - Utopia PROC Solutions for MDG OTC Codes.
• /UGI1/MDG_PROC_PQM_01 - Utopia PROC Solutions for MDG - Process Quality Metrics

Choose Activate (✔) for each BC-Set. Ignore warnings on missing workflow processor and choose "Save Changes (Despite Warnings)".

3 Link Log. Actions with UI Application and Bus. Act.: Standard Definition

The Logical Actions in Table 1 are delivered with the Utopia SERVICE MASTER Solutions for MDG™ Suite.

Table 1 SERVICE MASTER Objects Logical Actions UI Application and Bus Act. Linkage - Delivered

The logical actions in Table 2 need to be added 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.

Table 2 SERVICE MASTER Objects Logical Actions UI Application and Bus Act. Linkage – Manual Entry Required

4 Verify Remaining Process Modeling Settings

Adjust and enhance default change request values as needed. The following describes minimal settings for a basic governance process.

Review and define statuses for change requests and their processing options. New statuses can be added.

For more information, see Customizing for Master Data Governance under General Settings → Process Modeling → Change Requests → Edit Statuses of Change Requests.

Status Table

Check that the following business activities are assigned to the default data model U2:

Service Master

• USM1 Create Service Master
• USM2 Change Service Master
• USM3 Display Service Master
• USM6 Mark Service Master for Deletion
• USMA Mass Update Service Master
• USMB Import Service Master

5 Verify UI Modeling (Optional)

UI configuration activities are relevant if you want to change the UI or if the U2 data model has been enhanced. You can specify and hide entity types for the data model U2.

Verify pre-delivered field properties for data model U2 in Customizing under General Settings → UI Modeling → Define Field Properties for UI.

The Web Dynpro application and application configuration in the PFCG role determine the UI displayed.

Verify UI modeling for data model U2 and the following Web Dynpro applications:

6 Set Up Search

MDG offers search options for data in change requests, including active and inactive data. Search options differ in capabilities and landscape requirements, particularly in including classification data.

• SAP search engine-based search (TREX search) offers full search capabilities.
• Database Search uses the generic search provider interface, requires manual configuration, and does not offer classification search.
• SAP HANA-based search (side-by-side) connects MDG from any database to an SAP HANA-based system for search, but does not include classification search.

In Release 7.2 of Utopia SERVICE MASTER Solutions for MDG™ Suite, Database Search is available. Additional search options are planned.

7 Configure Process Quality Metrics (Optional)

Example values are available for priorities, reasons, or rejection reasons for change requests. Run the BC-Set activation process (transaction code SCPR20) and enter /UGI1/MDG_PROC_PQM_01. Choose Activate and keep default settings.

These codes are used for change request analytics and can influence workflow-driven processes.

To update Process Quality Metrics (PQM), perform the activity in Customizing for Master Data Governance under General Settings → Process Modeling → Change Requests → Define Priorities / Reasons / Rejection Reasons for Change Requests.

Change Request Priorities

Change Request Reason

Reason for Rejection

8 Configure Workflow Tasks

Ensure necessary general settings for workflows and the organizational plan are defined in Customizing for SAP NetWeaver under Application Server → Business Management → SAP Business Workflow. Ensure active type linkages for Change Request (BUS2250) are set correctly.

For object type BUS2250, check that the Type Linkage Active indicator is active for the events CREATED, ACTIVATED, and ROLLED_BACK. Also, check that the Enable Event Queue indicator is active for the events ACTIVATED, and ROLLED_BACK, but not for the event CREATED.

The standard workflow template used by Master Data Governance for SERVICE MASTER is WS54300020.

To ensure general assignment of processors using the rule-based workflow, run the activity in Customizing for Master Data Governance under General Settings → Process Modeling → Workflow → Configure Workflow Tasks.

1. Go to application component CA-MDG-AF and choose Assign Agents.
2. Set the Dialog Processing (TS60807954) task as a General Task if not already set.

Utopia SERVICE MASTER Solution for MDG provides Agent Determination entries for the standard workflow template WS54300020. Assign one User ID (type "US") to each task requiring agent determination.

SAP and Utopia recommend using Organizational Management for flexibility and simplified maintenance. Assign Organizational Unit types (e.g., Positions "S") to the CR Type and Step, depending on the Org Structure or Single User.

Refer to Master Data Governance under General Settings → Process Modeling → Workflow → Other MDG Workflows → Assign Processor to Change Request Step Number (Simple Workflow).

Example: Entries determine that change request type 01 has the following properties: (a) evaluation by organizational units GROUPACC, GLACC, and GROUPMD; (b) approval by user X; (c) changes executed by organizational unit GROUPMD; and (d) final approval by user Y.

Hint: Usage of MDG-SERVICE MASTER by Utopia together with Extended ECM by OpenText™

9 Set Up Data Replication

References to Business Object Types (BO Types), Object ID Types, Messages, etc., correspond with SERVICE MASTER Objects within the Utopia SERVICE MASTER Solutions for MDG™ domain.

Table 3 SERVICE MASTER Business Object Types and Messages

Utopia SERVICE MASTER Solutions for MDG™ offers two options for replicating data from the MDG hub to connected systems and clients:

• Data replication using Application Link Enabling (ALE)
• Data replication using Application Link Enabling (ALE) with the Data Replication Framework

For more information, see Customizing under Application Server → IDoc Interface / Application Link Enabling (ALE) → SAP Business Workflow.

Set Up Data Replication Using ALE

Minimal settings for SERVICE MASTER Object message types:

1. Verify logical systems: Run transaction SALE and choose Basic Settings → Logical Systems. Both clients (source and target) must be defined as logical systems and assigned to relevant clients.
2. Check communication: Run transaction SALE and choose Communication → Created RFC Connections. Define the target partner system as an ABAP connection with type 3 and the same name as the target logical system. Perform a connection test. Define an ALE tRFC port using transaction WE21.
3. Maintain distribution model: Run transaction SALE (Display ALE Customizing) and choose Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views, or run BD64. Create a new model, add message types (SRVMAS), and specify source and destination systems.
4. Create partner profile: Run transaction SALE and choose Partner Profiles → Generate Partner Profiles, or run BD82. Select the model, enter the logical destination system, ALE-User (ALEREMOTE), and execute. Verify settings using transaction WE20.
5. Distribute model view to receiving system: Run transaction SALE and choose Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views, or run BD64. Select the model, choose Edit → Model view → Distribute. Verify the receiving system is marked.
6. Create partner profile (in receiving client): Run transaction SALE and choose Modeling and Implementing Business Processes → Partner Profiles → Generate Partner Profiles, or run BD82. Select the distributed model, enter the hub logical system name, ALE-User, and execute. Check the process code using WE20.

Set Up Data Replication Using ALE with DRF

Replication of master data from MDG Hub to connected client systems can be scheduled, triggered, and monitored using the Data Replication Framework (DRF) with ALE.

If using ALE and DRF together, deselect change pointers for the corresponding message type to improve performance. This is applicable only if all MDG systems are integrated using ALE and DRF.

Relevant customizing for data replication:

• ALE (See Set Up Data Replication Using ALE above)
• Key Mapping (See Key Mapping below)
• ALE Audit (See Customizing for ALE Audit below)
• Data Replication Framework (DRF)

Customizing for Data Replication Framework (DRF)

1. Use transaction DRFIMG to check filter objects. Select Enhance Default Settings for Outbound Implementation → Define Filter Objects. Ensure the main filter object is available for each SERVICE MASTER object.
2. Optionally, check the correct assignment of Object ID Type, BO Types, and Object Node Types via Enhance Default Settings for Outbound Implementation → Define Business Objects and Object Identifiers → Define Object Identifiers.
3. Check that the Key Structure Assignment for all entity types exists. If not, create the entry via Enhance Default Settings for Outbound Implementation → Define Business Objects and Object Identifiers → Assign Key Structures to Object Identifiers. Assign the Key Structure /UGI1/_S_U2_DRF_SERVICE to Object Type 968.
4. Define technical settings for the business system. Enter transaction DRFIMG and navigate to Define Custom Settings for Data Replication → Define Technical Settings → Define Technical Settings for Business Systems. Specify the receiver system, logical system for IDoc communication, and RFC destination.
5. Create the replication model and assign it to the outbound implementation. Enter transaction DRFIMG, navigate to Data Replication → Define Custom Settings for Data Replication → Define Replication Models. Select Define Replication Model and choose New Entries. Enter a replication model and description. In the Data Model field, enter U2. Assign the appropriate outbound implementation and target system.

10 Customizing for ALE Audit (Optional)

Configure client and hub systems for confirmation of replicated materials back to the MDG hub.

In the client system make the following settings:

1. Select Distribution Model: Run transaction BD64 and choose Change/Display. Select the distribution model and choose Add Message Type. Enter Sender, Receiver, and Message Type (ALEAUD).
2. Select Partner Profile: Run transaction SALE and choose Partner Profiles → Generate Partner Profiles, or run BD82. Select the distribution model, enter the hub logical system name, ALE-User, and execute. Verify settings using transaction WE20.

In the hub system make the following settings:

1. Distribution Model: Run transaction BD64 and check that the Distribution Model View with partner profile was created.
2. Partner Profile: Run transaction WE20 and check that the partner profile exists. Select Receiver Logical System, choose Change, and choose Create Outbound Parameter. Enter Message Type ALEAUD, Receiver Port, Output Mode (Transfer IDoc Immediately), Basic Type (ALEAUD01), and select Cancel Processing After Syntax Error. Choose Save. Run transaction BD64 to distribute the model view.
3. Configure DRF Customizing: Run transaction DRFIMG. Navigate to Data Replication → Define Custom Settings for Data Replication → Define Technical Settings for Business Systems. Select the receiver system (hub system) and double-click on Define Bus. Systems, BOs, Communication Channel. Enter the business object type 248 for Service and choose OK. Select the checkbox Upd.KM. Choose Save.

11 Choose where you want to run SAP Master Data Governance

SAP Master Data Governance can be run in the following environments:

• SAP NetWeaver Portal
• SAP NetWeaver Business Client

SAP NetWeaver Portal

SAP NetWeaver Portal content for Utopia SERVICE MASTER Solutions for MDG™ is derived from system PFCG roles. To create SAP NetWeaver Portal roles, log on to your portal and upload content information from your back-end system PFCG roles.

To upload portal content:

1. Set up your SAP NetWeaver Portal for MDG.
2. In Content Administration, choose Portal Content Management → Portal Content and select a portal content folder.
3. Right-click on the folder and choose New → Role → Role from Back End.
4. Select the system and client (or alias) to upload role information from.
5. Select the PFCG roles to upload.

To assign and personalize MDG portal roles:

1. Log on to the portal.
2. Choose Delegated User Administration.
3. Enter your User ID and choose Go.
4. Mark your user and choose Modify.
5. Select the Assigned Roles tab.
6. Enter MDG as the search criteria.
7. Select the portal role to add.
8. Choose Add and save.

Log off and log on again to the portal. For more information, see SAP Note 1685257.

SAP NetWeaver Business Client

If running SAP Master Data Governance on SAP NetWeaver Business Client, create, define, and configure roles in the SAP ERP system. Three roles contain authorization and navigation information, and one role (/UGI1/_MDGPROC_ALLUSR) contains basic access.

To assign and personalize the role Master Data Governance for SERVICE MASTER (/UGI1/_MDGPROC_ALLUSR), follow these steps:

1. On the SAP Easy Access screen, choose Tools → Administration → User Maintenance → Role Administration → Roles, or run transaction PFCG. Choose role /UGI1/_MDGPROC_ALLUSR.
2. Assign and personalize the role /UGI1/_MDGPROC_ALLUSR to your users. In the role, edit the Personalization Key SAP Master Data Governance (R_FMDM_MODEL) on the Personalization tab. Define the default model U2 and related UI configuration.
3. Verify and restrict authorization objects within the roles.
4. On the SAP Easy Access screen, choose Tools → Administration → User Maintenance → Users. Run transaction SU01 and assign the Master Data Governance for SERVICE MASTER: All Users (/UGI1/_MDGPROC_ALLUSR) for application to the MDG user.

Repeat these steps to assign additional authorization roles.

12 Final Steps

SAP and Utopia recommend regenerating the data model at the end of setup steps to ensure clear code generation.

Before running Master Data Governance processes like Create Service, assign the data model U2 to your user. Alternatively, the user administrator can maintain the Personalization Parameter for your user profile: SAP Master Data Governance R_FMDM_MODEL.

If other data models are active (e.g., Financials (0G), Material Master (MM), Business Partner/Customer/Supplier (BP)), additional entries may appear.

13 Workflow Templates for SERVICE MASTER in Utopia EAM Solutions for MDG™

13.1 Workflow Template WS54300020

Utopia delivers the SAP standard workflow template WS54300020 for the approval process. This forwards the change request as a work item to appropriate processors, and the change request status is updated automatically.

This workflow template consists of the following steps:

1. Start workflow: The workflow starts when a change request is created by a user (e.g., a Plant Maintenance Technician).
2. Execute changes: The master data specialist receives a work item to execute changes. They can send the request back for revision (Step 3) or proceed to checking (Step 4).
3. Revision after rejection: The person responsible for processing a rejected change request decides whether to revise it. If revised, it goes back to the master data specialist (Step 2). If withdrawn, the status becomes Final Check Rejected, and changes are reset (Step 6).
4. Perform final check: The system validates the change request. The master data steward receives a work item for final check. They review validation results and approve or reject. Rejection sends it back for revision (Step 3).
5. Activate changes: If approved, the system activates the changes (Step 5). Changes are activated in the central system. If DRF is enabled with ALE, changes are sent to target systems. Manual replication is also available.
6. End workflow: The system ends the workflow.