Mdg100 en Col10 Ilt Fv Inst a4

MDG100 Master Data Governance

.

.

INSTRUCTOR HANDBOOK INSTRUCTOR-LED TRAINING . Course Version: 10 Course Duration: 4 Day(s) Material Number: 50120594

SAP Copyrights and Trademarks

© 2014 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. ●

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

●

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

●

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

●

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

●

Oracle is a registered trademark of Oracle Corporation

●

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

●

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

●

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

●

●

Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

●

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

●

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

●

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© Copyright . All rights reserved.

iii

iv


About This Handbook This handbook is intended to both complement the instructor-led presentation of this course and to serve as a reference for self-study. Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used.

This information is displayed in the instructor’s presentation

Demonstration

Procedure

Warning or Caution

Hint

Related or Additional Information

Facilitated Discussion

User interface control

Example text

Window title

Example text


v

vi


Contents ix

Course Overview

1

Unit 1:

2 11 23

Lesson: Governing High-Quality Master Data Exercise 1: Execute a Master Data Search Unit 2:

24 29 35

Unit 3:

70 79 85 89 95 99 101 108 111 123 124 127 130 133 136 141 145

120 Minutes 30 Minutes 20 Minutes 60 Minutes 25 Minutes 60 Minutes 30 Minutes

Multiple Object Processing Lesson: Processing Multiple Objects in a Single Change Request Exercise 6: Assign New Cost Center Change Requests to an Edition Lesson: Executing Mass Changes Exercise 7: Execute a Mass Change Exercise 8: Update a Mass Change Lesson: Executing Data File Transfers with Multiple Objects Exercise 9: Upload Material Records to Master Data Governance Lesson: Processing Master Data Hierarchy Records Exercise 10: Process Supplier Hierarchy Records

Unit 4:

90 Minutes 20 Minutes

Single Object Processing Lesson: Managing Master Data Changes Exercise 2: Change Material Data Records Exercise 3: Search for Material Records and Create a Copy of a Record Lesson: Processing Parallel Workflow Steps Exercise 4: Process Parallel Workflow Steps for Supplier Records Lesson: Processing Customer Master Data on a Client System Exercise 5: Process Customer Master Data on a Client System

39 43 55 59 69

Master Data Governance Processes

90 Minutes 15 Minutes 60 Minutes 15 Minutes 10 Minutes 60 Minutes 30 Minutes 30 Minutes 15 Minutes

Change Request Monitoring and Analysis Lesson: Tracking Change Request Information Exercise 11: Track Change Request Information Lesson: Monitoring Change Request Status Exercise 12: Monitor Change Request Status Lesson: Analyzing Change Request Metrics Exercise 13: Retrieve Process Time Metrics Exercise 14: Analyze Processing Time Duration



vii

153

Unit 5:

154

90 Minutes

161

Lesson: Configuring Master Data Governance Processes and the User Interface Exercise 15: Verify User Configuration

177 182 187

Exercise 16: Change a Standard Workflow Template User Interface Lesson: Adding a Step to an Existing Configuration Exercise 17: Add a Step to an Existing Configuration

30 Minutes 40 Minutes 15 Minutes

203

Unit 6:

204 211 217 221 227 235

Unit 7:

275 276 285 293 297 306 313 323

45 Minutes 60 Minutes 45 Minutes 60 Minutes 20 Minutes

Data Transfer and Data Replication Lesson: Transferring Data within Master Data Governance Exercise 20: Export Data within Master Data Governance Exercise 21: Import Data within Master Data Governance Lesson: Configuring Data Replication within Master Data Governance Exercise 22: Configure Data Replication Exercise 23: Replicate Data within Master Data Governance

261 267 Unit 8:

10 Minutes

Data Quality and Search Configuration Lesson: Configuring Search and Duplicate Checks Lesson: Building Validations for Data Quality Exercise 18: Build Validations for Data Quality Lesson: Building Derivations for Data Quality Exercise 19: Test Custom Data Quality Rules

236 241 249 253

viii

Process and User Interface Configuration

80 Minutes 15 Minutes 15 Minutes 75 Minutes 10 Minutes 20 Minutes

Custom Object Handling Lesson: Creating a Custom Data Model Exercise 24: Create a Custom Data Model Lesson: Creating a Custom User Interface Exercise 25: Create a User Interface Configuration Lesson: Creating a New Change Request Configuration Exercise 26: Create a New Change Request Configuration Exercise 27: Create and Test a User Menu



Course Overview

TARGET AUDIENCE This course is intended for the following audiences: ●

Application Consultant

●

Business Process Architect

●

Business Process Owner/Team Lead/Power User

●

Solution Architect


ix

x


UNIT 1

Master Data Governance Processes

Lesson 1 Governing High-Quality Master Data Exercise 1: Execute a Master Data Search

2 11

UNIT OBJECTIVES ●

Process master data

●

Govern master data centrally

●

Replicate central master data


1

Unit 1 Lesson 1 2

Governing High-Quality Master Data

LESSON OVERVIEW In this lesson, you will learn how to process master data, govern master data centrally, and replicate central master data. LESSON OBJECTIVES After completing this lesson, you will be able to: ●

Process master data

●


●


SAP Enterprise Master Data Management There has been a shift in the way organizations are approaching a master data solution. There are two approaches to master data management. One approach is having master data that is created across different systems within and from outside the enterprise. The master data is then consolidated into a single view to be consumed for various business purposes such as global reporting, Global Data Synchronization, and business analytics. This solution is the traditional approach organizations have taken with master data. A newer approach in master data management is creating up-front line of business processes to have a correct, consistent, and complete master data foundation for business transactions. This approach is needed for end-to-end enterprise master data management and is gaining broad adoption. To accommodate this new approach, SAP first developed the SAP NetWeaver Master Data Management (MDM) system. MDM defines, maintains, and shares consistent definitions of master data across multiple systems within an enterprise. The MDM solution is successful, but customers wanted the application more closely tied to SAP Business Suite ERP (SAP ERP). SAP Enterprise Master Data Governance (MDG) was developed to integrate master data management and SAP ERP. MDG is a system of decision rights and accountabilities for information-related processes carried out for data models. The process models describe specifically who is responsible for which information and what actions they can take. ●

2

The following components are included in the SAP Enterprise MDM product portfolio: -

SAP Master Data Governance—creates master data centrally

-

SAP NetWeaver MDM—consolidates master data

-

SAP Information Steward and Data Services—manages master data quality


Lesson: Governing High-Quality Master Data

Figure 1: MDM Product Portfolio Overview

The SAP Enterprise MDM product portfolio includes applications that you can deploy individually or together based on your company's business needs. For example, you can start with either SAP NetWeaver MDM to consolidate master data for global analytics or SAP Master Data Governance (MDG) for Financials to use in the financial business process.

Master Data Governance for the Central Creation of Master Data MDG enables you to create, maintain, and replicate master data centrally. MDG is the industry’s first governance application to manage master data through a centralized governed process. MDG is built on Line of Business processes and business rules across Business Partner, Customer, Supplier, Material, Financial, and custom domains. MDG enables you to create farreaching master data that impacts the process and data integrity of related applications. SAP Master Data Governance is integrated with SAP Information Steward and Data Services for end-to-end governance.

SAP NetWeaver Master Data Management and the Consolidation of Master Data Records SAP NetWeaver MDM gives you the ability to consolidate master data from different systems. You can use SAP NetWeaver MDM to aggregate, harmonize, and enrich master data. Specific master data consolidation categories include master data key cross-referencing, global reporting, global data synchronization, and product cataloging. SAP NetWeaver MDM is also integrated with SAP Information Steward and SAP Data Services to provide data quality management.

Master Data Governance Business Processes


3

Unit 1: Master Data Governance Processes

Figure 2: Process Flow Archetype

The MDG maintenance process starts when a user requests new master data, changes to existing master data, or when changes to master data are requested by data flowing into the system through an API. A master data request causes the system to generate a change request. A change request is a container that keeps all intended changes in a staging area, separate from the active master data. This process ensures that changes are only moved to production after final approval. The change request moves through a user-defined workflow template until everyone in the workflow views the change request and the master data is completed. Change requests can also store incomplete, inactive data during the workflow. Storing incomplete data allows a company to determine who will contribute specific information to the new record without affecting the active master data. The system continuously validates data during maintenance with existing business logic and customization settings. The system validation also integrates services for data enrichment and cleansing. Data enrichment and cleansing include checking addresses against reference data from an SAP Data Services system. Companies can add their own validation rules. Near the end of the workflow, a user approves the changes. After approval, the system moves the data from the staging area into the active master data. The system makes the data available to business processes and replicates the appropriate data to other systems. Organizations can place a subset of all master data attributes under central governance. These attributes can be enriched in the receiving systems according to local needs.

High-Level Architecture

4



Figure 3: High-Level Architecture

MDG is built on top of the Application Server for ABAP (AS for ABAP), similar to the main SAP Business Suite components. Some components of MDG are in a software layer below SAP ERP. These components can be reused by SAP ERP applications. Other components of MDG are in a software layer above SAP ERP and use existing SAP ERP coding, such as the built-in validations for SAP ERPrelated master data. MDG uses SAP solutions for enterprise information management (EIM) components such as fuzzy searches for enterprise search and SAP Data Services for address validation. MDG provides HTML-based user interfaces (UIs) based on Web Dynpro for ABAP and roles that can be accessed either through the SAP NetWeaver Portal or through the SAP NetWeaver Business Client. The MDG Data Replication Framework (DRF) manages the distribution of master data to SAP and non-SAP systems using technologies like ALE IDoc and Enterprise Services.

Key Capabilities


5


Figure 4: Business Process Performance

Master Data Governance is a powerful software product that includes many features for business suite customers. The following capabilities facilitate business process performance: ●

Delivers an out-of-the-box solution

●

Provides an integrated object model

●

Maintains governance, collaboration, and data quality

●

Provides robust data replication

●

Allows reusability and extensibility

Integrated Object Model SAP MDG includes the Financials, Material, Supplier, and Customer domains. These data models can be extended, or you can create your own. The Financials data model includes the following information: ●

Chart of accounts

●

General ledger accounts and their hierarchies

●

Company data

●

Profit and cost centers and their hierarchies

●

Most elements and their hierarchies

The Material data model contains over 300 attributes, which includes the following information:

6

●

General data

●

Units of measure

●

Tax information



●

Classification

●

Valuation and costing data

●

Sales organizations

●

Distribution channels

The Supplier data model is based on a broad range of generic business partner and SAP ERPspecific attributes including the following data: ●

Addresses

●

Business Partner relationships

●

Purchasing data

●

Company code data

The Customer data model is based on the generic business partner and SAP ERP-specific attributes including the following information: ●

Sales area data

●

Company code data

●

Tax indicators

Workflow and User-Centric Collaboration

Figure 5: Governance and Collaboration

MDG enables collaboration through integrated workflow templates. The workflow templates guide the process to multiple users who create or change master data. MDG is based on SAP NetWeaver Application Server for ABAP (AS for ABAP) and is embedded into SAP ERP. Companies can adapt MDG processes based on existing SAP business logic or by using new a new SAP ERP system running MDG only. Companies can also combine validations based on SAP business logic with other freely defined validation rules. These capabilities help companies achieve data quality from the start. MDG provides many out-of-the-box features including data models, UIs, workflow templates, and validations. All of these features can easily be adapted to a company’s needs.


7


Adaptations can include, for example, changing workflow templates or assigning different validations. MDG uses the flexibility and reporting capabilities of SAP Business Workflow. You can define the process in a linear model, or you can define the process using a distributed model. In a distributed model, different departments or locations maintain and approve only the data for which they are responsible. This model is defined within roles such as Business User, Master Data Steward, and Master Data Manager. You can adapt processes to accommodate business networks already in use.

Data Quality Overview

Figure 6: Data Quality

Data Quality MDG enables companies to implement specific data quality criteria as defined in the company's information governance initiatives. MDG helps you avoid duplicate data entries. Duplicate prevention is based on high-quality detection algorithms that include fuzzy logic from SAP Enterprise Search and phonetic search and standardization of data provided by SAP Data Services. You can enrich data and validate addresses using SAP Data Services postal validation. You can validate addresses based on custom-defined validation rules such as integrity rules, derivations, and other simple checks. You can specify postal validation criteria using the SAP BRFplus rule modeling tool. You can also use SAP Information Steward together with MDG for integrated data quality analysis and remediation. Data Quality Remediation Process MDG ensures that standards are observed when master data is created and changed. If master data does not comply with changing standards, then the objects with errors are identified with data quality services. With a data quality tool or your own implementation, these problems are solved. Data quality remediation (DQR) provides the process integration of identifying master data objects with errors in a data quality tool for the SAP Information Steward. To use this process, implement a data quality tool that is not part of the delivery of MDG. The data quality tool analyzes master data according to a set of data quality rules to detect objects with errors. A

8



data quality check can be done in a periodic batch run based on master data that was previously loaded from MDG systems and other systems. Typically, the Master Data Specialist wants to identify the objects with errors with the highest priority or with similar quality issues using a data quality tool. A data quality tool offers filtering of the objects with errors according to a rule (or a set of rules). MDG allows the master data specialist to select the criteria for the filtering that is done by the data quality tool. Alternatively, MDG can integrate a data quality tool specific UI that allows you to select filtering criteria. DQR retrieves the objects with errors and displays them for investigation by the master data specialist. The master data specialist selects an object with errors and creates a change request for data quality remediation. Using the data quality remediation process, it is possible to create multiple change requests at once, one for each of the selected objects, or one change request can be used for multiple objects.

Reuse and Extensibility

Figure 7: Reusability and Extensibility of Standard Content

MDG lets you reuse extensions that you have already stored in the SAP Business Suite. You can include these extensions directly in the MDG data models. You can also reuse the business logic that you have created in the SAP Business Suite, such as validating newly created master data. All SAP customers create extensions to SAP’s standard master data model. Many of these customer extensions prescribe specific master data creation and change processes. To support these extensions, MDG offers customers flexible and extensible features to adapt these standards to their needs. The most important benefit is enabling customers to add these extensions while continuing to employ MDG’s out-of-the-box features.

Comprehensive Searches To avoid creating duplicate records, perform a comprehensive system search before creating a new object. The following features and criteria are available from the search tool: ●

Search method – Select a search method and include fuzzy search logic if desired.


9


●

●

●

Saved searches – Select a saved search to reuse, or discard saved searches using the delete icon. Search criteria – Add and remove search parameters, and use combination of multiple parameters. Search results – View and sort search results.

Editions and the Change Request Process To aid in the governance of Financial master data, MDG includes "editions" integrated into Financial change requests. Editions help to control the effective date of approved master data. The following conditions apply to a change request process with an edition: ●

●

●

●

●

●

The edition is created before creating change requests. The change request is assigned to a specific edition. Several change requests can be assigned to an edition. The change request includes the business reason for changing the master data and controls the approval and change process. The edition is released when all change requests assigned to the edition are approved or withdrawn. The edition cannot be assigned new change requests after it is released. The replication of a change request to local systems is triggered either by approving a single change request or by approving the edition as a whole.

How to Execute a Master Data Search For the demonstration steps and data, see the exercise Execute a Master Data Search.

10


Unit 1 Exercise 1 11

Execute a Master Data Search

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. Before you can add additional products, you determine that the main lab does not have enough capacity to ensure the quality of the new products. You will need to move the quality processes of the existing product line Demo CD to another quality lab. In this exercise, when values include ##, replace the characters with the numbers that your instructors assigned to you. Access the Training System and Log In 1. On the SAP system, open the connection ZME and log into the system. Dialog box

Field

Value

SAP

Client

800

SAP

User

Provided by your instructor

SAP

Password


SAP

Language

EN

2. Launch NetWeaver Business Client. 3. Search for material ACT-DCD-##.


11

Unit 1 Solution 1 12

Execute a Master Data Search

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. Before you can add additional products, you determine that the main lab does not have enough capacity to ensure the quality of the new products. You will need to move the quality processes of the existing product line Demo CD to another quality lab. In this exercise, when values include ##, replace the characters with the numbers that your instructors assigned to you. Access the Training System and Log In 1. On the SAP system, open the connection ZME and log into the system. Dialog box

Field

Value

SAP

Client

800

SAP

User


SAP

Password


SAP

Language

EN

a) In the SAP dialog box, enter a new password. Enter a password that you can remember because you will need to use it again in other exercises. b) Choose Enter. c) In the System Messages dialog box, choose Enter. 2. Launch NetWeaver Business Client. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. 3. Search for material ACT-DCD-##. a) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. b) On the Material Governance Homepage screen, choose Search Material. c) On the Search: Materials screen, below the Search Criteria table, choose Hide Classification Criteria. d) In the Search Criteria table, in the last row, in the first column for search attributes, choose Description (medium text).

12



e) In the second column for the relation operator, choose Contains. f) In the third column for the search attribute value, enter Demo. g) Choose Search. h) In the Search Criteria table, go to the first row with the search attribute Material, and in the third column for search attribute values, enter ACT*. i) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.


13


Data Replication

Figure 8: Robust Data Replication

After maintaining and approving the master data on the central MDG system, you can replicate the data to all SAP and non-SAP systems that will need the master data. MDG Data Replication Framework (DRF) supports the organization and execution of data replication. MDG DRF is designed to support your company's existing replication and distribution. The MDG DRF framework is built on the replication mechanisms already used in SAP applications and services. MDG DRF tracks what will be distributed, where it goes, and the success of the distribution. In DRF, you can subscribe the distribution of master data to systems based on filter criteria – such as only tracking materials for plant 1000 with material type FERT that are distributed to system XYZ. Table 1: Data Replication Framework Mechanisms Replication

Replication Techniques

●

Automatic or manual replication to SAP and non-SAP systems

●

Peer-to-peer or mediated replication

●

Data Replication Framework (DRF) controlling mechanisms: -

-

-

●

Replication Features

●

●

14

Application Link Enabling (ALE) for SAP ERP, R/3, and non-SAP systems Service-Oriented Architecture (SOA) service for SAP and non-SAP systems Remote Function Call (RFC) and File for SAP and non-SAP systems

Core Interface Function (CIF) for SAP SCM and middleware for SAP CRM and SRM Can replicate selected data to a specific client system by defining filters, controlled by DRF Supports different object IDs or customizing keys in hub and client systems, mapping in MDG or NetWeaver Process Integration



MDG provides key mapping, value mapping, distribution monitoring, and error resolution. Key mapping tracks different historical keys for existing master data in decentralized systems and makes sure that one instance of the data is maintained centrally. Value mapping lets you distribute data into systems that might have a different understanding of the values of an attribute. For example, distributing material type FERT from the original system to a system in which the same material type is called HALB. Distribution monitoring is a log that lets you monitor the details of distribution so that suitable actions can be taken for erroneous records. For example, you can view how many objects were successfully replicated and to which target systems.

Data Transfer The following use cases apply to extraction and load: ●

●

Initial load in the MDG implementation phase loads data into a new MDG system. Initial load while operating MDG, loads data from new client systems into running MDG system.

●

Delta loads are high volume transferred from already connected client systems.

●

Extractions are high volume transfers from MDG to client systems.

Figure 9: Extraction and Load Overview

The following key capabilities apply to extraction and load: ●

Extracts data from client systems and MDG system including master data, key mapping, and value mapping.

●

Performs data transformation from IDoc format to SOA messages.

●

Uploads data to the MDG system including master data, key mapping, and value mapping.


15


Deployment Options

Figure 10: MDG Deployment Options

MDG is part of SAP ERP. To install MDG, first install SAP ERP including relevant Enhancement Packages. When you run MDG processes they are part of a full SAP ERP system. You can deploy MDG in one of two ways in relation to your existing systems: 1. Introduce a completely new system with a dedicated master data hub. This system is a complete SAP ERP system. You only use the MDG functions to distribute the master data to the parts of the system running business processes. 2. Install MDG on an existing SAP ERP system for certain master data domains and run MDG on this system. MDG manages master the data for those domains, such as Material Data. The approved data from MDG processes is available directly to the business processes that run on that system and are distributed to all other systems that need it. The second option can also be implemented as a single SAP ERP system. You can co-deploy MDG with that system, which involves upgrading your systems and switching on the MDG Business Functions. Even if you do not want to distribute the master data to any receiving system — which is rare — you can realize the following benefits of using MDG: ●

●

16

Separate incomplete or unapproved data from production data through MDG staging Use MDG workflow templates to distribute maintenance workflow templates that have been executed to multiple people

●

Enhance validations beyond the hard-coded checks of SAP ERP

●

Improved prevention of duplicates and all the other features of MDG



LESSON SUMMARY You should now be able to: ●

Process master data

●


●



17


18


Unit 1

19

Learning Assessment

1. What does Master Data Governance allow you to do? Choose the correct answers. X

A Create

X

B Consolidate

X

C Maintain

X

D Replicate

2. The SAP Enterprise MDM product portfolio includes applications that you can only deploy individually. Determine whether this statement is true or false. X

True

X

False

3. What is a change request? Choose the correct answer. X

A It is a container that keeps all intended changes in a staging area, separate from the productive master data.

X

B It is a container that includes all changes and ensures that changes are moved to production as quickly as possible.

X

C It is a container that only stores complete data in the workflow.

X

D It is a container that keeps approved data separate from the workflow.


19

Unit 1: Learning Assessment

4. What domains are available in Master Data Governance? Choose the correct answers. X

A Customer

X

B Financial

X

C Material

X

D Supplier

X

E Functional Location

5. What is key mapping used for? Choose the correct answer. X

A Key mapping tracks similar historical keys for new master data.

X

B Key mapping tracks different historical keys for new master data.

X

C Key mapping tracks similar historical keys for existing master data.

X

D Key mapping tracks different historical keys for existing master data.

6. Value mapping lets you distribute data into systems that might have a different understanding of the values of an attribute. Determine whether this statement is true or false.

20

X

True

X

False


Unit 1

21

Learning Assessment - Answers

1. What does Master Data Governance allow you to do? Choose the correct answers. X

A Create

X

B Consolidate

X

C Maintain

X

D Replicate

2. The SAP Enterprise MDM product portfolio includes applications that you can only deploy individually. Determine whether this statement is true or false. X

True

X

False

3. What is a change request? Choose the correct answer. X

A It is a container that keeps all intended changes in a staging area, separate from the productive master data.

X

B It is a container that includes all changes and ensures that changes are moved to production as quickly as possible.

X

C It is a container that only stores complete data in the workflow.

X

D It is a container that keeps approved data separate from the workflow.


21

Unit 1: Learning Assessment - Answers

4. What domains are available in Master Data Governance? Choose the correct answers. X

A Customer

X

B Financial

X

C Material

X

D Supplier

X

E Functional Location

5. What is key mapping used for? Choose the correct answer. X

A Key mapping tracks similar historical keys for new master data.

X

B Key mapping tracks different historical keys for new master data.

X

C Key mapping tracks similar historical keys for existing master data.

X

D Key mapping tracks different historical keys for existing master data.

6. Value mapping lets you distribute data into systems that might have a different understanding of the values of an attribute. Determine whether this statement is true or false.

22

X

True

X

False


UNIT 2

Single Object Processing

Lesson 1 Managing Master Data Changes Exercise 2: Change Material Data Records Exercise 3: Search for Material Records and Create a Copy of a Record

24 29 35

Lesson 2 Processing Parallel Workflow Steps Exercise 4: Process Parallel Workflow Steps for Supplier Records

39 43

Lesson 3 Processing Customer Master Data on a Client System Exercise 5: Process Customer Master Data on a Client System

55 59

UNIT OBJECTIVES ●

Change a master data record

●

Create copies of records

●

Process parallel workflow steps for supplier records

●

Process customer master data on a client system


23

Unit 2 Lesson 1 24

Managing Master Data Changes

LESSON OVERVIEW In this lesson, you will learn how to change a master data record and create copies of records. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


●


Master Data Governance Process

Figure 11: Master Data Governance Process Flow

The MDG maintenance process typically starts when a user requests new master data, requests changes to existing master data, or when changes to master data are requested by data flowing into the system. A master data request causes the system to generate a change request. A change request is a container that keeps all intended changes in a staging area, separate from the active master data. The staging area ensures that changes are only moved to production after final approval. The change request moves through a defined workflow until everyone in the workflow instance views the change request and the master data is completed.

24


Lesson: Managing Master Data Changes

Change requests can also store incomplete, inactive data during the workflow. Storing incomplete data allows a company to determine who will contribute specific information to the new record without affecting the active master data. The system continuously validates data during maintenance with existing business logic and customization settings. The system validation can also integrate services for data enrichment and cleansing. Data enrichment and cleansing include checking addresses against reference data from an SAP Data Services system. Companies can add their own validation rules. Near the end of the workflow, a user approves the changes. After approval, the system moves the data from the staging area into the active master data. The system makes the data available to business processes and replicates the appropriate data to other systems. Organizations can place a subset of all master data attributes under central governance. These attributes can be enriched in the receiving systems according to local needs

Workcenter Roles The roles in MDG are structured consistently with access to change requests and data exchange. Financials has an additional Workcenter for editions. SAP provides templates of typical roles that customers can copy and modify to create their own roles. The following list describes Workcenter roles process: ●

A user selects an assigned role.

●

The user then accesses the Workcenter based on their roles.

●

The user triggers processes from the Workcenter or from the user work list.

General Change Request Workflow Process

Figure 12: General Change Request

You can use the create change request process to create any type of change request. The change request type determines the following elements: ●

The data model and entity types can be maintained

●

The workflow template the system uses


25

Unit 2: Single Object Processing

●

The UI configuration, if applicable

When creating a change request, the requestor enters a description what they want changed or created. A master data expert, who can also be the requestor, then enters the master data according to the description of the requestor. The workflow can also include additional steps for users to enter comments or specific master data. The submission for final approval is then triggered either by a person in the workflow or by an automated rule. After final approval, the master data is activated and available for replication to local systems. If the final approver rejects the change request, a special rework step can be triggered. The person designated to rework the data can determine what changes to make and then resubmit or withdraw the change request.

Staging Area Usage

Figure 13: Request and Change Request Workflow Template Process

The following steps make up a request and change request workflow process: ●

●

●

●

Request — Creation of a change request including the reason for the request and other information such as attachments. Maintain -

Users add comments.

-

The system retrieves active master data.

-

The system maintains the master data and updates it in the staging area.

Validate — Validation happens upon request, when users save changes, and after a save in the background. Approve -

-

26

The approval process is part of collaboration by an adaptable workflow template. The approval activates new data, and the system moves the new data from the staging area to the active database.



●

Replicate — Automatic replication by the system to non-SAP and SAP systems.

You can configure the workflow process change requests for differently specific applications and customers.

How to Change Material Data Records For the demonstration steps and data, see the exercise Change Material Data Records.


27


28



Change Material Data Records

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line and is starting to manufacture mini CDs. You have been asked to create the correct CD labels. To support the new product, you have been asked to maintain additional master data to reflect the business in the SAP ERP system. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Search for all materials with the descriptions demo and label in material ACT. 2. Edit material ACT-DCD-## so that the Lab/Office is 002. 3. Approve the change request for ACT-MCD-##. 4. Review the change in SAP ERP.


29


Change Material Data Records

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line and is starting to manufacture mini CDs. You have been asked to create the correct CD labels. To support the new product, you have been asked to maintain additional master data to reflect the business in the SAP ERP system. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Search for all materials with the descriptions demo and label in material ACT. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) On the Material Governance Homepage, choose Search Material. f) On the Search: Material screen, in the Search Criteria table, in the last row, in the first column for search attributes, choose Description (medium text). g) In the second column for the relation operator, choose Contains. h) In the third column for the search attribute value, enter demo. i) Choose Search. j) In the first column for search attributes, choose Material. k) In the third column for search attribute values, enter ACT. l) Choose Search. 2. Edit material ACT-DCD-## so that the Lab/Office is 002. a) In the Results List, choose ACT-DCD-##. b) On the Material: ACT-DCD-## screen, choose Edit. c) On the General tab, in the Description field, enter Change Laboratory on ACTDCD-##. d) In the Due Date field, enter tomorrow's date. e) In the Design Data section, in the Lab/Office field, enter 002. f) Choose Check.

30



g) Choose Submit. 3. Approve the change request for ACT-MCD-##. a) In the navigation panel, choose Change Requests → Change Requests and Documents → My Change Requests. b) In the Change Requests table, choose the change request you created. c) On the Material: ACT-DCD-01 screen, choose Activate. d) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. 4. Review the change in SAP ERP. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MMO3. b) Choose Enter. c) On the Display Material (Initial Screen), in the Material field, enter ACT-DCD-##. d) Choose Continue. e) On the Select Views dialog box, choose Basic Data 1. f) Choose Continue. g) On the Display Material ACT-DCD-## (Finished Product) screen, view the Lab/Office field. h) Choose Environment → Display Changes. i) On the Display Changes: Material Overview screen, in the List of all Change Documents for material ACT-DCD-## table, in the Changed By field, select WF_BATCH. j) Choose Enter. k) Choose Back until you return to the SAP Easy Access - User Menu screen.


31


Master Data Governance User Interface

Figure 14: Central Workcenter for Master Data Maintenance

All activities associated with creating and maintaining master data are combined in one workcenter for each domain. Companies can establish this workcenter as the standard hub for creating and changing master data. If your company does not use the SAP Enterprise Portal, you can use a workcenter based on SAP NetWeaver Business Client. The following business challenges have been expressed by some SAP customers: ●

●

●

Master data is maintained on different computer systems. Different transactions are performed to complete common maintenance tasks such as change, create, and delete. Planned changes are not transparent or shared to other systems.

The following business values can be achieved using SAP Workcenters: ●

Activities required to complete master data governance on one system are bundled into one system.

●

Central deployment and authorization ensures comprehensive governance.

●

Localize and personalize the UI to meet customer needs.

Specific Processes in Master Data Governance The following domain-specific processes are available in Master Data Governance: ●

Mass loading of master data

●

Searching for object instances

●

Centrally creating new object instances

●

Change existing single object instances -

32

Make general changes



●

-

Extend existing object instance, such as adding a new company code

-

Block or phase out an existing object instance

Replicating specific object instances into specific target systems

Specific Processes in Material Governance

Figure 15: Material Governance Specific Processes

MDG features many built-in processes, including domain-specific processes for material governance. Many of these processes employ user interface components specific to the domain. Table 2: Processes and Standard Business Activities for the Material Domain Processes Specific to the Material Domain

Standard Business Activities

Create material

MAT1

Process material

MAT2

Display material

MAT3

Mark material for deletion

MAT6

Process multiple materials

MATA

Import material

MATB

These material domain processes are preconfigured with a set of BRFplus rules for the rulebased workflow template. You can import and enhance these rules based on the requirements of your system. MDG includes standard material workcenters in the user menu, which correspond to the preconfigured material domain processes.


33


Figure 16: Material Specific Rule-based Workflow Template

How to Search for Material Records and Create a Copy of a Record For the demonstration steps and data, see the exercise Search for Material Records and Create a Copy of a Record.

34



Search for Material Records and Create a Copy of a Record

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. You have been asked to maintain additional master data to reflect the business in the SAP ERP backend system. Your company has also started to manufacture mini CDs and needs the appropriate labels. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Search for all materials with the description label in materials group 00213. 2. Copy the existing label to the new material ACT-MCD-## using the data in the following table and note the change request ID. Field

Value

Material

ACT-MCD-##

Due Date

Enter tomorrow's date

Description

Create Mini-CD Label ##

Note the change request ID.

3. Approve the change request for ACT-MCD-##. 4. View the new change request.


35


Search for Material Records and Create a Copy of a Record

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. You have been asked to maintain additional master data to reflect the business in the SAP ERP backend system. Your company has also started to manufacture mini CDs and needs the appropriate labels. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Search for all materials with the description label in materials group 00213. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) On the Material Governance screen, choose Search Material. f) On the Search Material screen, in the Search Criteria table, in the last row, in the first column for search attributes, choose Description (medium text). g) In the second column for the relation operator, choose Contains. h) In the third column for the search attribute value, enter label. i) Choose Search. j) At the end of the Description (medium text) row, choose Add Row. k) In the new row, in the first column for search attributes, choose Material Type. l) In the third column for search attribute values, choose ROH (Raw Materials). m) Choose Search. n) At the end of the Description (medium text) row, choose Add Row. o) In the new row, in the first column for search attributes, choose Material Group. p) In the Search Criteria table, in the first row, go to the first row with the search attribute Material Group, and in the third column for search attribute values, enter 00213. q) Choose Enter. 2. Copy the existing label to the new material ACT-MCD-## using the data in the following table and note the change request ID.

36



Field

Value

Material

ACT-MCD-##

Due Date

Enter tomorrow's date

Description

Create Mini-CD Label ##

Note the change request ID. Answers will vary. a) In the Results List, select ACT-LCD-##. b) Choose Copy. c) On the Material: New screen, in the Material field, enter the data from the table. d) On the Change Request screen, enter the data from the table. e) Choose Continue. f) On the Material New, ACT-MCD-## screen, in the General Data section, in the Description field, enter the data from the table. g) In the Descriptions section, enter the data from the table. h) Choose Submit and note the change request ID. 3. Approve the change request for ACT-MCD-##. a) On the Material New, ACT-MCD-## screen, in the navigation panel, choose Change Requests → Change Requests and Documents → My Change Requests. b) Select Change Request ID you noted in the previous task. c) On the Material: ACT-MCD-## screen, choose Activate. d) Choose Back until you return to the SAP Easy Access - User Menu screen. 4. View the new change request. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MM03. b) Choose Enter. c) On the Display Material (Initial Screen), in the Material field, enter ACT-MCD-##. d) Choose Select Views. e) In the Select Views dialog box, choose Basic Data 1. f) On the Display Material ACT-MCD-## (Finished Product) screen, choose Environment → Display Changes. g) Choose Back until you return to the SAP Easy Access - User Menu screen.


37


LESSON SUMMARY You should now be able to:

38

●


●



Unit 2 Lesson 2 39

Processing Parallel Workflow Steps

LESSON OVERVIEW In this lesson, you will learn how to process parallel workflow steps for supplier records. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Supplier Record Creation Process

Figure 17: Change Request Workflow Template Process

The change request workflow template can be configured with parallel approval steps for specific parts of the process. The process ends when all parallel approval steps have been completed.

Parallel Processing of Supplier Data


39


Figure 18: Supplier Workflow Template Parallel Process

Figure 19: Supplier Workflow Template Process Completion

The change request workflow can be configured with an intermediate approval step workflow template.

40


Lesson: Processing Parallel Workflow Steps

How to Process Parallel Workflow Steps for Supplier Records For the demonstration steps and data, see the exercise Process Parallel Workflow Steps for Supplier Records.


41


42



Process Parallel Workflow Steps for Supplier Records

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. Recently there have been some quality issues with one of your supplier's packaging materials. The head of procurement has asked you to add a new supplier that can be used as an alternative provider. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. Search for a Supplier 1. Check that the new supplier with a postal code of 68* has not already been created. 2. Narrow your search to include only suppliers located in the city of Hockenheim. Create a New Supplier 1. Create a new organization using the data in the following table. Dialog Box

Field

Value

Available Change Request Type

List of Available Change Request Types

Create Supplier-EhP6

Organization: $, Konrad ## Kartonagen/ D-68799

Description

## New Supplier


Due Date

Select tomorrow's date.


Business Partner ID/ Grouping

Internal Number Assignment


Name 1

Konrad ## Kartonagen


Search Terms

●


●

In the first field, enter ##. In the second field, enter Konrad.

43


Dialog Box

Field

Value


Street/House Number

●

●


Postal Code/City

●

●


Country

DE


Region

08


Language

DE

In the first field, enter Speyer Strasse In the second field, enter ##. In the first field, enter 68799 In the second field, enter Hockenheim

2. Select a role for the business partner called FLVN01 in the account group Vendors. 3. Create a vendor for the business partner using the data from the following table. Field

Value

Company Code

001

Reconciliation

160000

Planning Group

A1

Terms of Payment

0003

Payment Methods

●

2

●

A

●

E

4. Add the SAP ERP purchasing organization details using the data in the following table and return to the Change Request screen.

44

Field

Value

Purchasing Organization

1000

Order Currency

EUR

Terms of Payment

0003



Field

Value

Incoterms

●

In the first field, enter CIF

●

In the third field, enter Hockenheim

5. Check the change request, submit it for approval, and note the change request number. Note the change request number.

Approve the Create Vendor Change Request 1. Approve the creation of the business partner data object. 2. Refresh the Change Request tab. 3. Finalize the company code dependent data. 4. Refresh the Change Request tab. 5. Approve the company code dependent data. 6. Refresh the Change Request tab. 7. Finalize the purchasing organization dependent data process. 8. Refresh the Change Request tab. 9. Approve the purchasing organization dependent data. Review the Change Request 1. Open the new business partner and note the Business Partner ID and ERP Vendor number. Note the Business Partner ID. You will use this ID in other exercises.

Note the ERP Vendor number.

2. View the workflow log details. Review Key Mapping Information 1. Search for the business partner number you noted earlier using the data in the following table.


45


Field

Value

Object Type

Business Partner

Object Identifier

Business Partner Number

ID Value

Enter the business partner ID you noted earlier.

View the New Data in SAP ERP 1. Change the business partner's vendor data to display in the BP role AAA MDG: FI Vendor (CVI).

46



Process Parallel Workflow Steps for Supplier Records

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. Recently there have been some quality issues with one of your supplier's packaging materials. The head of procurement has asked you to add a new supplier that can be used as an alternative provider. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. Search for a Supplier 1. Check that the new supplier with a postal code of 68* has not already been created. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Supplier Governance. e) In the navigation panel, choose Change Requests → Supplier Processing → Search Supplier. f) On the Search Supplier screen, in the Search Method drop down menu, choose Address Data. g) In the Postal Code search attribute field, in the search value field, enter 68*. h) Choose Search. 2. Narrow your search to include only suppliers located in the city of Hockenheim. a) At the end of the search attribute fields, choose the Insert New Row button. b) In the new row, in the first field for search attributes, in the drop-down menu, select City. c) In the search value field, enter Hockenheim. d) Choose Search. Create a New Supplier 1. Create a new organization using the data in the following table.


47


Dialog Box

Field

Value

Available Change Request Type

List of Available Change Request Types

Create Supplier-EhP6


Description

## New Supplier


Due Date



Business Partner ID/ Grouping

Internal Number Assignment


Name 1

Konrad ## Kartonagen


Search Terms

●


Street/House Number

●

●

●


Postal Code/City

●

●


Country

DE


Region

08


Language

DE

In the first field, enter ##. In the second field, enter Konrad. In the first field, enter Speyer Strasse In the second field, enter ##. In the first field, enter 68799 In the second field, enter Hockenheim

a) In the Search Results table, choose New → Organization. b) Complete the Available Change Request Types dialog box using the data from the table.

48



c) Choose OK. d) On the Organization: $, (No Description Available) screen, enter the data from the table. e) Choose Save. 2. Select a role for the business partner called FLVN01 in the account group Vendors. a) On the Organization: $, Konrad ## Kartonagen/D-68799 screen, in the Roles section, choose New. b) In the new row, in the BP Role column, choose the drop-down button. c) In the Search: BP Roles dialog box, select FLVN01. 3. Create a vendor for the business partner using the data from the following table. Field

Value

Company Code

001

Reconciliation

160000

Planning Group

A1

Terms of Payment

0003

Payment Methods

●

2

●

A

●

E

a) On the Organization: $, Konrad ## Kartonagen/D-68799 screen, in the ERP Vendors Section, choose New. b) On the Organization: $, Konrad ## Kartonagen/D-68799 - ERP Vendor screen, in the ERP Vendor: Company Codes section, choose New. c) On the Organization: $, Konrad ## Kartonagen/D-68799 - ERP Vendor Company Code screen, in the ERP Vendor: Company Code section, in the Company Code field, enter the data from the table. d) In the ERP Vendor Company Code: Accounting Information section, in the Reconciliation field, enter the data from the table. e) In the Planning Group field, enter the data from the table. f) In the ERP Vendor Company Code: Payment Data section, in the Terms of Payment field, enter the data from the table. g) In the ERP Vendor Company Code: Automatic Payment Transactions section, in the Payment Methods field, on your keyboard, press CTRL, and then select the options from the table. h) Choose Done. 4. Add the SAP ERP purchasing organization details using the data in the following table and return to the Change Request screen.


49


Field

Value

Purchasing Organization

1000

Order Currency

EUR

Terms of Payment

0003

Incoterms

●

In the first field, enter CIF

●

In the third field, enter Hockenheim

a) On the Organization: $, Konrad ## Kartonagen/D-68799 - ERP Vendor screen, in the ERP Vendor: Purchasing Organizations section, choose New. b) On the Organization: $, Konrad ## Kartonagen/ D-68799 - ERP Vendor Purchasing Organization screen, in the Purchasing Organization field, enter the data from the table. c) In the ERP Vendor: Purchasing Organization: Conditions section, in the Order Currency field, enter the data in the table. d) In the Terms of Payment field, enter the data from the table. e) In the Incoterms row, enter the data from the table. f) Choose Done. g) On the Organization: $, Konrad ## Kartonagen/D-68799 - ERP Vendor screen, choose Done. 5. Check the change request, submit it for approval, and note the change request number. Note the change request number. Answers will vary. a) On the Organization: $, Konrad ## Kartonagen/D-68799 screen, choose Check. b) Choose Submit. c) Note the change request number. d) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. Approve the Create Vendor Change Request 1. Approve the creation of the business partner data object. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, in the navigation panel, choose Change Requests.

50



e) On the Change Requests tab, choose your change request. f) Choose Approve. g) Choose Close to close the internet browser window and return to the SAP Business Client screen. 2. Refresh the Change Request tab. a) On the SAP Business Client screen, choose Refresh. 3. Finalize the company code dependent data. a) On the SAP Business Client screen, choose Process Change Request : SUPPLIER (Standard) Data of Company Code. b) On the Organization: $, Konrad ## Kartonagen/D-68799 Hockenheim screen, choose Finalize Processing. c) Choose Close to close the internet browser window and return to the SAP Business Client screen. 4. Refresh the Change Request tab. a) On the SAP Business Client screen, choose Refresh. 5. Approve the company code dependent data. a) On the SAP Business Client screen, choose Process Change Request : SUPPLIER (Standard) Data of Company Code. b) On the Organization: $, Konrad ## Kartonagen/D-68799 Hockenheim screen, choose Approve. c) Choose Close to close the internet browser window and return to the SAP Business Client screen. 6. Refresh the Change Request tab. a) On the SAP Business Client screen, choose Refresh. 7. Finalize the purchasing organization dependent data process. a) On the SAP Business Client screen, choose Process Change Request , SUPPLIER (Standard) Data of Purchasing Organization. b) On the Organization: $, Konrad ## Kartonagen/D-68799 Hockenheim screen, choose Finalize Processing. c) Choose Close to close the internet browser window and return to the SAP Business Client screen. 8. Refresh the Change Request tab. a) On the SAP Business Client screen, choose Refresh. 9. Approve the purchasing organization dependent data. a) On the SAP Business Client screen, choose Approve Change Request : SUPPLIER Data of Purchase Organization. b) On the Organization $, Konrad ## Kartonagen/D-68799 Hockenheim screen, choose Approve. c) Choose Close to close the internet browser window and return to the SAP Business Client screen.


51


Review the Change Request 1. Open the new business partner and note the Business Partner ID and ERP Vendor number. Note the Business Partner ID. You will use this ID in other exercises. Answers will vary. Note the ERP Vendor number. Answers will vary. a) On the SAP Business Client screen, choose Change Requests → Change Requests and Documents → My Change Requests. b) In the My Change Request table, choose your change request ## New Supplier. c) On the Organization: $, Konrad ## Karatonagen/D-68799 Hockenheim screen, in the Supplier Details section, note the business partner ID. d) In the ERP Vendor section, note the ERP Vendor number. 2. View the workflow log details. a) On the Organization: $, Konrad ## Kartonagen/D-68799 Hockenheim screen, choose Workflow Log. b) On the Workflow Log for Change Request screen, view the workflow log details. c) Choose Close to close the Workflow Log internet browser window. d) Choose Close to close the Organization: $, Konrad ## Kartonagen/D-68799 Hockenheim internet browser window and return to the SAP Business Client screen. Review Key Mapping Information 1. Search for the business partner number you noted earlier using the data in the following table. Field

Value

Object Type

Business Partner

Object Identifier

Business Partner Number

ID Value

Enter the business partner ID you noted earlier.

a) On the SAP Business Client screen, choose Data Exchange → Data Replication → Search Key Mapping. b) On the Search Key Mapping screen, enter the data from the table. c) Choose Search Objects.

52



d) In the search results table, view the results. e) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. View the New Data in SAP ERP 1. Change the business partner's vendor data to display in the BP role AAA MDG: FI Vendor (CVI). a) On the SAP Easy Access - User Menu screen, in the Command field, enter BP. b) Choose Enter. c) On the Maintain Business Partner screen, in the Business Partner field, enter the business partner ID you noted earlier. d) Choose Enter. e) On the Display Organization: screen, in the Display in BP Role drop-down menu, choose AAA MDG: FI Vendor (CVI). f) On the Display Organization: , role AAA MDG: FI Vendor (CVI) screen, choose the Vendor: General Data tab. g) In the Vendor Number field, locate the vendor number. h) Choose Back until you return to the SAP Easy Access - User Menu screen.


53



54



Unit 2 Lesson 3 53

Processing Customer Master Data on a Client System

LESSON OVERVIEW In this lesson, you will learn how to process customer master data on a client system. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Client Maintenance Process for the Customer Domain

Figure 20: Client Maintenance For Customers - Process

The business function, Master Data Governance for Customer on the designated SAP ERP client (MDG_CUST_ERPCLIENT_1), provides features for decentralized customer master data governance. It enables you to search and compare corresponding data on the hub system before creating or changing customer master data on a client system. If the customer data is not already available on the client, you can copy the customer master data from the hub system to the client system. The data can be edited in the client system. This business function provides features for decentralized customer master data governance. It enables you to search and compare corresponding data on the hub system before creating or changing customer master data on a client system. If the customer data is not already


55


available on the client, you can copy the customer master data from the hub system to the client system. The data can be edited in the client system. Use the following client maintenance process strategy for customers: 1. Search from the client system. ●

The requestor searches for customers and suppliers from the client.

●

The results include entries from the client and Hub.

2. Copy from the Hub to the client system. ●

The results include entries currently available only on the Hub system.

●

The requestor needs this customer and supplier also to appear on the client.

●

The requestor copies the entry from the Hub to the client.

3. Change the client system. After copying an entry, the requestor can change the customer and supplier copied from the Hub. 4. Transfer changes to the Hub. ●

The system transfers any changes made on the client to the same entry on the Hub.

●

The system executes the governance workflow.

●

After final approval, the system replicates changes to all client systems.

Figure 21: Client Maintenance Search on Hub

Use the following client maintenance strategy to search in and copy from on the Hub: 1. Search from the client system.

56

●

The requestor searches customers from the client system.

●

The results include entries from the client and Hub.


Lesson: Processing Customer Master Data on a Client System

2. Copy from the Hub to the client system. The requestor copies an entry from the Hub to the client. Use the copy function to add a customer role to the business partner in case there is no customer role assigned in MDG Hub. The copy function uses the synchronous MDG search service BusinessPartnerBasicDataByElementsQueryResponse. A valid SOA manager configuration is required to call the service proxy. You can also use an RFC enabled wrapper function module instead of the service proxy. The function module requires an RFC connection to the MDG Hub in the table MDG_BS_BP_SRCCHN. The following copy function uses operating class CL_MDG_BS_ECC_CUST_INBOUND: 1. The system finds business partner data on the MDG Hub using the RFC enabled function module MDG_BS_BP_DRF_EXTRACT_READ. 2. The requestor uses the MDG business partner replicate service inbound interface to create the business process and customer on the client. MDG Business Partner Search Service

Figure 22: MDG Business Partner Search Service

The synchronous SOA search service interface is named BusinessPartnerBasicDataByElementsQueryResponse. The service consumer is available in software component SAP_BS_FND 731. You can search for specific criteria such as name, address data, roles, identification numbers, relationships, and contact person. The search mode is configurable customizing view V_USMD_PDCHK_MOD and supports database, address, and enterprise searches. There are two methods of completing service calls in the client system. You can call a consumer proxy, which requires SOA manager configuration in the MDG client and Hub. You can also call RFC enabled wrapper function module MDG_BS_BP_SEARCH in the MDG Hub, which requires an RFC connection to the MDG Hub. Client Maintenance in SAP ERP Technical Details


57


The following technical details affect MDG client maintenance: ●

●

●

As a precondition, configure customer/vendor integration (CVI) to ensure that business partners are maintained for customers in the background. Function module MDG_BS_ECC_BP_OUTBOUND triggers distribution to MDG. Activate this function module in table CRMC_BUT_CALL_FU, Function Modules for BP Data Exchange. This activation is completed using switch BC-set assigned to the business function MDG_CUST_ERPCLIENT_1. Function module MDG_BS_ECC_BP_OUTBOUND calls MDG Business Partner Outbound Service Interface CL_MDG_BP_BUPA_SI_OUT.

MDGC Client Scenario Key Mapping In the following scenario, you start with a business partner ID on the MDG Hub. This business partner not only has an externally readable business partner number but a universally unique identifier (UUID). When the business partner is copied from the hub to the remote client, the client creates a new business partner number, but uses the same UUID. When adding the customer role to the business partner on the client, a new customer number is created on the client. The new customer number triggers a change request on the hub that enhances the hub business partner with customer data using the same UUID.You can use the key mapping function to view mappings between object instances through the connection of their object IDs. In business processes with several systems, each object instance requires one or more object IDs to ensure it can be identified and mapped to other object instances. During data replication, the object instance is replicated from a central system to one or more target systems. During the process, each system can use its own logic to create object IDs. The Web Dynpro application (MDG_BS_WD_ANALYSE_IDM) is used to search for examples of key mapping between the ID values of object instances. One of these object instances is the business partner UUID. The UUID is a 128-bit number generated according to an algorithm that is guaranteed to be unique in time and space from all other UUIDs. It consists of an IEEE 802 Internet Address and various time stamps to ensure uniqueness.

How to Process Customer Master Data on a Client System For the demonstration steps and data, see the exercise Process Customer Master Data on a Client System.

58



Process Customer Master Data on a Client System

Business Example Your company is in the CD manufacturing business and is beginning to create Business Partners with corresponding SAP ERP customers. Your company wants to know if the MDG Hub will reflect the new Business Partner information when the data is replicated to another system and subsequently changed in that system. You have been asked to investigate how MDG works in a Hub and Client scenario. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. Create a Business Partner 1. In the Customer Workcenter, create a new organization using the data from the following table and note the business partner ID. Field

Value

Change Request ID

Description

Create BP with Address Only ##

Due Date


Title

Company

Name 1

BP Solo ##

Search Terms (field 1)

MDG


IRO

Street/House Number

●

Main Street

●

123##

●

987##

●

Berlin

Postal Code/City

Country

DE

Language

DE


59


Note the Business Partner ID.

2. View the business partner record. Search for a Client Remotely 1. Log off of SAP ERP client 800 and log on to SAP ERP client 900. 2. Search for the customer MDG. 3. Copy the HUB-only customer from the MDG hub to the client and note the Customer ID. Note the internal ID.

Note the Customer ID.

4. Log off of SAP ERP client 900 and log on to SAP ERP client 800.

60



Process Customer Master Data on a Client System

Business Example Your company is in the CD manufacturing business and is beginning to create Business Partners with corresponding SAP ERP customers. Your company wants to know if the MDG Hub will reflect the new Business Partner information when the data is replicated to another system and subsequently changed in that system. You have been asked to investigate how MDG works in a Hub and Client scenario. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. Create a Business Partner 1. In the Customer Workcenter, create a new organization using the data from the following table and note the business partner ID. Field

Value

Change Request ID

Description

Create BP with Address Only ##

Due Date


Title

Company

Name 1

BP Solo ##


MDG


IRO

Street/House Number

●

Main Street

●

123##

●

987##

●

Berlin

Postal Code/City

Country

DE

Language

DE


61


Note the Business Partner ID. Answers will vary.

a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Customer Governance. e) In the navigation panel, choose Change Requests → Customer Maintenance → Search Customer. f) On the Search Customer screen, in the Search Results section, choose New → Organization. g) On the Organization: $ screen, enter the data from the table. h) Choose Check. i) Choose Submit. j) Choose Refresh until the Approve and Reject buttons appear. k) Choose Approve. l) Choose Refresh until your system generated business partner ID appears. m) In the Customer Details section, note your Business Partner ID number. n) Choose Close. o) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. 2. View the business partner record. a) On the SAP Easy Access - User Menu screen, in the Command field, enter BP. b) Choose Enter. c) On the Maintain Business Partner screen, in the Business Partner field, enter your business partner ID number. d) Choose Enter. e) Choose Back until you return to the SAP Easy Access - User Menu screen. Search for a Client Remotely 1. Log off of SAP ERP client 800 and log on to SAP ERP client 900. a) Log off of SAP ERP client 800. b) Log on to SAP ERP client 900 with the credentials provided by your instructor. 2. Search for the customer MDG.

62


Lesson: Processing Customer Master Data on a Client System

a) On the SAP Easy Access - User Menu screen, in the Command field, enter XD03. b) Choose Enter. c) In the Customer Display: Initial Screen dialog box, choose the Customer field dropdown button. d) On the Customer Account Number dialog box, select the Customers in MDG hub by Address Attributes tab. e) In the Search Term 1 field, enter MDG. f) Choose Enter. 3. Copy the HUB-only customer from the MDG hub to the client and note the Customer ID. Note the internal ID. Answers will vary. Note the Customer ID. Answers will vary. a) In the results table, in the Name 1/last name column, choose BP Solo ##. b) Choose Copy Customer. c) In the Customer Role Selection dialog box, choose FLCU01 Customer. d) Choose Enter. e) In the Messages dialog box, note the internal ID and customer number associated with your business partner ID from the hub. f) Choose Enter. g) On the Customer Display: Initial Screen dialog box, choose Continue. h) On the Customer Display: General Data screen, note the address information. i) Choose Back to return to the Customer Display: Initial Screen dialog box. j) On the Customer Display: Initial Screen dialog box, choose Cancel to return to the SAP Easy Access screen. 4. Log off of SAP ERP client 900 and log on to SAP ERP client 800. a) Log off of SAP ERP client 900. b) Log on to SAP ERP client 800 with the credentials provided by your instructor


63



64



Unit 2

63

Learning Assessment

1. When does the MDG maintenance process start? Choose the correct answers. X

A It starts at regularly scheduled intervals.

X

B It starts each time the system is launched.

X

C It starts when a user requests new master data.

X

D It starts when the system administrator manually initiates it.

2. How are activities associated with creating and maintaining master data combined in a work center? Choose the correct answers. X

A There is one work center for all domains.

X

B There is one work center for each domain.

X

C There are multiple work centers for each domain.

X

D Every company customizes their own unique work centers.

3. The change request workflow template can be configured with parallel approval steps. Determine whether this statement is true or false. X

True

X

False

4. When does a parallel process end? Choose the correct answer. X

A The process ends when the first step is approved.

X

B The process ends when all approval steps are approved.

X

C The process ends when the assigned user manually ends the process.

X

D The process never ends.


65


5. In the MDG Hub and client maintenance for customers, what is the copy function used for? Choose the correct answers.

66

X

A The copy function is used to add a business partner to a customer role.

X

B The copy function is used to add a business partner to the MDG hub.

X

C The copy function is used to add a customer role to the business partner.

X

D The copy function is used to add a customer role to the MDG hub.


Unit 2

65


1. When does the MDG maintenance process start? Choose the correct answers. X

A It starts at regularly scheduled intervals.

X

B It starts each time the system is launched.

X

C It starts when a user requests new master data.

X

D It starts when the system administrator manually initiates it.

2. How are activities associated with creating and maintaining master data combined in a work center? Choose the correct answers. X

A There is one work center for all domains.

X

B There is one work center for each domain.

X

C There are multiple work centers for each domain.

X

D Every company customizes their own unique work centers.

3. The change request workflow template can be configured with parallel approval steps. Determine whether this statement is true or false. X

True

X

False


67


4. When does a parallel process end? Choose the correct answer. X

A The process ends when the first step is approved.

X

B The process ends when all approval steps are approved.

X

C The process ends when the assigned user manually ends the process.

X

D The process never ends.

5. In the MDG Hub and client maintenance for customers, what is the copy function used for? Choose the correct answers.

68

X

A The copy function is used to add a business partner to a customer role.

X

B The copy function is used to add a business partner to the MDG hub.

X

C The copy function is used to add a customer role to the business partner.

X

D The copy function is used to add a customer role to the MDG hub.


UNIT 3

Multiple Object Processing

Lesson 1 Processing Multiple Objects in a Single Change Request Exercise 6: Assign New Cost Center Change Requests to an Edition

70 79

Lesson 2 Executing Mass Changes Exercise 7: Execute a Mass Change Exercise 8: Update a Mass Change

85 89 95

Lesson 3 Executing Data File Transfers with Multiple Objects Exercise 9: Upload Material Records to Master Data Governance

99 101

Lesson 4 Processing Master Data Hierarchy Records Exercise 10: Process Supplier Hierarchy Records

108 111

UNIT OBJECTIVES ●

Process multiple objects in a single change request

●

Schedule changes using editions

●

Process multiple objects

●

Execute mass changes

●

Execute data file transfers with multiple objects

●

Process master data hierarchy records


69

Unit 3 Lesson 1 68

Processing Multiple Objects in a Single Change Request

LESSON OVERVIEW In this lesson, you will learn how to process multiple objects in a single change request, schedule changes using editions, and process multiple objects. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


●


●


Different Types of Change Requests

Figure 23: Categories of Change Request Types

There are three categories of change requests in Financials: ●

Single object change requests that use a special workflow

●

Multiple object change requests that include multiple object types

●

Form-based change requests used only for single-object maintenance

Characteristics of Change Request Types In Financials, the change request type is a central element of the Master Data Governance process. Change request types are linked to edition types and are a single-object type. The entity types used in a change request type depend on the contents of the edition. If a form-

70


Lesson: Processing Multiple Objects in a Single Change Request

based template is used as an entity type, assign the template in the change request type for each entity type. Each entity type can have its own template. SAP delivers several change request types with predefined, form-based templates.

Editions with Assigned Object Changes

Figure 24: Editions with Assigned Object Changes

Change requests describe the business rationale for changing master data and control the approval and change process. For master data that is maintained through the use of editions, first create an edition, then assign each change request to the specific edition. Multiple change requests can be assigned to a single edition. When all change requests for an edition are approved or withdrawn, the edition as a whole can be released and no further change requests can be created. Data replication to local systems can be triggered either by the approval of a single change request or the entire edition.


71

Unit 3: Multiple Object Processing

Characteristics of Editions

Figure 25: Characteristics of Editions

An edition can be described as a container that stores the master data in change requests for a specified period of time. Editions are distributed using the Distribution Monitor, which propagates the master data to their target systems. Assign the change requests to an edition. Edition Type Rules

Figure 26: Edition Type Rules

An edition type restricts the list of entity types for which master data may be requested. An edition type can include some or all of the entity types in the data model, but must contain at least one entity type.

Edition Elements and Options The following edition elements and options are available:

72



●

Technical edition name

●

Description

●

Edition type

●

Validity dates

●

Comments

●

Immediate Distribute Change Requests

If you use the Immediately Distribute Change Requests option, the change requests are distributed automatically upon their final approval. This option eliminates the need to release and distribute the edition.

Edition Distribution Monitor

Figure 27: Edition Distribution Monitor

Before you can replicate data, set the appropriate options during the customizing process. You can control the replication process from the Distribution Monitor. The Distribution Monitor lets you replicate previously released editions.

How to Schedule Changes using Editions Your company is in the CD manufacturing business and wants to open up a new sales office in the beautiful city of Montreal, Canada by the middle of next month. You know that you need at least one cost center ready so that all expenses can be booked correctly. 1. Create an edition using the data in the following table. Field

Value

Edition

CC_Mon_##


73


Field

Value

Description

New Cost Montreal Cost Center

Type

Cost Center in Data Model 0G

Valid From (Period/Year)

The 15th of next month

a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Financials Master Data Governance. e) In the navigation panel, choose Editions → Create Editions. f) On the Create Edition screen, enter the data from the table. g) Choose Save. h) Choose Close. 2. Create a new change request and change the standard data model to 0G. a) In the navigation panel, choose Change Request → Create Change Request. b) On the Create Change Request: Step 1 (General Data) screen, choose Change Model. c) On the Change Model screen, in the Standard Data Model drop-down menu, choose 0G. d) Choose Save and Apply. 3. Enter the data for the new change request using the data in the following table.

74

Screen Name

Field

Value

Create Change Request: Step 1 (General Data)

Description

New Montreal Sales Office ##


Type

Cost Center - Single Processing


Edition

CC_Mon_##


CO Area

2000


Cost Center

3000##

Create Change Request: Step 2 (Reason for Change)

Explanation

New Sales Cost Center for Montreal

Create Change Request: Step 3 (Changes)

Cost Center Category

3



Screen Name

Field

Value


Company Code

4000


Business Area

BA##


Functional Area

1000


Responsible Person

MDG100-##


Description (short)

Montreal Sales Office ##

a) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table. b) Choose Next. c) On the Create Change Request: Step 2 (Reason for Change) screen, enter the data from the table. d) Choose Next. e) On the Create Change Request: Step 3 (Changes) screen, enter the data from the table. f) Choose Next. g) In the Warning in Consistency Check dialog box, choose Save. h) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit. i) Choose Close. 4. Approve the change request. a) In the navigation panel, choose Change Requests → My Change Requests. b) On the My Change Requests screen, choose New Montreal Sales Office ##. c) Choose Finalize Processing. d) Choose Close to return to the My Change Requests screen. e) On the My Change Requests screen, choose Refresh. f) Choose New Montreal Sales Office ##. g) Choose Approve. h) In the Confirmation Prompt dialog box, choose Yes. i) Choose Close to return to the My Change Requests screen. j) On the My Change Requests screen, choose Refresh. k) Choose Close.


75


Types of Change Requests for Financials

Figure 28: Categories of Financial Change Requests

The change request type is a central element of the Financials process. Change request types are linked to edition types, which means that the entity types that can be used in the change request type depend on the contents of the edition type. Each entity type can have its own template. If a form-based template is used, it is required that you assign the template for each entity type. Several single-object change request types with predefined form-based templates are available. The following three change request types are available: ●

Single-object—uses a special workflow template

●

Multiple-object—includes multiple object types

●

Form-based—uses predefined templates solely for single-object maintenance

One-Step and Two-Step Object Change Request Types for Financials Single Object Change Request Type and Two-Step Change Request Type ●

●

Single object change request type -

In the configuration settings, check Single Object.

-

Use with simple workflow template WS75700040.

-

In the UI, create change requests and maintain changes to be made.

Two-step change request type -

In the configuration settings, check Objects Required.

-

Use with advanced workflow template WS75700027.

-

In the UI, create change requests, specified objects (entity type to be changed), and maintain changes to be made.

Both simple and advanced workflow templates can contain a single object or multiple objects. The change request process consists of the following steps:

76



1. Specify the object or objects within a workflow that must change. 2. Execute the changes on an individual object level or on the overall change request level. You can select the Single Object checkbox for either workflow type, but usually only applies to the simple workflow templates. This option requires only a single step because the simple workflow already contains approval for the changes to the objects within it. If you select the Objects Required checkbox, the change request requires two steps because you will have to specify the individual objects in the change request before the changes can be made. Use the workflow template for advanced workflow templates for this type of change request.

How to Maintain Account Detail for Cost Center Change Request For the demonstration steps and data, see the exercise Assign New Cost Center Change Requests to an Edition.

How to Release an Edition In this demonstration, when values include ##, replace the characters with your group number. 1. Verify the change request CC_MON_## is available in the edition. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Financial Master Data Governance. e) In the navigation panel, choose Editions. f) On the Editions screen, on the All tab, in the results table, select CC_MON_##. g) Choose Run Validation. h) Choose Validation Log. i) On the All tab, choose Change Status → Mark for Release. j) Choose Change Status → Release.

How to Distribute a Change Request for Financials In this demonstration, when values include ##, replace the characters with your group number. 1. Distribute the released edition.


77


a) In the Financials Master Data Governance Workcenter, in the navigation panel, choose Distribution Monitor. b) On the All tab, choose CC_MON_## → Cost Center 3000##. c) Choose Replicate. d) Choose Refresh. 2. Verify the 3000## cost center is active. a) In the Financials Master Data Governance Workcenter, in the navigation panel, choose Change Requests → Entity Search. b) On the Search for Entities screen, in the Entity Type drop-down menu, choose Cost Center. c) In the Search Criteria table, choose Edition as the search attribute and CC_MON_## as the search value. d) Choose Search. e) In the search results table, find Cost Center 3000##. f) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.

78



Assign New Cost Center Change Requests to an Edition

Business Example Your company wants to open up a new sales office in the beautiful city of Montreal sometime in the next two months. You have been asked to have at least one cost center ready when the new office opens so that all expenses can be recorded correctly. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Create a Change Request for the New Cost Center 1. Create a new change request using the data in the following table. Screen Name

Field

Value


Description

New Sales Office, Montreal ##


Type



Edition

CC _MON_##


CO Area

2000


Cost Center

3000##


Explanation

This change request is for the new sales office in Montreal.


Department

Montreal



3


Company Code

4000


Business Area

BA##


Functional Area

1000


79


Screen Name

Field

Value


Currency

CAD


Person Responsible

MDG100-##


Language

French

Process the Change Request for the New Cost Center 1. Locate your cost center change request New Sales Office, Montreal ##. 2. Finalize and approve the change request New Sales Office, Montreal ##.

80



Assign New Cost Center Change Requests to an Edition

Business Example Your company wants to open up a new sales office in the beautiful city of Montreal sometime in the next two months. You have been asked to have at least one cost center ready when the new office opens so that all expenses can be recorded correctly. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Create a Change Request for the New Cost Center 1. Create a new change request using the data in the following table. Screen Name

Field

Value


Description

New Sales Office, Montreal ##


Type



Edition

CC _MON_##


CO Area

2000


Cost Center

3000##


Explanation

This change request is for the new sales office in Montreal.


Department

Montreal



3


Company Code

4000


Business Area

BA##


Functional Area

1000


81


Screen Name

Field

Value


Currency

CAD


Person Responsible

MDG100-##


Language

French

a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Financial Master Data Governance. e) In the navigation panel, choose Change Requests → Create Change Request. f) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table. g) Choose Next. h) On the Create Change Request: Step 2 (Reason for Change) screen, enter the data from the table. i) Choose Next. j) On the Create Change Request: Step 3 (Changes) screen, enter the data from the table. k) Select the Translation tab. l) Choose Add Row. m) In the Description table, enter the data from the table. n) On the Translation tab, complete the English row using the data from the table. o) Choose Next. p) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit. Process the Change Request for the New Cost Center 1. Locate your cost center change request New Sales Office, Montreal ##. a) In the Workcenter toolbar, choose Financial Master Data Governance. b) In the navigation panel, choose Change Requests → My Change Requests. c) On the My Change Requests screen, in the Change Requests table, choose New Sales Office, Montreal ##. 2. Finalize and approve the change request New Sales Office, Montreal ##. a) On the Process Change Request screen, choose Finalize Processing.

82



b) On the Process Change Request screen, choose Close. c) On the My Change Request screen, choose Refresh. d) Choose New Sales Office, Montreal ##.


83



84

●


●


●



Unit 3 Lesson 2 81

Executing Mass Changes

LESSON OVERVIEW In this lesson, you will learn how to execute mass changes. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Multi-Object Processing Capabilities

Figure 29: Multi-Object Processing Capabilities

Typically change requests apply to a single master data object. Besides just search, display, and maintenance of single instances of workcenter records, you can also process mass changes involving many workcenter records. In Master Data Governance for Financials, mass processing can be used for the following operations: ●

Processing multiple selected objects of the same entity type in one step

●

Applying the same changes to the selected objects during one transaction

●

Performing multiple transactions and selections using the same change request

●

Working on the same change request using multiple processors

Before you start a mass process, ensure that an open change request of the appropriate request type exists and that you are a valid processor of that change request.


85


Hierarchy processing is another type of multiobject processing that falls under the category of multiple processing. Multiple processing allows you to perform multiple activities, including single changes on one or multiple entity types, during one transaction

Mass Change Process

Figure 30: Mass Change Process

The mass change service allows you to replace the selected workcenter records and their selected content with a new value in each field for all selected workcenter records. Updating multiple workcenter records is a two-step process. First you create a change request for multiple workcenter records, then you use the Mass Change service to enter the details for the changes you want to make. To update multiple workcenter records, complete the following steps: 1. Create a mass change request. 2. Select the entities to be altered by the mass change. 3. Replace or initialize values for the fields with one dedicated value. 4. Review the results and execute the change. 5. Assign the mass change request.

Mass Change Updates In Financials, if you want to synchronize multiple changes, you can group them into editions. Editions allow you to group all changes together and then activate all approved change requests for that edition simultaneously. For both customers and suppliers, MDG supports search, display, change, and creation of single master data sets as well as mass processing or changes to hierarchies. All changes are kept in the central system's staging area until approval. Then they can be distributed to operational systems by using either SAP Enterprise Services or the file upload

86


Lesson: Executing Mass Changes

and download features. You can also trigger mass changes from within hierarchy processing, which allows you to download the links between the hierarchy nodes.

How to Execute a Mass Change For the demonstration steps and data, see the exercise Execute a Mass Change.

How to Update a Mass Change For the demonstration steps and data, see the exercise Update a Mass Change.


87


88



Execute a Mass Change

Business Example Your company wants to broaden their product line to include custom CD labels. A new lab named Lab G## has been built and is ready to begin quality control of the new custom CD labels. Assign the production of the new custom CD labels to Lab G##. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Create a New Material Change Request 1. Create a mass material change request using the data in the following table and note the change request number. Screen Name

Field

Value


Description

Mass Change at Lab##


Due Date


Create Change Request: Step 2 (Reason for Changes)

Explanation

Lab## is ready to begin producing custom CD labels.

Note the change request number.

Start a Mass Change 1. Select materials for mass change using the data in the following table. Dialog Box

Field

Value

Mass Change Material: Step Material 1 (Define Selection)

ACT*##

Mass Change Material: Step Description (medium text) 1 (Define Selection)

Label*


89


Dialog Box

Field

Mass Change Material: Step Scope of Selection 2 (Refine Selection)

Mass Change Material: Step Lab/Office 3 (Define Values)

Value ●

ACT-BCD-##

●

ACD-LCD-##

●

ACT-MCD-##

Lab Group ##

2. Approve the mass change request.

90



Execute a Mass Change

Business Example Your company wants to broaden their product line to include custom CD labels. A new lab named Lab G## has been built and is ready to begin quality control of the new custom CD labels. Assign the production of the new custom CD labels to Lab G##. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Create a New Material Change Request 1. Create a mass material change request using the data in the following table and note the change request number. Screen Name

Field

Value


Description

Mass Change at Lab##


Due Date



Explanation

Lab## is ready to begin producing custom CD labels.

Note the change request number. Answers will vary. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) In the navigation panel, choose Change Requests → Processing of Multiple Materials → Create Change Request. f) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table. g) Choose Next.


91


h) On the Create Change Request: Step 2 (Reason for Changes) screen, enter the data from the table. i) Choose Next. j) On the Create Change Request: Step 3 (Changes) screen, choose Next. k) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit. l) Note the change request number. Start a Mass Change 1. Select materials for mass change using the data in the following table. Dialog Box

Field

Value

Mass Change Material: Step Material 1 (Define Selection)

ACT*##

Mass Change Material: Step Description (medium text) 1 (Define Selection)

Label*

Mass Change Material: Step Scope of Selection 2 (Refine Selection)

Mass Change Material: Step Lab/Office 3 (Define Values)

●

ACT-BCD-##

●

ACD-LCD-##

●

ACT-MCD-##

Lab Group ##

a) In the navigation panel, choose Change Requests → Processing of Multiple Materials → Mass Change. b) On the Mass Change Material: Step 1 (Define Selection) screen, enter the data from the table. c) Choose Next. d) On the Mass Change Material: Step 2 (Refine Selection) screen, in the Scope of Selection table, select the materials from the table. e) Choose Next. f) On the Mass Change Material: Step 3 (Define Values) screen, in the Changeable Attributes table, enter the data from the table. g) Choose Next. h) On the Mass Change Material: Step 4 (Check and Execute) screen, choose Execute Changes. i) In the Select Change Request dialog box, in the Change Request drop-down menu, choose Mass Change at Lab ##. j) Choose Enter. 2. Approve the mass change request.

92



a) In the navigation panel, choose Change Requests → Change Requests and Documents → My Change Requests. b) Select the change request ID from the previous task. c) Choose Activate. d) Choose Back until you return to the SAP Easy Access - User Menu screen.


93


94



Update a Mass Change

Business Example Your company has always had a hard time keeping material keys consistent and synchronized at your various facilities. As business administrator you try to maintain Excel files on your computer with all the different material keys used at each facility, but it is a difficult, inefficient method. To synchronize and maintain your material keys company-wide, your company is implementing Master Data Governance. Your job is to move the company's material keys to Master Data Governance. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Search for Key Mappings 1. Search for a key mapping using the data in the following table. Field

Value

Object Type

Material

Object Identifier

Material ID (external format/ERP)

Business System

R3_800

ID Value

ACT-BCD-##

Create a New Key Mapping 1. Create a key mapping material object using data in the following table. Field

Value

Business Object Type

Material

Business System

R3_800

System ID

BI_900

Object ID Type/Object ID

●


●

ACT-BCD-##

Replicate your Key Mapping Objects 1. Replicate the key mapping object named ACT-BCD-##. 2. Verify that an IDoc number was generated.


95


Update a Mass Change

Business Example Your company has always had a hard time keeping material keys consistent and synchronized at your various facilities. As business administrator you try to maintain Excel files on your computer with all the different material keys used at each facility, but it is a difficult, inefficient method. To synchronize and maintain your material keys company-wide, your company is implementing Master Data Governance. Your job is to move the company's material keys to Master Data Governance. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Search for Key Mappings 1. Search for a key mapping using the data in the following table. Field

Value

Object Type

Material

Object Identifier


Business System

R3_800

ID Value

ACT-BCD-##

a) On the Workcenter toolbar, choose Material Governance. b) In the navigation panel, choose Data Exchange → Data Replication → Replicate by Replication Model. c) On the Search Key Mapping screen, enter the data from the table. d) Choose Search Objects. e) In the search results, view the data. Create a New Key Mapping 1. Create a key mapping material object using data in the following table.

96

Field

Value

Business Object Type

Material

Business System

R3_800

System ID

BI_900



Field

Value

Object ID Type/Object ID

●


●

ACT-BCD-##

a) In the navigation panel, choose Data Exchange → Data Replication → Create and Edit Key Mapping. b) On the Key Mapping Material: ACT-BCD-## screen, complete the Object Selection fields using data from the table. c) Choose Show. d) On the Key Mapping Material: ACT-BCD-## screen, choose Add Row. e) In the Mapped Object table, in row 2, enter the data from the table. f) Choose Save. Replicate your Key Mapping Objects 1. Replicate the key mapping object named ACT-BCD-##. a) On the Workcenter toolbar, choose Material Governance. b) In the navigation panel, choose Data Exchange → Data Replication → Replicate by Material Selection c) On the Replication by Object Selection screen, in the Business Object Type drop down menu, choose Material. d) In the Business Objects to be Replicated table, enter ACT-BCD-##. e) Select the Test Run Only checkbox. f) In the Target System Selection table, select BI_900. g) On the Replication by Object Select screen, choose Replication. 2. Verify that an IDoc number was generated. a) In the Replication Log by Object Selection screen, choose Display Log. b) On the Replication Log for Manual Replication screen, in the Replication Log table, choose the entry with your user ID. c) In the Replication Log Messages table, view the data. d) Choose Close. e) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.


97



98



Unit 3 Lesson 3 95

Executing Data File Transfers with Multiple Objects

LESSON OVERVIEW In this lesson, you will learn how to execute data file transfers with multiple objects. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Data File Transfer Execution

Figure 31: Data Transfer Related Components

File upload and download components can be used to transfer multiple objects to and from the MDG system. Unlike XML-based components, file upload and download components offer comma separated value (CSV) transfers of data entities to the staging area for load scenarios. File upload and download components support the processing of multiple objects for all data models including custom objects. These components cover initial load scenarios for financials and custom objects.


99


Master data objects can span several entities, which are often uploaded separately. The system does not cover dependencies, which limits the use case for complex business objects such as Business Partner, Vendor, Customer, and Material. The file download web user interface is USMD_FILE_DOWNLOAD, and the file upload web user interface is USMD_FILE_UPLOAD.

Data File Download

Figure 32: Data Export and Import

File download is available for all data models and supports one entity at a time. You select criteria to define which data the system includes in the file being created. System hierarchy support allows you to download the links between the hierarchy nodes. Variants define the file structure, which is configured once and can be used later for both downloads and uploads.

Data File Upload The system lists the change requests that are assigned to the user and checks to see if the object already exists in a change request. The system rejects the upload when it is not assigned to the user. The report USMD_DATA_TRANSFER_BACKEND can be executed in the background. The report system selects a change request for each file and assigns the change request to the user of the report.

How to Upload Material Records to Master Data Governance For the demonstration steps and data, see the exercise Upload Material Records to Master Data Governance.

100



Upload Material Records to Master Data Governance

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. You have realized that some of the basic data attributes for existing master data records are not aligned. You have requested a file download of the records that are affected. Once the relevant attributes have been aligned you would like to import the changes directly from a file into MDG rather than create a single change request for every record requiring a change. The following exercise will show you the export and import functionality related to this scenario. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Download and save the file ACT-*## using the data in the following table. Screen Name

Field

Value

File Download: Step 1 (Determine Entity Type)

Entity Type

Material

File Download: Step 1 (Determine Entity Type

Type of Transfer

Attributes

File Download: Step 2 (Define Selection)

Material

ACT-*##

File Download: Step 3 (Define File Structure)

Selected

Add the following Entity Type/Attributes to Data Row: Industry Sector, Material Type, Material, Description (medium text), and Base Unit of Measure.

2. View the file_download.txt file on your local computer and add the letter "A" after the group number. 3. In the SAP Business Client, create a new change request and note the change request number using the data in the following table. Screen Name

Field

Value


Description

Upload Materials ##


Explanation

Upload Materials ##


101


Screen Name

Field

Value


Objects to be Changed table Material

4. Upload the file_download.txt file using the data in the following table. Screen Name

Field

Value

File Upload: Step 1 (Determine Entity Type)

Entity Type

Material

File Upload: Step 3 (Define File Structure)

Selected

Add the following Entity Type/Attributes to Data Row: Industry Sector, Material Type, Material, Description (medium text), and Base Unit of Measure

5. Activate the upload data change request. 6. View the uploaded change request.

102



Upload Material Records to Master Data Governance

Business Example Your company is in the CD manufacturing business and has enhanced an existing product line. You have realized that some of the basic data attributes for existing master data records are not aligned. You have requested a file download of the records that are affected. Once the relevant attributes have been aligned you would like to import the changes directly from a file into MDG rather than create a single change request for every record requiring a change. The following exercise will show you the export and import functionality related to this scenario. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Download and save the file ACT-*## using the data in the following table. Screen Name

Field

Value

File Download: Step 1 (Determine Entity Type)

Entity Type

Material

File Download: Step 1 (Determine Entity Type

Type of Transfer

Attributes

File Download: Step 2 (Define Selection)

Material

ACT-*##

File Download: Step 3 (Define File Structure)

Selected

Add the following Entity Type/Attributes to Data Row: Industry Sector, Material Type, Material, Description (medium text), and Base Unit of Measure.

a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) In the navigation panel, choose Change Requests → Processing of Multiple Materials → File Download. f) Choose Change Model.


103


g) On the Change Model screen, in the Standard Data Model drop-down menu, choose MM. h) Choose Save. i) On the File Download: Step 1 (Determine Entity Type) screen, enter the data from the table. j) Choose Next. k) On the File Download: Step 2 (Define Selection) screen, enter the data from the table. l) Choose Next. m) On the File Download: Step 3 (Define File Structure) screen, in the Selected list, select Data Row. n) In the Available list, select the appropriate Entity Type/Attribute listed in the table, and choose Add. o) When all Entity Types/Attributes are added, choose Next. p) On the File Download: Step 4 (Determine Download Settings) screen, choose Next. q) Choose Next. r) On the File Download: Step 5 (Check and Execute) screen, choose Execute Download. s) On the File Download screen, choose Save File. t) Save the file to the Library → Documents folder using the default name. 2. View the file_download.txt file on your local computer and add the letter "A" after the group number. a) In the Windows Start menu, choose Documents. b) In the Windows Explorer, open file_download.txt. c) In the file_download file, in the Material EQ line, add the letter A after the group number. For example, the file name should look like this example: ACT-BCD-##A. d) Choose File → Save. e) Close the file. f) Close Windows Explorer. 3. In the SAP Business Client, create a new change request and note the change request number using the data in the following table.

104

Screen Name

Field

Value


Description

Upload Materials ##


Explanation

Upload Materials ##


Lesson: Executing Data File Transfers with Multiple Objects

Screen Name

Field

Value


Objects to be Changed table Material

a) On the SAP Business Client screen, in the navigation panel, choose Change Requests → Processing of Multiple Materials → Create Change Request. b) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table. c) Choose Next. d) On the Create Change Request: Step 2 (Reason for Changes) screen, enter the data from the table. e) Choose Next. f) On the Create Change Request: Step 3 (Changes) screen, enter the data from the table. g) Choose Next. h) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit. i) Note the change request number. Note: Do not choose Close because it exits the application. 4. Upload the file_download.txt file using the data in the following table. Screen Name

Field

Value

File Upload: Step 1 (Determine Entity Type)

Entity Type

Material

File Upload: Step 3 (Define File Structure)

Selected

Add the following Entity Type/Attributes to Data Row: Industry Sector, Material Type, Material, Description (medium text), and Base Unit of Measure

a) In the navigation panel, choose Change Requests → Processing of Multiple Materials → File Upload. b) On the File Upload: Step 1 (Determine Entity Type) screen, enter the data from the table. c) Choose Next. d) On the File Upload: Step 2 (Define File Structure) screen, in the Selected list, select Data Row.


105


e) In the Available list, select the appropriate Entity Type/Attribute listed in the table, and choose Add. f) When all Entity Types/Attributes are added, choose Next. g) On the File Upload: Step 3 (Determine Upload Settings) screen, next to the File Name field, choose Load File. h) In the Load File dialog box, choose Browse. i) In the Documents folder, select the file_download.txt file and choose Open. j) In the Load File dialog box, choose Enter. k) Choose Next. l) In the Select Change Request dialog box, select your change request. m) Choose Enter. n) On the File Upload: Step 4 (Check and Execute) screen, choose Execute Upload. 5. Activate the upload data change request. a) In the navigation panel, choose Change Requests → Change Requests and Documents → My Change Requests. b) In the My Change Requests table, choose the change request number for Upload Material. c) On the Activate Change Request screen, choose Run Validation. d) When the message displays stating that the validation for the change request has started, choose Check. e) When the no errors found message displays, choose Activate. f) Close the Activate Change Request tab. 6. View the uploaded change request. a) In the navigation panel, choose Change Request → Material Processing → Search Material. b) In the Search Criteria section, in the Material row, in the third field, enter ACT-BCD##A. c) Choose Search. d) In the Search Result table, choose the material ID for ACT-BCD-##A. e) Choose Close to close the internet browser window, and return to the SAP Easy Access - User Menu screen.

106


Lesson: Executing Data File Transfers with Multiple Objects




107

Unit 3 Lesson 4 104

Processing Master Data Hierarchy Records

LESSON OVERVIEW In this lesson, you will learn how to process master data hierarchy records. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Master Data Hierarchy Record Processing

Figure 33: Hierarchy Record Processing

Hierarchies in MDG are independent objects that you maintain using single object change requests. To maintain a hierarchy, associate entities in a structured way through predefined relationships. You define the relationships between entities in the data model. You stage and activate hierarchies in MDG-generated tables. Develop replication models to replicate hierarchies — or parts of hierarchies — in the business application tables. The replication models determine the relevant hierarchy information and pass it on to the application layer.

108


Lesson: Processing Master Data Hierarchy Records

Mass Change of a Hierarchy Structure MDG includes hierarchy processing capabilities. Hierarchy processing lets you process multiple objects in a single transaction. Before assigning objects to a hierarchy using hierarchy processing, maintain the structure of the hierarchy using the regular change request processes. Hierarchy structures are separate entity types. The following options are available during hierarchy maintenance: ●

Open the hierarchy to selected levels or to all levels.

●

Assign, move, copy, and delete object assignments to hierarchy nodes.

●

Start single change processing of the assigned objects.

The following additional functions are available for financial hierarchies: ●

Search for unassigned objects.

●

Perform a consistency check.

How to Process Supplier Hierarchy Records For the demonstration steps and data, see the exercise Process Financial Reporting Structure Hierarchy Records.


109


110



Process Supplier Hierarchy Records

Business Example Your company has decided that the supplier master data from an acquired SAP ERP system should be enhanced with a hierarchy based on the supplier's location by country or region. You have been asked to create the new hierarchies within the governance framework and have the hierarchies approved before they are deployed. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Create a hierarchy change request using the data in the following table and note the change request number. Screen Name

Field

Value


Description

Supplier Country Hierarchy ##


Due Date



Explanation

New Supplier Country Hierarchy ##


Objects to be Changed

Business Partner ID


2. Create a new hierarchy using the data in the following table. Field

Value

BPartner Hierarchy

SUP_COUNTRY_##

Description

Supplier by Countries ##

3. Create a structure node using the data in the following table. Field

Value

Structure Node

EMEA


111


Field

Value

Description

European Countries

4. Create a second node structure using the data in the following table. Field

Value

Structure Node

AMA

Description

American Countries

5. Create a structure node for AMA using the data in the following table. Field

Value

Structure Node

NA

Description

North America

6. Create a second structure node for AMA using the data in the following table. Field

Value

Structure Node

LA

Description

Latin America

7. Assign Supplier ID DE004600 to the hierarchy using the data in the following table. Field

Value

Business Partner ID

D*

Insert as Subnode

Select this checkbox

8. Assign Supplier ID DE004701 to the hierarchy using the data in the following table. Field

Value

Business Partner ID

D*

Insert as Subnode


9. Approve your hierarchy to your change request. 10. Approve your change request.

112



Process Supplier Hierarchy Records

Business Example Your company has decided that the supplier master data from an acquired SAP ERP system should be enhanced with a hierarchy based on the supplier's location by country or region. You have been asked to create the new hierarchies within the governance framework and have the hierarchies approved before they are deployed. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Create a hierarchy change request using the data in the following table and note the change request number. Screen Name

Field

Value


Description

Supplier Country Hierarchy ##


Due Date



Explanation

New Supplier Country Hierarchy ##


Objects to be Changed

Business Partner ID

Note the change request number. Answers will vary. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Supplier Governance. e) On the Supplier Governance screen, in the Processing of Multiple Suppliers section, choose Create Hierarchy Change Request. f) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table.


113


g) Choose Next. h) On the Create Change Request: Step 2 (Reason for Changes) screen, enter the data from the table. i) Choose Next. j) On the Create Change Request: Step 3 (Changes) screen, select the object from the table. k) Choose Next. l) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit. m) Note the change request number. 2. Create a new hierarchy using the data in the following table. Field

Value

BPartner Hierarchy

SUP_COUNTRY_##

Description

Supplier by Countries ##

a) In the Supplier Governance workcenter, in the navigation panel, choose Change Requests → Processing of Multiple Suppliers → Hierarchy Processing. b) On the Hierarchy Processing: Business Partner ID screen, choose Continue. c) Choose Insert. d) On the Create Business Partner Hierarchy screen, enter the data from the table. e) Choose Transfer. 3. Create a structure node using the data in the following table. Field

Value

Structure Node

EMEA

Description

European Countries

a) On the Hierarchy Processing: Business Partner ID screen, in the Business Partner ID table, select SUP_COUNTRY_##. b) Choose Insert → Create New Structure Node. c) On the Create New Structure Node dialog box, enter the data from the table. d) Choose Transfer. 4. Create a second node structure using the data in the following table.

114

Field

Value

Structure Node

AMA

Description

American Countries



a) On the Hierarchy Processing: Business Partner ID screen, in the Business Partner ID table, select SUP_COUNTRY_##. b) Choose Insert → Create New Structure Node. c) On the Create Structure Node dialog box, enter the data from the table. d) Choose Transfer. 5. Create a structure node for AMA using the data in the following table. Field

Value

Structure Node

NA

Description

North America

a) On the Hierarchy Processing: Business Partner ID screen, in the Business Partner ID table, expand AMA. b) Choose Insert → Create New Structure Node. c) On the Create New Structure Node dialog box, enter the data from the table. d) Choose Transfer. e) In the Business Partner ID table, choose SUP_COUNTRY_## → NA. f) Choose Rank Lower. 6. Create a second structure node for AMA using the data in the following table. Field

Value

Structure Node

LA

Description

Latin America

a) On the Hierarchy Processing: Business Partner ID screen, in the Business Partner ID table, choose SUP_COUNTRY → AMA. b) Choose Insert → Create New Structure Node. c) On the Create New Structure Node screen, enter the data from the table. d) Choose Transfer. e) In the Business Partner ID table, choose SUP_COUNTRY_## → LA. f) Choose Rank Lower. 7. Assign Supplier ID DE004600 to the hierarchy using the data in the following table. Field

Value

Business Partner ID

D*

Insert as Subnode



115


a) On the Hierarchy Processing: Business Partner ID screen, in the Business Partner ID table, choose SUP_COUNTRY_## → EMEA. b) Choose Insert → Business Partner ID. c) In the Insert Business Partner ID dialog box, in the first empty Business Partner ID field, in the drop-down menu, in the List of Values: Business Partner ID dialog box, in the Business Partner ID field, enter the data from the table. d) Choose Start Search. e) In the search results table, choose DE004600. f) Choose OK. g) In the Insert Business Partner ID dialog box, select the Insert as Subnode checkbox. h) Choose Transfer. 8. Assign Supplier ID DE004701 to the hierarchy using the data in the following table. Field

Value

Business Partner ID

D*

Insert as Subnode


a) On the Hierarchy Processing: Business Partner ID screen, in the Business Partner ID table, choose SUP_COUNTRY_## → EMEA. b) In the Insert Business Partner ID dialog box, in the first empty Business Partner ID field, in the drop-down menu, in the List of Values: Business Partner ID dialog box, in the Business Partner ID field, enter the data from the table. c) Choose Start Search. d) In the search results table, choose DE004701. e) Choose OK. f) In the Insert Business Partner ID dialog box, select the Insert as Subnode checkbox. g) Choose Transfer. 9. Approve your hierarchy to your change request. a) On the Hierarchy Processing: Business Partner ID screen, choose Check. b) In the Select Change Request dialog box, in the Change Request drop-down menu, select the change request you made earlier. c) Choose Transfer. d) Choose Save. 10. Approve your change request. a) In the Supplier Governance Workcenter, in the navigation panel, choose Change Requests → Change Requests and Documents → My Change Requests. b) On the My Change Requests screen, select your change request number.

116



c) On the Process Change Request screen, choose Run Validation. d) Choose Validation Log. e) On the Validation Log screen, in the Validation Log table, select the entry. f) In the Messages table, view the log. g) Choose Close to close the internet browser and return to the Process Change Request screen. h) On the Process Change Request screen, choose Finalize Processing. i) Choose Close. j) On the My Change Requests screen, choose Refresh. k) Select your change request. l) On the Approve Change Request screen, choose Approve. m) Choose Close. n) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.


117



118



Unit 3

115

Learning Assessment

1. In the Financials domain, which of the following categories are types of change requests? Choose the correct answers. X

A Company-based change requests

X

B Form-based change requests

X

C Multiple object change requests

X

D Single object change requests

2. What does the Distribution Monitor control? Choose the correct answer. X

A Approval and change process

X

B Change requests

X

C Editions

X

D Replication process

3. A simple workflow can contain which objects? Choose the correct answer. X

A Single objects

X

B Multiple objects

X

C Single and multiple objects

X

D No objects

4. In Master Data Governance for Financials, mass processing is used for processing multiple selected objects of the same entity type in a single operation. Determine whether this statement is true or false. X

True

X

False


119


5. File upload and download components can be used only to transfer single objects to and from the MDG system. Determine whether this statement is true or false. X

True

X

False

6. What objects comprise an SAP ERP hierarchy maintained in MDG? Choose the correct answers.

120

X

A Data models

X

B Dependent objects

X

C Independent objects

X

D Replication model


Unit 3

117


1. In the Financials domain, which of the following categories are types of change requests? Choose the correct answers. X

A Company-based change requests

X

B Form-based change requests

X

C Multiple object change requests

X

D Single object change requests

2. What does the Distribution Monitor control? Choose the correct answer. X

A Approval and change process

X

B Change requests

X

C Editions

X

D Replication process

3. A simple workflow can contain which objects? Choose the correct answer. X

A Single objects

X

B Multiple objects

X

C Single and multiple objects

X

D No objects


121


4. In Master Data Governance for Financials, mass processing is used for processing multiple selected objects of the same entity type in a single operation. Determine whether this statement is true or false. X

True

X

False

5. File upload and download components can be used only to transfer single objects to and from the MDG system. Determine whether this statement is true or false. X

True

X

False

6. What objects comprise an SAP ERP hierarchy maintained in MDG? Choose the correct answers.

122

X

A Data models

X

B Dependent objects

X

C Independent objects

X

D Replication model


UNIT 4

Change Request Monitoring and Analysis

Lesson 1 Tracking Change Request Information Exercise 11: Track Change Request Information

124 127

Lesson 2 Monitoring Change Request Status Exercise 12: Monitor Change Request Status

130 133

Lesson 3 Analyzing Change Request Metrics Exercise 13: Retrieve Process Time Metrics Exercise 14: Analyze Processing Time Duration

136 141 145

UNIT OBJECTIVES ●

Track change request information

●

Monitor change request status

●

Define service level agreements

●

Retrieve processing time metrics

●

Analyze processing time duration


123

Unit 4 Lesson 1 120

Tracking Change Request Information

LESSON OVERVIEW In this lesson, you will learn how to track change request information. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Change Request Tracking

Figure 34: Direct Actions in the Flexible Worklist

The flexible MDG user interface allows direct actions from both the SAP Portal and NetWeaver Business Client. The SAP Portal provides a Java based universal work list (UWL). The SAP Business Client provides a personal object work list (POWL) built on Web Dynpro for ABAP. You can select and display change requests by criteria and perform direct actions on a selected object. You can also select and display change requests by object. You can view all the change requests that you have created by choosing My Change Requests. This option opens a side panel with a graphic summary of your change requests. You can add more queries to the side panel.

124


Lesson: Tracking Change Request Information

Change Request Information The list of Change Requests (CR) contains an option to display the workflow log of each CR. By default, the workflow log displays dialog steps. You can also display CR status, processors of completed steps, and potential processors for steps that are still to be performed. You can also display a list of workflow steps executed by the system in the background.

How to Track Change Request Information For the demonstration steps and data, see the exercise Track Change Request Information.


125

Unit 4: Change Request Monitoring and Analysis

126



Track Change Request Information

Business Example As a master data steward, you have been asked to monitor the company change requests to determine if there are any issues hindering timely completion. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Open your new change request ## New Supplier. 2. Edit your change request.


127


Track Change Request Information

Business Example As a master data steward, you have been asked to monitor the company change requests to determine if there are any issues hindering timely completion. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Open your new change request ## New Supplier. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Supplier Governance. e) In the navigation panel, choose Change Requests → My Change Requests. f) In the change request table, choose ## New Supplier. 2. Edit your change request. a) On the Organization: screen, choose Change Documents. b) Choose Close. c) On the Organization: screen, choose Workflow Log. d) On the Workflow Log for Change Request screen, in the Work Item ID column, choose any link. e) On the On the Change Request screen, choose Log. f) Choose Close. g) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.

128


Lesson: Tracking Change Request Information




129

Unit 4 Lesson 2 126

Monitoring Change Request Status

LESSON OVERVIEW In this lesson, you will learn how to monitor change request status. LESSON OBJECTIVES After completing this lesson, you will be able to: Monitor change request status

●

Change Request Status Table 3: Change Request Status Codes Change Request Status

Description

00

To Be Evaluated

01

To Be Considered and Approved

02

Changes to Be Executed

03

To Be Revised

04

Final Check to Be Performed

05

Final Check Approved

06

Final Check Rejected

07

Activation Failed

08

Approved, to Be Replicated

09

Dependent Data to Be Processed/Approved

10

To Revise: Perform Changes

11

Process Errors After Activation

12

Approved, Contact Person to Be Processed

99

No Status Set

A change request status serves two main purposes. The first purpose is to inform the processor of the current processing state and what changes to complete. The second purpose is to control whether you can change the change request attributes. The status code is the value assigned by the system to the change request in the workflow template or the rule-based workflow decision tables. The description is delivered to the processor’s inbox describing the current status and the possible next steps.

130


Lesson: Monitoring Change Request Status

The following table lists the types of changes you can make to a change request, which is indicated by the permitted processing value: Table 4: Types of Change Request Changes Permitted Processing

Full Description

L – Change of Object List

Allows you to modify a change request header and add or remove objects. You cannot change the attributes of an object when this processing permission is in effect. For example, use this permission type when you expect users to approve or reject change requests without changing any values.

O – Execution of Changes

Allows you to change all data in the change request. Use this processing permission status when an expert or a master data steward is required to edit a change request.

(space) – No Processing

Prevents users from changing the change request including actions. While the change request is in this processing status, the system does not display the action buttons assigned using step types.

Once a change request is in status 05 or 06, the status can no longer be changed. Status 05 and 06 are automatically set when a change request is activated or rejected. You can change the workflow template to add new status entries.

Replication Status Monitoring Table 5: Replication Status Indicators Replication Status Indicator

Description Error. There was an error in sending the message to the target system or an error in posting the message in the target system. Caution. The message is sent or about to be sent, but the message is not yet posted. Success. The message is posted in the target system.

No status indicator

No attempt at replication was made in the system.

The Master Data Steward Replication Status UI lets you check the replication status of specific objects using a less technical view than the replication log. If you identify replication problems, have the problems evaluated by a Master Data Administrator.


131


The object type code handling can be different depending on the business object. For example, the Business Partner is handled by object type 986, which is used in the SAP UI, but is automatically exchanged by object type 147 in the web UI.

How to Monitor Change Request Status For the demonstration steps and data, see the exercise Monitor Change Request Status.

132



Monitor Change Request Status

Business Example As a master data steward, you have been asked to monitor the status of company change requests created over a period of time. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. View the change request processing time report as a list. 2. Show change request status details using the data in the following table.


133


Monitor Change Request Status

Business Example As a master data steward, you have been asked to monitor the status of company change requests created over a period of time. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. View the change request processing time report as a list. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Governance for Flight Data Model. e) In the Analysis of Change Request Process section, choose Status Report (List View). 2. Show change request status details using the data in the following table. a) On the Change Requests: Status screen, view the default criteria. b) In the Status of Change Requests table, choose Show Details. c) On the Status Overview: Priority All, screen, view the change request status details. d) In the Material Maintenance MM01/02 row, in the Created column, choose the number. e) On the Display Change Requests screen, view the data. f) Choose Close. g) On the Status Overview: Priority All, screen, choose Rejection Reasons. h) On the Rejection Reasons: Priority All, screen, view the data. i) Choose Close to close the internet browser windows.

134


Lesson: Monitoring Change Request Status


Monitor change request status


135

Unit 4 Lesson 3 132

Analyzing Change Request Metrics

LESSON OVERVIEW In this lesson, you will learn how to define service level agreements, retrieve processing time metrics, and analyze processing time duration. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


●


●


Analytics Optimization

Figure 35: Analytics Optimize Master Data Processes

Use analytics to optimize master data processes. Analytics are targeted to the roles Master Data Steward and Master Data Expert. The following benefits are possible through the use of analytics: ●

●

136

Analysis — Analyze the processing times and statuses of change requests, which involves monitoring business activities, tracking compliance with Service Level Agreements (SLA), and optimizing processes. General — Use statistics and graphics to identify and resolve gaps in processes, remove bottlenecks, and fix errors. Navigate directly to change requests with issues so that you can change the request.


Lesson: Analyzing Change Request Metrics

●

●

Processing Times — Detect peak and off-peak times during change request processing. Compare processing times to SLAs and identify which change requests meet or exceed a specified due date. You can also measure how long it takes to process change requests by change request type and data model. Statuses — Identify which change request types are processed the fastest. View summaries of the statuses of change requests such as final rejected, final approved, and created. You can also analyze why change requests of a certain type include errors or are rejected.

The following key metrics can be included in analytics for data models and change request types: ●

●

Processing Times -

Average processing time

-

Total change requests for a certain time frame

-

Total change requests that violated the SLA

-

Total change requests with no KPIs defined

-

Total change requests that exceeded a due date

Statuses -

Summary of statuses such as final rejected, final approved, and created.

-

Top 10 reasons why change requests are rejected.

The following dimensions can be included in analytics: ●

Change request type

●

Yearly, quarterly, monthly, or weekly

●

Priority of change request

Change Request Priorities

Figure 36: Change Request Priorities


137


You can optionally 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 are used for change request analytics and process quality analysis and to influence the workflow template-driven processes. You can optionally define print forms for change requests. The default form is USMD_EDITION_CREQUEST. This option is only relevant if printed forms are required.

Service Level Agreements

Figure 37: Definition of a Service Level Agreement

You can define a separate SLA for each priority level of a change request type. The following attributes can be specified for each SLA: ●

Days

●

Hours, Half Days

How to Define a Service Level Agreement In the following section the service level agreement (SLA) will be defined for a specific change request type. The SLA is defined based on the change request priority assigned when a change request in raised. In this demonstration, when values include ##, replace the characters with your group number. 1. Change the priority of service level agreement change request type SUPPL1P1. a) On the Easy Access - User Menu screen, choose MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Create Change Request Type. d) On the Change View "Type of Change Request": Overview screen, choose Service Level Agreement for Change Request Types.

138



e) In the Type of Change Request list, select SUPPL1P1. f) Choose BC Set: Change Field Values. g) In the Priority column, verify that the priority has been created by the system. h) Choose Back until you return to the SAP Easy Access - User Menu screen.

Business Context Viewer

Figure 38: Status Report Side Panel

Business Context Viewer makes it easier for a user to find all related information for a business object. The Side panel shows the information directly on the screen of the application. Summary functions are achieved through automatic integration with the Business Context Viewer. The side panel graphically summarizes status data and the status of your own change requests. For any time frame or change request priority, you can see an overview of how many change requests are completed and rejected, completed and accepted, and created. This information is available for the whole organization, for data models within the organization, and for change request types within each data model. You can navigate to the individual change requests that are causing problems. You can also view the main reasons why change requests are being rejected.


139


Figure 39: My Change Requests Side Panel

How to Retrieve Process Time Metrics For the demonstration steps and data, see the exercise Retrieve Process Time Metrics.

140



Retrieve Process Time Metrics

Business Example As a master data steward, you have been asked to monitor the if company change requests created over a period of time are being completed within the specified time duration. In this example, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Open the Processing Time (List View) screen. 2. View the change request processing times.


141


Retrieve Process Time Metrics

Business Example As a master data steward, you have been asked to monitor the if company change requests created over a period of time are being completed within the specified time duration. In this example, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Open the Processing Time (List View) screen. a) On the Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Analysis of Change Request Process. e) Below the Workcenter toolbar, choose Processing Time (List View). 2. View the change request processing times. a) On the Change Request: Processing Time screen, in the Processing Time of Change Requests section, select Show Details b) On the Processing Time: Priority All, screen, in the Due Date Compliance and SLA Compliance for Data Models and Associated Change Request Types table, in the Material Maintenance MM01/02 row, in the Total Amount of Change Requests column, choose the number. c) On the Display Change Requests screen, view the data. d) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.

142



Processing Time Duration

Figure 40: Processing Time List View

After you specify a priority and a time frame, you can find out whether change requests across the organization are meeting or violating target processing times. This information is available for the whole organization, for data models within the organization, and for change request types within each data model. You can access statistical information in the list view and graphical illustrations in the graphical view. In the Processing Time (List View), you can navigate to the individual change requests that are causing problems. You can access, monitor, and analyze change request process times from each application area by priority and a weekly, monthly, quarterly, or yearly basis. Results are organized by data model and change request type and show the following change request status: ●

Due date exceeded

●

SLA violated

●

On time

●

No KPI defined

If there are less than 200 entries in the report list, you can view a detailed list of change request data. The following KPIs are monitored for processing time compliance: ●

SLA by change request priority and type

●

Due date

The following color code indicates KPI processing time compliance: ●

Red—At least one change request exceeds a due date or violates an SLA.

●

Yellow—At least one change request has no KPI is defined.

●

Green—All KPIs are defined and all change requests have been completed on time.

Processing Time Duration Graphical Report

Figure 41: Analyze Processing Time of Change Requests Graphical View

You can view a graphical report of change request processing time durations by priority, time scale, date, and status. Change request processing time status is indicated by the following color code:


143


●

Red—SLA violation

●

Pink—Due date exceeded

●

Green—On time

●

Blue—No KPI defined

How to Analyze Processing Time Duration For the demonstration steps and data, see the exercise Analyze Processing Time Duration.

144



Analyze Processing Time Duration

Business Example You are a master data steward. Part of your job is to analyze the processing times and statuses of change requests including monitoring business activities, tracking compliance with Service Level Agreements (SLA), and optimizing processes. You have been asked to analyze change request processing time duration. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Open the Processing Time (List View). 2. View change request processing time details.


145


Analyze Processing Time Duration

Business Example You are a master data steward. Part of your job is to analyze the processing times and statuses of change requests including monitoring business activities, tracking compliance with Service Level Agreements (SLA), and optimizing processes. You have been asked to analyze change request processing time duration. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Open the Processing Time (List View). a) On the SAP Easy Access – User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) On the Material Governance Homepage, in the Process Reporting section, choose Processing Time (List View). 2. View change request processing time details. a) On the Change Request: Processing Time screen, in the Processing Time of Change Requests section, select Show Details. b) Choose Close. c) Choose Close to close the internet browser and return to the SAP Easy Access - User Menu screen.

146





●


●



147


148


Unit 4

145

Learning Assessment

1. The Workflow Log displays which types of information? Choose the correct answers. X

A Data model

X

B Processors

X

C Roles

X

D Status

2. What is the purpose of a change request status? Choose the correct answers. X

A It controls whether changes can be made to the change request attributes

X

B It gives the current processing state.

X

C It halts a change request process when the status is marked incomplete.

X

D It states what changes will be made.

3. Analytics is used to optimize master data processes. Determine whether this statement is true or false. X

True

X

False

4. What is the Side Panel used for? Choose the correct answer. X

A Creating new change requests

X

B Displaying the work flow graphically

X

C Manage user roles and access

X

D Presenting status data and reports


149


5. You can monitor the change request process based on which of the following attributes? Choose the correct answers.

150

X

A Change request type

X

B Data model

X

C Priority

X

D Time scale


Unit 4

147


1. The Workflow Log displays which types of information? Choose the correct answers. X

A Data model

X

B Processors

X

C Roles

X

D Status

2. What is the purpose of a change request status? Choose the correct answers. X

A It controls whether changes can be made to the change request attributes

X

B It gives the current processing state.

X

C It halts a change request process when the status is marked incomplete.

X

D It states what changes will be made.

3. Analytics is used to optimize master data processes. Determine whether this statement is true or false. X

True

X

False


151


4. What is the Side Panel used for? Choose the correct answer. X

A Creating new change requests

X

B Displaying the work flow graphically

X

C Manage user roles and access

X

D Presenting status data and reports

5. You can monitor the change request process based on which of the following attributes? Choose the correct answers.

152

X

A Change request type

X

B Data model

X

C Priority

X

D Time scale


UNIT 5

Process and User Interface Configuration

Lesson 1 Configuring Master Data Governance Processes and the User Interface Exercise 15: Verify User Configuration Exercise 16: Change a Standard Workflow Template User Interface

154 161 177

Lesson 2 Adding a Step to an Existing Configuration Exercise 17: Add a Step to an Existing Configuration

182 187

UNIT OBJECTIVES ●

Configure Master Data Governance processes

●

Manage Master Data Governance roles

●

Configure workflow assignments

●

Change a standard workflow template user interface

●

Add a step to an existing configuration


153

Unit 5 Lesson 1 150

Configuring Master Data Governance Processes and the User Interface

LESSON OVERVIEW In this lesson, you will learn how to configure Master Data Governance processes, manage Master Data Governance roles, configure workflow assignments, and change a standard workflow user interface. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


●


●


●


Master Data Governance Configuration Activating the MDG Switches

Figure 42: Switch Framework

MDG is completely switch enabled. MDG will not appear in Customizing without being activated nor will you be able to start any default processing before activating MDG. MDG is activated by setting the relevant switches in the Switch Framework. Standard Customizing Path for MDG using IMG

154


Lesson: Configuring Master Data Governance Processes and the User Interface

Figure 43: Customizing Path for MDG Using IMG

The Customizing path for MDG is in the Implementation Guide (IMG) and provides access to the following elements: ●

Cross-application components including processes and tools for enterprise applications

●

MDG customization

●

Data Replication Framework (DRF)

MDG in the IMG Structure The following MDG settings are available in the IMG: ●

Data modeling

●

UI modeling

●

Data quality and search

●

Process modeling

●

Data replication

●

Mass data load


155

Unit 5: Process and User Interface Configuration

Elements of Change Request Customizing

Figure 44: Change Request Process Configuration

The change request process configuration is connected to the data model and user interfaces. Several change request types can be assigned to a single business activity. The following attributes are determined by the change request type: ●

Workflow template

●

Data model

●

Entity types

The status of a change request and its workflow template steps are used in the process logic. The following options are determined by the change request and workflow template settings: ●

The actions possible in the UI

●

The next workflow template step

●

The next change request status

Master Data Governance Scope Configuration Governance scope indicates which fields you want to govern. By default, all entities and attributes in the data model are governed, but you can customize these settings. You can determine scope at the entity level and at the attribute level. If you mark an entity "out-ofscope," or not governed, then none of its attributes or sub-entities are governed. When an entity is governed, then all of its key and mandatory attributes are governed. You can govern non-key and optional attributes of an entity or take them out-of-scope. On a change request, attributes marked "out-of-scope" display in read-only mode. Attributes can be hidden on a change request using different UI configuration methods.

156



Figure 45: Governance Scope Configuration

You can configure governance scope during or after the implementation of MDG. If you define scope after implementation, the system processes pre-existing change requests with the data that had been entered regardless of the governance scope settings. The following conditions apply to entity types and attributes that are removed from the governance scope: ●

They cannot be changed in a change request.

●

They are shown as read-only when displayed on a change request.

●

They can be imported to the active area but not through a change request.

●

They can be replicated and exported.

●

They cannot be changed in a mass change request.

●

●

They can be used for derivations, but their values cannot be derived, only used as input for derivations. They can be easily added again to the governance scope.

How to Start Master Data Governance Configuration In the Implementation Guide (MDGIMG), there are specific steps required to set up Master Data Governance. In MDGIMG, you can find the Customizing settings and the activities to execute MDG. The following configuration processes are available: ●

●

●

●

●

Creation of New Content for Master Data Governance: Create new content without using a template. Enhancement of Master Data Governance Content: Enhance existing Master Data Governance content. Structure of the Data Model and Database Tables: Model master data structures. Setting Up New Business Activities: Create individual master data objects without creating a change request beforehand. Configuration of the Workflow: Configure the workflow for the change request process in Master Data Governance.


157


●

●

●

●

●

●

Using Search Providers for Master Data Governance: Utilize search providers for master data. Configuring Data Replication: Change settings for data replication within the Data Replication Framework (DRF). Value Mapping: Map internal Customizing element codes to a list of external customizing code values. Setting Up Web Dynpro Applications in Customizing: create and edit UI configurations for the Web Dynpro applications delivered by SAP. Enabling Detailed Analysis of Change Requests: Monitor system settings in detail. Making Changes to Governance Application Programming Interface: Develop new UIs that enhance your Master Data Governance applications and are consistent with the existing software. 1. Navigate to the start point for Master Data Governance Configuration. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, expand General Settings. You can select the options in the General Settings folder to configure MDG. a) Choose Back until you return to the SAP Easy Access - User Menu screen.

Master Data Governance Roles Rules and Menu Entries for NetWeaver Business Client and Enterprise Portal

Figure 46: Roles and Menu Entries for Work Centers

The Master Data Governance Workcenter enables you to access functions in SAP NetWeaver Business Client and the SAP Enterprise Portal. MDG delivers several roles for each domain. The MENU role ensures that the navigation menu is available to everyone. The remaining roles provide all the required role-based abilities for MDG. The following roles are delivered for each standard domain:

158



●

Master Data Governance for : Menu (SAP_MDGx_MENU)

●

Master Data Governance for : Display (SAP_MDGx_DISP)

●

Master Data Governance for : Requester (SAP_MDGx_REQ)

●

Master Data Governance for : Specialist (SAP_MDGx_SPEC)

●

Master Data Governance for : Data Steward (SAP_MDGx_STEW)

The letter x is replaced with letter indicating the role's domain: C for Customer, F for Financials, M for Material, and S for Supplier. There is a special role for analytics that includes a template for Custom Objects and a sample application called SFlight with an MDG Administrator role. NetWeaver Business Client Basic Information for HTML SAP NetWeaver Business Client (NWBC) provides a UI client as a single point of entry to SAP applications. NWBC provides access to both existing SAP GUI transactions and new applications based in Web Dynpro. NWBC is available in HTML and desktop versions. NWBC for HTML is a light-weight, browser-based shell using built-in PFCG roles available only on ABAP systems for casual use. This system renders all SAP GUI transactions using the SAP GUI for HTML rendering engine. NetWeaver Business Client Basic Information for Desktop NWBC for Desktop is a .NET application intended for power users. The desktop version uses the SAP GUI rendering engine directly, when it is installed. NWBC for Desktop can access a single ABAP system with the PCFG as a role repository or access an SAP NetWeaver Portal using the Portal Conent Directory (PCD) as a role repository.

How to Verify User Configuration For the demonstration steps and data, see the exercise Verify User Configuration.


159


160



Verify User Configuration

Business Example Your company's new CD product is a huge success. To help manage all of the new suppliers, a new master data management administrator has been hired. The administrator starts on Monday and you have been asked to verify that the new user has been assigned the appropriate Master Data Governance roles and authorizations. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Verify a Role Assignment 1. Verify the authorizations contained within the role SAP_MDGS_REQ.


161


Verify User Configuration

Business Example Your company's new CD product is a huge success. To help manage all of the new suppliers, a new master data management administrator has been hired. The administrator starts on Monday and you have been asked to verify that the new user has been assigned the appropriate Master Data Governance roles and authorizations. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. Verify a Role Assignment 1. Verify the authorizations contained within the role SAP_MDGS_REQ. a) On the SAP Easy Access - User Menu screen, in the Command field, enter SU01. b) Choose Enter. c) On the User Maintenance: Initial Screen, in the User field, enter your user ID. d) Choose Display. e) On the Display Users screen, select the Roles tab. f) In the Role Assignments table, double-click SAP_MDGS_REQ. g) On the Display Roles screen, choose the Authorizations tab. h) Choose Display Authorization Data. i) In the Information dialog box, choose Enter. j) On the Display Role: Authorizations screen, go to SAP_MDGC_REQ → SAP Master Data Governance → Type of Change Request → Type of Change Request. Note: This role is not restricted to any supplier change request type. k) Choose Back to return to the SAP Easy Access - User Menu screen.

162



High-Level Business Workflow Components

Figure 47: High-Level Business Workflow Components

The integrated inbox lets you view and administer work items and supports all mail functions of SAP Workplace. The System Work Item Manager processes workflow activities, including deadline monitoring. When workflow activities include methods that run in the background, the System Work Item Manager initiates the background processes.

Single Processing of Supplier and Customer Records

Figure 48: Processing of Suppliers - Workflow Templates


163


For MDG Supplier and Customer domains, SAP provides a set of predefined workflow templates for the most common record processing scenarios. This section describes each of these workflow templates with the corresponding dialog step numbers. Note that these step numbers are not in numerical order nor do they indicate a sequence, but instead describe the agent assignment. The following predefined workflow templates apply to the Supplier domain: ●

●

●

●

●

●

164

WS54300005: Create Supplier -

Step 1: Approval (decision)

-

Step 4: Revision after Rejection

-

Step 5: Data Maintenance (subworkflow)

-

Step 6: Approval (subworkflow)

-

Step 7: Activation (decision)

WS54300007: Process/Change Supplier -


-


-


WS60800059: Block/Unblock Supplier -


-


-


WS60800068: Mark Supplier for Deletion -


-


-


WS60800095: Mass Approval (BP Hierarchies, & BP Mass Maintenance) -

Step 1: Processing

-


-


-


-


WS72100006: BP Initial Load -

Step 1: Processing

-




-


-


-


Figure 49: Processing of Customers - Workflow Templates

The following predefined workflow templates apply to the Customer domain: ●

●

●

WS54300003: Process Single Customer (Create, Change, Block/Unblock, & Mark For Deletion) -


-


-


WS46000023: Local Maintenance: Create Customer (additional steps for duplicate processing) -

Step 1: Maintenance of Duplicate Entries

-


-


-


-

Step 5: Address Rework/Review

WS46000027: Local Maintenance: Process Customer (additional steps for duplicate processing) -



165


-


-


-

Step 4: Address Revision after Validation

Processor Assignment to a Workflow Template Step

Figure 50: Assign Processor to Workflow Template Step Number

When defining a Change Request Type, a workflow template is assigned to determine how that change request is processed. Predefined workflow templates include a set of interactive steps that require user input. Each step is identified by a number that is unique in the specific workflow template. The system uses this unique number to assign an agent — a single or a group of processors — to the specific workflow template step. The following types of agents exist in the system: ●

C—Job

●

O—Organization unit

●

S—Position

●

US—User ID

The first three agents are maintained in the organizational structure. The user ID agent is maintained in the user master.

Enhanced Financial Workflow Templates

Figure 51: Enhanced MDG Financial Workflow Template

166



The advanced financial workflow template WS75700043 allows for Entity Type-specific processors. An enhanced financial workflow template is only available for Change Request Types with the flag Objects Required. This workflow template is similar to the basic workflow template but includes a feature to assign separate processors for each entity.

Supplier Agent Determination For change request types and their workflow template steps, assign the relevant agents. Agents can refer to a single user or a complete organization unit. Company code and the purchasing organization can be used to determine agents in the standard delivered Supplier workflow templates. The BAdI MDG_BS_SUPPL_WF_AGENT_ERP is used to switch between BRFplus agent determination and the original table-driven method.

Supplier Agent Determination Filter Table 6: Supplier Agent Determination Entries Type

Step

CoCode

Purch. Org. Flag Central Data Changed

Object Type

ID

SUPPL1P1

01

—

—

—

O

50000050

SUPPL1P1

02

—

—

—

O

50000050

SUPPL1P1

03

—

—

—

O

50000050

SUPPL1P1

04

—

—

—

O

50000050

SUPPL1P1

05

—

—

—

O

50000050

SUPPL1P1

05

1000

—

—

US

BRF_CC10 00

SUPPL1P1

05

—

1000

—

US

BRF_PO00 02

SUPPL1P1

06

—

—

—

O

50000050

In addition to assigning agents to step numbers in pre-defined workflow templates, SAP delivers an improved method to assign agents for Suppliers using BRFplus. In addition to the step number, company code and purchasing organization IDs can be used for agent determination. Switching between the original table-driven method and the BRFplus method is done in with object MDG_BS_BP_WORKFLOW_SWITCH.


167


Master Data Governance Workflow Template

Figure 52: Master Data Governance Workflow Template

Master Data Governance allows flexibility in the SAP Business Workflow. The following types of business workflow templates are available: ●

Standard business workflow templates, which include predefined, fixed content

●

Rule-based workflow templates, which include default content delivered for Material

The rule-based workflow template is flexible and can handle any process in any MDG domain. Some of the predefined workflow templates are generic enough to be used with any object. However, unlike the rule-based template, the processing steps of the predefined workflow templates are fixed and cannot be changed. Changing a fixed, predefined workflow template involves making a copy of the original template and then changing to copy. Each change request type can be assigned a single workflow template and both are linked in the change request type definition table. The Material workflow template uses a two-step approval process for governance purposes. The following process ensures compliance with the two-step rule: 1. The business user requests creation of a material or a change to material data and submits a change request. 2. The master data expert is notified through the Worklist that the new change request is created. The expert reviews the data, which can be changed or enhanced, and then approves the request. If the expert wants to send back the request for clarification, an additional process for revision and resubmission is included in the standard workflow template. This process includes the following steps:

168



1. The business user requests the creation of a material or the change of material data and submits the change request. 2. The master data expert is notified through the worklist that the new change request is created. The expert reviews the data, which can be changed or enhanced, and sends the review back to the business user for revision and clarification. 3. The business user can cancel the request or adjust the data and then resubmit the request. 4. The master data expert reviews and revises the request. If the data is complete and correct, the change request is approved, otherwise it is sent back to the user for revision.

Workflow Template Assigned to Change Request Types A default set of change request types is delivered with Master Data Governance for Material and activated using the Business Configuration Set (BC-Set). Each change request type is assigned to one of the predefined Business Activities. You can use the default change request types or create your own. The connection to the workflow template determines the main processing logic of the change request. For Material, the standard rule-based workflow template WS60800068 is delivered. The following Material change request types are provided: ●

MAT01—Create material

●

MAT02—Change material

●

MAT06—Mark material for deletion

●

MAT0A—Process multiple materials

●

MAT0B—Import material

The actual processing logic of a rule-based workflow template is defined using a predefined set of BRFplus applications where steps and agents are determined dynamically.


169


Generic Workflow Template

Figure 53: Rule-Based Workflow Template

SAP provides the standard rule-based workflow template WS60800068. This template is a dynamic solution that can be easily customized for each MDG process. The standard SAP business workflow template is enhanced with a rule-based engine. The rule-based workflow template is controlled through a special set of BRFplus applications that have the same signature and contain the same set of decision tables. Each change request type has its own BRFplus application with its own copy of those decision tables. Populating those tables is a customization task that occurs during implementation projects. You can use the sample customization tasks as a template for further enhancements. The following decision tables are maintained: ●

Next-step table—Identifies the next step in the process.

●

Dialog agent table—Identifies the processors of an interactive dialog step.

●

Background-step table—Identifies the type, or processing pattern, of a background step.

The rule-based workflow template has a main loop that checks whether a next step exists. Inside the loop, the first task is to read the next step and the assigned agents. Next, the main branch of the workflow is a CASE or IF statement in which processing patterns are evaluated. Based on the pattern that is identified in the corresponding decision table, workflow instance control is routed through a single specific branch in each iteration. Finally, the condition to exit the loop is triggered, which results in completion of the workflow instance. The CASE statement contains the following options for the processing pattern:

170



Table 7: Background Step Table Step Type

Step Type Name

Processing Pattern

01

UI Dialog

Determines the interactive dialog step in the corresponding decision table

02

Call Synch. Method

Calls the specified method

03

Call Sub-Workflow

Calls the specified workflow template

04

Call Data Replication

Replicates data at an exact point in the process without waiting for the replication schedule

05

Activation (do not bypass snapshot)

Activates the data, considering the snapshot that was taken when a change request was initially created

06

Activation (bypass snapshot) Activates the data regardless of the snapshot date

07

Validate Change Request

Runs validations in the background

08

Roll Back Change Request

Rolls back any changes

98

Error

Issues an error in the process

99

Complete (Sub)Workflow

Marks change requests as completed

Each process step customized in the BRFplus application decision table has one these processing patterns. Consider the following example: Table 8: Next-Step Table Process Step

Description

Step Type

Step 1

Interactive processing

Type 01

Step 2

Validation

Type 07

Step 3

Interactive final approval step Type 01

Step 4

Activation

Type 06

Step 5

Completion

Type 99


171


Default Workflow in Rule-Based and Classic Templates

Figure 54: Default Workflow in Rule-Based and Classic Templates

The figure Default Workflow in Rule-Based and Classic Templates illustrates a standard twostep rule process in the rule-based workflow template using BRFplus. The following symbols show the steps, status, and actions that are represented in the BRFplus decision tables: ●

Chevrons—The steps, whether manual or automated steps

●

Dark rectangles—The statuses, visible in worklists and workflow inboxes

●

Black arrows and text—The actions, either triggered by the user or automated

A status is assigned to the change request for each step. The actions determine the progress from one step to the next. The following steps and actions are used in the figure Default Workflow in Rule-Based and Classic Templates: ●

●

●

●

172

Step 00: The business user initiates a change request by starting to create or change a material. As long as the data is saved in draft mode, no workflow is triggered. Technically, the change request is kept in cluster tables for temporary storage. Action Submit: When the change request is submitted, the workflow is triggered and the data transferred to the staging area. If the workflow is not started, the status changes to 02: Changes to be executed. Step 90: The master data expert verifies and enhances the data and performs the final check. Action 09 Activate: The expert triggers the activation of the data. System tasks, which are not shown in the figure, ensure that the data is validated before physical activation. Inconsistencies, potential duplicates, and ungoverned changes in the backend are detected and communicated to the expert through messages and the error log.



●

●

Step 91: An automated workflow task activates the data in the active area. If this operation is successful, the status 05: Final check approved is set. Actions in the background complete the workflow. Step 99: The workflow is approved and complete. The change request is no longer active.

The revision steps are triggered and performed as shown in the figure Default Workflow in Rule-Based and Classic Templates. In the default workflow setting, only the original requestor can withdraw a change request.

Generic Workflow Template Controlled by Rules

Figure 55: Generic Workflow Template Controlled by Rules

The Material workflow template includes a simple, single-approver, rule-based workflow template configuration, which can be enhanced during implementation. The same process logic is configured for all MDG Material processes such as Create, Process, and Mark for Deletion.

Workflow Template Step Types and Actions Every dialog step, which is an interactive step, in the rule-based workflow template configuration requires an assigned type. Examples of these dialogs steps include Check Change Request and Activate Change Request. A step type signifies which actions can be taken for a step by providing a set of buttons that appear in the UI for each step in the change request. An action such as Approve or Send for Revision indicates that a decision should be made by the user. MDG provides a predefined set of actions and step types. You can add new actions and step types in the following tables: ●

Actions: Maintenance View V_USMD220C

●

Step Types: Maintenance View V_USMD230C

●

Assignment of Actions to Step Types: Maintenance View V_USMD2301


173


Enhanced Change Requests Existing single-approver, rule-based workflow template configurations can optionally be enhanced by adding an interactive expert review step just before the approver step. An enhanced change request workflow template might consist of the following steps: 1. The standard, delivered, rule-based workflow configuration sends the change request from the requestor to the approver. 2. The change request goes from the requestor to the expert. 3. If the expert agrees, the change request goes to the approver once the expert agrees. 4. If the expert disagrees, the change request goes to back to the requestor. Extensibility Checklists One major focus of MDG is reuse and extensibility. It is common for customers to make extensions to the standard SAP master data models. Many companies have specific master data creation and change processes. MDG offers the flexibility and extensibility features to adapt the standard model to their needs. This flexibility allows customers to make extensions and still benefit from MDG’s out-of-the-box capabilities. The following checklist includes the high-level steps required to extend the standard MDG data model and process: ●

●

●

●

Data Model -

Create a data model

-

Create entity types

-

Create relationships

-

Save and activate the data model

UI Configuration -

Create a new UI configuration

-

Configure the UIBB

-

Set the attributes of the fields

Process Modeling -

Create business activity

-

Create a change request type

-

Define the workflow template

-

Set up the organizational structure

-

Assign processors

-

Create a role

Test the Process -

174

Create a change request



-

Process the change request

-

Approve the change request

How to Change a Standard Workflow Template User Interface For the demonstration steps and data, see the exercise Change a Standard Workflow User Interface.


175


176



Change a Standard Workflow Template User Interface

Business Example You are a master data specialist for an airline. The company has asked you to create a UI for business users to maintain flight landing details. You want to configure the steps in the standard workflow template to display in the correct UI. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to 1. Find the existing UI configurations ZMDG_SF_APPL_FLIGHT_CQ and ZMDG_SF_APPL_FLIGHT_RQ. 2. View the simplified UI configuration for ZMDG_SF_APPL_FLIGHT_RQ. 3. Change the UI in the first step of your change request using the data in the following table. Element

Value

Type of Chg. Request

SFZ##

UI Application Name

USMD_ENTITY_VALUE2

User Interface per Change Request Step/ Configuration Name

ZMDG_SF_APPL_FLIGHT_RQ

4. Change the check type to Basic Checks Only for entity SFZ##, step 00. 5. Check the assigned UI using the data in the following table. Field

Value

Airline

LH

Flight Number

##

Type

Create Flight Connection (Group ##) SFZ##


177


Change a Standard Workflow Template User Interface

Business Example You are a master data specialist for an airline. The company has asked you to create a UI for business users to maintain flight landing details. You want to configure the steps in the standard workflow template to display in the correct UI. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to 1. Find the existing UI configurations ZMDG_SF_APPL_FLIGHT_CQ and ZMDG_SF_APPL_FLIGHT_RQ. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → UI Modeling → Edit UI Configuration. d) On the Manage UI Configurations screen, find the two UI configurations. 2. View the simplified UI configuration for ZMDG_SF_APPL_FLIGHT_RQ. a) On the Manage UI Configurations screen, choose ZMDG_SF_APPL_FLIGHT_RQ. b) Choose Edit. c) On the Editor for the Web Dynpro ABAP Application Configuration screen, choose Continue in Display Mode. d) On the Application Configuration ZMDG_SF_APPL_FLIGHT_RQ screen, in the Assign Web Dynpro Component table, in the Configuration Name column, choose ZMDG_SF_APPL_FLIGHT_OIF_RQ. e) On the Component Configuration ZMDG_SF_APPL_FLIGHT_OIF_RQ, Variant "Flightschedule" screen, choose Show UIBB Preview. f) On the Component Configuration ZMDG_SF_PFLI_FORM_RQ screen, view the simplified UI. g) Choose Close to exit the Configure Component and Manage UI Configuration tabs. 3. Change the UI in the first step of your change request using the data in the following table.

178

Element

Value


SFZ##

UI Application Name

USMD_ENTITY_VALUE2



Element

Value

User Interface per Change Request Step/ Configuration Name

ZMDG_SF_APPL_FLIGHT_RQ

a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Configure Properties of Change Request Step. b) On the Change View "User Interface per Change Request Step": Overview screen, in the Type of Chg. Request field, enter the value from the table. c) On the Display View "Type of Change Request": Overview screen, choose Type of Change Request → User Interface per Change Request Step. d) In the User Interface per Change Request Step table, choose 00. e) In the UI Application Name field, enter the data from the table. f) Choose Enter. g) On the Change View "User Interface per Change Request Step": Overview screen, in the User Interface per Change Request Step/Configuration Name field, enter the data from the table. h) Choose Back until you return to the Display IMG screen. 4. Change the check type to Basic Checks Only for entity SFZ##, step 00. a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Configure Properties of Change Request Step. b) On the Change View "Entity Types per Change Request Step": Overview screen, in the Type of Chg Request search field, select SFZ##. c) On the Display View "Type of Change Request": Overview screen, choose Type of Change Request → Change Request Step → Step 00. d) In the Chg. Req. Step field, select 00. e) In the Entity Types per Change Request Step table, select PFLI. f) In the CheckLogic column, in the drop-down menu, choose Basic Check Only. g) Choose Save. h) Choose Back until you return to the SAP Easy Access - User Menu screen. 5. Check the assigned UI using the data in the following table. Field

Value

Airline

LH

Flight Number

##

Type

Create Flight Connection (Group ##) SFZ##


179


a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Master Data Governance for Custom Objects. e) In the Single Object Processing section, choose Create Change Request. f) On the Create Change Request screen, choose Change Model. g) On the Change Model screen, in the Standard Data Model field drop-down menu, choose SF. h) Choose Save. i) Choose Apply. j) On the Create Change Request screen, in the Entity Type field drop-down menu, choose Connection Number. k) On the Create Change Request: Create Flight Connection screen, enter the data from the table. l) Choose Continue. The UI no longer shows the airport codes for departures and arrivals. m) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.

180





●


●


●



181

Unit 5 Lesson 2 176

Adding a Step to an Existing Configuration

LESSON OVERVIEW In this lesson, you will learn how to add a step to an existing configuration. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


User Interface Configuration and Adaptation

Figure 56: User Interface Configuration and Adaptation

A UI is defined by both a UI application and a UI configuration. The UI configuration defines the look and feel of the UI.

182


Lesson: Adding a Step to an Existing Configuration

User Interface Adaptation Options

Figure 57: User Interface Adaptation Options

The user interface is configured using Floorplan Manager (FPM). FPM is a Web Dynpro ABAP application that provides a framework for developing new Web Dynpro ABAP application interfaces consistent with SAP UI guidelines. A FPM UI can be adapted using the following techniques: ●

Personalization

●

Customization without context-based adaptation

●

Configuration

●

-

Enhancement

-

Copying the application

Modification (not recommended)


183


User Interface Best Practices

Figure 58: User Interface Best Practices

It is easiest to customize the SAP predefined configurations. FPM UIs can be enhanced through two main methods: configuration and customization. FPM configuration is a workbench object that requires development access because changes are cross-client. Standard configurations are delivered with FPM applications. These configurations, like most standard objects, can be enhanced directly by using the enhancement framework. FPM applications can also be created from scratch or copied and modified. The standard FPM applications can also be customized. Almost everything that can be done in configuration can be done in customization. Configuration is mainly intended for development resources while customization is meant for application consultants and subject matter experts who don't have developer access. The primary distinction between configuration and customization is whether desired changes are the same for all change request types and steps. If the changes are all the same, then either configuration or customization can be used. If changes are intended only for specific steps or specific change request types, then you will have to create new FPM custom configurations.

184



Context-Based Adaptations in the User Interface

Figure 59: Context Based Adaptations in the User Interface

While other adaptation techniques are user-specific, client-specific, or system-specific, context-based adaptation offers UI configuration based on the data displayed on the screen. MDG applications deliver prebuilt integration into context-based adaptations. For example, when working with business partners, the address format can be automatically adjusted based on the value entered for the Country field. In the United States, the UI displays a field called State, in Germany, the same field is labeled Region, and in Canada, the same field is labeled Province. Displaying or hiding classifications is dependent on the value of the Material Type field for the Material domain. In the Material domain, the application configuration BS_MAT_OVP contains the component configurations BS_MAT_OVP_CBA and BS_MAT_OVP_LAYOUT. For the Action DELETE, an adaptation is available where some UIBBs are hidden and the Mark for Deletion flag is shown. In the Supplier and Customer domains, FPM is also adapted to handle the action DELETE as well as the action BLOCK, where fields needed for blocking a business partner are displayed. You can adapt the user interface in the following ways: ●

Initialize the displayed data when creating a new entity—BAdI derivations (MDG fields) / coding (non-MDG fields)

●

Restrict the values displayed in a drop-down list or selection field group—FPM feeder class

●

Restrict the values displayed in the input help—FPM feeder class

●

●

●

Dynamically control the visibility of fields in the user interface and the properties that determine if fields are required or display-only—Context-based adaptation or change request step customizing Define navigation destinations of hyperlink and button UI elements—Actions (MDG change request) / FPM navigation (non-MDG change request UIs) Check if the lead selection of a table can be changed—FPM feeder class


185


How to Add a Step to an Existing Configuration For the demonstration steps and data, see the exercise Add a Step to an Existing Configuration.

186



Add a Step to an Existing Configuration

Business Example You are a business administrator for an airline. You have been asked to enhance the company's UI so that airline specialists can see flight landing details, but the company does not want requestors to have access to the flight landing information. You have been asked to enhance the standard business process with a new process step so that specialists can access the information. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Verify that a new field named ZZTOCID has been added to the SF Flight Data Model. 2. Verify that a new UI initial screen named USMD_ENTITY_VALUE2 has been added to the SF Flight Data Model. 3. View the configuration of change request steps 01, 02, and 03 using the data in the following table. Step

Web Dynpro Application

Configuration Name

00

USMD_ENTITY_VALUE2

ZMDG_SF_APPL_FLIGHT_R Q

01

USMD_ENTITY_VALUE2

ZMDG_SF_APPL_FLIGHT_C Q

02

USMD_ENTITY_VALUE2


03

USMD_ENTITY_VALUE2


4. Add a new change request step named Landing Quota Specialist using the data in the following table. Column

Value


SFZ##

CR Step

4

Description (Medium Text)

Check Landing Quota

5. Verify that a new action named Check Landing Quota has been added to the SF Flight Data Model. 6. Verify that a new change request step type has been added to the Check Landing Quota check request step 04.


187


7. Verify that the status for the Check Landing Quota change request step has been added to the change request. 8. Enhance the rule-based workflow for change request SFZ## by adding Check Landing Quota as a flight connection detail. 9. Add condition alias QUO to start the user determination using the data in the following table. Field

Value

Condition Alias

QUO

User Agt. Grp. No.

001

Step Type

3

User Agent Type

S

User Agent Value

50010130

10. Add the following data to the rule-based, single value decision table. Column

Value

CR Previous Step

01 (Add Connection Details)

Previous Action

CQ (Check Landing Quota)

11. Configure the Check Landing Quota change request step to navigate from the Landing Quota confirmation step to the Approve step. Field

Value

CR Previous Step

04

Previous Action

05

Condition Alias

APP

New Change Request Step

03

New CR Status

04

12. Add the step specific UI configuration to the change request step. Field

Value

Step

04

UI Application Name

USMD_ENTITY_VALUE2

Configuration Name

ZMDG_SF_APPL_FLIGHT_CQ

13. Run the new process and verify that the requestor and specialist UIs are configured correctly using the data in the following table and note the change request number.

188

Field

Value

Airline

LH

Flight Number

99##



Field

Value

Type

Change Flight Connection (Group ##) SFZ##

Description

LH 99##

Start Country Key

DE

Departure City

Frankfurt

Destination Country Key

US

Destination City

San Francisco


14. Process your change request. Field

Value

Departure Airport

FRA

Destination Airport

SFO


189


Add a Step to an Existing Configuration

Business Example You are a business administrator for an airline. You have been asked to enhance the company's UI so that airline specialists can see flight landing details, but the company does not want requestors to have access to the flight landing information. You have been asked to enhance the standard business process with a new process step so that specialists can access the information. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Verify that a new field named ZZTOCID has been added to the SF Flight Data Model. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → Configuration Workbench. d) On the Configuration Workbench screen, choose SF. e) On the Data Model: SF,MDGFoundation Example: Flight Data Model screen, in the Entity Types section, in the entity types list, choose PFLI. f) In the Details: PFLI section, choose the Attributes tab. g) On the Attributes tab, choose ZZTOCID. h) On the Data Model: SF,MDGFoundation Example: Flight Data Model screen, on the Attributes tab, verify the entry ZZOCID is in the table. i) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. 2. Verify that a new UI initial screen named USMD_ENTITY_VALUE2 has been added to the SF Flight Data Model. a) On the Display IMG screen, choose Master Data Governance → General Settings → UI Modeling → Edit UI Configuration. b) On the Manage UI Configurations screen, select SF, ZMDG_SF_APPL_FLIGHT_CQ. c) Choose Edit. d) On the Editor for the Web Dynpro ABAP Application Configuration screen, choose Continue in Display Mode.

190



e) On the Application Configuration ZMDG_SF_APPL_FLIGHT_CQ screen, in the Assign Web Dynpro Component table, in the Configuration Name column, choose ZMDG_SF_APPL_FLIGHT_OIF_CQ. f) Choose Edit. g) On the Component Configuration ZMDG_SF_APPL_FLIGHT_OIF_CQ, Variant "Flightschedule" screen, select Show UIBB Preview. h) In the Preview section, view the configuration results. i) Choose Close to close all of the internet browser windows and return to the Display IMG screen. 3. View the configuration of change request steps 01, 02, and 03 using the data in the following table. Step

Web Dynpro Application

Configuration Name

00

USMD_ENTITY_VALUE2


01

USMD_ENTITY_VALUE2


02

USMD_ENTITY_VALUE2


03

USMD_ENTITY_VALUE2


a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Configure Properties of Change Request Step → SFZ##. b) In the Display View "Type of Change Request": Overview screen, choose Type of Change Request → User Interface per Change Request Step. c) In the Change View "User Interface per Change Request Step": Overview screen, choose enter the data from the table. d) Choose Save. e) Choose Back until you return to the Display IMG screen. 4. Add a new change request step named Landing Quota Specialist using the data in the following table. Column

Value


SFZ##

CR Step

4

Description (Medium Text)

Check Landing Quota


191


a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Workflow → Rule-Based Workflow → Define Change Request Steps for Rule-Based Workflow. b) On the Change View " Workflow Step Numbers": Overview screen, choose New Entries. c) On the New Entries: Overview of Added Entries screen, enter the data from the table. d) Choose Save. e) Choose Back until you return to the Display IMG screen. 5. Verify that a new action named Check Landing Quota has been added to the SF Flight Data Model. a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Workflow → Define Actions for Change Request UIs. b) In the Information dialog box, choose Enter. c) On the Change View "Edit Actions": Overview screen, choose Check Landing Quota. d) Choose View Details. e) Choose Back until you return to the Display IMG screen. 6. Verify that a new change request step type has been added to the Check Landing Quota check request step 04. a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Workflow → Define Step Types and Assign Actions. b) In the Information dialog box, choose Enter. c) In the Change View "Step Types": Overview screen, in the Step Types list, choose Add Flight Connection Details (incl. Check Quota). d) On the Change View "Step Types": Details screen, locate the Add Flight Connection Details (incl. Check Quota) entry. e) Choose Step Types → Assign Actions. f) On the Change View "Assign Actions": Overview screen, view the assigned actions. g) Choose Back until you return to the Display IMG screen. 7. Verify that the status for the Check Landing Quota change request step has been added to the change request. a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Edit Statuses of Change Requests. b) On the Change View "Maintenance of Status of Change Requests": Overview screen, choose Landing Quota to be Confirmed. c) View the entry for Landing Quota to be confirmed. d) Choose Back to return to the Display IMG screen. 8. Enhance the rule-based workflow for change request SFZ## by adding Check Landing Quota as a flight connection detail.

192



a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Workflow → Rule-Based Workflow → Configure Rule-Based Workflow. b) On the Process Definition of Rule-Based Workflow screen, in the Type of Change Request field, enter SFZ##. c) Choose Continue. d) On the BRFplus: Catalog Browser screen, in the Table Contents section, in the Step Type column, select 3 (Process Change Request). e) On the Business Rule Framework plus screen, choose USMD_SSW_CATA_SFZ## → Decision Tables → User Agent Decision Tables. f) Choose Edit. g) In the Table Contents section, in the PRC row, in the Step Type column, choose 3 (Process Change Request). h) Place your cursor in the Process Change Request field. i) In the All Values: FDT: Elementary Data Type Text (SSTRING) dialog box, choose x. j) Choose OK. 9. Add condition alias QUO to start the user determination using the data in the following table. Field

Value

Condition Alias

QUO

User Agt. Grp. No.

001

Step Type

3

User Agent Type

S

User Agent Value

50010130

a) On the Business Rule Framework plus screen, in the Table Contents table, select PRC. b) Choose Copy Row. c) Choose Insert Row. d) In the new row, enter the data from the table. e) Choose Save. f) Choose Activate. 10. Add the following data to the rule-based, single value decision table. Column

Value

CR Previous Step

01 (Add Connection Details)

Previous Action

CQ (Check Landing Quota)


193


a) On the Business Rule Framework plus screen, choose USMD_SSW_CATA_SFZ## → Decision Tables → Single Value Decision Tables. b) In the Table Contents table, choose Insert New Row. c) Add the data from the table. d) Choose Save. 11. Configure the Check Landing Quota change request step to navigate from the Landing Quota confirmation step to the Approve step. Field

Value

CR Previous Step

04

Previous Action

05

Condition Alias

APP

New Change Request Step

03

New CR Status

04

a) On the Business Rule Framework plus screen, in the Decision Table: DT_SINGLE_VAL_SFZ## section, in the Table Contents table, choose New Row. b) In the new row, enter the data from the table. c) Choose Save. d) In the Table Contents table, select the row with the entries 01 (Add Connection Details and 06 (Send for Revision). e) Choose Copy Row. f) Choose Insert Copied Row. g) In the new row, in the CR Previous Step column, enter the data from the table. h) Choose Save. i) Choose Activate. j) In the Confirm Activation dialog box, choose Yes. k) Choose Close to close the internet browser window and return to the Display IMG screen. 12. Add the step specific UI configuration to the change request step.

194

Field

Value

Step

04

UI Application Name

USMD_ENTITY_VALUE2

Configuration Name

ZMDG_SF_APPL_FLIGHT_CQ



a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Configure Properties of Change Request Step. b) On the Display View "Type of Change Request": Overview screen, choose Type of Change Request. c) In the Display View "Type of Change Request": Overview screen, in the Type of Change Request table, select SFZ##. d) Choose Type of Change Request → User Interface for Change Request Step. e) On the Change View "User Interface per Change Request Step": Overview screen, in the User Interface per Change Request Step table, in the Step column, select 04. f) Enter the data from the table. g) Choose Save. h) Choose Back until you return to the SAP Easy Access - User Menu screen. 13. Run the new process and verify that the requestor and specialist UIs are configured correctly using the data in the following table and note the change request number. Field

Value

Airline

LH

Flight Number

99##

Type

Change Flight Connection (Group ##) SFZ##

Description

LH 99##

Start Country Key

DE

Departure City

Frankfurt

Destination Country Key

US

Destination City

San Francisco

Note the change request number. Answers will vary. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Governance for Flight Data Model. e) On the Process Flight Connections section, choose Create Flight Connection.


195


f) On the Create Change Request: Create Flight Connection screen, enter the data from the table. g) Choose Continue. h) On the Create Change Request: Connection Number 99## screen, enter the data from the table. i) Choose Submit. j) On the Create Change Request Connection Number: 99## screen, note the change request number. 14. Process your change request. Field

Value

Departure Airport

FRA

Destination Airport

SFO

a) On the Create Change Request Connection Number: 99## screen, choose Show My Change Requests. b) On the My Change Requests screen, select your change request. c) On the Process Change Request: Connection Number 99## screen, enter the data from the table. d) Choose Check Quota. e) On the My Change Request screen, select your change request. f) On the Process Change Request: Connection Number 99## screen, choose Finalize Processing. g) On the My Change Request screen, select your change request. h) On the Approve Change Request: Connection Number 99## screen, choose Approve. i) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.

196






197


198


Unit 5

193

Learning Assessment

1. MDG is almost entirely switch enabled. Determine whether this statement is true or false. X

True

X

False

2. What is governance scope? Choose the correct answer. X

A It indicates which domains are available

X

B It indicates which fields are governed

X

C It indicates which forms are shown to the user

X

D It indicates the layout of a change request

3. How many roles are available for each domain? Choose the correct answer. X

A Three

X

B Four

X

C Five

X

D Six

4. Workflow activities can include methods that run in the background. Determine whether this statement is true or false. X

True

X

False


199


5. Master Data Governance supports two SAP business workflow templates? Determine whether this statement is true or false. X

True

X

False

6. How many steps are there in the Master Data Governance for Material approval process? Choose the correct answer. X

A 1

X

B 2

X

C 3

X

D 4

7. What application do you use to configure the UI? Choose the correct answer. X

A Floorplan Manager

X

B HTML

X

C Web Dynpro

X

D XML

8. What is context-based adaptation? Choose the correct answer.

200

X

A It is when the system administrator updates the user interface.

X

B It is when the user customizes the user interface.

X

C It is when the user interface influences user input.

X

D It is when user input influences the user interface.


Unit 5

195


1. MDG is almost entirely switch enabled. Determine whether this statement is true or false. X

True

X

False

2. What is governance scope? Choose the correct answer. X

A It indicates which domains are available

X

B It indicates which fields are governed

X

C It indicates which forms are shown to the user

X

D It indicates the layout of a change request

3. How many roles are available for each domain? Choose the correct answer. X

A Three

X

B Four

X

C Five

X

D Six

4. Workflow activities can include methods that run in the background. Determine whether this statement is true or false. X

True

X

False


201


5. Master Data Governance supports two SAP business workflow templates? Determine whether this statement is true or false. X

True

X

False

6. How many steps are there in the Master Data Governance for Material approval process? Choose the correct answer. X

A 1

X

B 2

X

C 3

X

D 4

7. What application do you use to configure the UI? Choose the correct answer. X

A Floorplan Manager

X

B HTML

X

C Web Dynpro

X

D XML

8. What is context-based adaptation? Choose the correct answer.

202

X

A It is when the system administrator updates the user interface.

X

B It is when the user customizes the user interface.

X

C It is when the user interface influences user input.

X

D It is when user input influences the user interface.


UNIT 6

Data Quality and Search Configuration

Lesson 1 Configuring Search and Duplicate Checks

204

Lesson 2 Building Validations for Data Quality Exercise 18: Build Validations for Data Quality

211 217

Lesson 3 Building Derivations for Data Quality Exercise 19: Test Custom Data Quality Rules

221 227

UNIT OBJECTIVES ●

Configure search and duplicate checks

●

Build validations for data quality

●

Build derivations for data quality


203

Unit 6 Lesson 1 198

Configuring Search and Duplicate Checks

LESSON OVERVIEW In this lesson, you will learn how to configure search and duplicate checks. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Data Search Capabilities

Figure 60: Data Search

The Search function is the initial action a user must take to work with data. MDG's powerful search feature offers the following benefits: ●

●

Efficiency—Fast responses save time when searching. Data Quality—Changing the correct data prevents existing data from being duplicated unnecessarily.

Configurable Search Providers

Figure 61: Configurable Search Providers

The following three search providers are available depending on your technical deployment and configuration:

204


Lesson: Configuring Search and Duplicate Checks

●

●

●

Exact search -

Based on a database query

-

Embedded in MDG

-

Requires no additional software components

Enterprise search -

Based on embedded Enterprise search and TREX

-

Free-text and attribute-based searches

-

Fuzzy search

Fuzzy search for address data -

Based on Business Address Services of SAP Basics (BAS-DES)

-

Requires an additional software component such as SAP Data Quality

Note: Exact search is embedded in the MDG Application Foundation and technically is always possible. However, due to applicability it is not enabled in the standard delivery of the MDG for Material master.

Search Results

Figure 62: Search Results

When searching for master data, the search results are created using the following method: 1. Search for active objects matching the search criteria. 2. Retrieve corresponding inactive objects from staging while ignoring the search criteria. 3. Search for inactive objects matching the search criteria. 4. Retrieve corresponding active objects while ignoring search criteria. In steps 1 and 3, the search is performed until the maximum number of results is reached. Therefore, the result table may contain more lines than the maximum number of results.

Search Provider Customization You can create additional search applications for the Search for Entities using Web Dynpro application USMD_Entity_Search, as well as the search provider. For each search application,


205

Unit 6: Data Quality and Search Configuration

you can assign as an access class the system to be used for the search. The system derives the access class from the data model. Using the BAdI Search for Entities (USMD_SEARCH), you can influence the search attributes and toolbar for the search results. If you do not want to use any of the access classes provided for a search application, create your own access class using the ABAP Workbench. The following search provider types can be chosen: ●

ES—Provider for enterprise search

●

AD—Provider for address search based on BAS-DES

●

DB—Provider for database search

The following options can be selected for the chosen providers: ●

●

Free text—The provider supports free-text searches and MDG displays the corresponding field in the search UI. Fuzzy—The provider supports error-tolerant searches and MDG displays a checkbox in the search UI to enable this mode.

Web Dynpro Search Application Several links to launch the search UI can be configured in the workcenters of NetWeaver Portal and NetWeaver Business Client. The Web Dynpro application USMD_ENTITY_SEARCH provides the search UI and displays the results. Information about which search provider to use is passed in the parameter SEARCH_MODE.

Fuzzy Search for Address Data MDG for Supplier supports the use of the BAS-DES interface for providing a fuzzy search for address data. The installation and configuration of an additional component such as SAP Data Quality Services, is required to perform this type of search.

Note: As a guideline, follow the information in SAP note 176559 for Business Address Services (BAS). By default, the link Fuzzy Search Using Addresses is not available in the workcenters for SAP Portal and SAP NetWeaver Business Client. You will have to enable fuzzy search as part of the configuration.

206



Figure 63: Fuzzy Search for Address Data

If the fuzzy search is used, the search criteria are limited to the fields that are supported by the BAS interface and the provider used. The search capabilities provided also depend on the provider used.

Duplicate Check Configuration

Figure 64: Duplicate Check Configuration

Duplicate check configuration promotes effectiveness and efficiency by preventing the creation of duplicate records in the following ways: ●

Checking early in the process

●

Embedding checks in the process

●

Detecting a high percentage of matches

Duplicate checking can be tailored through the provider by reusing search providers like Enterprise Search or SAP Data Quality. Providers can be selected by data model and entity type. Using Duplicate Checking To configure duplicate checking, configure the duplicate check for an entity type. Based on the data model, you define which search mode the system must use and which thresholds should apply. The following conditions apply when determining duplicate records: ●

Records that have a matching score lower than the low threshold are not considered duplicates.


207


●

●

Records that have a matching score that falls between the defined low and high thresholds are considered potential duplicates. Records that have a matching score higher than the high threshold are considered identical.

For business partners such as suppliers, the following search providers can be used: ●

Database search

●

Enterprise search

●

Business Address Services (BAS)

For Material, Enterprise Search (ES) can be used as the search provider for duplicate checking. The BAS setting ensures that the system searches for potential duplicates using the BAS-DES interface.

How to Configure Duplicate Checks Duplicate checks validate the data that you input and allow you to control the creation of duplicate data records. When you input data to create a new change request, the system compares the data you have entered against data already in the system. If the data you have entered matches one or more existing records, the system warns that you are about to create a duplicate record. For example, when you add a new business partner, you enter their name and address. The system compares the new data with existing business partner records in the database and identifies any records that are potential duplicates. Each potential duplicate record is given a score indicating the probability of it being a duplicate record. When a duplicate record is identified, you can either proceed with or cancel the creation of the new duplicate record. In business, it is sometimes necessary to create a duplicate record. For example, a bank customer may have a personal account and a commercial account, each containing common data. You can create a match profile to control which data attributes the system uses to identify duplicate records. For example, to check name and address data, you can configure your match profile to compare name, house number, street, and postal code and disregard the city and country data. You can specify mandatory fields, which must contain a value for the duplicate check to be performed. You can also assign a relative weight to each field indicating the importance of that field in identifying duplicate records. The system can then prioritize certain data attributes for the purposes of the comparison. When the system has completed a duplicate check, it displays a score for each potential duplicate record. This score is calculated based on relative weights and indicates the probability that the new record is a duplicate. For example, two addresses with identical postal codes could be considered more likely to be duplicate records than two addresses in the same country. 1. Selecting the search application as ES. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter.

208



c) On the Display IMG screen, choose General Settings → Data Quality and Search → Search and Duplicate Check → Define Search Applications. d) In the Information dialog box, choose Continue. e) On the Change View "Define Search Application": Overview screen, in the Define Search Application table, select ES. 2. Add a new duplicate check profile using the data in the following table. Field

Value

Data Model

MM

Entity Type

Material

Match Profile ID for Duplicate Check

MATCH_MM_MATERIAL

Short Description

MM Duplicate Check Profile

a) In the Dialog Structure navigation panel, double-click Define Search Application → Match Profile. b) On the Change View "Match Profile": Overview screen, choose New Entries. c) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Data Model field, choose the Select button. d) On the Data Model (1) screen, choose MM. e) Choose Copy. f) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Entity Type field, choose the Select button. g) On the Entity Type (1) screen, choose Material. h) Choose Copy. i) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Match Profile ID for Duplicate Check field, enter MATCH_MM_MATERIAL. j) Choose Save. k) In the Prompt for Workbench Request dialog box, in the Request field, choose New. l) In the Create Request dialog box, in the Short Description field, enter MM Duplicate Check Profile. m) Choose Save. n) Choose Enter. 3. View the fields that are being used as match criteria. a) On the New Entries: Overview of Added Entries screen, select the new entry. b) In the Dialog Structure navigation panel, double-click Define Search Application → Match Profile → Relevant Fields.


209


c) On the Change View "Relevant Fields": Overview screen, to see which fields are being used as match criteria. d) Choose Back until you return to the Display IMG screen. 4. Set up the duplicate check using the data in the following table. a) On the Display IMG screen, choose Master Data Governance → General Settings → Data Quality Search → Search and Duplicate Check → Configure Duplicate Check for Entity Types. b) On the Change View "Maintenance View for Duplicate Check Mode of Data Model" screen, choose New Entries. c) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Data Model field, choose the Select button. d) On the Data Model (1) screen, choose MM. e) Choose Copy. f) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Entity Type field, choose the Select button. g) On the Entity Type (1) screen, choose Material. h) Choose Copy. i) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Search Mode field, choose the Select button. j) On the Search Mode (1) screen, choose ES. k) Choose Copy. l) On the New Entries: Overview of Added Entries screen, in the Match Profile table, in the Maintenance View for Duplicate Check of Data Model field, enter MATCH_MM_MATERIAL. m) Choose Save. n) Choose Back until you return to the SAP Easy Access - User Menu screen.


210



Unit 6 Lesson 2 203

Building Validations for Data Quality

LESSON OVERVIEW In this lesson, you will learn how to build validations for data quality. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Inherited SAP ERP Validations

Figure 65: Inherited SAP ERP Validations

MDG uses validations to ensure data quality. When existing SAP ERP validations are reused they are referred to as inherited validations. The following are examples of inherited data validation: ●

Code lists such as regions or states in a country

●

Simple checks such as format-based checking of postal codes

●

Rules modeled using Business Rules Framework plus (BRFplus)

●

Rules coded using Business Add-Ins (BAdIs), which can accommodate user requirements too specific to be included in the standard delivery

The domains for Supplier and Material inherit validations of the reuse active area including customization and consistency checks in SAP ERP.

Self-Defined Validations

Figure 66: Self-Defined Validations


211


BRFplus can be used to create self-defined validation rules. Rule definitions are specific to a single data model. Each data model contains its own BRFplus validation application. Each application contains a folder called CHECK_ENTITY under which all check functions are built. Validation functions must follow the naming convention CHECK_. These functions only validate single entities. Cross-entity validation is not possible using this method.

Self-Defined Validations using Business Add-Ins

Figure 67: Self-Defined Validations Using Business Add-Ins

You can use BAdIs to specify check on entities, change requests, and editions. When an entity is checked, the method CHECK_ENTITY is called once for each entity type in the changed master data. Using this method, you can define all rules for checking the entities in the data model. When a change request is checked, the following methods are called in the following order: ●

●

●

CHECK_CREQUEST_START CHECK_CREQUEST is called once for each entity type of the changed master data in the change request CHECK_CREQUEST_FINAL

When an edition is checked, the following methods are called consecutively: ●

●

●

CHECK_EDITION_START CHECK_EDITION is called once for each entity type of the changed master data in the edition CHECK_EDITION_FINAL

Standard Settings In the standard system, the BAdI implementation USMDZ3_RULE_BADI is activated for the delivered data model 0F. This implementation is automatically executed for this data model and is filter-dependent. The data model MODEL and the entity type ENTITYTYPE serve as filters. The USMDZ3_RULE_BADI is located in the enhancement implementation USMDZ3_IMP_RULE_SERVICE_BADI. This BAdI is not for multiple use. Similar to derivations, BAdI USMD_RULE_SERVICE_CROSS_ET can be used for cross-entity validations. However, this BAdI only returns warning messages. All error messages are converted to warnings so the correction of errors identified using this BAdI cannot be enforced. Other techniques such as enrichment spots can be used to enforce cross-entity error correction.

212


Lesson: Building Validations for Data Quality

Validation of Complete Address Information

Figure 68: Validation Of Complete Address Information

SAP Business Address Services (BAS) offers functions for managing addresses in the Supplier domain. An address is subordinate to an associated object such as a customer, a purchase order, or a plant. Validation can take the form of either simple checks or selection lists. Using BAS for address validation requires the installation and configuration of an additional component: SAP Business Objects Data Quality Management (DQM). DQM provides address validation and duplicate address checking for business partners. The following steps describe the overall process of address validation: 1. An incomplete or erroneous address is entered. 2. A selection list is proposed by address validation. 3. The user selects from the list. 4. The address validation completes the information. 5. The correct address is entered for the business partner. Data quality remediation provides process integration of identifying master data objects with errors in a data quality tool. For example, using the SAP Information Steward as a data quality tool can correct data that is being processed in MDG. To use this process, you will have to implement SAP Information Steward or a third-party data quality tool that is not part of the delivery of MDG. After you have implemented a data quality tool, you can use the data quality remediation to do the following: ●

●

●

Analyze master data according to a set of data quality rules to detect objects with errors Select filtering criteria by the master data specialist if a data quality tool offers filtering of objects with errors according to a rule (or a set of rules) Retrieve objects with errors and display them for investigation by the master data specialist The master data specialist selects an object with errors and creates a change request for the data quality remediation.

Configuration Process The following high-level steps describe the configuation process: 1. Execute the Customizing activity Define Data Quality Service. 2. Copy the Floorplan Manager (FPM) Configuration Templates. 3. Adapt the Copied Configurations of the FPM. 4. Configure Change Request Process for DQR.


213


5. Provide the DQR function to your users by adding the Web Dynpro application with the copy of the DQR configuration to the role menu.

How to Create a Check Function Clarify that the following is the create a check function in BRFplus that is relevant for data model MM. Note: Complete demonstration steps 1 through 4 before students start the exercise Create a Check Function. If you do not complete demonstration steps 1 through 4, the exercise will fail. In this demonstration, when values include ##, replace the characters with your group number. 1. Define a new validation check rule based on data model MM. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → Data Quality and Search → Validations and Enrichments → Define Validation and Derivation Rules. d) On the Definition of Rules for Validations and Derivations screen, in the Data Model field, enter MM. e) Choose Continue to open Business Rule Framework plus. 2. Create a new function using the data in the following table. Field

Value

Name

CHECK_MATERIAL

Short Text

Check Material

Text

Check the MDG Material field values

a) On the Business Rule Framework plus screen, choose FMDM_MODEL_MM. b) In the Check Entity context menu, choose Create Object Node → Create Function. c) In the Create Function dialog box, enter the data from the table. d) Choose Create and Navigate to Object. e) In the Node Check Material dialog box, choose OK. 3. Add a signature to the new function using the data in the following table.

214

Field

Operator

Value

Data Object Type

is equal to

Structure



Field

Operator

Value

Name

is equal to

Mat*

a) On the Business Rule Framework plus screen, choose FMDM_MODEL_MM → Trigger Function → Check Entity → Check Material. b) In the Function: CHECK_MATERIAL, Check Material section, select the Signature tab. c) Choose Add Existing Data Object. d) In the Object Query dialog box, enter the data from the table. e) Choose Search. f) In the Result List, choose Material. 4. Create a new ruleset using the data in the following table. Field

Value

Name

RS_CHECK_MATERIAL

Short Text

RS_CHECK_MATERIAL

Text

Ruleset for general material checks in MDG

a) In the Function: CHECK_MATERIAL, Check Material section, select the Assigned Rulesets tab. b) In the Ruleset table, choose Create Ruleset. c) In the Create Ruleset dialog box, enter the data from the table. d) Choose Create and Navigate to Object. e) In the Changes Will be Lost dialog box, choose Yes. f) On the Ruleset: RS_CHECK_MATERIAL screen, choose Save. 5. Create a rule for the user MDG100-##. a) On the Ruleset: MDG100_##_RS01_CHECK_MAT screen, in the RS Check Material section, in the Rules section, choose Insert Rule → Create. b) On the (1) Rule: No Description is Available (Enabled Rule) screen, choose Assign Condition → Use Value Range From → Default Objects → Current User. c) In the current user row, in the second field, enter MDG100-##. d) Choose Change Condition → Add More Conditions. e) In the If section, in the Or drop-down menu, choose And. f) Next to the field, choose the context menu button. g) In the context menu, choose Use Direct Value Range From → Context → Laboratory. h) In the If section in the Material-Laboratory row, in the is equal to drop-down menu, choose is initial. 6. Create a new log using the data in the following table.


215


Field

Value

Type

Log Message (Action)

Name

MDG100-##-MDG_LAB_Initial

Short Text

## Msg Lab Initial

Text

## Message that Laboratory is initial

Is Reusable

Select checkbox.

Text

Group ## - Please maintain laboratory

Type

Warning

a) On the (1) Rule: No Description is Available (Enabled Rule) screen, RS Check Material section, next to the label Then, choose Add → Perform Action → Create. b) In the Create Object dialog box, enter the data from the table. c) Choose Create and Navigate to Object. d) In the message dialog box, choose Yes. e) On the Log Message: MDG100_##_MSG_LAB_INITIAL, ## Msg Lab Initial screen, enter the data from the table. f) Choose Save. g) Choose Activate. h) Choose Back until you return to the RS_CHECK_MATERIAL screen. 7. Activate the ruleset that contains the new rule. a) On the Rule: RS_CHECK_MATERIAL screen, choose Save. b) Choose Activate. c) On the Confirm Activation dialog box, choose Yes. d) Choose Back to return to the Function: CHECK_MATERIAL, Check Material screen. 8. Verify that the ruleset is assigned and active. a) On the Function: CHECK_MATERIAL, Check Material screen, select the Assigned Rulesets tab. b) Choose Close to the internet browser window and return to the SAP Easy Access - User Menu screen.

How to Build Validations for Data Quality For the demonstration steps and data, see the exercise Build Validations for Data Quality.

216



Build Validations for Data Quality

Business Example You are a business administrator for a CD company that has recently acquired another company. The material specialists from the acquired company have no experience with SAP ERP. You have been asked to build some custom validations to ensure that the data they enter for materials meet the required standards. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Define a new validation check rule based on data model MM. 2. Create a rule for the user MDG100-##. 3. Create a new log using the data in the following table. Field

Value

Type


Name


Short Text

## Msg Lab Initial

Text


Is Reusable

Select checkbox.

Text


Type

Warning

4. Activate the ruleset that contains the new rule. 5. Verify that the ruleset is assigned and active.


217


Build Validations for Data Quality

Business Example You are a business administrator for a CD company that has recently acquired another company. The material specialists from the acquired company have no experience with SAP ERP. You have been asked to build some custom validations to ensure that the data they enter for materials meet the required standards. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Define a new validation check rule based on data model MM. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → Data Quality and Search → Validations and Enrichments → Define Validation and Derivation Rules. d) On the Definition of Rules for Validations and Derivations screen, in the Data Model field, enter MM. e) Choose Continue to open Business Rule Framework plus. f) On the Business Rule Framework plus screen, choose FMDM_MODEL_MM. 2. Create a rule for the user MDG100-##. a) On the Function: CHECK_MATERIAL, Check Material screen, select the Assigned Rulesets tab, b) On the Assigned Rulesets tab, choose RS_CHECK_MATERIAL. c) On the Ruleset: MDG100_##_RS01_CHECK_MAT screen, in the RS Check Material section, in the Rules section, choose Insert Rule → Create. d) On the (1) Rule: No Description is Available (Enabled Rule) screen, choose Assign Condition → Use Value Range From → Default Objects → Current User. e) In the current user row, in the second field, enter MDG100-##. f) Choose Change Condition → Add More Conditions. g) In the If section, in the Or drop-down menu, choose And. h) Next to the field, choose the context menu button. i) In the context menu, choose Use Direct Value Range From → Context → Laboratory. j) In the If section in the Material-Laboratory row, in the is equal to drop-down menu, choose is initial.

218



3. Create a new log using the data in the following table. Field

Value

Type


Name


Short Text

## Msg Lab Initial

Text


Is Reusable

Select checkbox.

Text


Type

Warning

a) On the (1) Rule: No Description is Available (Enabled Rule) screen, RS Check Material section, next to the label Then, choose Add → Perform Action → Create. b) In the Create Object dialog box, enter the data from the table. c) Choose Create and Navigate to Object. d) In the message dialog box, choose Yes. e) On the Log Message: MDG100_##_MSG_LAB_INITIAL, ## Msg Lab Initial screen, enter the data from the table. f) Choose Save. g) Choose Activate. h) Choose Back until you return to the RS_CHECK_MATERIAL screen. 4. Activate the ruleset that contains the new rule. a) On the Rule: RS_CHECK_MATERIAL screen, choose Save. b) Choose Activate. c) On the Confirm Activation dialog box, choose Yes. d) Choose Back to return to the Function: CHECK_MATERIAL, Check Material screen. 5. Verify that the ruleset is assigned and active. a) On the Function: CHECK_MATERIAL, Check Material screen, select the Assigned Rulesets tab. b) Choose Close to the internet browser window and return to the SAP Easy Access - User Menu screen.


219



220



Unit 6 Lesson 3 211

Building Derivations for Data Quality

LESSON OVERVIEW In this lesson, you will learn how to build derivations for data quality. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Self-Defined Derivations

Figure 69: Self-Defined Derivations

Values of change request fields can be derived using BRFplus. This functionality is accessed in transaction MDGIMG. When this activity is started, the system generates a custom BRFplus application for the data model being configured using the naming convention: FMDM_MODEL_<2-char data model name>. For example, the name for data model MM would be FMDM_MODEL_MM. A catalog with a predefined structure is created in the application. By default, the system displays object descriptions instead of technical names. In the following sample data model structure, the technical names are used: ●

●

TRIGGER_FUNCTION (folder) -

CHECK_ENTITY (folder)

-

CHECK_CHANGE_REQUEST (folder)

-

CHECK_EDITION (folder)

-

CHECK_ENTITY_HRY (folder)

-

CHECK_CHANGE_REQUEST_HRY (folder)

-

CHECK_EDITION (folder)

-

DERIVATION (folder)

DATA_OBJECT (folder containing all data objects and entities of the specific data model being validated) -

SAPFMDM_CREQUEST_TYPE (data object)

-

SAPFMDM_CREQUEST (data object)


221


The auto-generated BRFplus application is technically a custom object that follows the sample structure with a pre-defined, case-sensitive naming convention. The MDG application framework looks for specific folder names and then looks for trigger functions with specific naming conventions within these folders. Add single entity derivation rule functions to the DERIVATION folder following this naming convention: DERIVE_. For example, the derivation rule for the entity ACCOUNT is DERIVE_ACCOUNT. If you want to change the data model after the BRFplus application is generated, run program USMD_ADAPT_BRF. This application only regenerates the folder structure and data objects. Only objects that follow the naming convention are impacted. Since the BRFplus application is a custom object, additional custom folders, functions, and data objects can be added as long as they follow the naming convention. The regeneration program does not overwrite any files. The application USMD_ADAPT_BRF application only works for single entities. It does not handle cross-entity derivations. Any single derivation function can only contain fields from the same entity. You can run cross-entity derivations using a special BAdI.

Self-Defined Derivations using Business Add-Ins

Figure 70: Self-Defined Derivation Using Business Add-In

You can use a BAdI to specify which field values are to be derived from the values of other fields in the master data. Standard Settings In the standard system, the BAdI implementation USMDZ3_RULE_BADI is activated for the delivered data model 0F. This implementation is automatically executed for this data model. This BAdI is filter-dependent, and data model MODEL and the entity type ENTITYTYPE serve as filters. This BAdI is not for multiple use. The USMDZ3_RULE_BADI is located in the enhancement implementation USMDZ3_IMP_RULE_SERVICE_BADI. BAdI Implementation MDG_BS_BP_DESCRIPTION You can use the BAdI method IF_EX_USMD_RULE_SERVICE~DERIVE_ENTITY from the BAdI implementation MDG_BS_BP_DESCRIPTION to derive the business partner description from a business partner's name and address. If you want to create a customer-specific BAdI implementation for the same filter value (ENTITYTYPE = BP_HEADER), deactivate the BAdI implementation MDG_BS_BP_DESCRIPTION before activating the customer-specific BAdI implementation. To retain the function of the BAdI implementation MDG_BS_BP_DESCRIPTION and to make sure that you receive corrections from SAP Notes, derive a customer-specific implementing class from implementing class CL_MDG_BS_BP_DESCRIPTION and redefine its methods as required. BAdI Implementation MDG_BS_BP_TAXJURCODE You can use the BAdI method IF_EX_USMD_RULE_SERVICE~DERIVE_ENTITY from the BAdI implementation MDG_BS_BP_TAXJURCODE to derive the tax jurisdiction code from the address. If you want to create a customer-specific BAdI implementation for the same filter value (ENTITYTYPE = AD_POSTAL), deactivate the BAdI implementation MDG_BS_BP_TAXJURCODE before activating the customer-specific BAdI implementation.

222


Lesson: Building Derivations for Data Quality

To retain the function of the BAdI implementation MDG_BS_BP_TAXJURCODE and to make sure that you receive corrections from SAP Notes, derive a customer-specific implementing class from implementing class CL_MDG_BS_BP_TAXJURCODE and redefine its methods as required. BAdI Implementation MDG_BS_SUPPL_ACCGRP_ID You can use the BAdI method IF_EX_USMD_RULE_SERVICE~DERIVE_ENTITY from the BAdI implementation MDG_BS_SUPPL_ACCGRP_ID to derive the account group and vendor number from the business partner. If you want to create a customer-specific BAdI implementation for the same filter value (ENTITYTYPE = BP_HEADER), deactivate the BAdI implementation MDG_BS_SUPPL_ACCGRP_ID before activating the customer-specific BAdI implementation. To retain the function of the BAdI implementation MDG_BS_SUPPL_ACCGRP_ID and to make sure that you receive corrections from SAP Notes, derive a customer-specific implementing class from implementing class CL_MDG_BS_SUPPL_ACCGRP_ID and redefine its methods as required. Note: This BAdI uses interface IF_EX_USMD_RULE_SERVICE. For more information, display the interface in the Class Builder. BAdI Implementation USMD_RULE_SERVICE_CROSS_ET BAdI USMD_RULE_SERVICE_CROSS_ET can be used for cross-entity derivations. This BAdI is used when one or more entities influence the derivation of fields in a different entity. Data Quality Remediation Configuration The following prerequisites are required to use data quality remediation in MDG: ●

●

●

Install a data quality tool in your system landscape. Install a data quality connector in the MDG system. The data quality connector consists of an ABAP class that implements the interface IF_MDG_DQR_DQ_SERVICE Optionally, implement the BAdI Event Handling for Data Quality Remediation. Note: For more information, see the documentation of this BAdI under General Settings → Data Quality and Search → Business Add-Ins.

Use the following configuration steps to use the data quality remediation in MDG: 1. Execute the Customizing activity Define Data Quality Service. 2. Copy the Floor Plan Manager (FPM) Configuration Templates. 3. Choose a package for the copied configurations. 4. Configure the change request process for DQR.


223


How to Create a Derivation Function for Data Quality As a Master Data Requestor you have been asked to ensure that if Industry Sector data is not maintained for a material that the Industry Sector setting is replaced by default information. To ensure the data quality, build a new customer derivation function.

Note: Complete this demonstration before students start the exercise Create a Derivation Function for Data Quality. If you do not complete this demonstration, the exercise will fail. 1. Create a new derivation function using the data in the following table. Field

Value

Name

DERIVE_MATERIAL

Short Text

Derive Material

Text

Derive the MDG Material field values

a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → Data Quality and Search → Validations and Enrichments → Define Validation and Derivation Rules. d) On the Definition of Rules for Validations and Derivations screen, in the Data Model field, enter MM. e) Choose Continue to open Business Rule Framework plus. f) On the Business Rule Framework plus screen, choose FMDM_MODEL_MM. g) In the Derivation context menu, choose Create Object Node → Create Function. h) In the Create Function dialog box, enter the data from the table. i) Choose Create and Navigate to Object. j) In the Node Derive Material dialog box, choose OK. 2. Add a signature to the new function using the data in the following table. Field

Operator

Value

Data Object Type

is equal to

Structure

Name

is equal to

Mat*

a) On the Business Rule Framework plus screen, choose FMDM_MODEL_MM → Trigger Function → Derivation.

224



b) In the Function: DERIVE_MATERIAL, Derive Material section, select the Signature tab. c) Choose Add Existing Data Object. d) In the Object Query dialog box, enter the data from the table. e) Choose Search. f) In the Result List, choose Material. 3. Create a new ruleset using the data in the following table. Field

Value

Type

Ruleset

Name

RS Derive Material

Short Text

RS Derive Material

Text

Ruleset for general material derivation in MDG

Application

FMDM_MODEL_MM

a) In the Function: DERIVE_MATERIAL, Derive Material section, select the Assigned Rulesets tab. b) Choose Create Ruleset. c) In the Create Ruleset dialog box, enter the data from the table. d) Choose Create and Navigate to Object. e) In the Changes Will be Lost dialog box, choose Yes. f) In the Ruleset: RS_DERIVE_MATERIAL, RS Derive Material section, in the Rules section, choose Insert Rule → Create. 4. Add a new derivation rule to the derivation rule set. Field

Operator

Value

Data Object Type

is equal to

Element

Text

is equal to

Ind*

a) On the (1) Rule: No Description is Available (Enabled Rule) screen, choose Assign Condition → Use Value Range From → Default Objects → Current User. b) Next to the Current User row, in the second field, enter your user ID. c) Choose Change Condition → Add More Conditions. d) In the If section, in the Or drop-down menu, choose And. e) Next to the field, choose the context menu button. f) In the context menu, choose Use Direct Value Range From → Context → More. g) In the Content Query dialog box, enter the data from the table.


225


h) Choose Search. 5. Assign the Industry field to the derivation rule. Field

Operator

Value

Data Object Type

is equal to

Element

Text

is equal to

Ind*

a) In the Content Query dialog box, in the Result List, choose Material → Industry b) On the (1) Rule: No Description is Available (Finished Rule) screen, in the If section in the Material-Laboratory row, in the is equal to drop-down menu, choose is initial. c) In the Then section, choose Assign Value to Context → Context → More. d) On the Content Query dialog box, enter the data from the table. e) Choose Search. 6. Set the derivation rule to determine the value of a field. a) In the Content Query dialog box, in the Search Results table, choose Material → Industry. b) Choose OK. c) On the (1) Rule: No Description Available (Enabled Rule) screen, in the Then section, in the (1) Change Value Of row, in the second field, enter M. d) Choose OK. e) On the Ruleset: RS_DERIVE_MATERIAL, RS Derive Material screen, choose Save. f) Choose Activate. g) On the Confirmation Activation dialog box, choose Yes. h) Choose Close to close the internet browser window.

How to Test Custom Data Quality Rules For the demonstration steps and data, see the exercise How to Test Custom Data Quality Rules.

226



Test Custom Data Quality Rules

Business Example As a Master Data Steward, you are concerned about the quality of records created in MDG. You have built some custom data quality rules to preserve data quality levels. To test these rules, create a material record. In this exercise, when values include ##, replace the characters with the number your instructor assigned to you. 1. Create a new material using the data in the following table to test the new data quality rule. Field

Value

Material

MDG100-##-001

Change Request Type

MAT01

Description

Test Group ##

Base Unit of Measure

EA

Material Type

FERT

Description

Test Group ##


227


Test Custom Data Quality Rules

Business Example As a Master Data Steward, you are concerned about the quality of records created in MDG. You have built some custom data quality rules to preserve data quality levels. To test these rules, create a material record. In this exercise, when values include ##, replace the characters with the number your instructor assigned to you. 1. Create a new material using the data in the following table to test the new data quality rule. Field

Value

Material

MDG100-##-001

Change Request Type

MAT01

Description

Test Group ##


EA

Material Type

FERT

Description

Test Group ##

a) On the SAP Easy Access – User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) In the navigation panel, choose Change Requests → Material Processing → Create Material. f) On the Material: New screen, enter the data from the table. Hint: Expand the Descriptions section to find the Description field.

g) Choose Continue. h) On the Material: New, MDG100-##-001 screen, enter the data from the table. i) Choose Check.

228



j) Note the warning message in the screen header. k) Choose Cancel. l) In the Warning dialog box, choose OK. m) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.


229



230



Unit 6

219

Learning Assessment

1. What search providers are available in MDG? Choose the correct answers. X

A Fuzzy search

X

B Enterprise search

X

C Exact search

X

D HTML search

2. You cannot create additional search applications for the Search for Entities. Determine whether this statement is true or false. X

True

X

False

3. What do build validation do? Choose the correct answer. X

A Check change requests

X

B Ensure data quality

X

C Validate work flow

X

D Validate the UI

4. BRFplus can be used to create customized data validation rules and can also be used to derive values. Determine whether this statement is true or false. X

True

X

False


231


5. You can use BAdIs to create what customer-specific checks? Choose the correct answers.

232

X

A Change requests

X

B Editions

X

C Entities

X

D Field values

X

E User authorizations


Unit 6

221


1. What search providers are available in MDG? Choose the correct answers. X

A Fuzzy search

X

B Enterprise search

X

C Exact search

X

D HTML search

2. You cannot create additional search applications for the Search for Entities. Determine whether this statement is true or false. X

True

X

False

3. What do build validation do? Choose the correct answer. X

A Check change requests

X

B Ensure data quality

X

C Validate work flow

X

D Validate the UI

4. BRFplus can be used to create customized data validation rules and can also be used to derive values. Determine whether this statement is true or false. X

True

X

False


233


5. You can use BAdIs to create what customer-specific checks? Choose the correct answers.

234

X

A Change requests

X

B Editions

X

C Entities

X

D Field values

X

E User authorizations


UNIT 7

Data Transfer and Data Replication

Lesson 1 Transferring Data within Master Data Governance Exercise 20: Export Data within Master Data Governance Exercise 21: Import Data within Master Data Governance

236 241 249

Lesson 2 Configuring Data Replication within Master Data Governance Exercise 22: Configure Data Replication Exercise 23: Replicate Data within Master Data Governance

253 261 267

UNIT OBJECTIVES ●

Export data within Master Data Governance

●

Import data within Master Data Governance

●

Configure data replication within Master Data Governance


235

Unit 7 Lesson 1 224

Transferring Data within Master Data Governance

LESSON OVERVIEW In this lesson, you will learn how to export data within Master Data Governance and import data within Master Data Governance. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


●


Methods to Export Master Data

Figure 71: Methods to Export Master Data

Depending on the release of the SAP client system, the three different scenarios shown in the figure Methods to Export Master Data are possible when you export master data.

236


Lesson: Transferring Data within Master Data Governance

Note: ●

●

Financials does not use the Data Export/Data Import Framework. It uses the File Upload/File Download functionality instead. For business partners, the transaction BUPA_SEND, which includes full address data, is available.

Export Process Details To export material master data, configure a logical system for XML-IDOC extraction to the application server file system in each client system. The following steps are required: 1. Create a logical system. 2. Add IDoc types MATMAS and CLFMAS to Distribution Model (BD64). 3. Create an Outbound Partner Profile (WE20). 4. Create an XML-file port for IDoc processing (WE21).

Note: These prerequisites are also required for exports based on CREMAS and CREMDM.

Export Options

Figure 72: Export Options

Configure the following export options to export master data and mapping information:


237

Unit 7: Data Transfer and Data Replication

●

Description

●

Object type

●

Package size

●

Target directory

●

Communication channel

●

Variant

Export Settings Set the following options to export data: ●

Object type—Set business partners, value mapping, and key mapping.

●

Description—Identify export processes used in monitoring and logging.

●

Variant—Select options for the object type to be exported.

●

File prefix—Enter the prefix used for file names.

Export Object Types The export object type is a master data object like Business Partner or Supplier, but the system can also export value-mapping, key-mapping, and customizing data that is bound to the master data objects. Value-mapping is used to export customizing code lists from a client system. Code lists are used in the MDG system for mappings that are performed in the data replication processes. A key mapping export is used to export information about duplicate records from the MDG system to an external data quality service. Customizing data used for reference can be extracted through the use of additional objects in the variant. Technical Settings Set the following technical setting options to export data: ●

Communication channel—Export data to a file for consumption by a service. Select Export to File for mass data. If Consumption by a Service is chosen, the data is sent by using the respective service

●

Target directory—Choose the logical directory that is used for the export.

●

Package size—Set the number of objects per file.

●

●

Target System—Include value mapping in the master data export process and extract the value-mapping data to define the target system. A target system might have a different configuration leading to the need for value-mapping between the configurations. The system executes the value-mapping based on the target system specified in the export Delta export—Only export records that have changed since the most recent export that used the same variant. Delta extractions also depend on the variant. A new variant always exports the objects according to the selection options specified.

Schedule Settings Set the following scheduling options to export data:

238



●

●

Scheduling—Set this flag to indicate whether the export is done immediately or scheduled for later. Date—Schedule a specific date and time for export.

Set the following parallel processing setting options to export data: ●

Parallel processing—Set this flag to indicate whether the export is done using parallel processes.

●

Queue name—Enter the qRFC queue name that is registered in transaction SMQ2.

●

Number of processes—Enter the maximum number of processes used in parallel.

Export Data Actions The following actions can be initiated when exporting data: ●

●

●

The Export Data action starts the master data export process. If a variant has been defined, the Number of Selected Objects action allows you to determine the number of objects to be exported. This number can be greater than the number selected, because additional business partner relationships might be exported in addition to the business partner objects. The Display Monitoring action allows you to go directly to the monitoring process once the data export has been started.

Processes and Logs

Figure 73: Processes and Logs

From the Monitor Data Transfer screen, logs can be displayed for each master data transfer process: export, conversion, and import.

How to Export Data within Master Data Governance For the demonstration steps and data, see the exercise Export Data within Master Data Governance.


239


240



Export Data within Master Data Governance

Business Example Your company has decided that the material master data from an acquired SAP ERP system should be included in your company's SAP MDG system. Export the master data records from the existing SAP ERP system before importing them into MDG using the import framework. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Create a material using the data in the following table. Screen Name

Field

Value

Create Material (Initial Screen)

Material

MAT_##


Material Type

FERT


Industry Sector

M

Create Material MAT_## (Finished Product)

Description

Material ##



EA


Old Material Number

RERP39-##

2. Extract material MAT_## using the data in the following table. Field

Value

Material

MAT_##

Logical System

MDGMAT

3. View the IDoc number. Field

Value

Search in Segment

E1MARAM

Search in Field

MATNR

For Value

MAT_##


241


Export Data within Master Data Governance

Business Example Your company has decided that the material master data from an acquired SAP ERP system should be included in your company's SAP MDG system. Export the master data records from the existing SAP ERP system before importing them into MDG using the import framework. In this exercise, when the values include ##, replace the characters with the number your instructor assigned to you. 1. Create a material using the data in the following table. Screen Name

Field

Value


Material

MAT_##


Material Type

FERT


Industry Sector

M


Description

Material ##



EA


Old Material Number

RERP39-##

a) Log on to client 900. b) On the SAP Easy Access - User Menu screen, in the Command field, enter MM01. c) Choose Enter. d) On the Create Material (Initial Screen), enter the data from table. e) On the keyboard, choose ENTER. f) In the Select Views dialog box, choose View Basic Data 1. g) Choose Enter. h) On the Create Material MAT_## (Finished Product) screen, enter the information from the table. i) Choose Save.

242



j) Choose Back until you return to the SAP Easy Access - User Menu screen. k) Log off of client 900. 2. Extract material MAT_## using the data in the following table. Field

Value

Material

MAT_##

Logical System

MDGMAT

a) Log on to client 800. b) On the SAP Easy Access - User Menu screen, in the Command field, enter BD10. c) Choose Enter. d) On the Send Material screen, enter the data in the table. e) Choose Enter. f) Choose Execute. g) In the two information dialog boxes that appear, choose Enter. h) Choose Back until you return to the SAP Easy Access - User Menu screen. 3. View the IDoc number. Field

Value

Search in Segment

E1MARAM

Search in Field

MATNR

For Value

MAT_##

a) On the SAP Easy Access - User Menu screen, in the Command field, enter WE09. b) Choose Enter. c) On the IDoc Search for Business Content screen, in the Criteria for Search in Data Records section, enter the data from the table. d) Choose Execute. e) On the IDoc Search for Business Content screen, in the IDoc number column, doubleclick the IDoc number. f) On the IDoc Display screen, choose IDoc → Data Records → E1MARAM. g) In the Content of Selected Segment section, view the extraction details. h) Choose Back until you return to the SAP Easy Access - User Menu screen.


243


Import Process Details

Figure 74: Import Master Data

You can choose a directory from the logical directories defined in transaction FILE and in the Data Transfer Customizing Activities. You can create several object-specific directories or directories specific for load processes. You can use transaction CG3Z to upload data from your local file system to the application server and upload other options such as remote access to the application server directories.

Import Options Select Options You can set the following import options: ●

●

●

●

●

●

●

●

●

●

●

●

●

●

Object Type—Select the objects to import including business partner, business partner relationship, material classification, value mapping, and key mapping. Description—Enter text that describes the import processes in monitoring and logging. Overwrite—Control whether an import overwrites existing files in the target system. For business partners, including suppliers, vendors, and customers, overwrite is the default option and cannot be changed. Custom Converter—Select to use a user-defined conversion. This option is not needed if the imported file format is standard IDoc or SOA-based. Governance—Set to have data loaded into the staging area and create a change request. Duplicate Check—Set to check for duplicate information during import if the change request type defines a duplicate check. Post Processing—Set for failed objects. Post processing can be done manually using either Forward Error Handling or IDoc Monitoring, or automatically using a change request process. Change Request Type—Set to route an imported object automatically to a workflow. Scheduling—Set to determine if the import is completed immediately or scheduled for a specific time. Date—Set to schedule a specific date and time. Parallel Processing—Set to determine whether the import is completed using parallel processes. Queue Name—Enter the qRFC name registered in transaction SMQ2. Number of Processes—Enter the maximum number of processes that can be completed in parallel. Data Sources—Select the source directories to import objects from.

You can have multiple associations for each object and subobject type.

244



Object Type The object type is a master data object like Business Partner or Supplier, but the system can also import value-mapping and key-mapping data. Use value-mapping to transfer customizing code lists from one system to another. These code lists can be used in the MDG system for mappings that are performed in data replication processes. Key-mapping export is used to export information about duplicates from the MDG system to an external Data Quality Service. You can also use the SAP report R_MDG_IDM_UPLOAD to import key-mapping data from plain text or comma separated value (CSV) files. For a text file, all objects are stored directly one below the other to build one mapping group. One mapping object is stored with all identifiers in one line. Each field is separated by a semicolon (;), and each mapping group is separated by a line containing a forward slash (/) in the first column. The following example shows the sequence of the fields: ObjectType;GroupReference;SystemReference;ObjectIdentifierType; BusinessSystem;IDValue;...;ObjectIdentifierType;BusinessSystem; IDValue ObjectInformation:(ObjectType;GroupReference;SystemReference) Identifier 1-n: (ObjectIdentifierType;BusinessSystem;IDValue) For a CSV file, each line contains the data of one mapping group object. The fields have the same order as text files and are separated by a semicolon (;), and each mapping group is separated by a line containing a forward slash (/) in the first column. Custom Converter Third party systems may not be able to create supported message types during an MDG upload. Use an external conversion to support third-party formats, or implement a converter BAdI for the upload. Converter and BAdIs are defined in MDG Customizing.

Import Actions

Figure 75: Import Master Data Actions

Import Master Data Actions


245


The following actions are available when importing master data: ●

Import and Simulate Import—Starts the import or simulated import process

●

Custom Converter settings—Includes a customer-defined converter in the import process

●

Display Monitoring—Monitors import progress

Import Process Monitoring and Details

Figure 76: Import Master Data Monitoring Processes and Logs

You can monitor import processes and logs using the Web Dynpro application MDG_BS_DL_MONITOR_CONF. This application displays logs for data export, conversion, and import. You can monitor import details using the Web Dynpro application MDG_BS_DL_MONITOR_CONF. This application generates a list of import processes that can be used as input for repeated exports from the client system. This application also generates a list of objects that failed to import.

Data Transfer Configuration

Figure 77: Data Transfer Configuration

The following data transfer settings can be configured: ●

246

Define Object Types -

Relationship to Business Object Type

-

Implementing classes



●

●

●

-

Additional selection fields

-

Sequence of objects to be processed

-

Business activities to be used during import

Define File Source / Archive Directory -

File source directory

-

Archive directory

Define File Converter -

Customer-specific converter

-

XML data mapping

BAdI file converter

How to Import Data within Master Data Governance For the demonstration steps and data, see the exercise Import data within Master Data Governance.


247


248



Import Data within Master Data Governance

Business Example Your company had decided that the material master data from an acquired SAP ERP system will be included in your company's SAP MDG system. The new master data records will be loaded into MDG system using an XML-based file structure and the MDG import framework. In this exercise, when values include ##, replace the characters with the number that your instructor provided to you. 1. Import the material using the data in the following table and note your run number. Field

Value

Object Type

Material - 194

Description

Group ##

Post Processing

Manual Post Processing

Object Type

Material

Source Directory

MDG_INITIAL_LOAD

Note your run number.

2. Verify the run number. 3. Verify that material MM_## has been loaded.


249


Import Data within Master Data Governance

Business Example Your company had decided that the material master data from an acquired SAP ERP system will be included in your company's SAP MDG system. The new master data records will be loaded into MDG system using an XML-based file structure and the MDG import framework. In this exercise, when values include ##, replace the characters with the number that your instructor provided to you. 1. Import the material using the data in the following table and note your run number. Field

Value

Object Type

Material - 194

Description

Group ##

Post Processing

Manual Post Processing

Object Type

Material

Source Directory

MDG_INITIAL_LOAD

Note your run number. Answers will vary. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Material Governance. e) In the navigation panel, choose Data Exchange → Data Transfer → Import Master Data. f) On the Import Master Data and Mapping Information screen, enter the data from the table. g) In the Data Sources table, choose Add. h) In the Select Related Object dialog box, choose Material. i) Choose OK.

250



j) On the Import Master Data and Mapping Information screen, in the Source Directory column, enter the source directory from the table. k) Choose Import and note the run number. 2. Verify the run number. a) On the Import Master Data and Mapping Information screen, choose Display Monitoring. b) Choose Search. c) In the Search Results table, double-click your run number to see the import details. d) Choose Back until you return to the SAP Easy Access - User Menu screen. 3. Verify that material MM_## has been loaded. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MM02. b) Choose Enter. c) On the Change Material (Initial Screen), in the Material field, enter MAT_##. d) Choose Select View(s). e) In the Select View(s) dialog box, select Basic Data 1. f) Choose Enter. g) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen.


251



252

●


●



Unit 7 Lesson 2 241

Configuring Data Replication within Master Data Governance

LESSON OVERVIEW In this lesson, you will learn how to configure data replication within Master Data Governance. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Data Replication Key Capabilities

Figure 78: Data Replication Key Capabilities

Replication is supported by both SAP systems and non-SAP systems. Replication can be started in the following ways: ●

Workflow-triggered to run automatically

●

Scheduled to run automatically

●

Started manually

Replication controlled by the Data Replication Framework (DRF) supports the following capabilities: ●

Flexibility to replicate selected data to specific systems by defining filters


253


●

Support of key mapping and value mapping

●

Replication using services, ALE, RFC, and files

●

Support for peer-to-peer or mediated communication

●

Monitoring of replication activities and failures

Data replication content for SAP and non-SAP systems consists of the following categories for Supplier and Customer: Table 9: Data Replication Categories for Supplier and Customer Client

Supplier Medium of Communication

Customer Medium of Communication

ERP 4.0 and earlier

IDoc CREMAS

IDoc DEBMAS

ERP 4.0 to 4.6C

●

IDoc CREMAS

●

IDoc DEBMAS

●

ADRMAS

●

ADRMAS

ERP 6.0, Ehp5 and earlier

●

●

●

●

●

ERP Ehp6 and later

●

●

SRM 7.01 and earlier

●

●

254

IDoc CREMAS (standard single SAP ERP supplier) ADRMAS (standard SAP ERP supplier) IDoc CREMDM (bulk IDoc for initial load; includes addresses) IDoc BUPA_INBOUND_MAIN_S AVE (industry business partner) BUPA_INBOUND_REL_SA VE (industry business partner) BusinessPartnerReplicate Request service BusinessPartnerRelations hipReplicateRequest service IDoc BUPA_INBOUND_MAIN_S AVE BUPA_INBOUND_REL_SA VE

●

●

●

●

●

●

●

●

●

IDoc DEBMAS (standard single SAP ERP customer) ADRMAS (standard SAP ERP customer) IDoc DEBMDM (bulk IDoc for initial load; includes addresses) IDoc BUPA_INBOUND_MAIN_S AVE (industry business partner) BUPA_INBOUND_REL_SA VE (industry business partner) BusinessPartnerReplicate Request service BusinessPartnerRelations hipReplicateRequest service IDoc BUPA_INBOUND_MAIN_S AVE BUPA_INBOUND_REL_SA VE


Lesson: Configuring Data Replication within Master Data Governance

Client SRM 7.02 and later

Supplier Medium of Communication ●

●

Non-SAP systems

●

●

BusinessPartnerReplicate Request service BusinessPartnerRelations hipReplicateRequest service BusinessPartnerReplicate Request service BusinessPartnerRelations hipReplicateRequest service

Customer Medium of Communication ●

●

●

●

BusinessPartnerReplicate Request service BusinessPartnerRelations hipReplicateRequest service BusinessPartnerReplicate Request service BusinessPartnerRelations hipReplicateRequest service

Data replication content for SAP and non-SAP systems consist of the following categories for Financials and Material: ●

●

Financials -

Enterprise Services

-

ALE

Material -

MATMAS IDoc

-

CLFMAS IDoc

-

Enterprise Services

Data Replication Modes and Filters Replication Modes

Figure 79: Data Replication Modes

DRF supports the following replication modes:


255


●

●

Automatic -

Scheduled as a background job

-

Triggered by the workflow

Manual -

Triggered in the SAP web UI

-

Triggered using the transaction DRFOUT

Filter Types The following filter types are available: ●

Explicit

●

Implicit

●

Segment

Explicit filters are configured by the customer and are either simple or complex. Simple filters are defined for each attribute in a single SAP ERP entity root table. The evaluation of simple filters is generic so that they can be easily enhanced by adding another attribute to the filter. No code change is required to enhance simple filters. Complex filters are not directly related to the SAP ERP entity root table but can be evaluated by certain function modules or methods like selected nodes of the article hierarchy or the merchandise category hierarchy. The interpretation of the semantics of complex filters is coded using the corresponding APIs. Code changes are required to enhance complex filters. Implicit filters are offered by the system (reusable APIs). These filters are executed by the system and can be switched on or off only by using the configuration options on the Replication Model's Outbound Implementation level. Examples of implicit filters include checks of certain materials and store combinations by listing conditions or selling periods. Segment filters are used to exclude parts, or segments, of the Business Object from replication.

Key and Value Mapping

Figure 80: Key Mapping

256



Key mapping is a set of remote keys that maps objects in a repository, for example, a record or attribute value, to equivalent objects on a remote system. SAP uses ID mapping to map certain attributes that the repository receives and then map the internal keys back to the attribute values. Attribute values include payment terms, country, region, and gender. DRF can maintain and execute mappings based on global data types (GDT) and data elements. Context-dependent mapping, such as mapping regions based on the country, is also supported. Value Mapping Uploading of value-mapping data to MDG is supported. Value mapping is used to transfer central mapping information from one system to another. System-specific mapping, or code lists, can be used for mappings that are performed in data replication processes, according to the following guidelines: ●

Each system in the landscape is connected.

●

Inbound and outbound mapping is executed in each system.

Figure 81: Value Mapping in the Hub Configuration

The value mapping configuration information shown in the graphic Value Mapping in the Hub Configuration is summarized in the following table. Table 10: Value Mapping Configuration Values in the Message

Internal Values (MDG Hub)

Values come from one of the global code lists Values come from the AD_TITLE data for the Global Data Type (GDT) element. This data element is associated FormOfAddressCode. This code list has a list with the AD_TITLE domain. agency ID of MDG_GLOBAL and a list version ID of 1. Codes are 0001=Ms., 0002=Mr., and 0003=Company.

Codes are 0001=Ms., 0002=Mr., and 0004=Company.

Values are mapped to the values described in Values are mapped to the values described in the Internal Values (MDG Hub) column. the Values in the Message column.


257


No mapping is necessary for the codes Ms. and Mr. because they are identical in the Hub and the global list.

Figure 82: Value Mapping in the Target Configuration

The value mapping configuration information shown in the graphic Value Mapping in the Target Configuration is summarized in the following table. Table 11: Value Mapping Configuration Values in the Message

Internal Values (MDG Hub)

Values come from one of the global code lists Values come from the AD_TITLE data for the Global Data Type (GDT) element. This data element is associated FormOfAddressCode. This code list has a list with the AD_TITLE domain. agency ID of MDG_GLOBAL and a list version ID of 1. Codes are 0001=Ms., 0002=Mr., and 0003=Company.

Codes are 0001=Mr., 0002=Ms., and 0003=Company.

Values are mapped to the values described in Values are mapped to the values described in the Internal Values (MDG Hub) column. the Values in the Message column. The figure Value Mapping in the Target Configuration shows that mappings are required in the target system because the codes for Ms. and Mr. are not identical in the target system and the global list. This configuration is the recommended approach when the client is available.

258



Figure 83: Value Mapping in the System-Specific List

No mappings are necessary in the target system for the codes Ms. and Mr. because they are identical in the target system and system-specific list. In this instance, mappings are necessary in the Hub. This configuration is the recommended approach if mapping in the client is not available, for example in earlier SAP releases or non-SAP systems.

Data Replication Monitoring

Figure 84: Data Replication Monitoring

Data replication monitoring in DRF is based on the following capabilities: ●

●

SAP standard tools, including the application log and Computing Center Management System (CCMS) alerts, which can drill down into technical monitoring functions such as ALE and Process Integration (PI) monitoring DRF-specific capabilities, which monitor replication status on a business object level

How to Configure Data Replication For the demonstration steps and data, see the exercise Configure Data Replication.


259


260



Configure Data Replication

Business Example You are acting as a master data steward or administrator. You are responsible to ensure that master data created in MDG is distributed to all connected client systems in the landscape. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Configure replication model ZRM_## using the data in the following table. Column

Value

Replication Model

ZRM_##

Description

Team ## Replication Model

Log Days

15

2. Create a new request with the short description New Replication Model ##. 3. Assign the outbound implementation 986_3 for replication using the data in the following table. 4. Assign a target system and outbound parameters for replication using the data in the following table. Element

Selection

Target System

ZME_900

Outbound Parameter field

PACK_SIZE_BULK

Outbound Parameter Value field

100

5. Activate replication model ZRM_## using the data from the table. Field

Value

Program

ZR_ACTIVATE_REPLICATION_MODEL

GV_MODEL

ZRM_##

6. Create a filter for replication model ZRM_## to filter for your business partner.


261


Configure Data Replication

Business Example You are acting as a master data steward or administrator. You are responsible to ensure that master data created in MDG is distributed to all connected client systems in the landscape. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Configure replication model ZRM_## using the data in the following table. Column

Value

Replication Model

ZRM_##

Description

Team ## Replication Model

Log Days

15

a) On the SAP Easy Access - User Menu screen, in the Command field, enter DRFIMG. b) Choose Enter. c) On the Display IMG screen, choose Data Replication → Define Custom Settings for Data Replication → Define Replication Models. d) On the Change View "Define Replication Model": Overview screen, choose New Entries. e) In the Data Replication Model table, enter the data from the table. f) Choose Save. 2. Create a new request with the short description New Replication Model ##. a) In the Prompt for Customizing Request dialog box, choose Create Request. b) In the Create Request dialog box, in the Short Description field, enter New Replication Model ##. c) Choose Save. d) Choose Continue. 3. Assign the outbound implementation 986_3 for replication using the data in the following table. a) In the Define Replication Model table, choose ZRM_##. b) On the New Entries: Overview of Added Entries screen, double-click Define Replication Model → Assign Outbound Implementation.

262



c) In the Change View "Assign Outbound Implementation": Overview screen, choose New Entries. d) In the Assign Outbound Implementation table, in the Outbound Implementation column, enter 986_3. e) Choose Save. 4. Assign a target system and outbound parameters for replication using the data in the following table. Element

Selection

Target System

ZME_900

Outbound Parameter field

PACK_SIZE_BULK

Outbound Parameter Value field

100

a) In the Assign Outbound Implementation table, select 986_3, Outbound Impl. for BP/REL via Service. b) Select Define Replication Model → Assign Outbound Implementation → Assign Target Systems for Repl. Model/Outb. Impl. c) In the Assign Target Systems for Repl. Model/Outb. Impl table, choose New Entries. d) On the New Entries: Overview of Added Entries screen, enter the data from the table. e) Choose Save. f) Choose Define Replication Model → Assign Outbound Implementation → Assign Outbound Parameters. g) In the Change View "Assign Outbound Parameter": Overview screen, choose New Entries. h) On the New Entries: Overview of Added Entries screen, select the data from the table. i) Choose Save. j) Choose Back until you return to the SAP Easy Access - User Menu screen. 5. Activate replication model ZRM_## using the data from the table. Field

Value

Program

ZR_ACTIVATE_REPLICATION_MODEL

GV_MODEL

ZRM_##

a) On the SAP Easy Access - User Menu screen, in the Command field, enter SE38. b) Choose Enter. c) On the ABAP Editor: Initial Screen, in the Program field, enter the data from the table. d) Choose Execute.


263


e) On the Activate Replication Model screen, in the GV_MODEL field, enter the data from the table. f) Choose Execute. g) Choose Back until you return to the SAP Easy Access - User Menu screen. 6. Create a filter for replication model ZRM_## to filter for your business partner. a) On the SAP Easy Access - User Menu screen, in the Command field, enter DRFF. b) Choose Enter. c) On the Filter Criteria screen, in the Query by Replication Model - All Replication Models table, choose Team ## Replication Model. d) Choose Create. e) On the Create Filter Criteria screen, in the Filter Criteria to Include Business Objects fields, choose Business Partner in the first field, is in the second field, and your business partner ID in the third field. f) Choose Save. g) Choose Close to close the internet browser window and to return to the SAP Easy Access - User Menu screen.

264



How to Replicate Data within Master Data Governance For the demonstration steps and data, see the exercise Replicate Data within Master Data Governance.


265


266



Replicate Data within Master Data Governance

Business Example As a master data steward, you are responsible for replicating master data from the MDG Hub to connected client systems. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Replicate data for replication model ZRM_##. 2. Monitor the status of your replication model ZRM_##. 3. Analyze the application log to verify that the data is replicated to SAP ERP client 900.


267


Replicate Data within Master Data Governance

Business Example As a master data steward, you are responsible for replicating master data from the MDG Hub to connected client systems. In this exercise, when values include ##, replace the characters with the number that your instructor assigned to you. 1. Replicate data for replication model ZRM_##. a) On the SAP Easy Access - User Menu screen, in the Command field, enter DRFOUT. b) Choose Enter. c) On the Execute Data Replication screen, in the Replication Model field, enter ZRM_##. d) Choose Execute. e) On the Display Logs screen, in the Message Text table, in the Process Outbound Implementation Outbound Impl. for BP/REL via Services (986_3) row, in the Det. Column, choose Details Exist. f) In the Message Text table, in the Filter Object MDG_BP_SFT - 986 BP Service Filter: end result of filtering row, in the Det. column, choose Details Exist. g) On the Application ZRM_## - Team ## Replication Model/Business Object 986 screen, in the Objects After Filter Execution table, in the Partner column, double-click your business partner ID. h) On the Monitor for Processed XML Messages screen, view the XML message. i) Choose Back to return to the SAP Easy Access - User Menu screen. 2. Monitor the status of your replication model ZRM_##. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch SAP NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Supplier Governance. e) In the navigation panel, choose Data Exchange → Data Replication → Monitor Replication. f) On the Application Monitoring screen, in the Replication Model field drop-down menu, choose Team ## Replication Model. g) Choose Continue.

268



h) On the Application Monitoring: Team ## Replication Model screen, in the Replication Logs: Team ## Replication Model table, choose the last row with the current date, time, and user name. i) In the Replication Log Messages table, view the replication log. j) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. 3. Analyze the application log to verify that the data is replicated to SAP ERP client 900. a) Log on to SAP ERP client 900. b) On the SAP Easy Access - User Menu screen, in the Command field, enter BP. c) Choose Enter. d) On the Maintain Business Partner screen, in the Business Partner field, enter your business partner ID e) Choose Enter. f) Choose Back until you return to the SAP Easy Access - User Menu screen. g) Log out of SAP ERP client 900. h) Log on to SAP ERP client 800.


269



270



Unit 7

257

Learning Assessment

1. Which data transfer logs are available? Choose the correct answers. X

A Conversion

X

B Export

X

C Import

X

D Processing time

2. Which types of objects can be imported? Choose the correct answers. X

A Business partner

X

B Control table data

X

C Key mapping

X

D Material classification

X

E Value mapping

3. Key mapping is a set of remote keys that maps objects in a repository. Determine whether this statement is true or false. X

True

X

False

4. Data Replication Key Capabilities supports which systems? Choose the correct answer. X

A Non-SAP systems

X

B SAP systems

X

C Both SAP and non-SAP systems

X

D Neither SAP or non-SAP systems


271


5. What is value mapping used for? Choose the correct answer.

272

X

A To export central mapping information to another system

X

B To export internal mapping information to another internal application

X

C To transfer central mapping information from one system to another

X

D To transfer central mapping information within a single system


Unit 7

259


1. Which data transfer logs are available? Choose the correct answers. X

A Conversion

X

B Export

X

C Import

X

D Processing time

2. Which types of objects can be imported? Choose the correct answers. X

A Business partner

X

B Control table data

X

C Key mapping

X

D Material classification

X

E Value mapping

3. Key mapping is a set of remote keys that maps objects in a repository. Determine whether this statement is true or false. X

True

X

False


273


4. Data Replication Key Capabilities supports which systems? Choose the correct answer. X

A Non-SAP systems

X

B SAP systems

X

C Both SAP and non-SAP systems

X

D Neither SAP or non-SAP systems

5. What is value mapping used for? Choose the correct answer.

274

X

A To export central mapping information to another system

X

B To export internal mapping information to another internal application

X

C To transfer central mapping information from one system to another

X

D To transfer central mapping information within a single system


UNIT 8

Custom Object Handling

Lesson 1 Creating a Custom Data Model Exercise 24: Create a Custom Data Model

276 285

Lesson 2 Creating a Custom User Interface Exercise 25: Create a User Interface Configuration

293 297

Lesson 3 Creating a New Change Request Configuration Exercise 26: Create a New Change Request Configuration Exercise 27: Create and Test a User Menu

306 313 323

UNIT OBJECTIVES ●

Create a custom data model

●

Create a custom user interface

●

Create a new change request configuration

●

Create a new change request user menu


275

Unit 8 Lesson 1 262

Creating a Custom Data Model

LESSON OVERVIEW In this lesson, you will learn how to create a custom data model. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


Data Modeling Entity Types

Figure 85: Data Modeling Entity Types

Entity Types The MDG metamodel is an entity-relationship model (ERM) that features entities for usage and storage. These entities have the following properties: ●

Entity types -

Type 1—Main Data, which features governance and persistence in MDG This entity has a table in the MDG staging area, where unapproved data is stored. Upon approval, the data is moved to the SAP ERP table for database persistence and deleted from the staging area.

-

Type 2—Check table with no governance and persistence in MDG This persistence check table is found only in the MDG area. It does not have any corresponding table in SAP ERP.

276


Lesson: Creating a Custom Data Model

-

Type 3—Check table with no governance and no persistence in MDG, but has persistence in Business Suite tables The data of this persistence check table type is derived from the SAP ERP table and does not have a table in the MDG area.

-

●

●

Type 4—Dependent Data, which is similar to Main Data but can only be maintained with an entity of Type 1

Attributes -

Existing data elements can be used to reuse storage types 1 and 4

-

Search help can be assigned

-

Can be set as mandatory

Hierarchies -

Name dependent, version dependent or both

-

Hierarchy attributes (edge attributes) to be defined

-

Allowed hierarchy entity types can be defined for mixed hierarchies

-

Intervals as leaves possible

Storage Types The following storage types entities are available: ●

●

●

●

Storage Type 1—Entities linked to change request types as the main entity type and where the governance processes occur Storage Type 2—Entities used as a flex check tables Storage Type 3—Entities used as a reuse check table. A generic access class exists to evaluate the domain values of this entity type. Storage Type 4—Entities that are included in the change request maintenance process, but are maintained together with a Type 1 entity

Hint: Instead of using a Type 2 entity you can create a check table manually in the DDIC (ABAP dictionary) and assign it to a data element. If you use a Type 2 entity then you can stay within the MDG modeling environment, although you must still have the data element.

Storage and Usage Types The following table summarizes the storage characteristics of the entity types:


277

Unit 8: Custom Object Handling

Table 12: Storage Type Characteristics Storage Type 1

Storage Type 2

Storage Type 3

Storage Type 4

To be used for entity types that are maintained in MDG.

To be used for entity types that are not maintained by MDG and which are not available in the system.

To be used for entity types that are not maintained by MDG and which are available in the system.

To be used for entity types that are maintained in MDG in the context of another (owning) entity type.

●

●

●

●

●

●

Data storage and staging area generated, edition-dependent Can be fully modeled (can hold attributes, references, and so on) Maintenance by change request (entry point) Optional assignment of data elements (technical properties, storage type 1, UI texts) Check table and domain fix values behind data elements are ignored Storage type 4 goes to generated check table

●

●

●

●

●

●

Data storage generated, no edition, no staging No further modeling possible (only check and text table generated)

●

●

●

●

No maintenance by change request Mandatory assignment of data elements (technical properties, storage type 1, UI texts) Check table and domain fix value behind data elements are ignored

●

●

Storage type 4 goes to generated check table

No data storage generated

●

No further modeling possible No maintenance in MDG at all Mandatory assignment of data element (technical properties, storage type 1, UI texts) Check table and domain fix value behind data element are used

●

●

Data storage and staging area generated, edition-dependent Can model attributes and relationships, but is Storage Type 1 dependent Maintenance by change request (No entry point, maintenance through owning storage type 1 entity type)

Storage type 4 goes to check-text table or domain fix value behind data element. Nonkey fields in check table are ignored

Use Storage Type 1 for the following conditions: ●

Main tables or any table to be maintained in MDG

●

No qualifying relationships (only leading and referencing)

Use Storage Type 2 to look up data to be maintained in MDG but without attributes. Use Storage Type 3 to look up data to be maintained outside of MDG without attributes. Use Storage Type 4 for the following conditions: ●

278

When an entity of Type 1 is extended with additional fields based on the value of the Type 4 entity with which has a leading relationship



●

●

When it can have only one leading relationship and one qualifying relationship. All other relationships must be either qualifying or referencing When it has key fields coming from its leading and qualifying relationships

Active and Inactive Data

Figure 86: Active and Inactive Data

MDG separates data into the following areas: ●

Active area—holds data that is ready to be used by applications

●

Staging area—holds data that is not yet approved but is currently part of a change request

For optimized integration and flexibility, MDG allows the following modes for the active area: ●

●

Reuse active area (reuse mode) – Existing structures (database tables) of applications are used, for example, MDG for Material uses MARA table in SAP ERP. The Reuse active area can be used for custom objects. Generated active area (flex mode) – Tables defined in the MDG data model are used to store active data. This mode is used in MDG for Financials.

The figure Active and Inactive Data shows the flex and reuse modes when MDG is being deployed with SAP ERP. When using the MDG Hub, then all master data domains would be in flex mode. Replication models are of strategic importance in a Hub scenario.


279


Data Modeling Relationships

Figure 87: Data Modeling Relationships

The following types of data modeling relationships can be defined: ●

●

Referencing—Specifies that the from-entity type is an attribute of the to-entity type. Leading or Qualifying—Specifies that the from-entity type is on a higher level than the toentity type. In this case the from-entity type is automatically taken as the key in the generated tables.

The difference between the relationship types Leading and Qualifying is only applicable for toentity types with storage and use type 4. The master data of these to-entity types is processed in the context of the entity type that is assigned using the leading relationship. The following rules apply to the entity types: ●

●

●

●

Attributes can be added only for Type 1 and Type 4. Type 1 can use only the Leading and Referencing relationships but does not use the Qualifying relationship. Type 2 allows the Leading relationship but does not allow the Qualifying relationship. Type 4 can have any type of relationship, but must have only one Leading relationship and at least one Qualifying relationship.

The following rules apply to when determining the type of relationship between E2 and E1: ●

●

●

280

If E2 has a key of E1 as a primary key, then use the Leading relationship. If E2 has a key of E1 as a primary key and E2 is Type 4, only Qualifying relationship can be used. If E2 has a key of E1 but no primary key, then use the Leading relationship.



Figure 88: Entity Type Relationships

The entity and the attributes correspond to fields of MARC table and are also be displayed in the UI. The types of entities are indicated in the numbered circles. The following are keys of the MARC table are material and plant number: ●

●

●

A leading relationship (Type 1) from the MARA table (Material) to the MARC table (Plant data), which means you will be able to maintain plant data within a material master. This relationship also defines one of the keys for the MARC table. A qualifying relationship (Type 4) from the T001W table to the MARC table. This relationship defines the other key of the MARC table. A referencing relationship (Type 3) which characterizes the other SAP ERP check tables.

These check tables can be considered equivalent to the customizing tables in the SAP ERP system.


281


Process Configuration

Figure 89: Determination of Field Properties in the UI

The determination of field properties within the UI is defined by the following elements: ●

Change request step-specific field properties

●

BAdI implementation

●

MDG data model configuration

●

Field properties from the reuse area

●

Level 1 overrules level 2, which overrules level 3, which overrules level 4

The relevance of checks can be defined on the following levels: ●

●

Change request step and entity combination—Reduce checks to Basic Check Only or All Configured Check Change request step—All checks can be set to Not Relevant except Basic Check

The following field checks are required: ●

●

Required fields—Executed by the MDG Framework or by the Reuse Area check. This check depends on the Reuse Class implementation. Custom Objects—Use the Reuse Area Check; however, this check depends on the complexity and existing checks of the object

The Change Request Specific Configuration is also available for Supplier, Customer, and Material and the following required field checks are executed:

282

●

Reuse Area Checks, for Supplier and Customer

●

MDG Framework where Reuse Area Checks are set to Not Relevant, for Material



Figure 90: Process Configuration

The UI is determined for each entity type by the change request type. The UI can be overwritten by a user-specific assignment for the data model or a change request stepspecific setting. Several change request types can be assigned to a single business activity; however, the user must select the change request type to be used. The change request type determines the following configuration details: ●

The workflow template

●

The data model and entity types

The workflow template defines the possible workflow steps. The status of the change request and the workflow step are used in the process logic of the workflow template to determine the following aspects of that workflow: ●

The possible actions in the UI

●

The next workflow template step

●

The status of the next change request

How to Create a Custom Data Model For the demonstration steps and data, see the exercise Create a Custom Data Model.


283


284



Create a Custom Data Model

Business Example You are a business administrator for a company that has just acquired an airline company. You have been asked to plan and create a simple data model for the airline. In this exercise, when values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table. Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22

W

23

X

24


285


Letter (%)

Group Number (##)

Y

25

Z

26

1. In the configuration workbench, open data model Z%. 2. Edit data model Z% using the data in the following table. Field

Value

Entity Type

CARR

Description

Airline

SU Type

1 - Changeable via Change Request

Medium Text: Length

20

Data Element

S_CARR_ID

3. Add attributes to the data model and create a transport request using the data in the following table. Column or Field

Value

Attribute

URL

Description

Airline URL

Data Element

S_CARRURL

Short Description

Group ## - new data model & process

4. Define a new entity type using the data in the following table. Field

Value

Entity Type

CURR

Description

Currency

SU Type

3 - Not Changeable via MDG; No Generated Tables

Data Element

S_CURRCODE

Validity of Entity

No Edition

Deletion

Deletion Allowed

5. Define outgoing relationships for the currency entity type and create a transport request using the data in the following table.

286

Field

Value

Relationship

CARR_CURR

To-Entity Type

CARR

Relationship Type

Referencing



Field

Value

Cardinality

1:N

Data Element

S_CURRCODE

Description

Airline Currency

6. Check and activate the data model, then view the activation log. 7. Display data model Z%.


287


Create a Custom Data Model

Business Example You are a business administrator for a company that has just acquired an airline company. You have been asked to plan and create a simple data model for the airline. In this exercise, when values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table.

288

Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22

W

23

X

24



Letter (%)

Group Number (##)

Y

25

Z

26

1. In the configuration workbench, open data model Z%. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGDT. b) Choose Enter. c) On the Configuration Workbench screen, choose Z%. 2. Edit data model Z% using the data in the following table. Field

Value

Entity Type

CARR

Description

Airline

SU Type

1 - Changeable via Change Request

Medium Text: Length

20

Data Element

S_CARR_ID

a) On the Data Model Z%,RKT Custom Object Group 01 screen, choose Edit. b) In the Entity Types section, choose New. c) Enter the data from the table. 3. Add attributes to the data model and create a transport request using the data in the following table. Column or Field

Value

Attribute

URL

Description

Airline URL

Data Element

S_CARRURL

Short Description

Group ## - new data model & process

a) On the Data Model Z%,RKT Custom Object Group 01 screen, select the Attribute tab. b) Choose New. c) In the attribute table, enter the data from the table. d) Choose Save. e) In the Transport Request Manager dialog box, select the Create New radio button. f) Enter the data from the table. g) Choose OK. 4. Define a new entity type using the data in the following table.


289


Field

Value

Entity Type

CURR

Description

Currency

SU Type

3 - Not Changeable via MDG; No Generated Tables

Data Element

S_CURRCODE

Validity of Entity

No Edition

Deletion

Deletion Allowed

a) On the Data Model Z%,RKT Custom Object Group 01 screen, choose Edit. b) In the Entity Types section, choose New. c) Enter the data from the table. 5. Define outgoing relationships for the currency entity type and create a transport request using the data in the following table. Field

Value

Relationship

CARR_CURR

To-Entity Type

CARR

Relationship Type

Referencing

Cardinality

1:N

Data Element

S_CURRCODE

Description

Airline Currency

a) On the Data Model Z%,RKT Custom Object Group 01 screen, select the Outgoing Relationships tab. b) In the Entity Types section, in the Outgoing Relationships table, choose New. c) Enter the data from the table. d) Choose Save. 6. Check and activate the data model, then view the activation log. a) On the Data Model Z%,RKT Custom Object Group 01 screen, choose Check. You can ignore the active area has no entry and no change documents error messages. b) Choose Activate. c) Choose View Log. d) Choose Close. e) Choose Close to close the internet browser window and return to the SAP Easy Access - User Menu screen. 7. Display data model Z%.

290



a) On the SAP Easy Access - User Menu screen, in the Command field, enter SA38. b) Choose Enter. c) On the ABAP: Program Execution screen, in the Program field, enter Z%. d) Choose Execute. e) On the Active Data Model Z% (Enabled Elements Only) screen, view your entire data model. f) Choose Back until you return to the SAP Easy Access - User Menu screen.


291



292



Unit 8 Lesson 2 279

Creating a Custom User Interface

LESSON OVERVIEW In this lesson, you will learn how to create a custom user interface. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


User Interface Modeling MDG Custom Object Configuration Overview

Figure 91: MDG Custom Configuration

MDG custom configuration consists of the following elements: ●

Data modeling—Create and edit data models.

●

UI modeling—Create and edit UI configurations.

●

●

Process modeling—Create business activities and change requests, and assign processors to workflow steps. Data Replication—Define replication models.

Custom User Interface Creation User Interface Creation Floorplan Manager


293


Figure 92: User Interface Configuration Floorplan Manager

Create and maintain a UI configuration for every data model used in single processing when processing a change request. Set up UI configuration using the Floorplan Manager (FPM). FPM is a Web Dynpro ABAP application that provides a framework for developing UIs consistent with the SAP UI guidelines. The following components make up an FPM application and can be configured: ●

FPM_GAF_COMPONENT

●

FPM_OVP_COMPONENT

●

FPM_OIF_COMPONENT

Data Model Connection

Figure 93: Change Request Process Configuration

294


Lesson: Creating a Custom User Interface

The UI configuration is determined by entity and change request types. The UI configuration can be overwritten by a user-specific assignment for the data model or by a specific change request step setting. You can assign several change request types to a single business activity. The following properties are determined by the change request type: ●

Workflow template

●

Data model

●

Entity type

The system uses the status of the change request and the workflow step to determine: ●

The possible actions in the UI

●

The next workflow step

●

The next change request status

How to Create a User Interface Configuration For the demonstration steps and data, see the Create a User Interface Configuration.


295


296



Create a User Interface Configuration

Business Example You are a business administrator for a company that has just acquired an airline company. You maintain the airline's master data. You have been asked to create a simple user interface in the style of a form to input and display data. In this exercise, when values include ##, replace the characters with the number your instructor provided to you. When values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table. Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22


297


Letter (%)

Group Number (##)

W

23

X

24

Y

25

Z

26

1. Create a new UI configuration with a prefix of Z##. 2. Start a deep-copy of select USMD2_ENTITY_VALUE2 and assign the $TMP package for the local object. 3. Navigate to the new application configuration and assign a data model Z## to the application configuration. 4. Navigate to the OIF configuration and create a new variant entity type using the data in the following table. Field

Value

ID

CARR

Name

Airline

5. Enter the component IDs using the data in the following table. Field

Value

Main View ID

MAINVIEW_1

Main View Name

Main View 1

Subview ID

SUBVIEW_1_1

Subview Name

Subview 1 1

6. Configure the UIBB form using the data in the following table. Field

Value

Component

FPM_FORM_UIBB

Window Name

FORM_WINDOW

Configuration Name

Z%_FORM_AIRLINE

7. Remove variants VARIANT_2 and USMD_DUMMY. 8. Create a new UIBB configuration for UI configuration Z##_USMD_ENTITY_VALUE2_OIF using the data in the following table.

298

Field

Value

Configuration Name

Z%_FORM_AIRLINE

Description

Z% Airline Form



9. Configure the Form UIBB Schema using the following list of fields. ●

CARR_CURR

●

TXTMI

●

URL

10. Change the field width of Element: URL to 30em. 11. Change the labels of the fields using the data in the following table. Section

Field

Value

Attributes of Element: CARR_CURR

Label

Airline Local Currency

Attributes of Element: TXMI

Label

Airline Description

Attributes of Element: URL

Label

Airline URL

12. Change the order fields to the following sequence. 1. Element: Airline Description 2. Element: Airline Local Currency 3. Element: Airline URL


299


Create a User Interface Configuration

Business Example You are a business administrator for a company that has just acquired an airline company. You maintain the airline's master data. You have been asked to create a simple user interface in the style of a form to input and display data. In this exercise, when values include ##, replace the characters with the number your instructor provided to you. When values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table.

300

Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22



Letter (%)

Group Number (##)

W

23

X

24

Y

25

Z

26

1. Create a new UI configuration with a prefix of Z##. a) On the SAP Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → UI Modeling → Edit UI Configuration. d) On the Manage UI Configurations screen, choose Create. e) On the Floorplan Manager: Application Hierarchy Browser - Application: USMD_ENTITY_VALUE2 screen, choose Change Affixes. f) In the Change Affixes of Target Configuration IDs dialog box, enter Z##. g) In the Suffix field, delete the value. h) Choose OK. i) On the Floorplan Manager: Application Hierarchy Browser - Application: USMD_ENTITY_VALUE2 screen, in the Target Configuration ID column, verify that the new affix values have been added. 2. Start a deep-copy of select USMD2_ENTITY_VALUE2 and assign the $TMP package for the local object. a) On the Floorplan Manager: Application Hierarchy Browser - Application: USMD_ENTITY_VALUE2 screen, choose Start Deep-Copy. b) In the Select Package dialog box, choose Local Object. c) On the Floorplan Manager: Application Hierarchy Browser - Application: USMD_ENTITY_VALUE2 screen, verify that the message Deep-copy Z##_USMD_ENTITY_VALUE2 of configuration USMD_ENTITY_VALUE2 successfully created is displayed at the top of the screen. 3. Navigate to the new application configuration and assign a data model Z## to the application configuration. a) On the Floorplan Manager: Application Hierarchy Browser - Application: USMD_ENTITY_VALUE2 screen, in the Application Hierarchy: Configuration Level table, in the Target Configuration ID column, choose Z##_USMD_ENTITY_VALUE2. b) On the Application Configuration Z##_USMD_ENTITY_VALUE2 screen, choose Edit. c) In the (USMD_MODEL) field, enter Z%. d) Choose Save. 4. Navigate to the OIF configuration and create a new variant entity type using the data in the following table.


301


Field

Value

ID

CARR

Name

Airline

a) On the Application Configuration Z##_USMD_ENTITY_VALUE2 screen, choose in the Assign Web Dynpro Component section, in the Configuration Name column, choose Z##_USMD_ENTITY_VALUE2_OIF. b) On the Component Configuration Z##_USMD_ENTITY_VALUE2_OIF, Variant "MustBeDeleted!" screen, choose New → Variant. c) In the Properties dialog box, enter the data from the table. d) Choose OK. 5. Enter the component IDs using the data in the following table. Field

Value

Main View ID

MAINVIEW_1

Main View Name

Main View 1

Subview ID

SUBVIEW_1_1

Subview Name

Subview 1 1

a) In the Navigation panel, choose Variant CARR → Main Screens. b) On the Object Instance Schema tab, choose Main View: Main View 1. Note: You may have to scroll down to find the Object Instance Schema tab. c) On the Attributes of Main View: Main View 1 tab, enter the data from the table. d) On the Object Instance Schema tab, choose Main View: Main View 1 → Subview: Subview 1 1. e) On the Attributes of Subview: Subview 1 1 screen, enter the data from the table. 6. Configure the UIBB form using the data in the following table. Field

Value

Component

FPM_FORM_UIBB

Window Name

FORM_WINDOW

Configuration Name

Z%_FORM_AIRLINE

a) On the Object Instance Schema tab, choose Main View: Main View 1 → Subview: Subview 1 1 → UIBB (1). b) On the Attributes of UIBB: FORM_WINDOW section, enter the data from the table.

302



7. Remove variants VARIANT_2 and USMD_DUMMY. a) In the Navigation panel, choose VARIANT_2. b) Choose Delete. c) In the Delete Elements dialog box, choose OK. d) In the Navigation panel, choose USMD_DUMMY. e) Choose Delete. f) In the Delete Elements dialog box, choose OK. g) Choose Save. 8. Create a new UIBB configuration for UI configuration Z##_USMD_ENTITY_VALUE2_OIF using the data in the following table. Field

Value

Configuration Name

Z%_FORM_AIRLINE

Description

Z% Airline Form

a) In the Create Configuration dialog box, enter the data from the table. b) Choose OK. c) In the Select Package dialog box, choose Local Object. d) In the Edit Parameters dialog box, choose OK. a) On the Object Instance Schema tab, choose Main View: Main View 1 → Subview: Subview 1.1 → UIBB (1). b) Choose Configure UIBB. c) On the internet browser Configure Component tab, choose Close. 9. Configure the Form UIBB Schema using the following list of fields. ●

CARR_CURR

●

TXTMI

●

URL

a) On the Component Configuration Z%_FORM_AIRLINE screen, choose the Form UIBB Schema tab. b) On the Form UIBB Schema tab, choose Element → Add Group. c) In the table, in the Element column, choose Group 1. d) Choose Child Element → Add Elements to Group. e) In the Edit Group dialog box, choose the fields from the list. f) Choose OK. g) On the Component Configuration Z%_FORM_AIRLINE screen, choose


Attributes.

303


10. Change the field width of Element: URL to 30em. a) On the Component Configuration Z%_FORM_AIRLINE screen, on the Form UIBB Schema tab, choose Element: URL. b) In the Attributes of Element: URL section, in the UI Element Width field, enter 30em. 11. Change the labels of the fields using the data in the following table. Section

Field

Value

Attributes of Element: CARR_CURR

Label


Attributes of Element: TXMI

Label

Airline Description

Attributes of Element: URL

Label

Airline URL

a) On the Form UIBB Schema tab, choose Element: CARR_CURR. b) In the Attributes of Element: CARR_CURR section, in the Label field, enter the data from the table. c) On the Form UIBB Schema tab, choose Element: TXTMI. d) In the Attributes of Element: TXTMI section, in the Label field, enter the data from the table. e) On the Form UIBB Schema tab, choose Element: URL. f) In the Attributes of Element: URL section, in the Label field, enter the data from the table. 12. Change the order fields to the following sequence. 1. Element: Airline Description 2. Element: Airline Local Currency 3. Element: Airline URL a) On the Form UIBB Schema tab, choose a row and drag it to the proper position. b) Choose Save. c) Choose Close to close the internet browser window. d) Choose Back to return to the SAP Easy Access - User Menu screen.

304






305

Unit 8 Lesson 3 292

Creating a New Change Request Configuration

LESSON OVERVIEW In this lesson, you will learn how to create a new change request configuration and create a new change request user menu. LESSON OBJECTIVES After completing this lesson, you will be able to: ●


●


Change Request Framework Technical Concepts

Figure 94: Process Configuration

The services in the Workcenter are links to UIs. These services are assigned to a business activity, which defines the following aspects of the change request: ●

Data model

●

Change request type

Several change request types can be assigned to one business activity; however, the user must select the change request type to use. The change request type defines the following aspects of the change request: ●

306

Workflow, which defines the workflow steps and tasks


Lesson: Creating a New Change Request Configuration

●

Change request steps, which defines the processors

A data model can have many UI configurations that define the UI building blocks (UIBB) for entity types. The UI configuration used depends on several different configuration steps. The assignment of change request step types to step numbers is completed using the following processes: ●

BRFplus decision tables for rule-based workflow templates

●

Workflow steps for other MDG workflow templates

Figure 95: Change Request Technical Concept


307


Change Request Framework Overview

Figure 96: Change Request Framework Overview

The change request framework is structured using logical components. The highest level is where a logical action is defined. A logical action is simply an action. For example, CREATE is a logical action that represents the act of creating something. Similarly, DELETE is a logical action that represents the act of deleting something. Use business activities to add business context into a logical action. For example, "Create Material" is a business activity in which the logical action of CREATE is applied to a business entity Material. To carry out a business activity, one or more processes can be defined. A process is represented by a change request type. Each process contains multiple change requests. Each step has a type that represents the set of actions and decisions that can be performed. At each step, the status of the change request changes to indicate its current state at that specific step. When a user acts on a step by pushing an action button, an action is triggered that starts the next step and changes the step status. Every step, whether interactive or in the background, is represented by a workflow step, which corresponds to a workflow task.

308



Change Request Process Logical Actions

Figure 97: Change Request Logical Actions

A logical action is a high-level process definition that is not tied to any business object. Logical actions offer the following advantages: ●

Flexible navigation between user interfaces

●

Enhanced determination of business activities


309


Change Request Business Activities

Figure 98: Change Request Business Activities

A business activity implements the logical action on a particular business object type. It is a configuration object that is associated with a change request type. If a business activity is associated with more than one change request type, select which change request type to execute. You can link logical actions with a UI application and a business activity. Linking the business activity with a UI involves the following steps: 1. Decide which business activity to use. 2. Use the standard definition process model to view the UI, or use the custom definition process model to customize navigation to the next UI. 3. Specify the target UI based on the business object, logical action, and current UI.

310



Business Activities Determination

Figure 99: Change Request Business Activity Determination

It is also possible to specify the business activity to be used for application-specific UIs based on the current UI and logical action.

Figure 100: Change Request UI Applications

A list of UI applications that can be used as the source or target UI is also available. UIs can be categorized into the following groups:


311


●

●

Application-specific UIs -

Supplier, Customer—Business Partner (BP)

-

Material (MAT)

Generic UIs (USMD) -

Financials

-

Custom Objects

How to Create a New Change Request Configuration For the demonstration steps and data, see the exercise Create a New Change Request Configuration.

312



Create a New Change Request Configuration

Business Example You are a business administrator for a company that has just acquired an airline company. The airplanes in the new fleet need maintenance. You have been asked to create a new change request configuration for airplane maintenance. In this exercise, when values include ##, replace the characters with the number your instructor assigned to you. When values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table. Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22


313


Letter (%)

Group Number (##)

W

23

X

24

Y

25

Z

26

1. Create a business activity using the data in the following table. Column

Value

Bus.Acty

Z%C1

Description (medium text)

Z% Create Airline

Data Model

Z%

Short Description

New Business Activity Z%C1

2. Create a change request type using the data in the following table. Column

Value

Type of Change Request

Z%C1A

Data Model

Z%

Single Object

Select the checkbox

Main Entry Type

CARR

Workflow

WS75700040

3. Assign an entity type to the new change request type using the data in the following table. Column

Value

Entity Type

CARR

Configuration Name

Z%_USMD_ENTITY_VALUE2

4. Link business activity Z%C1 to your new change request using the data in the following table. 5. Assign a processor to workflow steps 1 through 3 using the data in the following table. Type of Chg. Request

Step

Description

OT

Agent ID

Z%C1A

1

Processing

US

MDG100-##

Z%C1A

2

Final Check

US

MDG100-##

Z%C1A

3

Revision

US

MDG100-##

6. Personalize the user data for R_FMDM_MODEL using standard data model ## using the following table.

314



Field

Value

User

MDG100-##

Search Term

FMDM

Standard Data Model

Z%

UI Configuration



315


Create a New Change Request Configuration

Business Example You are a business administrator for a company that has just acquired an airline company. The airplanes in the new fleet need maintenance. You have been asked to create a new change request configuration for airplane maintenance. In this exercise, when values include ##, replace the characters with the number your instructor assigned to you. When values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table.

316

Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22



Letter (%)

Group Number (##)

W

23

X

24

Y

25

Z

26

1. Create a business activity using the data in the following table. Column

Value

Bus.Acty

Z%C1

Description (medium text)

Z% Create Airline

Data Model

Z%

Short Description

New Business Activity Z%C1

a) On the Easy Access - User Menu screen, in the Command field, enter MDGIMG. b) Choose Enter. c) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Business Activities → Create Business Activities. d) In the Information message, choose Continue. e) On the Change View "Business Activity: Definition": Overview screen, choose New Entries. f) In the Business Activity: Definition table, in the new row, enter the data from the table. g) Choose Save. h) On the Prompt for Workbench Request dialog box, choose New. i) In the Create Request dialog box, in the Short Description field, enter the data from the table. j) Choose Save. k) In the Prompt for Workbench Request dialog box, choose Continue. l) Choose Back until you return to the Display IMG screen. 2. Create a change request type using the data in the following table. Column

Value

Type of Change Request

Z%C1A

Data Model

Z%

Single Object

Select the checkbox

Main Entry Type

CARR


317


Column

Value

Workflow

WS75700040

a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Change Requests → Create Change Request Type. b) On the Change View "Type of Change Request": Overview screen, choose New Entries. c) On the New Entries: Overview of Added Entries screen, in the Type of Change Requests table, in the new row, enter the data from the table. d) On your keyboard, press ENTER. 3. Assign an entity type to the new change request type using the data in the following table. Column

Value

Entity Type

CARR

Configuration Name


a) On the New Entries: Overview of Added Entries screen, in the Dialog Structure navigation panel, choose Type of Change Request → Entity Types. b) On the Change View "Entity Types": Overview screen, choose New Entries. c) On the New Entries: Overview of Added Entries screen, in the Entity Types table, in the new row, enter the data from the table. d) On your keyboard, press ENTER. e) In the Configuration Name column, enter the data from the table. 4. Link business activity Z%C1 to your new change request using the data in the following table. a) On the New Entries: Overview of Added Entries screen, in the navigation panel, choose Type of Change Request → Business Activities. b) On the Change View "Business Activities": Overview screen, choose New Entries. c) In the Business Activities table, in the new row, in the Bus. Activity column, enter Z%C1. d) Choose Save. e) In the Message Have Been Issued dialog box, choose Save Changes. f) Choose Back until you return to the Display IMG screen. 5. Assign a processor to workflow steps 1 through 3 using the data in the following table.

318


Step

Description

OT

Agent ID

Z%C1A

1

Processing

US

MDG100-##

Z%C1A

2

Final Check

US

MDG100-##

Z%C1A

3

Revision

US

MDG100-##



a) On the Display IMG screen, choose Master Data Governance → General Settings → Process Modeling → Workflow → Other MDG Workflows → Assign Processor to Workflow Step (Simple Workflow). b) On the Change View "Assignment of Processors to Workflow Step Number": Overview screen, choose New Entries. c) On the New Entries: Overview of Added Entries screen, enter the data in the table for steps 1, 2, and 3. d) Choose Save. e) Choose Back until you return to the SAP Easy Access - User Menu screen. 6. Personalize the user data for R_FMDM_MODEL using standard data model ## using the following table. Field

Value

User

MDG100-##

Search Term

FMDM

Standard Data Model

Z%

UI Configuration


a) On the SAP Easy Access - User Menu screen, in the Command field, enter SU01. b) Choose Enter. c) On the User Maintenance: Initial Screen, in the User field, enter your ID. d) Choose Change. e) On the Maintain Users screen, select the Personalization tab. f) In the table, choose Find. g) In the Find dialog box, in the Search Term field, enter the data from the table. h) Choose Continue. i) In the Find dialog box, choose Close. j) In the table, double-click SAP Master Data Governance. k) On the Maintain Users screen, in the Standard Data Model field, enter the data from the table. l) In the Setting Dependent on Data Model table, in the UI Configuration field, enter the data from the table. m) Choose Continue. n) On the Maintain Users screen, choose Save. o) Choose Back until you return to the SAP Easy Access - User Menu screen.


319


Step-Specific User Interfaces

Figure 101: Step-Specific User Interfaces

Process modeling of change requests allows you to redefine the UI based on the type of change request. Configuring properties at the change request step level enhances process flexibility. This type of configuration overrules the configuration set at the Logical Action's Business Activity level.

User Interface Navigation and Adaptation

Figure 102: User Interface Navigation and Adaptation

320



A UI is defined by a UI application and a UI configuration. The UI configuration defines the look and feel of the UI. Based on the change request step, the system checks to determine whether a specific UI is configured. If the UI is configured, then it is used. If not, the system obtains the business object type for the business activity and checks to determine whether a UI is available from the navigation table based on the logical action performed. If the UI is found at this point, it is used. If the UI is not found, the system obtains the UI based on the change request type, data model, or personalization.

How to Create and Test a User Menu For the demonstration steps and data, see the exercise Create and Test a User Menu.


321


322



Create and Test a User Menu

Business Example You run an airplane maintenance facility. You want your employees to access Master Data Governance from the SAP portal or SAP NetWeaver Business Client. Create a new role with an appropriate user menu. In this exercise, when values include ##, replace the characters with the number your instructor assigned to you. When values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table. Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22


323


Letter (%)

Group Number (##)

W

23

X

24

Y

25

Z

26

Create a New User Menu 1. Copy the role SAP_MDGX_MENU and rename it ##_SAP_MDGX_MENU. 2. Edit the role ##_SAP_MDGX_MENU with the description ## Master Data Governance for Custom Objects: Menu. 3. Create a new folder named ## Airline Maintenance. 4. Add a Web Dynpro Application transaction to the ## Airline Maintenance folder using the data in the following table. Field

Value

Web Dynpro. Applicat.

USMD_ENTITY_SEARCH

Description

Search ## Airline

Parameter

PROCESS

Value

Z%CA

5. Add another Web Dynpro Application transaction to the ## Airline Maintenance folder using the data in the following table. Field

Value


USMD_ENTITY_VALUE2

Description

Process ## Airline

Parameter

IS_CREQ_MODE

Value

X

6. View the new user menu in SAP NetWeaver Business Client. Test the New Business Scenario 1. Create a new change request and change the standard data model to 2. Create and submit a change request using the data in the following table.

324

Screen Name

Field

Value


Description

My First Airline ##


Type

## Airline Single Maintenance



Screen Name

Field

Value


Airline

Z%


Explanation

This is my first airline.


Airline Description (medium Air Z% text)



EUR


Airline URL

www.air-Z%.com

3. Approve your change request My First Airline ##. 4. View the new entity for Air Z%.


325


Create and Test a User Menu

Business Example You run an airplane maintenance facility. You want your employees to access Master Data Governance from the SAP portal or SAP NetWeaver Business Client. Create a new role with an appropriate user menu. In this exercise, when values include ##, replace the characters with the number your instructor assigned to you. When values include %, replace the character with the letter that represents the number that your instructor assigned to you using the following table.

326

Letter (%)

Group Number (##)

A

01

B

02

C

03

D

04

E

05

F

06

G

07

H

08

I

09

J

10

K

11

L

12

M

13

N

14

O

15

P

16

Q

17

R

18

S

19

T

20

U

21

V

22



Letter (%)

Group Number (##)

W

23

X

24

Y

25

Z

26

Create a New User Menu 1. Copy the role SAP_MDGX_MENU and rename it ##_SAP_MDGX_MENU. a) On the SAP Easy Access - User Menu screen, in the Command field, enter PFCG. b) Choose Enter. c) On the Role Maintenance screen, in the Role field, enter SAP_MDGX_MENU. d) Choose Copy Role. e) In the Query dialog box, in the To Role field, enter ##_SAP_MDGX_MENU. f) Choose Copy All. 2. Edit the role ##_SAP_MDGX_MENU with the description ## Master Data Governance for Custom Objects: Menu. a) On the Role Maintenance screen, choose Change. b) On the Change Roles screen, in the Description field, enter ## Master Data Governance for Custom Objects: Menu. c) Select the User tab. d) On the User tab, select all of the rows that do not have your user ID. e) Choose Delete Row. 3. Create a new folder named ## Airline Maintenance. a) Choose the Menu tab. b) On the Menu tab, choose Role Menu → Master Data Governance for Custom Objects. c) Choose Create Folder. d) In the Create a Folder dialog box, enter ## Airline Maintenance. e) Choose Continue. 4. Add a Web Dynpro Application transaction to the ## Airline Maintenance folder using the data in the following table. Field

Value


USMD_ENTITY_SEARCH

Description

Search ## Airline

Parameter

PROCESS


327


Field

Value

Value

Z%CA

a) On the Menu tab, choose Role Menu → Master Data Governance for Custom Objects → ## Airline Maintenance. b) Choose Transaction → Web Dynpro Application. c) On the Web Dynpro Application dialog box, enter the data from the table. d) Choose Continue. 5. Add another Web Dynpro Application transaction to the ## Airline Maintenance folder using the data in the following table. Field

Value


USMD_ENTITY_VALUE2

Description

Process ## Airline

Parameter

IS_CREQ_MODE

Value

X

a) On the Menu tab, choose Role Menu → Master Data Governance for Custom Objects → ## Airline Maintenance. b) Choose Web Dynpro Application. c) On the Web Dynpro Application dialog box, enter the data from the table. d) Choose Continue. e) On the Change Roles screen, choose Save. f) Choose Save. g) Choose Back until you return to the SAP Easy Access - User Menu screen. 6. View the new user menu in SAP NetWeaver Business Client. a) On the SAP Easy Access - User Menu screen, in the Command field, enter NWBC. b) Choose Enter. c) On the Launch NetWeaver Business Client screen, choose /nwbc. d) On the SAP Business Client screen, on the Workcenter toolbar, choose Master Data Governance for Custom Objects. e) In the navigation panel, view your new menu item ## Airline Maintenance. Test the New Business Scenario 1. Create a new change request and change the standard data model to a) On the Workcenter toolbar, choose Financial Master Data Governance. b) In the Change Requests section, choose Create Change Requests.

328



c) On the Create Change Request Step 1 (General Data) screen, choose Change Model. d) On the Change Model dialog box, in the Standard Data Model field, enter Z%. e) Choose Save and Apply. 2. Create and submit a change request using the data in the following table. Screen Name

Field

Value


Description

My First Airline ##


Type

## Airline Single Maintenance


Airline

Z%


Explanation

This is my first airline.


Airline Description (medium Air Z% text)



EUR


Airline URL

www.air-Z%.com

a) On the Create Change Request: Step 1 (General Data) screen, enter the data from the table. b) Choose Next. c) On the Create Change Request: Step 2 (Reason for Change) screen, enter the data from the table. d) Choose Next. e) On the Create Change Request: Step 3 (Changes) screen, enter the data from the table. f) Choose Next. g) On the Create Change Request: Step 4 (Check and Submit) screen, choose Submit. h) On the Create Change Request screen, choose Show My Change Requests. 3. Approve your change request My First Airline ##. a) On the My Change Requests screen, select your change request My First Airline ##. b) On the Process Change Request: Air Z% screen, choose Finalize Processing. c) Choose Close. d) On the My Change Requests screen, choose My Change Requests. e) On the Approve Change Request: Air Z% screen, choose Approve.


329


f) Choose Close to close the internet browser windows and return to the SAP Business Client screen. 4. View the new entity for Air Z%. a) On the SAP Business Client screen, choose Change Requests → Entity Search. b) On the Search for Entities screen, in the Entity Type drop-down menu, choose Airline. c) In the Search Results table, choose Air Z%. d) Choose Close to close the internet browser and return to the SAP Easy Access - User Menu screen.

330





●



331


332


Unit 8

319

Learning Assessment

1. How many types of storage are available for entities? Choose the correct answer. X

A 1

X

B 2

X

C 3

X

D 4

2. Referencing, Leading, and Qualifying are all types of data modeling relationships. Determine whether this statement is true or false. X

True

X

False

3. What is Floorplan Manager used for? Choose the correct answer. X

A Creating a new data model

X

B Processing change requests

X

C Setting up the UI configuration

X

D Viewing the process workflow

4. The services in the Workcenter are links to what? Choose the correct answer. X

A Change Requests

X

B Data Models

X

C User Interfaces

X

D Workflow templates


333


5. Process modeling of change requests allows you to redefine the user interface based on _______________. Choose the correct answer.

334

X

A The business partner

X

B The type of change request

X

C The user's input

X

D The workflow template


Unit 8

321


1. How many types of storage are available for entities? Choose the correct answer. X

A 1

X

B 2

X

C 3

X

D 4

2. Referencing, Leading, and Qualifying are all types of data modeling relationships. Determine whether this statement is true or false. X

True

X

False

3. What is Floorplan Manager used for? Choose the correct answer. X

A Creating a new data model

X

B Processing change requests

X

C Setting up the UI configuration

X

D Viewing the process workflow


335


4. The services in the Workcenter are links to what? Choose the correct answer. X

A Change Requests

X

B Data Models

X

C User Interfaces

X

D Workflow templates

5. Process modeling of change requests allows you to redefine the user interface based on _______________. Choose the correct answer.

336

X

A The business partner

X

B The type of change request

X

C The user's input

X

D The workflow template


Mdg100 en Col10 Ilt Fv Inst a4

Recommend Documents