MDG Config Mat 80 SP00

Configuration Guide Document version: 1.0 – 2015-06-03

Master Data Governance for Material

PUBLIC

Document History

Caution Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: xxx /xxx The following table provides an overview of the most important document changes. Table 1 Version

Date

Description

1.0

2015-06-03

Final Version

2

PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.

Master Data Governance for Material Document History

Content

1

Master Data Go vernance for Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2

Services to be Activated for MDG Web Dynpro Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15

Configuring Master Data Governance for Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Activate th the Data Model MM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Activate Business Configuration Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Configuring Business Context Viewer for MDG Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Verify UI Modeling (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Set Up Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Verify Data Quality and Search Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Configure Ch Change Request Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Configure Wo Workflow Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Set Up the Rule-Based Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Set Up Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuring SO SOA Ma Manager for Master Data Governance for Material . . . . . . . . . . . . . . . . . . . . . . . . . 34 Set Up Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Choose where you want to run SAP Master Data Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Final St Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Document Management System (DMS) Integration (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4 4.1

Adapting Master Data Governance for Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Data Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Concept of the MDG Data Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Data Mod Mode el for Master Data Governance for Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Extending th Extending t he Data Model for Master Data Governance for Material . . . . . . . . . . . . . . . . . . . . . . . 51 Transportation of Data Models to the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Transporta Defining Data Models in the Configuration Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 UI Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Managing off UI Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Managing o Master Data Governance for Material UI Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Configuring Web Dynpro Page and Panel Titles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Configurin Process-Oriented an Process-O and Hi Hierarchical Ov Overview Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Data Quality and Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Search Pr Pro oviders for Master Data Governance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Definition off Validations and Derivations in BRFplus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Definition o Checks and Derivations for Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Data Qual Qualiity Remediation Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Process Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Defining a Governance Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Setting Up New Business Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Configuration of the Change Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Configurat Scope for Hierarchy-Specific Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Navigation to the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Navigation

4.2 4.3

4.4

Master Data Governance for Material Content


3

4.5 4.6

4.7

4.8

4

Enabling Detailed Analysis of Change Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Value Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Value Mapping: Use of Global Code Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Value Mapping: Use of System-Specific Code Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Value Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Key Mapping for Material Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Key Mapping for Other IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing for ALE Audit (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Governance Ap Application Pr Programming In Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


114 119 120 121 123 124 124 124 125 125 127

Master Data Governance for Material Content

1


Master Data Governance for Material enables you to monitor and control the creation, editing, and deletion of material master data. This documentation provides the information you require to set up Master Data Governance for Material. It supplements the information provided in Customizing as well as the information about activities that you need to execute in addition to configuring Customizing settings.

Master Data Governance for Material Master Data Governance for Material


5

2

Services to be Activated for MDG Web Dynpro Applications

For security reasons the services delivered for Web Dynpro applications initially are available in an inactive state only. You have to activate the services you want to use.

Activities To activate the services, proceed as described below: 1.

On the Maintain Services screen Services screen (transaction SICF), make sure that the Hierarchy Type SERVICE Type SERVICE is selected, enter the Service Name , Name , and choose Execute Execute . .

2.

Choose

Serv Se rvic ice/ e/Ho Host st

Acti Ac tiva vate te , to activate the service.

Note You have to perform the procedure for each single service you want to activate. Once you have activated a service it cannot be reset to inactive. The table below provides a list of the services used in the respective components of SAP MDG, central governance . . governance Table 2 Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

S / MDG-BP

APB_LA APB _LAUNC UNCHPA HPAD D Lau Launch nchpad pad

x

BS_OVP_BP

x

Web Dynpro Component for BP OVP

BS_OVP_CC

Cleansing Case

x

Application CONFIGURE_APP

Application

LICATION

Configuration

CONFIGURE_COM Configure PONENT

Component

CUSTOMIZE_COM Component PONENT

Configurator for the Administrator Layer

DRF_ADHOC_REP

Adhoc Replication

LICATION

Model

6


Master Data Governance for Material Services to be Activated for MDG Web Dynpro Applications

Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

x

x

x

x

x

x

x

DRF_FILTER_POW Filter Maintenance x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

S / MDG-BP

DRF_FILTER_BO_F Filter Criteria PM DRF_FILTER_POW Application L_AC

Configuration for Filter POWL

L_QAF_AC

POWL

DRF_FPM_OIF_MO Monitoring Web NITORING

Dynpro Application

DRF_FPM_SEG_FL Application TR_POPUP_AC

configuration for the popup

DRF_MANUAL_RE

Manual

PLICATION

Replication

FPM_CFG_HIERAR FPM Application CHY_BROWSER

Hierarchy Browser

IBO_W IBO _WDA DA_I _INB NBOX OX

Lean Le an Wor Workf kflo low w Inbox Application

MDG_ANLY_CR_R

Change Request

EJ_REASON

Rejection reason

MDG_BS_CONVER Master Data File TOR

x

x

Convertor

MDG_BS_DL_DISP Web Dynpro

x

x

x

x

Data Load Monitor x

x

x

x

MDG_BS_FILE_IM

Application for File x

x

x

x

PORT

Import

MDG_BS_GEN_M

Generic Mass

C_OVP

Change

LAY_LOG

Application MDG_BS_DL_DIS PLAY_LOG

MDG_BS_DL_MO NITOR_CONF

x

Application MDG_BS_MAT

MDG-M: UI (entry

x

point) MDG_BS_MAT_M

MDG-M: Mass

C

Change UI


x


7

Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

S / MDG-BP

MDG_BS_MAT_OV MDG-M: UI with P

x

CBA

MDG_BS_MAT_SE MDG-M: UI, ARCH

Search

MDG_BS_WD_AN

Analyse ID Web

ALYSE_IDM

Dynpro

MDG_BS_WD_ID_

Web Dynpro

MATCH_SERVICE

Application

x

x

x

x

x

x

x

x

x

x

x

x

x

MDG_BS_WD_ID_ MATCH_SERVICE MDG_BS_WD_RSI

Display

_DISPLAY

Replication Status Display

MDG_CREQUEST_ Application for GRAPH_ANALYSI

x

Flash

S MDG_CR_PROCES Processing Time

x

TIME_TREE MDG_DATALOAD_ Export Master EXPORT_WDA

x

Data and Mapping Information

MDG_DISPLAY_C

Cell Colors used

OLORS

for Highlighting

x

x

x

x

OVP fo forr MDG MDG Da Data ta x

x

x

x

Changes MDG_ MD G_DQ DQR_ R_OV OVP P

Quality Remediation MDG_EXTR_FPM_

Extractor

x

CMP MDG_FILE_UPLOA File Uploader

x

D_CMP MDG_MONITOR_C Application R_PROCESTIME

x

x

x

Configuration for Monitoring CR Processing Time

MDG_TRANSFOR

Transformer

MER_FPM_CMP

component for

x

FPM MDGF MD GF_O _OVP VP_G _GEN EN

8

MDGMD G-F F Ap Appli plica catio tion n


x


Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

S / MDG-BP

OIF_CF OIF _CFG_C G_CENT ENTER ER BCV Con Config figura uration tion

x

Center (FPM) POWL

Personal Object

x

Work List USMD_APPLICATI

Web Dynpro

ON_LOG

Application

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

USMD_APPLICATI ON_LOG USMD_BRFPLUS_

BRFplus Catalog

CATALOG_BROW

Browser

SER USMD_CHANGE_

Change

DOCUMENT

Documents

USMD_CREQUEST Create Change _CREATE

Request

USMD_CREQUEST USMD_CREQUES _PROCESS

T_PROCESS

USMD_CREQUEST Workflow _PROTOCOL2

Information

USMD_DISTRIBUT Web Dynpro E

Application USMD_DISTRIBU TE / Component FPM_OIF_COMPO NENT

USMD_EDITION

Edition

x

USMD_EDITION_C Edition

x

OMPARE

Comparison

USMD_EDITION_C Display of Change REQUEST

x

x

x

x

Requests of an Edition

USMD_EDITION_H Edition History

x

ISTORY2 USMD_ENTITY

Collective

x

x

x

x

x

x

Processing of an Entity USMD_ENTITY_SE Search for Entities ARCH



9

Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

x

x

S / MDG-BP

USMD_ENTITY_VA Single Processing LUE2

of an Entity

USMD_FILE_DOW

File Download

x

x

x

x

x

x

x

x

x

x

NLOAD USMD_FILE_UPLO File Upload AD USMD_ISR_PROC

ISR Processing of

ESS

a Change Request

USMD_MASS_CH

Mass Change

x

x

x

x

MDG: MD G: Ap Appli plica catio tion n

x

x

x

x

ANGE USMD US MD_O _OVP VP_G _GEN EN

for Custom Objects USMD_REMOTE_

Remote Where-

WHERE_USED

Used List

USMD_RULE

Rule Engine

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

Configuration for Validation and Derivation USMD_SEA EAR RCH

MDG Ge Generic Search

USMD_UI_CONFIG Manage UI URATION

Configuration

USMD_S USM D_SSW_ SW_RUL RULE E Def Defini inition tion of Rules Rules for Rule-Based Workflow USMD_WF_NAVIG

Workflow-Based

ATION

Navigation

USMD_WHERE_U

Where-Used List

x

ACL Maintenance

x

x

x

x

x

x

x

x

x

x

x

x

x

SED WDA_AUTH_OIF_ ACL_FRAME WDA_BS_ANLY_LI Simplified ST

Reporting: Simple List on BI Query

WDA_BS_ANLY_LI List ST_OVP

10



Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

x

S / MDG-BP

WDA_CF WDA _CFG_E G_ENTR NTRY Y Ent Entry ry She Sheet et of BCV Configuration Center (POWL) WDA_CFG_GAF_W Configuration IZARD

Wizard

WDA_CFG_LAUNC Launchpad HPAD

Maintenance

WDA_CFG_OIF_U

Web Dynpro

GRP

Application /BCV/ WDA_CFG_OIF_U GRP / Component FPM_OIF_COMPO

WDA_MDG_DT_C

Configuration

ONF_WORKBENC

Workbench

H WDA_OIF_MANAG Manage Interface E

Models

WDA_OIF_DISPLA

Display OIF Model

x

x

x

x

WDA_OIF_CREAT

Create Outbound

x

x

x

x

E

Interface

WDA_OIF_WHERE

Interface Models

x

x

x

x

USED

Usage x

x

x

x

x

x

x

x

Y

WDA_QRM_BRF_O BRFplus Object BJMAN

Manager

WDA_SMT

Service Mapping Tool Web Dynpro Application

WDA_ WD A_UI UIF_ F_DA DASH SHB B

PCV PC V Das Dashb hboa oard rd

x

x

x

x

WDA_UIF_MAIN

PCV Main

x

x

x

x

WDA_UIF_SIDEPA

BCV Side Panel for x

x

x

x

NEL

Standalone Mode

WDC_CFG_PAGE_

Page Builder

x

x

x

x

x

x

x

x

BUILDER WDC_CFG_XC_ME Xcelsius Metadata TA

Extraction Standalone Application



11

Service

Name

MDG-C / MDG-

MDG-M

MDG-F

MDG-CO

x

x

x

x

x

x

x

x

S / MDG-BP

WDC_UIF_CHIP

BCV Ch Chip

WDC_UIF_COCKPI BCV Cockpit Start T WDR_ WD R_CH CHIP IP_P _PAGE AGE

wdr_ wd r_ch chip ip_pa _page ge

x

x

x

x

WD_GLOBAL_SET

Cross-Application

x

x

x

x

TING

Settings for Web

SAP GUI for HTML x

x

x

x

Dynpro ABAP WEBGUI

12



3

Confi fig guring Master Data Governance for Material

To use SAP Master Data Governance (MDG) for material, you need to carry out the steps described below.

Prerequisites Business Function

You have activated the following business functions: ●

Master Data Governance, Generic Functions ( MDG_FOUNDATION )

●

Master Data Governance, Generic Functions 2 ( MDG_FOUNDATION_2 )

●

Master Data Governance, Generic Functions 3 ( MDG_FOUNDATION_3 )

●

Master Data Governance, Generic Functions 7.0 ( MDG_FOUNDATION_4 )

●

Master Data Governance, Generic Functions 7.0 Feature Pack ( MDG_FOUNDATION_5 )

●

Master Data Governance, Generic Functions 8.0 ( MDG_FOUNDATION_6 )

●

Master Data Governance for Material ( MDG_MATERIAL )

●

Master Data Governance for Material 2 ( MDG_MATERIAL_2 )

●

Master Data Governance for Material 3 ( MDG_MATERIAL_3 )

●

Master Data Governance for Material 7.0 ( MDG_MATERIAL_4 )

●

Master Data Governance for Material 7.0 Feature Pack ( MDG_MATERIAL_5 )

●

Master Data Governance for Material 8.0 ( MDG_MATERIAL_6 )

Note Before you activate the business functions, ensure that you have the administration authorization for MDG. The required authorization objects are delivered with the authorization role SAP_MDG_ADMIN . In transaction PFCG , we recommend creating a copy of this role and assigning the relevant authorization values. For the authorization object USMD_DM Data Model you Model you need to assign the values for the authorization field USMD_MODEL Data Model (for Model (for example MM , BP , or 0G ) and the values for the authorization activity ACTVT Activity Activity (for (for example 01: Create or generate, or 02: Change). If you want to use Enterprise Services to load data into the active or staging area of the hub, activate the business function ERP_MATERIAL_SOA . For additional BCV Content activate business function /BCV/NWBC_SIDEPANEL . If you want to use the MDG for Material homepage or the Business Context Viewer, activate the business functions /BCV/MAIN and /BCV/MAIN_1 . For more information on the Business Context Viewer see, Business Context Viewer in Single Processing [external Processing [external document] . When you activate the MDG_Material business function the system activates the Material ( MM ) data model. Before continuing with system configuration, open transaction SFW5 and check if the activation has been completed by choosing Switch Framework Logs from Logs from the Goto Goto menu menu and selecting the corresponding entry. Set Up Workflow

Master Data Governance for Material Configuring Master Data Governance for Material


13

To use the rule-based workflow processes of MDG for material, you have defined general settings for SAP Business Workflow [external Workflow [external document] in Customizing for SAP NetWeaver under Application Server Business Mana Ma nage geme ment nt SA SAP P Busine Business ss Work Workfl flow ow . Remember to regenerate the authorization profile of SAP_ALL or include USMD* authorization objects into the authorization for the user WF-Batch. To activate the workflow features, use the semi-automated configuration in transaction SWU3 . You can also access these settings in Customizing under SA SAP P Net NetWe Weave averr Ap Appl plic icati ation on Se Serve rverr Bu Busi sine ness ss Ma Mana nage geme ment nt SAP Busin Business ess Work Workflo flow w Main Maintai tain n Standar Standard d Setting Settingss For further information see the documentation for the Configuration activity. Note the following when maintaining the settings: ●

When configuring the RFC destination you need superuser authorization to create the default WF-BATCH user.

●

Regenerate the authorization profile for SAP_ALL or include the USMD* authorization objects into the authorizations of the user WF-Batch.

●

For the Check Entries from HR Control Tables section Tables section you may need to execute report RHSOBJCH in transaction SE38 and keep the default settings.

●

Maintain the prefix numbers for the standard objects.

●

You do not need to maintain the Web Server node and Guided Procedures section.

Set Up Search

You must have installed and connected Enterprise Search either in embedded form or as central search engine service in order to use master data governance for material. If you don’t need to search for classifications you can replace the Enterprise Search with the standard database search or another search provider. Adjust Profile Parameters

Ensure that the profile parameter size for the Shared Objects Memory is Memory is the correct. To check this setting run transaction RZ11 and verify that the value for parameter abap/shared_objects_size_MB is between 200 and 300 megabytes. If you want to use the SAP NetWeaver Business Client with Client with single sign on, ensure that the parameters login/ create_sso2_ticket and login/accept_sso2_ticket are set correctly. Use transaction RZ11 to check that the host name is fully qualified for parameter icm/host_name_full . User Roles

In order to successfully conduct the next steps in the configuration process, you must have the following user roles assigned in the PFCG PFCG transaction: transaction: ●

SAP_BC_TREX_ADMIN

●

SAP_ESH_LOCAL_ADMIN

●

SAP_MDGA_MENU – Master Data Governance: Analytics

●

SAP_MDG_ADMIN – Master Data Governance: Administrator

This role contains authorizations for basic tasks relevant to the configuration and administration of SAP Master Data Governance (MDG) for all domains. Some authorizations allow critical activities. If you have multiple users involved in the configuration and administration of MDG content, we recommend you split this role into several new roles and give each new role a subset of the authorizations for this role. Such an approach ensures users only complete tasks they are responsible for and reduces the risk of critical errors. Authorizations for the MDG transactions are not included in this role. ●

Menu [external document] SAP_MDGM_MENU_06 – Master Data Governance for Material: Menu [external

●

Display [external document] SAP_MDGM_DISP_06 – Master Data Governance for Material: Display [external

●

Requester [external document] SAP_MDGM_REQ_06 – Master Data Governance for Material: Requester [external

14



●

SAP_MDGM_SPEC_06 – Master Data Governance for Material: Specialist [external Specialist [external document]

●

Steward [external document] SAP_MDGM_STEW_06 – Master Data Governance for Material: Data Steward [external

In addition, the authorization object PLM_SPUSR is needed if the Search Object Connector for Connector for enterprise search is created for the Enterprise Search Software Component PLMWUI or any Enterprise Search Software Component that includes PLMWUI . The role SAP_PAGEBUILDER_DISPLAY is required to use the Page Builder tool Builder tool for accessing homepages created using Page Builder . Builder . Web Dynpro Application Applications s

For security reasons the services services delivered for Web Dynpro applications are delivered in an inactive ve state. You must activate the services services you want to use. Use transaction SICF to activate the services. For a detailed detailed list of the relevant services, see Services to be Activated for Web Dynpro Applications [page 6] . 6] .

Process This process describes the minimal set of customizing steps and recommended check activities required to do the following: ●

Create materials

●

Change materials

●

Mark materials for deletion deletion

●

Process multiple materials materials

●

Multiple-record processing processing

You run the settings for this t his process in Customizing under Cro ss-Application Components Tools Too ls for Enterpr Enterprise ise Applic Applicatio ations ns Mas Master ter Data Data Governan Governance ce . 1.

Activate the Data Model MM [page 16]

2.

Activate Business Configuration Set [page 17]

3.

Configuring Business Context Viewer for MDG Material [page 18]

Processes and

4. Verify UI Modeling (Optional) [page 19] 5.

Set Up Search [page 20]

6. Verify Data Quality and Search Settings [page 22] 7.

Configure Change Request Settings [page 23]

8. Configure Workflow Tasks [page 26] 9. Set Up the Rule-Based Workflow [page 27] 10. Set Up Data Transfer [page 31] 11. Configuring SOA Manager for Master Data Governance for Material [page 34] 12. Set Up Data Replication [page 38] 13. Document Management System (DMS) Integration (Optional) [page 43] 14. Choose where you want to run SAP Master Data Governance [page 41] 15. Final Steps [page 43]



15

Result The system is configured for MDG for material. In addition, if data load has been done, mass changes and distribution to other systems can also be executed.

More Information ●

For information on functional restrictions, see SAP Note 1806108 for MDG 8.0.

●

Master Data Governance Security Guide [external Guide [external document]

for MDG 7.0 and SAP Note 2129261

Impact of Material Master Customizing Some Material Master customizing activities are relevant for Master Data Governance for Material: ●

Under the Configuring the Material Master node, Master node, the activity Define How Maintenance Statuses Are Determined in Data Transfer impacts Transfer impacts Master Data Governance for Material.

●

Under the Field Selection node, Under Selection node, all activities that change the field properties properties affect the field properties in Master Data Governance for Material. The field properties hidden, displayed, mandatory, and optional impact the Master Data Governance for Material fields.

●

Under the Basic Settings node, Settings node, all activities impact Master Data Governance for Material. Example settings include the output format of the material number and the material types.

●

Under the Settings for Key Fields node, Fields node, all activities impact Master Data Governance for Material. Example settings include the definition of material groups, and the settings for EANs.

●

Under the Data Transfer: Material Master node, Master node, the activity Define Required-Field Check for ALE/Direct Input impacts Master Data Governance for Material. There you define how the material master for industry is updated if required fields not belonging to the core maintenance status lack entries.

Setting Backend Fields to Read-Only If you operate a MDG hub, and if you make changes to fields under governance in the material master using a backend transaction ERP, these changes will be overwritten by the next change request created for that material. To prevent this, SAP recommends that you set fields under governance to ready-only in your non-hub systems. The recommended approach for this process in SAP systems is to define new material master backend data screens and screen sequences in the configuration activity Configuring the Material Master . Master .

3.1

Activate th the Da Data Mo Model MM MM

Check (or enhance) and activate the MM MM data data model including temporary IDs for internal number handling. 1.

Check whether whether you can use use the data data model delivered delivered by by SAP for managi managing ng your materia materiall master data data with MDG for material. Activate the delivered data model MM MM in in Customizing for Master Data Governance, Central Governance under Governance under Gene Ge nera rall Set Setti ting ngss Da Data ta Mod Model elin ing g Ed Edit it Dat Data a Mod Model el .

Note You can select the governance scope at any point after you activate the Data Model. The governance scope determines which fields from the data model can be edited by the Master Data Governance application.

16



Use this customizing activity to narrow the governance scope: Master Data Governance, Central Gove Go vern rnan ance ce Ge Gene nera rall Sett Settin ings gs Pr Proc oces esss Mode Modeli ling ng De Defi fine ne Gov Gover erna nanc nce e Scop Scope e By deactivating or reactivating an entity, a relationship, or an attribute you are not changing any dictionary or database object; you are only changing the ability of MDG to edit the chosen object. When you take a field out of governance scope it becomes read-only on the MDG UI and you may wish to remove it. You can use the Customizing activity Import BC Set to Reset Governance Scope to Scope to set the governance scope to the EHP6 model which contains only identifying and descriptive data.

Caution When upgrading to MDG 8.0 check 8.0 check that the active and inactive versions of your data models are the same. Changes to the data models, not dependent on business function switches, may occur due to corrections made by SAP. You should check and activate all models after the upgrade to MDG 8.0 is 8.0 is complete. To do this navigate to Ma Mast ster er Da Data ta Go Gove verna rnanc nce, e, Ce Cent ntral ral Go Gove verna rnanc nce e Ge Gene neral ral Se Sett tting ingss Da Data ta Mo Mode delin ling g Ed Edit it Data Model and activate any data models that have the entry Different in the column Active column Active Version . Version . 2. As Assi sign gn an in inte tern rnal al ke key. y. To support internal internal key assignment, run the activity in Customizing for Master Data Governance, Governance, Central Governance under Governance under Gen Genera erall Sett Setting ingss Dat Data a Mode Modeling ling Def Define ine Pre Prefix fixes es for Inte Internal rnal Key Ass Assignm ignment ent . Example: If you create new entries with the following values, all temporary IDs are prefixed with $ and an internal sequence number. ○

Data Model: MM

○

Entity Type: MATERIAL

○

Prefix: $

Note For MDG for material, authorizations cannot be defined here. Instead, the existing back-end authorizations are reused. For more information, see Customizing under Authorizations and Authorization Profiles .

Logi Lo gist stic icss – Ge Gene nera rall

Mate Ma teri rial al Mas aste terr

Too To ols

Main Ma inta tain in

Other customizing activities in data modeling are only relevant for the material domain if your data model needs to be enhanced. For more information, see Enhancement of Master Data Governance Content [external document] and Extending the Data Model for Master Data Governance for Material [page 51] . 51] .

3.2 3. 2

Acti Ac tiva vate te Bu Busi sine ness ss Co Conf nfig igur urat atio ion n Set Set

For create materials, change materials, mark materials for deletion and process multiple materials there are example change request types available. Open the document assigned to this activity in Customizing Master Data Governance, Central Governance under Governance under Masterr Data Govern Maste Governance ance for for Material Material Impor Importt Predefined Predefined Change Reque Request st Types Types . Open the link in the document and check that the BC-Set MDGM_MDG_MATERIAL_CREQUESTTYPE_6 is selected. To start, choose Activate choose Activate BC Set and Set and keep the default settings. For Multiple-Record Processing there Processing there are example change request types available. Run the following activity under Customizing for Master Data Governance under Mas Master ter Data Data Governan Governance ce for Mater Material ial Imp Import ort Predef Predefine ined d



17

Change Request Types for Multiple-Record Processing . Check that the BC-Set MDGM_MDG_MATERIAL_CR_MC_05 is selected. If you want to use the MDG for Material homepage or the Business Context Viewer (BCV) then activate the BC set Menu To Too ols Cu Cust stom omiz izin ing g Bu Busi sine ness ss Con Confi figu gura rati tion on Set Setss MDGAF_BCV and MDGMAT_BCV_70 under SAP Me Activation of BC Sets .

3.3 3. 3

Conf Co nfig igur urin ing g Busi Busine ness ss Con Conte text xt Vie Viewe werr for for MDG MDG Mate Materi rial al

You can use this function to view context-related information for your material master data in a side panel. You must activate the Business Context Viewer (BCV) to access the side panels for the Web Dynpro applications Create Material and Material and Change Material . Material .

Prerequisites The business content for MDG Material is delivered in the BC sets BCV Content for MDG Framework ( MDGAF_BCV ) and BCV Content for MDG Material Release 7.0 ( 7.0 ( MDGMAT_BCV_70 ). You must activate them in transaction SCPR20 .

Process To view this content, open the BCV side panel by choosing the Side Panel link Panel link in the upper right corner of your MDG Material user interface. From the side panel, select the following overviews you require from the dropdown list: Sales Overview

This BCV content provides you with a list of all sales orders created for the current material master data. Production Overview

This BCV content provides you with a list of all production orders created for the current material master data. Purchasing Purchasin g Overview

This BCV content provides you with a list of all purchase orders created for the current material master data. Changes Overview

This BCV content provides you with a list of changes raised by the current MDG change request. Thumbnail Overview

This BCV content provides you with a picture preview in the side panel if you have linked to documents with picture files for your material master data.

More Information Information For more information about BCV, see Business Context Viewer (BCV) [external (BCV) [external document]

18



3.4 3. 4

Ver eriify UI Mo Mode dellin ing g (Op (Opttio ion nal al))

UI configuration activities are only relevant if you want to change the UI or if the MM data model has been enhanced. In this Customizing activity, you can specify if and where the system hides the entity types for the data model MM . Verify the pre-delivered field properties for the data model MM in Customizing under Ge Gene nera rall Se Sett ttin ings gs UI Modeli Mod eling ng Def Define ine Fie Field ld Prop Properti erties es for UI . For data model MM only specific fields are disabled for some of the processes: ●

Example: Material Type ( MTART ) and Material ID ( MATERIAL ) are not available as fields in mass change processes.

The Web Dynpro application and the application configuration in the PFCG role combine with settings made in Customizing to determine the UI displayed. You need to verify the UI modeling for the following Web Dynpro application configurations: Table 3 Web Dynpro Application

Application Configuration

UI

MDG_BS_MAT

BS_MAT_INIT_06

Initial Screen

MDG_BS_MAT_OVP

BS_MAT_OVP_06

Process-oriented UI

MDG_BS_MAT_OVP

BS_MAT_OVP_06H

Hierarchical UI

MDG_BS_MAT_SEARCH

MDG_BS_MAT_SEARCH_06

Search UI

MDG_BS_MAT_SEARCH

MDG_BS_MAT_SEARCH_04H

Search UI with org-level details

Note Context based adaptations (CBA) are available for the following application configurations: BS_MAT_INIT_06 , BS_MAT_OVP_06 , and BS_MAT_OVP_06H . You can use context based adaptations (CBA) to influence the UI dynamically based on field values. CBAs are part of the component configurations. Context-based adaptations contain predefined values for dimensions. The predefined dimensions are: Logical Action , Action , Type of Change Request , Request , Material Type , Type , and Change Request Step . Step . These dimensions are defined in the schema BS_MAT . The predefined schema can be found in the view cluster FPM_VC_ADAPT_SCHEMA accessed through transaction SE54 . There are pre-delivered CBAs for the application configurations BS_MAT_INIT_06 , BS_MAT_OVP_06 , and BS_MAT_OVP_06H . An adaptation is delivered for the action Delete Delete . . Some UIBBs are hidden and the Mark for Deletion flag is shown. An adaptation is delivered for the change request type MAT0A (Load). In this case the UIBB containing the basic data contains the Mark for Deletion indicator Deletion indicator to enable the user to check and adapt it. If you use another change request type for the same purpose you have to create your own adaptation. CBA schema can be reused and enhanced with custom-defined dimensions. You can create your own schemas and UI configurations without modification. See the UI extensibility guides for more information.

Note You can view the Web Dynpro applications using transaction SE80 . The package name is MDG_BS_MAT_UI . If you want to restrict viewing and editing of the material description to the current logon language, see SAP Note 2130057

. If you want to use PDF print print forms you can activate the BC set



19

MDGM_MDG_MATERIAL_VC_USMD140_06 . This assigns the print form MDG_BS_MAT_PDF_06 to the relevant UI

configurations.

3.5

Set Up Search

MDG offers several options to search for the data in change requests including the active and inactive data. The search options are distinguished by their capabilities and their landscape requirements. The main difference is in their capability to include classification data in the search. These are the following options: ●

SAP search engine-based search ( TREX TREX search) search) offers full search capabilities.

●

You can use SAP HANA-based search to connect the MDG database to an SAP HANA-based system for search. See Configuring SAP HANA-Based Search for MDG [page 66] for 66] for more detail.

In MDG for material the default search provider is the SAP search engine based on TREX. If you want to configure the system for SAP HANA-based search, follow the instructions in the section SAP HANA-Based Search . Search . TREX-Based Search

For TREX-based search are two search options available: ●

Embedded Search (included in SAP NetWeaver on a local system)

●

SAP NetWeaver Enterprise Search (run centrally)

Embedded Search is limited to indexing and searching within a single SAP system (single SAPSID). In production scenarios with heavy data load it is mandatory to install a separate TREX instance that is used exclusively by Embedded Search for performance and sizing reasons. For installation information for TREX 7.1 see 7.1 see SAP note 1249465

.

Embedded Search

If you want to use Embedded Search, run the following activity in Customizing for SAP NetWeaver under and Ope Operati rationa onall Analyti Analytics cs Emb Embedd edded ed Sear Search ch .

Search

If you are not familiar with TREX or TREX is not yet activated, proceed as follows to make the basic settings: 1.

Connect to the TREX the TREX installation. During TREX installation, you created an RFC-destination for the TREX. Run transaction SM59 SM59 in in the TCP/IP connections section to verify that it exists and can be linked. Link the ABAP system to this TREX destination. For more information, see Customizing for SAP NetWeaver under NetW Ne tWea eave verr Ent Enter erpr pris ise e Sea Searc rch h TRE TREX X Se Sett TRE TREX X Des Destin tinat atio ion n .

Search Sea rch and Ope Operat ration ional al Anal Analytic yticss

SAP

Alternatively, you can run report ESH_ADM_SET_TREX_DESTINATION ESH_ADM_SET_TREX_DESTINATION . . 2. Cre Create ate and inde indexx the the conn connecto ectors. rs. SAP delivers the following two standard templates for MDG for material. You need to activate these templates and prepare them for indexing. ○

Material ( MATERIAL ) – for the active data residing on the standard tables MA* MA* and and related objects

○

Material Template for Template for MDG ( MDG_MATERIAL ) – for the inactive material data data linked to the MDG change requests

Open the Connector Administration Cockpit in Customizing for SAP NetWeaver under Search and Oper Op erat atio iona nall Analyt Analytic icss SA SAP P NetWe NetWeav aver er Ente Enterp rpri rise se Searc Search h Mo Mode delin ling, g, Admi Admini nist strat ratio ion, n, and Moni Monito torin ring g Op Open en Administration Cockpit . Alternatively, you can run the transaction ESH_COCKPIT . Make the following settings: 1.

20

To open open th the e Mode Modeler ler,, sele select ct th the e Modeler Modeler link. link. PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.


2.

In the Software Components menu Components menu choose Maintain Software Components and Components and choose Create Create . . Enter the name for the new software component and assign a package. Choose Create Create . . Enter a description for the new software component and choose Save Save . . Select a workbench request.

Note The new software component is necessary to get all extensions of the template MATERIAL , which are made in the included software component. When creating the search connector for MATERIAL and you have installed both, the MDG_APPL software component and the PLMWUI software component, you have to decide in which software component the MATERIAL connector is created. This is because both, MDG_APPL and PLMWUI are parent software components of SAP_APPL . Both the MDG_MATERIAL template and the MATERIAL template are used in the MDG applications (which are related to the software component MDG_APPL ). This requires that the related connectors are created in the software component MDG_APPL . However, applications related to the software component PLMWUI require, that the MATERIAL connector is created in the software component PLMWUI . However, as described above, each connector can only be created in one software component. To overcome this situation, you have to create a super component of MDG_APPL and PLMWUI . If you now create the MATERIAL or the MDG_MATERIAL connector, they are assigned to this new top level component. Related search templates can be used in all underlying software components. 3. Mark Mark your your new soft softwar ware e compone component nt and and choose choose in the the Software Component menu Component menu select Include Software Components . Components . Include the component MDG_APPL . Choose Save Save and and select Workbench Transport . . Repeat this process for the highest software component for the connector MATERIAL . For Transport example, if the software layer hierarchy is PLMWUI > EA-APPL > SAP-APPL use the software component PLMWUI but if the software layer hierarchy is EA-APPL > SAP-APPL then use the software component EA-APPL . 4. Go bac back k to to th the Administration Cockpit and Cockpit and select Create Create . . Select the new software component and search for the template MATERIAL . Once you have located the template, create the connector for the Enterprise Search . . Create the connector using the MATERIAL template first and wait for the job to complete before Search creating the connector using the MDG_MATERIAL template. 5. The The two two co conn nnec ecto tors rs Material Material and and Material Template for MDG are MDG are now visible with the status preparing and or prepared. Select the Material Material connector connector and from the Actions the Actions menu menu select Schedule Indexing . Indexing . On the new screen choose Show Input Form . Form . Next, choose the option for immediate indexing and the recurrence period. You can also activate real-time indexing if the sizing, parameters, and performance of the system allow for this. Select all object types and choose Copy Settings . Settings . This copies the default settings from the input form to all object types. The status of the connector is changed to Indexing Indexing . . 6. Ensure Ensure authorization authorization indexing. indexing. Enterprise Enterprise Search Search requires requires its own authorizati authorizations. ons. Authorizat Authorizations ions for all MDG users must be indexed on the Enterprise Search system. Search system. The system writes every new or changed user as an entry into the table ESH_AU_USR_UPD that contains the user IDs that have been changed since the last indexing of the technical object type USER_AUTHORITY . The object type USER_AUTHORITY and other object types which do not support real-time indexing need to be regularly scheduled for indexing on the Enterprise Search system. Search system. The object type USER_AUTHORITY can be found in the connector Material Material or or the connector MDG_MATERIAL . You cannot enable real-time indexing for USER_AUTHORITY . Once indexing is complete the two connectors should have the status Active . 3. Use Use the the re repo port rt ESH_TEST_SEARCH to verify the search function. In the Search Scope section, Scope section, enter a Connector ID . ID . Next, enter Default in the Request Request field field and execute the report.



21

○

MATERIAL returns the active material master data. The connector MATERIAL

○

The connector MDG_MATERIAL MDG_MATERIAL returns the inactive material master data. At least one active change request of type MAT* needs to exist with materials assigned to it, otherwise you will get a message that the search provider MDG_MATERIAL does not exist during the search and in the duplicate check of any change request where this is relevant.

For more information about TREX, see Configuration of the TREX Security Settings [external Settings [external document] . Search Engine Service

If you are running a central SAP NetWeaver Enterprise Search system and you connect other SAP NetWeaver systems with Embedded Search to the central system, follow the steps as described in Customizing for SAP NetWeaver under Se Sear arch ch Se Searc arch h Eng Engine ine Se Serv rvic ice e . SAP HANA-Based Search

To implement SAP HANA-based search follow these instructions: 1.

Enterr tran Ente transsac acti tion on MDGIMG and navigate to Mas Master ter Data Data Governan Governance, ce, Centr Central al Governan Governance ce Gen Genera erall Setti Se tting ngss Da Data ta Qua Qualit lity y and and Searc Search h Bu Busi sine ness ss Add Add-In -Inss BAd BAdI: I: Sea Searc rch h for for Data Data in in Reus Reuse e Acti Active ve Are Area a .

2. Deac Deactiv tivate ate the BAd BAdII imple implemen mentat tation ion MDG_BS_MAT_PP_SEARCH by deselecting the Active the Active (IMG) flag. (IMG) flag. 3. Fo Follo llow w the the inst instru ruct ction ionss in Configuring SAP HANA-Based Search for MDG [page 66] . 66] .

3.6 3. 6

Veri Ve rify fy Dat Data a Qua Quali lity ty and and Sea Searc rch h Set Setti ting ngs s

In the delivered standard, the SAP NetWeaver Enterprise Search is used for MDG for material. In this step, you can verify the following: ●

Existence of entry ES ES and and that Freeform Freeform , , and Fuzzy Fuzzy settings settings are activated This entry cannot be removed or deactivated (E-class entry delivered by SAP). You can verify these settings in Customizing for Master Data Governance under Governance under Ge Gene nera rall Sett Settin ings gs Da Data ta Qua Quali lity ty and and Sea Searc rch h De Defi fine ne Search Applications .

●

The pre-delivered Match Profile for Profile for the MM data model is MATCH_MM_MATERIAL . You can find this Match Profile in Profile in Customizing for Master Data Governance under Gen Genera erall Sett Setting ingss Dat Data a Qualit Quality y and and Sear Search ch Search Searc h and Duplic Duplicate ate Check Check Def Define ine Sear Search ch Appli Applicat cation ionss If you wish you can now define your own matching fields for calculating the potential duplicates and matching values.

●

Configuration of the duplicate check MATCH_MM_MATERIAL MM_MATERIAL If you want to run a duplicate check you have to assign the predelivered match profile MATCH_ or your own match profile to the MM data model and the MATERIAL entity type. Navigate to General Setti Se tting ngss Da Data ta Quali Quality ty and and Searc Search h Se Searc arch h and Dup Duplic licat ate e Chec Check k Co Conf nfig igur ure e Dupli Duplica cate te Che Check ck for for Ent Entit ity y Types . For search mode ES and data model MM select the field MPbased UI . UI . Thresholds are not considered.

You can configure this check in Customizing for Master Data Governance under Governance under Define Defin e Search Search Applica Applications tions Config Configure ure Duplica Duplicate te Check Check for for Entity Entity Types Types . ●

Data Quality and Search

Assignment of the delivered search object connector templates Ensure that for business object type 194 type 194 Material , Material , the delivered search object container MDG_MATERIAL MDG_MATERIAL and and the MDG_APPL software component is assigned. You can check this in Customizing for Master Data Governance under Governance under Ge Gene neral ral Set Setti ting ngss Search Searc h Assign Search Objec Objectt Connecto Connectorr Templates Templates to Object Object Types .

22


Data Da ta Qual Quality ity and and


3.7 3. 7

Con Co nfi figu gure re Ch Chan ange ge Req Requ uest Se Sett ttin ings gs

Depending on your requirements you might want to adjust and enhance the default change request values. The following information describes the minimal settings for a basic governance process. For more information about each customizing activity, see the relevant documentation for that customizing activity. 1.

Review and/or and/or define define which which statuses statuses the the change change requests requests can have, have, and which which processin processing g options options are enabled for those statuses. Optionally, you can add new statuses to be used in the change request types. For more information, see Customizing for Master Data Governance under Governance under Mode Mo delin ling g Ch Chan ange ge Req Reque uest stss Ed Edit it Stat Status uses es of of Chang Change e Requ Reques ests ts .

Gene Ge neral ral Se Sett tting ingss

Proce Pro cess ss

The following statuses are delivered for the SAP standard processes. Table 4 Status Value

Description

Permitted Processing

00

To Be Evaluated

Change of Object List

01

To Be Considered and Approved


02

Changes to Be Executed

Execution of Changes

03

To Be Revised


04

Final Check to Be Performed

No Processing

05

Final Check Approved

No Processing

06

Final Check Rejected

No Processing

07

Activation Failed

No Processing

08

Approved; to Be Replicated

No Processing

09

Dependent Data to Be Processed/


Approved 10

To Revise: Perform Changes


11

Process Errors After Activation


12

Approved, Contact Person to be

No Processing

Processed 99

2.

No Status Set

No Processing

Check that that the following following business business activit activities ies are in your your system system and that they they are assigned assigned to the default default data data model MM MM . . ○

MAT1 Create Material

○

MAT2 Process Material

○

MAT3 Display Material

○

MAT6 Mark Material for Deletion

○

MATA Process Multiple Materials

○

MATB Import Material

○

MATM Multiple-Record Processing



23

For more information, see Customizing for Master Data Governance under Governance under Mode Mo deli ling ng Bu Busi sine ness ss Ac Activ tiviti ities es Cr Crea eate te Bu Busi sine ness ss Ac Acti tivit vity y .

Gene Ge neral ral Se Sett ttin ings gs

Proce Pro cess ss

3. Create Create new new chang change e reques requestt types types for for data data model model MM MM , , or validate after import using business configuration sets (BC-Sets). For more information, see Customizing for Master Data Governance under Governance under Mode Mo deli ling ng Ch Chan ange ge Re Requ ques ests ts Cre Create ate Ch Chan ange ge Re Requ ques estt Typ Type e .


Proce Pro cess ss

The following table shows the change request types for data model MM MM . . Only the relevant columns are included. Table 5 Change Request

Data Model

Description

Single Object

Main Entity Type

Workflow

MAT01

MM

Create Material

Yes

MATERIAL

WS60800086

MAT02

MM

Change Material

Yes

MATERIAL

WS60800086

MAT06

MM

Mark Material for

Yes

MATERIAL

WS60800086

No

MATERIAL

WS60800086

Type

Deletion MAT0A

MM

Process Multiple Materials

MAT0B

MM

Import Material

No

MATERIAL

WS60800086

MATLMRP

MM

Multi Pro. for

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

No

MATERIAL

WS60800086

Planning Data (select) MATLPUR

MM

Multi Pro. for Purchasing Data (select)

MATLSAL

MM

Multi Pro. for Sales Data (select)

MATLUOM

MM

Multi Pro. for Dimensions Data (select)

MATMRP

MM

Multi Pro. for Planning Data (full)

MATPUR

MM

Multi Pro. for Purchasing Data (full)

MATSAL

MM

Multi Pro. for Sales Data (full)

MATUOM

MM

Multi Pro. for Dimensions Data (full)

24



The standard workflow template used by Master Data Governance for material is WS60800086 . This template is a rule-based workflow which uses BRF+ BRF+ decision decision tables. There is also a workflow template without BRF+ BRF+ , , which covers the same processes. If you want to use this template, replace template WS60800086 with template WS46000057 in the relevant change request type. The following settings should exist in the substructures of the change request types: ○

○

○

○

○

○

MAT01 ○

Entity type: MATERIAL , DRADBASIC , MATCHGMNG

○

UI Config: MDG_MM_APP_BS_MAT_GEN (Only relevant for Enhancement Package 5)

○

Msg. Output: W Issue Error Messages as Warnings

○

Business Activity: Create Material (MAT1)

○

Service Level Agreement for Change Request Types:

MAT02 ○

Same as for MAT01

○

Business Activity: Process Material (MAT2)

MAT06 ○

Same as for MAT01

○

UI Config: MDG_MM_APP_BS_DEL_GEN (Only relevant for Enhancement Package 5)

○

Business Activity: Mark Material for Deletion (MAT6)

MAT0A ○

Same as for MAT01

○

UI Config:

○

Business Activity: MATA Process Multiple Materials

MAT0B ○

Same as for MAT01

○

UI Config:

○

Business Activity: MATB Import Material

MATLMRP, MATLPUR, MATLSAL, MATLUOM, MATMRP, MATPUR, MATSAL, MATUOM ○

Entity type: MATERIAL

○

UI Config:

○

Msg. Output: Issue Error Messages as Warnings

○

Business Activity: Multi-Records Processing (MATM)

○

Service Level Agreement for Change Request Types:

4. You can configur configure e the properties properties of the the change request request steps. steps. This This is optional optional except for the the Multiple-Reco Multiple-Record rd Processing change request types. For more information see Customizing for Master Data Governance under Gene Ge nera rall Setti Setting ngss Pr Proc oces esss Mode Modeli ling ng Ch Chan ange ge Req Reque uest stss Co Conf nfig igur ure e Prope Propert rtie iess of Cha Chang nge e Requ Reques estt Step Step . For the Multiple-Record Processing change request types you can find the link to the example UI configuration under the view User Interface per Change Request Step . Step . For the change request types the following UI application names and configuration names are delivered for all steps using BC-sets:



25

Table 6

5.

Change Request Type

UI Application Name

Configuration Name

MATLMRP

MDG_BS_MAT_MC

MDG_BS_MAT_MC_MRP_DT

MATLPUR

MDG_BS_MAT_MC

MDG_BS_MAT_MC_PURCH_DT

MATLSAL

MDG_BS_MAT_MC

MDG_BS_MAT_MC_SALES_DT

MATLUOM

MDG_BS_MAT_MC

MDG_BS_MAT_MC_UOM_DT

MATMRP

MDG_BS_MAT_MC

MDG_BS_MAT_MC_MRP_IT

MATPUR

MDG_BS_MAT_MC

MDG_BS_MAT_MC_PURCH_IT

MATSAL

MDG_BS_MAT_MC

MDG_BS_MAT_MC_SALES_IT

MATUOM

MDG_BS_MAT_MC

MDG_BS_MAT_MC_UOM_IT

Optionally, you can define Optionally, define priorities priorities,, reasons, reasons, or rejection rejection reasons reasons for change change requests. requests. You You can enter codes codes and a short description to tag or classify your change requests. These codes can be used later for change request analytics (process quality analysis). They also can be used to influence the workflow-driven processes. For example, depending on the priority of a change request, you can mark it for special processing. Perform the following activity in Customizing for Master Data Governance under Governance under General Settings Proces Pro cesss Modelin Modeling g Cha Change nge Requ Request estss Def Define ine Prior Prioritie itiess / Reason Reasonss / Reject Rejection ion Reaso Reasons ns for for Change Change Requests .

6. Optionally, Optionally, you can define define print forms for for change change requests. requests. By By default, default, the form formUSMD_EDITION_CREQUEST USMD_EDITION_CREQUEST is used. This is relevant only if your own or multiple print forms are required. For more more information, see Customizing for Master Data Governance Governance under under Mode Mo deli ling ng Ch Chan ange ge Req Reque uest stss De Defi fine ne Prin Printt Form Form for for Cha Chang nge e Requ Reques ests ts .

3.8


Proce Pro cess ss

Configure Wo Workflow Ta Tasks

As a prerequisite you have made the necessary general settings for workflows and defined the organizational plan in Customizing for SAP NetWeaver under Application Server Business Management SAP Business Workflow . Ensure that the active type linkages for Material (BUS2250) are set correctly. Follow the instructions in Customizing for MDG under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow Ac Acti tiva vate te Ty Type pe Li Link nkag age e . For object type BUS2250 check that the Type Linkage Active indicator Active indicator is active for the events CREATED , ACTIVATED , and ROLLED_BACK . In addition, check that the Enable Event Queue indicator Queue indicator is active for the events ACTIVATED , and ROLLED_BACK , but not for the event CREATED . The standard workflow template used by Master Data Governance for material is WS60800086 WS60800086 . . In order to ensure the general assignment of processors using the rule-based workflow, run the following activity in Customizing for Master Data Governance under Governance under Ge Gene nera rall Sett Settin ings gs Pr Pro oce cess ss Mod Model elin ing g Wo Work rkfl flow ow Co Conf nfig igur ure e Workflow Tasks . 1.

Go to ap appli plica cati tion on co compo mpone nent ntCA-MDG-AF CA-MDG-AF and and choose Assign choose Assign Agents . Agents .

2.

Set the Dialog Processing ( Processing ( TS 60807954 ) task attributes, if it not already set. To do so, select the task, and choose Attributes choose Attributes . . You must assign an agent to a task in this step, in order to assign that agent as processor to a change request step. If you use an agent in your workflow that is not assigned as a processor to a task here, your workflow

26



will end in an error at runtime unless you have classified the task as a general task. There are four options you can choose from when assigning an agent to a task: ○

Choose General Task if Task if you want to be able to assign and forward the task to anyone.

○

Choose General Forwarding Allowed if Allowed if you want the task to be initially assigned to one of your possible agents but want to allow it to be forwarded to anyone.

○

Choose General Forwarding not Allowed if Allowed if you only want the task to be initially assigned and forwarded to possible agents.

○

Choose Forwarding not Allowed to Allowed to prevent any forwarding of the task.

Select the option you wish to use and choose Transfer Transfer . . Alternative procedure using the generic workflow maintenance transaction: 1.

Run Ru n tr tran ansa sact ctio ion n SW SWDD DD

2.

In the Workflow Workflow field, field, enter the workflow template WS60800086, the highest version is automatically chosen.

3. In the Navigation Navigation area area go to step 000073 Dialog Processing and Processing and select it. 4. In the Task Properties area, Properties area, choose Agent choose Agent Assignment for Task . Task . Choose the Agent the Agent Assignment for Task button. 5. On th the e next next sc scre reen en se sele lect ct Dialog Processing and Processing and choose the Attributes the Attributes button. button. 6. In the Task Task popup popup select the option you want and choose Transfer Transfer . . 7. Return to to th the Task Properties list Properties list and verify that the status icon beside Agent beside Agent Assignment is Assignment is green or yellow.

3.9 3. 9

Sett Up Se Up th the Ru Rule le-B -Bas ased ed Wo Work rkfl flo ow

MDG for material uses advanced workflow capabilities by combining the SAP Business Workflow with the SAP Business Rule Framework Framework plus (BRFplus) tool. This section describes how to activate and load the necessary settings for BRFplus. Check that the steps for Rule-Based Workflow are imported by the BC-Set by running the following activity in Customizing: Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow Ru Rule le-b -bas ased ed Wo Work rkfl flow ow De Defi fine ne Ch Chan ange ge Re Requ ques estt Steps for Rule-Based Workflow . The following are the default steps required for all change request types. This table shows an example for the MAT01 change request type: Table 7 Type of Change

Change Request Step

Keys

Request

Successful Validation

Description

Required

MAT01

0

Empty

Empty

Processing

MAT01

90

Empty

Checked

Final Check

MAT01

91

Empty

Empty

Activation

MAT01

92

Empty

Empty

Revision/Cancel BG

MAT01

93

Empty

Empty

Validation

MAT01

95

Empty

Empty

Revision Processing



27

Type of Change

Change Request Step

Keys

Request

Successful Validation

Description

Required

MAT01

99

Empty

Empty

Complete

Due to technical restrictions further settings cannot be included in the BC-sets. Perform the following checks and take action as required: 1.

Check for for existing existing decisions decisions tables and and generate generate the decision decision tables and and rules for for each change change request request type either in Customizing or by running the system transaction USMD_SSW_RULE . If this step is not possible, go to step 2, otherwise go to step 3.

2. Ex Expor portt the the conte content nt fro from m clien clientt 000 and import it into your hub client. 3.

Maintain your content Maintain content in the the decision tables, tables, reflectin reflecting g your governanc governance e process. process. You can use the the predelivered SAP content as a starting point.

More detail on these steps is available below. To activate and load the necessary settings for BRFplus proceed as follows: 1.

Check for for existing existing decisions decisions tables and and generate generate the decision decision tables and and rules for for each change change request request type in Customizing under Ge Gene nera rall Se Sett ttin ings gs Pr Proc oces esss Mo Mode dell llin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wo Work rkfl flow ow Co Conf nfig igur ure e Rule-Based Workflow Enter the change request types one after the other and choose the Continue Continue button. button. After reviewing the decision tables you can leave this step without any further activities. If you get an error that the object is not available, proceed to the next step, otherwise skip to step 3. You can also makes these settings using the transaction USMD_SSW_RULE.

2.

Export the content content from from client client 000 000 and import import it into your your hub hub client. client. 1.

Calll trans Cal transacti action on BRFp BRFplus lus in the the 000 000 clie client. nt.

2.

Choos ose e the Personalise Personalise button button and then choose Expert Expert from from the drop-down menu in the User Mode field Mode field or activate the flag Show Technical Aspects on Aspects on the General General tab. tab.

3.

Search for the object USMD_S USMD_SSW_CAT SW_CATA_MAT A_MAT01 01 using the Workbench Workbench menu menu by choosing Open Object . Object . Use the following values to search: ○

Object Type CA: Catalog

○

Name: USMD_SSW_CATA_MAT*

4. Fro From m the search search result result select select USMD_ USMD_SSW_ SSW_CAT CATA_M A_MAT0 AT011 5.

To export the the content from from client client 000, select select the application application in the the repository repository (not the the catalog entry) then choose To Too ols XML Exp Expo ort . Select the object and then select Export XML for Entire Application from Application from the Export XML menu. XML menu. Generate the XML file and download it. You can ignore the warnings on missing values not in the value list. The file size of each XML file should be approximately 101kb. The system may require you to assign the import to a transport.

6. To Import the content content into into your MDG MDG main client client run run the BRFplus BRFplus transa transaction, ction, from from theTools theTools menu menu choose XML choose XML Import , Import , select your XML file, and choose Upload File . File . 7.

Repeat Rep eat these these steps steps for for all releva relevant nt change change reque request st types. types.

The structure import will also include the values in the three pre-delivered decision tables. For testing the standard workflow configuration you need to copy and activate the two entries in the DT_USR_AGT_GRP_MATXX from user ANZEIGER to one or two existing user IDs in your system.

28



Note For the change request types for Multiple-Record Processing there Processing there are no BRFplus BRFplus decision decision tables delivered. You can use the Export To Excel and Excel and Import From Excel functions Excel functions in BRFplus BRFplus to to copy the decision tables from other change request types. 3.

Maintain your content Maintain content in the the decision tables, tables, reflectin reflecting g your governan governance ce process. process. You can use use the predelivered SAP content as a starting point.

Note If you extend the BRFplus decision tables make sure that the status of the final step is set to 05 Final Check Approved or Approved or 06 Final Check Rejected . Rejected . The following are the minimal settings for the relevant change request types. ○

DT_SINGLE_VAL_MAT01

○

DT_NON_USER_AGT_GRP_MAT01

○

DT_USER_AGT_GRP_MAT01

DT_NON_USER_AGT_GRP_MAT01 and DT_SINGLE_VAL_MAT01 contain the automated steps and follow-up logic used by the BRFplus. The follow-up logic can either result in an automated step or in a user task that will be made visible as a workflow. The users involved in the Master Data Governance process need to be included in table DT_USER_AGT_GRP_MAT01 so that they can receive and execute the workflow tasks. Maintain agents (for example the users or organizations in the Portal Content and Portal Role Assignment sections of this document) for all change request types and their associated workflow steps. Each condition alias that appears in the DT_SINGLE_VAL_MAT01 table needs at least one processor, either automatic or user (group). Therefore, for all non-automated steps at least one entry needs to exist in DT_USER_AGT_GRP_MAT01. Conduct this maintenance for all relevant change request types. Further details on the workflow concepts can be found here [page 101] . 101] . The following change request types appear in the standard delivery: MAT01, MAT02, MAT06, MAT0A, MAT0B, MATLMRP, MATLPUR, MATLSAL, MATLUOM, MATMRP, MATPUR, MATSAL, MATUOM. The following step types are pre-delivered by SAP: Table 8 Step Type

Short Description

Actions

1

Check Change Request

01 Agree; 02 Disagree

2

Approve Change Request

03 Approve; 04 Reject

3

Process Change Request

05 Finalize Processing; 06 Send for Revision

4

Revise Change Request

07 Resubmit; 08 Withdraw

5

Activate Change Request

09 Activate; 10 Send for Revision

6

Approve Change Request (Without

03 Approve; 06 Send for Revision

Rejection) 7

Revise Change Request (Without

05 Finalize Processing

Rejection)



29

Step Type

Short Description

Actions

8

Activate Change Request

09 Activate; 04 Reject

The following agent types exist: Table 9 User Agent Type

Short Description

US

U se r

O

Organizational Unit

C

Jo b

S

Position

AG

Ro l e

SU

Special User (Value for requestor: INIT. Value for previousstep user: LAST.)

The following is the standard content pre-delivered by SAP: DT_SINGLE_VAL_MAT01/2/6/A/B Table 10 Previous Step

Previous Action

Condition Alias

New Step

New Change Request Status

00 (Create Change

No value

1

90 (Final Check)

02 (Changes to be

Request) 90 (Final Check)

executed) 09 (Activate)

2

91 (Final Approval)

02 (Changes to be executed)

90 (Final Check)

91 (F (Fiina nall App Appro rova vall)

04 (Reject)

31 (A (Ac cti tiva vati tion on

3

4

95 (Revision

10 (To Revise:

Processing)

Perform Changes)

99 (Complete)

05 (Final Check

Successful) 91 (Fi (Fina nall App Appro rova vall)

<>31 <> 31 (A (Ac cti tiva vati tion on

Approved) 5

90 (Final Check)

11 (Process Errors

Successful) 92 (Revision/Cancel

No value

After Activation) 6

99 (Complete)

06 (Final Check

BG) 95 (Revision

Rejected) 07 (Request Again)

7

90 (Final Check)

02 (Changes to be

Processing) 95 (Revision

executed) 08 (Withdraw)

Processing)

8

92 (Revision/Cancel

02 (Changes to be

BG)

executed)

DT_USER_AGT_GRP_MAT01/2/6/A/B

30



Table 11 COND_ALIAS

AGENT_GROUP

STEP_TYPE

USER_TYPE

USER_VALUE

1;5;7

001

8 (Activate Change

US

ANZEIGER

US

ANZEIGER

Request) 3

001

4 (Revise)

DT_NON_USER_AGT_GRP_MAT01/2/6/A/B Table 12 COND_ALIAS

AGENT_GROUP

PROCESS_PATTERN

2

001

06 (Activation (Bypass Snapshot))

4;6

001

99 (Complete (Sub-)Workflow)

8

001

08 (Roll back change request)

Notes ○

It is necessary to activate your new entries for each of the three decision tables.

○

The quickest way to allow users to participate in any workflow step for testing purposes is to copy the two default entries in the DT_USER_AGT_GRP_MAT01/2/6/A tables and change the entries as follows: ○

User Type: AG Type: AG (Role) (Role)

○

User Value: SAP_MDGM_MENU_06 SAP_MDGM_MENU_06 (The (The MDGM role of PFCG/SU01)

○

If the system system cannot find a processor for your change requests requests check the background steps of the change requests workflow log to see if a work item with the description Set Status x for Change Request y is in process or in error. If this is the case regenerate the authorization profile of SAP_ALL or include USMD* authorization objects into the authorization for the user WF-Batch.

○

Choosing the process pattern 06 Activation (Bypass Snapshot) means Snapshot) means that the material will be activated, even if the material record was changed in the backend system since the change request was created. Any backend changes are lost upon activation.

3.10 3. 10 Se Sett Up Up Dat Data a Tra Trans nsfe ferr Data Transfer allows you to move master data between systems. These systems can be clients or your main Master Data Governance (MDG) system. The first step of a data transfer is the export of the master data to an IDoc-XML file, which you can save locally or on your application server. In the second step, you import the data into your central MDG system. During the import step you can decide if you want the new master data to appear directly in the active area, or if you want to work with change requests and import the data to the staging area. Data Export from Source System

To be able to export material master data, you need to configure the logical system for IDoc-XML export to the application server file system. The steps are as follows: 1.

Crea Cr eate te an XM XMLL-fi file le po port rt Use transaction WE21 WE21 to to create an XML-file port for IDoc processing. Ensure that you have network access from your local client to the directory configured in the XML-file port. Enter the port name, description, and the physical directory. Enter the function module EDI_PATH_CREATE_CLIENT_DOCNUM . . On the Outbound Trigger tab enter the RFC destination LOCAL_EXEC .



31

2. Cr Crea eate te Log Logic ical al Sys Syste tem m Open transaction SALE SALE and and then go to

Basi Ba sic c Setti Setting ngss

Logi Lo gica call Syst System emss to create a new logical system.

3. Ma Main inta tain in Dist Distrib ribut utio ion n Model Model Open transaction SALE SALE and and then go to Modeli Modeling ng and Impleme Implementin nting g Business Business Proces Processes ses Distribution Model and Distribute Views . You can also use transaction BD64 BD64 for for this.

Mainta Mai ntain in

1.

Switch Swit ch to to chan change ge mode mode an and d choos choose e Create Model View to View to create a new entry. Enter a short text and a technical identifier.

2.

Choose Add Message Type for Type for the newly created model. Enter a logical source system name and a destination system name and choose the message types MATMAS and CLFMAS .

4. Cr Crea eate te Pa Part rtne nerr Pr Prof ofile ile Run transaction SALE SALE and and then go to use transaction BD82 BD82 . . 1.

Partne Par tnerr Profi Profiles les

Genera Gen erate te Partn Partner er Prof Profile iless . Alternatively you can

Select the the newly created model model using using the input input help help for the the technical technical name and and then select the the logical logical destination system.

2. Ent Enter er the autho authoriz rized ed user user and the follo followin wing g values: values:

3.

○

Version : : 3 Version

○

Pack.Size : : 100 Pack.Size

○

Output Mode : Mode : Immediate Transfer

○

Inbound. Processing : Processing : Immediately

Choose Choos e Execute. Execute. You You can ignore the port port error error that that appears. appears.

5. Ca Call ll tr tran ansa sact ctio ion n WE20 WE20 and and make the following settings: 1.

Open the Partner Type LS folder LS folder and select the partner profile you created above.

2. Updat Update e the the mes messa sage ge ty types pes MATMAS MATMAS and and CLFMAS CLFMAS in in the Outbound Parameters section. Parameters section. The Receiver Port is Port is the XML-file port from the first step above. In the Basic Type field Type field enter MATMAS05 MATMAS05 for MATMAS and CLFMAS02 for CLFMAS CLFMAS . . 6. Te Test st cr creat eatio ion n of of IDO IDOC C XML XML 1.

Genera Gen erate te the IDocIDoc-XML XML for for materia materiall using using the trans transacti action on BD10 BD10 . .

2. Check Check the newly newly gener generated ated IDocs IDocs using using tran transac saction tionWE02 WE02 or or BD87 . . You can use the receiver port as the filter criteria in the Partner Port field. Port field. 3. Us Use e tr tran ansa sact ctio ion n AL11 AL11 to to find the XML files on the directory of your XML-file port. 4. To download download the the file for for analysis analysis purposes purposes to local director directory y use trans transaction actionCG3Y CG3Y . . Data Import into Target System (MDG Hub)

If you want to use parallel processing for data import it is recommended that you register your queue name prefixes in the QIN Scheduler so that they are executed automatically and do not have to be manually activated each time. To register the queue name follow these instructions: 1.

Run Ru n tra tran nsa sact ctio ion n SMQ2

2.

Choo oosse the Execute Execute button. button. This shows the list of current queues.

3.

From the Goto Goto menu, menu, select QIN Scheduler . Scheduler .

4. Choo oosse the Registration Registration button. button. 5.

In the Queue Name field, Name field, enter a prefix for your queues. Add an asterisk after the name to allow you to add additional text to the prefix when scheduling the export or import. Enter additional details as required.

6. Choose OK OK . .

32



Your new queue has been registered and will execute automatically. You should inform those working with the Import Master Data service Data service of the new queue name so that they can use it when creating new imports. The IDoc-XML files contain the following fields in the header section: Table 13 Field Name

Field Description

Value

SNDPRT

Partnertyp

LS

SNDPRN

Sender Partner Number

Defined in step 3 below.

SNDPOR

Sender Port


RCVPRT

Partnertyp

LS

RCVPRN

Receiver Partner Number


RCVPOR

Receiver Port


To be able to import IDoc-XML files the following set up activities need to be carried out: 1.

Use tra Use trans nsac acti tion on IDX1 IDX1 to to create two ports in the IDoc adapter, one for sending and the other for receiving. Enter the port, client, description, and RFC destination for each port. Both ports should have the RFC destination of the MDG hub. Check that the port names match the names in your IDoc-XML file for the SNDPOR and RCVPOR , see table above for details.

2. In tr tran ansa sact ctio ion n WE21 WE21 enter enter the receiver XML port using the same name as in step 1 above. Enter the port name under the folder XML File, and enter a description and a physical directory. In the function module field enter . . On the Outbound:Trigger Outbound:Trigger tab, tab, in the RFC destination field, enter EDI_PATH_CREATE_CLIENT_DOCNUM LOCAL_EXEC . 3. In tr tran ansa sact ctio ion n BD54 BD54 enter enter the sender and receiver partner numbers as logical system names. 4. In tra trans nsac acti tion on FILE FILE create create the logical file path name. Enter a Logical File and File and a Name Name . . In the Physical File field enter . . In the data format field enter BIN . In the Application the Application Area field Area field enter CA . . In the Logical Path field Path field enter the logical file path. 5. Open Open the Con Config figura uration tion act activit ivity y Ge Gene nera rall Setti Setting ngss Da Data ta Tra Trans nsfe ferr De Defi fine ne File File So Sour urce ce and and Arc Archi hive ve Directories for Data Transfer and assign your new logical file path name as a directory for data transfer. 6. In tra trans nsac acti tion on AL11 AL11 make make sure that the IDoc-XML files are stored under the logical path and that there are no other files stored in that directory. Double-click on the path to view the existing IDoc-XML file. You can use transaction CG3Z to to copy a local IDoc-XML file to the path. 7.

To tes testt the the data data impor import, t, ope open n the the Data Import service Import service from the Material Governance work Governance work center in the SAP NetWeaver Portal or Portal or SAP NetWeaver Business Client . Client . For more information, see Data Import [external Import [external document] .

You can use the Monitor Data Transfer [external Transfer [external document] application to get an overview of your data transfer processes.

More Information For more information on data transfer see How to Use the Data Import Framework for Material scn.sap.com/ docs/DOC-47519

.



33

3.111 3.1

Configuri Config uring ng SOA SOA Mana Manager ger for Mas Master ter Dat Data a Gove Governa rnance nce for Material

This document describes the configuration steps required to enable the load of material master data using pointto-point enterprise services communication without a process integration (PI) system.

Prerequisites Authorizations The following authorizations are required in the MDG hub system and in the MDG client system: ●

●

SAP_BC_WEBSERVICE_ADMIN_TEC , an administrative role for the SOA Manager.

Authorizations are assigned for transactions SU01 , SUIM , and PFCG .

Service Users in the ABAP Stack To create a service user in the MDG hub and in the MDG client system carry out the steps described below in both systems. 1.

Exec Ex ecut ute e tra trans nsac acti tion on SU01 , choose Create Create , , and enter a user.

2.

On the Roles Roles tab, tab, assign the role SAP_BC_WEBSERVICE_ADMIN_TEC .

Business Functions The following business functions must be active in the MDG hub system and in the MDG client system: ●

FND_SOA_REUSE_1 , Improvements for SOA Reuse Functions

Note To activate the business function, execute the following configuration activity: Customizing Implem Imp lement entatio ation n Guide Guide Act Activat ivate e Busines Businesss Function Functionss . By activating the business function, you can use the following cross-application tool improvements that facilitate the use of these services:

●

○

SOA Mapping Tool

○

Error Handling

○

Point-to-Point Enablement for Asynchronous Enterprise Services

ERP_MATERIAL_SOA , Master Data Governance for Material, Enterprise Services

Support for Point-to-Po Point-to-Point int Communication To activate support for the point-to-point communication, run the following activity in the MDG hub system and in the MDG client system: SAP Cus Custom tomizin izing g Imple Implemen mentati tation on Guid Guide e Cro Crossss-App Applic licatio ation n Compo Componen nents ts Pro Proces cesses ses and Tools Tools for for Enterpr Enterprise ise Applic Applicatio ations ns Ent Enterp erpris rise e Service Servicess Poi Point-t nt-to-P o-Poin ointt Enablem Enablement ent for for Asynchro Asynchronou nouss Enterprise Enter prise Servic Services es Activat Activate e Support Support for Point2P Point2Point oint Commu Communicatio nication n .

Configuration of the Web Service Runtime The technical configuration of the web service runtime is done according to SAP Note 1043195

34


.


Error and Conflict Handler To activate the error and conflict handler, run the following activity in the MDG hub system and in the MDG client system: SAP Cust Customi omizin zing g Implem Implement entatio ation n Guide Guide Cro Crossss-App Applica licatio tion n Compon Component entss Gen Genera erall Applic Applicatio ation n Functio Fun ctions ns Err Error or and Con Conflic flictt Hand Handler ler Act Activat ivate e Err Error or and Con Conflic flictt Hand Handler ler .

Procedure The following steps are required to configure the SOA Manager for MDG (transaction SOAMANAGER ) in the MDG hub and the MDG client system. 1.

Configure Config ure the the system system for point-t point-to-point o-point commun communication ication using enterp enterprise rise services services To create a new profile in the MDG hub and the MDG client system, carry out the steps described below in both systems. 1.

On the Technical Administration tab Administration tab choose Profiles Profiles . .

2.

Choose Choos e Create Create Profile, Profile, enter enter MDG as the the name, enter a description, description, and choose chooseNext Next . .

Note The profile names should be identical in the SOA manager settings for both the MDG hub and MDG client systems. 3.

Mark User ID/Password and ID/Password and choose Next Next . .

4. If neces necessar sary y enter enter proxy proxy setti settings ngs and and choose choose Finish Finish to to save the settings and activate the profile. 2. Co Conf nfig igur ure e the the clien clientt sett settin ing g To configure the client setting in the MDG hub and the MDG client system carry out the steps described below in both systems. 1.

On the Technical Administration tab, Administration tab, choose SAP Client Settings , Settings , and then choose Edit Edit . .

2.

Enter an Organization Name . Name .

3.

Enter a Business System and System and a Business System ID in ID in the format: XYZ_001 , where XYZ is the system ID and 001 is the client.

4. Choose Save Save . . 3.

Configure Config ure a provider provider system system for the Busines Businesss Scenario Scenario Configuratio Configuration n in MDG hub and and MDG client systems systems To configure a provider system for the business scenario configuration in the MDG hub and the MDG client system carry out the steps described below in both systems. 1.

On the Technical Administration tab, Administration tab, choose Provider Systems , Systems , then choose Create Create enter enter as name the system ID of the target system, for example XYZ_001 and select the profile name defined in step 1 and choose Next Next . .

2. Ent Enter er the the SLD Ident Identifi ifier er in for for followin following g format: format: (client).SystemName.(ABC).SystemNumber. (Installation Number).SystemHome.(Host) . For example, 416.SystemName.Q7B.SystemNumber. 0020270862.SystemHome.uxdbq7b .

Note The SystemNumber can be found under System Status SAP System Data Installa lattio ion n Number . The SystemHome can be found under System Status Database Data Host .



35

Note To identify the host name and port for access URL call transaction SMICM and from the Goto Goto menu menu choose Services Services . . Use the HTTPS host name and port displayed in the list. SAP recommend to use the message server host. 3. En Ente terr the the Ac Acces cesss URL URL fo forr WSIL and Logon Information under WSIL Services. 4. En Ente terr Us User for WSDL and a password for WSDL documents. 5.

Enter the Service User that User that you have created in the backend system. Choose Next Next . .

6. Enter the Business Application ID . ID . 1.

Choose Choos e Create Create to maintai maintain n a busines businesss application application ID in MDG hub hub System. System.

2.

Enter an applicatio application n name name and and a descri description, ption, for example example:: sap.com/BusinessApplicationABAP . sap.com/BusinessApplicationABAP .

3. Ent Enter er the bus busine iness ss appl applicat ication ion ID.

Note Note that the business application ID can be found in the counterpart system in the transaction SOAMANAGER under Technical Administration SAP Client Settings . Settings . 4. Press Finish Finish to to save and activate the system connection. 4. Edit Log Logon on Data Data for Bus Busine iness ss Scen Scenario ario To create a user account in the MDG hub and the MDG client system carry out the steps described below in both systems.

Note The back end user has to exist in both systems. 1.

On the Service Administration tab Administration tab choose Logon Data Management . Management .

2.

On the Maintenance Maintenance tab tab choose Create Create , , enter your data and choose Next Next . .

3.

Select User/Password User/Password or or X.509 as as Authentication Authentication Method . Method .

4. Enter the the user name that that you created created earlier earlier in the the backend system system and and choose choose Finish Finish . . 5. Ass Assign ign Logo Logon n Data Data to Busin Business ess Appli Applicati cation on To assign logon data to the business application in the MDG hub and the MDG client system carry out the steps described below in both systems. 1.

On the Service Administration tab Administration tab choose Logon Data Management . Management .

2.

On the Assignments Assignments tab tab choose Create Create . .

3. Us Use e the the inpu inputt help help to to sele select ct aProvider a Provider System/Business Application and Application and choose Next Next . . 4. Select Select the the user user name name you have have ente entered red in in step step 4 asLogon as Logon Data from Data from the drop down list and choose Finish . . Finish 6. Confi Configure gure System System for for Point-to-Po Point-to-Point int Communica Communication tion using using Service Groups To configure the system for point-to-point communication using service groups in the MDG hub system carry out the steps described below. 1.

36

Create Cre ate a busi busines nesss scenar scenario io in the the MDG MDG hub hub system. system. 1.

On the Service Administration tab Administration tab choose Business Scenario Configuration . Configuration .

2.

Choose Create Create , , enter your data and choose Next Next . .



2. Sele Select ct servi service ce definit definition ionss and assig assign n a profile. profile. 1.

Choose Cho ose Add to searc search h for for Serv Service ice Defi Definit nition ion..

2. In the the dia dialog log box se sear arch ch for for the theService Service Definition MaterialERPBulkReplicateRequest_In and choose Go Go . . Select it in the result list and choose Add choose Add to Worklist . Worklist . 3. Ass Assign ign Pro Profil file e to ser servic vice e defini definition tion.. 1.

Select Sele ct the the serv services ices def defini inition tion and cho choose ose Assign Assign Profile . Profile .

2. Se Sele lect ct th the e pro profi file le MDG , choose Assign choose Assign Profile , Profile , and choose Next Next . . 4. Select Service Service Groups Groups and Assign Assign Business Business Applicatio Applications ns in the Provider Provider System System Service Service Group: 1.

Choose Add Add to to search for the Service Group , Group , enter the service group Go . . MDG_BS_MAT_REPLICATE_CONF and choose Go

2.

Select MDG_BS_MAT_REPLICATE_CONF from the search result list and choose Add choose Add to Worklist . Worklist .

5. As Assi sign gn Bus Busin ines esss Applic Applicat ation ion 1.

Select the the service service group group from the the list and and assign assign it to the the business business application application by by choosing choosing Assign Assign Business Application . Application .

2.

Select the the provider system system and and the assigned assigned business business application application name name from the list list and choose choose Assign to Service Group . Group .

3.

Choose Finish Finish . .

6. Cre Create ate a busine business ss scena scenario rio in the the MDG client client syste system. m.

7.

1.

On the Service Administration tab Administration tab choose Business Scenario Configuration . Configuration .

2.

Choose Create Create , , enter your data and choose Next Next . .

Select Sele ct servi service ce definit definition ionss and assig assign n a profile. profile. 1.

Choose Add Add to to search for a service definition.

2. In the the dia dialog log box se sear arch ch for for the theService Service Definition Go . . Select MaterialERPBulkReplicateConfirmation_Out and choose Go MaterialERPBulkReplicateConfirmation_Out in the result list and choose Add choose Add to Worklist . Worklist .

8. To assign assign a profile to the the service definiti definitions ons in the MDG MDG client system system carry carry out the steps steps described described above in the corresponding chapter. 9. Select Service Service Groups Groups and Assign Assign Business Business Applicatio Applications ns in the Provider Provider System System Service Service Group: 1.

Choose Add Add to to search for the Service Group , Group , enter the service group MDG_BS_MAT_REPLICATE_REQ and choose Go Go . .

2. Sele Select ct it from from the searc search h result result list list and and choose choose Add Add to Worklist . Worklist . 10. To assign a business business application in the MDG client system carry out the steps described above in the corresponding chapter.

Note To activate the business scenario and changes in the SOA manager business scenario configuration choose Process List in List in the Pending Tasks page Tasks page under Service Administration . Administration . Confirm that all tasks are executed successfully.



37

More Information For more information about material services see How To-MDGM Enterprise Material Services Enhancement Guide ( scn.sap.com/docs/DOC-57645

).

3.12 3. 12 Se Sett Up Up Dat Data a Rep Repli lica cati tion on For Master Data Governance for Material you have two options for replicating data from the MDG hub to the connected systems and clients: ●

Data replication using Application Link Enabling (ALE)

●

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

For more information, see in Customizing under Application Server (ALE (A LE)) SA SAP P Bus Busin ines esss Wor Workf kflo low w .

IDoc Interface / Application Link Enabling

Set Up Data Replication Using ALE

The following process describes briefly the minimal settings required for the two main message types MATMAS and CLFMAS CLFMAS . . 1.

Veri Ve rify fy lo logi gica call sys syste tems ms Run transaction SALE SALE and and choose Ba Basi sic c Setti Setting ngss Lo Logi gica call Syst System emss . Both clients (source and target) need to be defined as logical systems and need to be assigned to the relevant clients.

2. Ch Chec eck k comm commun unic icat atio ion n Run transaction SALE SALE and and choose Com Commun munica ication tion Cre Create ated d RFC RFC Con Connec nection tionss . The target partner system has to be defined here as an ABAP connection with a connection type of 3 and with same name as the target logical system. Perform a connection test. 3. Ma Main inta tain in dis distr tribu ibuti tion on mod model el 1.

Run tra Run trans nsac acti tion on SALE SALE (Display (Display ALE Customizing) and choose Modeling and Implementing Business Processes Proce sses Maintai Maintain n Distrib Distribution ution Model and Distrib Distribute ute Views . Alternatively, run transaction BD64 (Maintenance of Distribution Model).

2. In cha change nge mode mode,, creat create e a new mode model. l. Choose the Create Model View pushbutton. View pushbutton. Enter a short text and a technical name. 3.

Choos ose e the Add Message Type pushbutton Type pushbutton for the newly created model.

4. Enter names names for for the logical logical source source and destinat destination ion systems systems and choose messag message e typeMATMAS type MATMAS . . 5. Rep Repeat eat poin points ts 3 and 4 for for messa message ge type type CLFMAS 4. Cr Crea eate te pa part rtne nerr pro profi file. le. 1.

Run tra Run trans nsac acti tion on SALE SALE and and choose Par Partne tnerr Profi Profiles les transaction BD82 BD82 (Generate (Generate Partner Profiles).

Genera Gen erate te Partn Partner er Prof Profiles iles . Alternatively, run

2. Sele Select ct the the newly newly cre created ated mode modell and in the the Partner System field, System field, enter the logical destination system. 3. Ent Enter er the the ALE-U ALE-User ser (th (the e default default val value ue is ALEREMOTE ) and the following values, and execute. Table 14

38

Field

Value

Version

3



Field

Value

PackSize

100

Output Mode

Transfer IDoc immediately

Inb. Parameters: Processing

Trigger Immediately

4. To verif verify y your your settin settings, gs, run tran transac sactio tion n WE20 WE20 and and from the Partner Profiles menu, Profiles menu, choose Partner Type LS . . Verify that Partner type LS is LS LS is the logical destination system. 5. In the the detail detail scre screen, en, the the chose chosen n messag message e type type MATMAS/CLFMAS MATMAS/CLFMAS should should appear. 5. Dis Distrib tribute ute model model view view to to receiv receiving ing syst system. em. 1.

Run tra Run trans nsac acti tion on SALE SALE and and choose Mode Modeling ling and Imple Implementin menting g Busine Business ss Proce Processes sses Distribution Model and Distribute Views . Alternatively, run transaction BD64 BD64 . .

2. Se Selec lectt the the new new model model and and cho choos ose e 3.

Ed i t

Model vi view

Maintain Mainta in

Distribute .

Verify that the correct correct receiv receiving ing system system is marked marked and and choose choose Enter .

4. Verify within the receiving receiving syste system m that the model model view was created. created. 6. Cre Create ate partn partner er profil profile e (in receiv receiving ing clien client). t). 1.

Run tra Run trans nsac acti tion on SALE SALE and and choose Mode Modeling ling and Implem Implementing enting Busine Business ss Proces Processes ses Generate Partner Profiles . Alternatively, run transaction BD82 BD82 . .

Partnerr Profiles Partne Profiles

2. Se Selec lectt the the dist distri ribu bute ted d model. model. 3.

Enter the ALE-Use ALE-User, r, and and the followin following g values, values, and execute. execute. Table 15 Field

Value

Version

3

PackSize

100

Output Mode

Transfer IDoc immediately


Trigger Immediately

Note If the protocol contains the error Port could not be created this created this can be ignored. 4. Check that that the correct correct process process code is being used. used. To do this go go to the details details for the inbound inbound parameter parameter message types and in Inbound Options check Options check that the parameter Process Code is Code is MATM for message type MATMS and is CLFM for message type CLFMAS . You can test the distribution using transaction BD10 BD10 . . Verify the results in the receiving client using transaction BD87 .

Note In the Configuration activity Define Technical Settings for Business Systems SAP Systems SAP recommends that you select the checkbox Status System Filter for Filter for the Material Material business business object. This ensures that if an object instance was previously sent to a target system, it continues to be sent in the future, independent of filter settings. Set Up Data Replication Using ALE with DRF



39

In Master Data Governance for Material the replication of material master data from MDG Hub to connected client systems can be scheduled, triggered, and monitored using the Data Replication Framework (DRF) in concert with the ALE.

Note If you are using ALE and DRF together to replicate materials you can improve performance by deselecting the change pointers for the MATMAS message type. You can do this in the Activate the Activate Change Pointers for Message Types configuration Types configuration activity. You should only do this if all your MDG systems are integrated using ALE and DRF together. If you use ALE without DRF in one or more connected systems do not disable the change pointers. The following customizing is relevant for data replication: ●

ALE (See Set Up Data Replication Using ALE above)

●

Enterprise Search (See Set Up Search above)

●

Key Mapping (See Key Mapping below)

●

ALE Audit (See Customizin Customizing g for ALE Audit below)

●

Data Replication Framework (DRF)

The following process outlines the steps required to perform the customizing for the last three points above. Customizing for Data Replication Framework (DRF)

1.

Run tra Run tran nsa sact ctio ion n DRFIMG and navigate to Enhanc Enhance e Default Default Settin Settings gs for for Outbou Outbound nd Implem Implementatio entation n Parameters to check if the outbound parameter PACK_SIZE_BULK is available.

Define

The following information should be available for this parameter: Table 16 Outbound Parameter

Description

Data Type

Value Length

PACK_SIZE_BULK

Package Size for Bulk

Integer

10

Messages

2. Use Use tr tran ansa sact ctio ion n DRFIMG to check if the filter objects below have been defined. Select Enhance Default Settings Settin gs for Outbou Outbound nd Imple Implementat mentation ion Defin Define e Filter Filter Objec Objects ts to view the filter object definitions. Check that the main filter object, MDG_BS_MAT is available. 3. Use Use tr tran ansa sact ctio ion n DRFIMG to check if the outbound implementation I_MAT has been defined. Select Default Defau lt Settings Settings for Outboun Outbound d Implementat Implementation ion Defin Define e Outbound Outbound Impleme Implementation ntationss .

Enhance

Choose Assign Choose Assign Segment Filter Objects and Objects and confirm that the following settings are made. Table 17 Type

Technical Name

Description

Segment Filter Object

F_MAT1

Plant segment of material


F_MAT2

Sales segment of material


F_MAT3

Storage segment of Material


F_MAT4

Tax class segment of material


F_MAT5

Valuation segment of material


F_MAT6

Class segment of material

4. Define the techn technical ical setting settingss for for the the business business syste system. m.

40



1.

Enterr tran Ente transsac acti tion on DRFIMG and navigate to Def Define ine Custo Custom m Setting Settingss for Data Data Replic Replicatio ation n Technical Techn ical Setting Settingss Defin Define e Technical Technical Settin Settings gs for for Business Business System Systemss .

Define Def ine

2.

In the Business System field System field specify the receiver system. In the Logical System field System field enter the Logical System used for IDoc communication. In the RFC Destination field Destination field enter the RFC destination to be used for RFC communication with the receiver system.

3. Se Selec lectt the the entr entry y and and click click on onDefine Define Bus. Systems, BOs . BOs . 4. In the BO Type field Type field enter the business object type 194 . In the Description Description field, field, enter a descriptive text. 5. Select Select the the entr entry y and and double double-cli -click ck on on Define Bus. Systems, BOs, Communication Channel . Channel . In the Communication Channel field Channel field enter the means you want to use to transmit data to the applications. In the Key Harm. field Harm. field specify if you want your keys harmonized between the hub and the client systems. 5.

Create the the replication replication model model and assign assign it to the outbound outbound implemen implementation tation as as follows: follows: 1.

Ente En terr tran transsac acti tion on DRFIMG .

2.

Navigat ate e to to Models .

3.

Select Define Replication Replication Model and Model and then select select New Entries . Entries .

Data Dat a Replic Replicatio ation n

Define Def ine Cus Custom tom Set Settin tings gs for for Data Data Rep Replic licatio ation n

Define Def ine Rep Replica licatio tion n

4. Enter a replication model and a description. In the Log Days field, Days field, you may enter the number of days after MM which you want an Application Log to expire. In the Data Model field, Model field, enter MM . . 5. Sele Select ct the newly newly defin defined ed replicat replication ion model model and choose choose Assign Outbound Implementation . Implementation . 6. Choose New Entries . Entries . 7.

Assign Ass ign the out outbou bound nd impl implemen ementat tation ion I_MAT .

8. Assig Assign n a target syst system em for for the the outbound outbound implemen implementation tation I_MAT . 9. Assign Assign the out outbou bound nd par paramet ameter er PACK_SIZE_BULK to the outbound implementation I_MAT with the Outbound Parameter Value 5. Value 5. 6. Sav Save e and act activat ivate e the repl replicat ication ion model model..

More Information For more information on data replication see Using the Data Replication Framework scn.sap.com/docs/ DOC-39574

.

3.13 3.1 3 Choose Choose whe where re you you want want to run run SAP SAP Mast Master er Data Data Governance You can run SAP Master Data Governance in either of the following environments: ●

SAP NetWeaver Portal

●

SAP NetWeaver Business Client

SAP NetWeaver Portal

The SAP NetWeaver Portal content for MDG for material is derived directly from the system PFCG roles. To create SAP NetWeaver Portal roles for your users you must log on to your portal and upload the content information from your back-end system PFCG roles.



41

To upload your portal content to the portal do the following: 1.

Set up you yourr SAP SAP NetW NetWeav eaver er Porta Portall for for MDG. MDG.

2.

In the Content Administration work Administration work center choose Por Portal tal Con Conten tentt Manag Managmen mentt a portal content folder to upload the portal content to. New

3. Rig Rightht-clic click k on the fol folder der and cho choose ose

Role

Portal Por tal Con Conten tentt and select

Role from Back End

4. Select the the system and and client (or the the connected connected system system alias) you want want to upload upload the role information information from. from. This should be your MDG system. 5. Fro From m the the list list dis display played ed selec selectt the the PFCG roles you want to upload the content from and begin the upload. Once uploaded you must assign and personalize the MDG portal roles as follows: 1.

Log Lo g on to th the e por porta tal. l.

2.

Choose Delegated User Administration . Administration .

3. En Ente terr your your Us User er ID ID and and choos choose e Go Go . . 4. Mar Mark k the the line line of of your your use userr and and choos choose e Modify Modify . . 5.

Sele lec ct the Assigned Roles tab. Roles tab.

6. Enter MDG MDG as the search criteria. 7.

Select Sele ct the the port portal al role role you wan wantt to to add. add.

8. Choose Add Add and and save. After assigning the user role you need to log off and log on again to the portal. For more information on uploading role information see SAP Note 1685257

.

SAP NetWeaver Business Client

If you are running SAP Master Data Governance on the SAP NetWeaver Business Client (and not on the SAP NetWeaver Portal), you need to create, define, and configure the roles for the Business Client in the SAP ERP system. There are four roles containing authorization and navigation information and one role ( SAP_MDGM_MENU_06 ) containing only navigation information. To assign and personalize the role Master Data Governance for Material: Menu ( SAP_MDGM_MENU_06 ) proceed as follows: 1.

On the SAP Eas Easy y Acces Accesss scre screen, en, cho choose ose To Too ols Administra rattio ion n User Ma Mainte ten nance Role Administration Roles or alternatively, run transaction PFCG (Role Maintenance). Choose role SAP_MDGM_MENU_06 . This role ensures that the necessary steps can be started without using the SAP NetWeaver Portal. This can be used for testing or if the portal is inactive.

2. Assign Assign and pers persona onaliz lize e the the role SAP_MDGM_MENU_06 to your users. In the role SAP_MDGM_MENU_04 on the Personalization tab, Personalization tab, edit the Personalization Key SAP Key SAP Master Data Governance ( R_FMDM_MODEL ): Define the standard model MM and the related UI configuration. 3.

Verify the the setting setting of the authoriz authorization ation objects objects within within the roles roles and restrict restrict them if required. required.

4. On the the SAP SAP Easy Easy Acce Access ss scre screen, en, choo choose se To Too ols Administra rattio ion n User Ma Mainte ten nance Users . Run transaction SU01 (User Maintenance) and assign the Master Data Governance for Material: Menu role ( SAP_MDGM_MENU_06 ) for application to the MDG user. Repeat these steps to assign additional authorization roles to your users.

42



3.14 Final St Steps Before you can run Master Data Governance services like Display Material , Material , you need to assign the data model MM to your user. Alternatively, the user administrator can update the following Personalization Object for Object for your user profile: R_FMDM_MODEL and add the MM data model as your standard data model.

3.15 3.1 5 Docum Document ent Man Manage agemen mentt System System (DM (DMS) S) Integ Integrat ration ion (Optional) You can use SAP Document Management System (DMS) System (DMS) with MDG for Material. You can use DMS to link documents to material master records in MDG. You can also create new documents using the MDG UI. To use DMS you must perform a number of customizing activities. You can find DMS customizing in the implementation guide under Cro Crossss-App Applic licatio ation n Com Compon ponent entss Doc Docume ument nt Man Manage agemen mentt . You can find the necessary information on DMS configuration in the SAP Library under help.sap.com . Follow this path: SA SAP P ER ERP P SA SAP P ER ERP P 6. 6.0 0 Ap Appl plic icat atio ion n He Help lp SA SAP P ER ERP P SA SAP P ER ERP P Cr Cros osss-Ap Appl plic icat atio ion n Fu Func ncti tion onss CrossCro ss-App Applica licatio tion n Com Compon ponent entss Doc Docume ument nt Man Manage agemen mentt . To integrate DMS with MDG you must set up a storage system. You can do this in customizing under Cross Application Components Document Management General Data Settings for Storage Systems . You can use the thumbnail picture function provided by the Business Context Viewer (BCV) if you have the BCV installed on your system. You can set up this function in customizing as follows: 1.

Define a defau Define default lt data data carrier carrier with with the the networ network k address address DEFAULT . You can do this in customizing under Cros Cr osss-Ap Appl plic icat atio ion n Com Compo pone nent ntss Do Docu cume ment nt Ma Mana nage geme ment nt Ge Gene neral ral Da Data ta De Defi fine ne Da Data ta Ca Carri rrier er .

2.

Define workstat workstation ion applications applications as valid valid for thumbnail thumbnail determinat determination. ion. You can do this this in customizi customizing ng under Cros Cr osss-Ap Appl plic icat atio ion n Compo Compone nent ntss Do Docu cume ment nt Mana Manage geme ment nt Ge Gene neral ral Data Data Se Setu tup p Works Workstat tatio ion n Applic Applicati ation on for Thumbnails (Images) .

3.

Ensure Ensur e the conten contentt server server service service is active; active; check OSS Note Note 685521 for valid logon data.

Note If you want to replicate document links into other target systems, you will need to distribute the documents and document links manually. There is no integration of ALE message types DOCMAS and DOLMAS into the data replication framework.



43

4

Adapting Ma Master Da Data Go Governance fo for Material

This documentation provides the information you require to change and enhance settings for Master Data Governance for Material. It supplements the information provided in the section Configuring Master Data Governance for Material . Material .

4.1

Data Modeling

The purpose of data modeling is to define the structure of the data storage. During the master data processing, a change request is used that stores the master data changes in a staging area. The data model can define a reuse area that is used for data storage after the change request processing has been completed and the related data has been activated. In this case, the system moves data from the staging area to a storage location that is connected by the access class of the reuse area. This storage location is called active area. If there is no reuse area defined, the same database tables that are used for the staging area, are also used to store active data. Then, no access class is involved, the system does not move data from one location to another, and MDG is used as the active area.

4.1.1

Concept of the MDG Data Modeling

A data model in Master Data Governance is comprised of various elements (entity types, attributes, and relationships) to enable you to model master data structures of any complexity in the system. These elements are described below. The system uses the data model to generate database tables for storing the data you enter when managing the master data. Which key fields and non-key fields these database tables contain depends on the structure of your data model.

Note This documentation supplements the information that is available in Customizing for Master Data Governance under Ge Gene nera rall Set Setti ting ngss Da Data ta Mod Model elin ing g Ed Edit it Dat Data a Mod Model el . Therefore, this documentation only covers the areas of the data model that require more background background information for better comprehension.

Entity Types You define entity types to model different types of master data in your data model. The system generates for each entity type the database tables that are needed for processing the master data in Master Data Governance . Governance . You can define the following properties for an entity type: ●

44

You use the validity of entity field to specify for an entity type whether the validity of master data changes is restricted to editions: PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.

Master Data Governance for Material Adapting Master Data Governance for Material

○

Edition When you create a change request to process entities for entity types with this validity concept, you need to assign the new change request to an edition. The corresponding change request type must reference an edition type. With this validity concept, the edition field is included in the database tables.

○

No Edition When you create a change request (to process entities) for entity types with this validity concept, you do not assign the new change request to an edition unless you want to create edition-dependent hierarchies in the change request. The corresponding change request type does not have to reference an edition type in this case. With this validity concept, the edition field is not included in the database tables.

●

You use storage/use type to specify whether and how master data can be changed in Master Data Governance . . The storage and use type also indicates which database tables are generated by the system: Governance ○

1 - Changeable via Change Request; Generated Database Tables The master data of this storage and use type can be changed in Master Data Governance with Governance with a change request. The system generates all necessary database tables: check and text tables as well as additional tables, for example, for attachments and sets. The common key fields of these tables are: ○

The entity type itself

○

The edition – if you previously specified in the data model that the validity of master data changes is restricted to editions

○

The entity types that are assigned to the entity type through leading relationships

Furthermore, all tables contain a checkbox that indicates whether the master data record is active. If the entity is stored in the MDG active area, this checkbox separates data in the staging from active data. If the entity is stored in a re-use area, this checkbox is used to mark a copy of the data from the active area as a snapshot at the time when the change request was created. This snapshot is used during activation of the data to detect conflicting changes that were done directly to the active area. The settings you make for the entity type (such as language dependency) result in additional key fields in the text table and the tables for attachments and sets. The non-key fields contained in the text table are the entity texts. The non-key fields contained in the check table are the attributes of the entity type. The attachment and set tables contain predefined nonkey fields. Furthermore, all database tables contain a checkbox that indicates the deletion of the master data record. For entities that are edition-based, this checkbox indicates the end of validity in time. For entities that are stored in a re-use active area, this checkbox is considered during activation to check if data needs to be deleted. The check table also contains attributes that record which user created or changed the data records and when this was done. ○

2 - Changeable w/o Change Request; Generated Check/Text Tables The master data of this storage and use type can be changed in Master Data Governance without Governance without a change request. The system generates only the check and text tables with the entity type as well as with the entity types assigned to the entity type through leading relationships as fixed key fields. The non-key fields contained in the text table are the entity texts. The check table does not contain nonkey fields.

○

3 - Not Changeable via MDG; No Generated Tables The master data of this storage and use type cannot be changed in Master Data Governance . Governance . Therefore, the system does not generate database tables. Instead, the system derives the available values from the domain that is assigned to the data element – either from the assigned value table or from the domain



45

fixed values. Entity types with this storage and use type are typically used as reference values in qualifying relationships. ○

4 - Changeable via Other Entity Type; Generated Database Tables The master data of this storage and use type can be changed in Master Data Governance only Governance only with a change request of an entity type with storage and use type 1 type 1 . . The entity type needs to be in a relationship with the relationship type leading leading and and assigned as the To-entity type to an entity type with storage and use type 1 type 1 . . The system generates the check table as described for storage and use type 1 type 1 , , but also generates the entity types that are assigned through qualifying relationships as key fields. The system does not generate a text table, attachments, or sets since entity texts are not allowed for entity types with this storage and use type.

The constraints described in the “Relationships” section apply when you assign a storage and use type to an entity type. ●

If you want to model the hierarchy arrangement of entities with specific entity types during master data processing, you can allow a hierarchy structure for each entity type. By doing this, you define whether these hierarchies are version-dependent or cross-name, or whether a combination of these attributes is to apply to the hierarchies. ○

If you create version-dependent hierarchies, you can define different hierarchy versions in Customizing for Master Data Governance under Governance under Ge Gene nera rall Setti Setting ngss Pr Proc oces esss Mode Modeli ling ng Cr Crea eate te Hie Hiera rarc rchy hy Ver Versi sion onss .

○

In cross-name hierarchies, the structure of the substructures – that is, the entities with their lower-level entities – is identical in all hierarchies.

You also define in the data model which entity type is to be used as an end node (without lower-level nodes) in the hierarchy, which entity type is to be used as the root node (hierarchy name) of the hierarchy, and which additional entity types are permitted for the hierarchy. By default, a hierarchy can contain one root node and multiple entities of the hierarchy-defining entity type. You can also assign other entity types with storage and use types 1 types 1 , , 2 2 , , and 3 and 3 to to the hierarchy.

Note Entities of the entity type that you define as the root node cannot be used as lower-level entities in the hierarchy. No relationships with relationship type Leading Leading can can be defined for the entity type itself. You can also specify in the data model whether the system is to restrict the validity of the hierarchy for an entity type to editions. The system automatically generates the database tables needed to store the hierarchies. They contain the following key fields:

46

○

The edition – if you previously specified in the data model that the validity of the hierarchy for this entity type is restricted to editions

○

A checkbox that indicates whether the master data record is active

○

The higher-level entity type

○

The higher-level entity

○

The lower-level entity type

○

The lower-level entity

○

The hierarchy version (if the hierarchy is version-dependent)

○

The hierarchy name (that is, the entity of the entity type you defined for the root node) if the hierarchy is not cross-name PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.


The table also contains a checkbox (as a non-key field) that indicates whether the respective master data record has been deleted, as well as a sequence number. This number specifies the sequence of the respective lower-level entities. ●

To define the technical properties of an entity type or the texts for field labels and input help on the user interface for Master Data Governance , Governance , you can assign an existing data element to the entity types with storage and use type 1 type 1 . . You must assign a data element to entity types with storage and use types 2 types 2 and and 3 3 . . This assignment is not permitted for entity types with storage and use type 4 .

Note If no data element is assigned to an entity type, you must use this entity type as a To-entity type in at least one relationship with the type Leading Leading or or Qualifying Qualifying . . ●

By assigning the type of key assignment , you specify for new entities created for an entity type whether the processors are to specify the key or whether this is to be assigned internally by the system. You can also define whether processors are permitted to later change these keys.

Note If you select a setting other than Key Cannot Be Changed; No Internal Key Assignment as Assignment as the type of key assignment, the generated database tables change as follows: ○

Check table The table key contains a technical field instead of the entity type and its higher-level entity types. The entity type and its higher-level entity types are included in the attribute area of the database table.

○

Hierarchy table The hierarchy table does not change.

○

Other tables The key for the tables contains a technical field instead of the entity type and its higher-level entity types. The system generates a mapping table. The database table key contains a technical field for the mapping table. The attribute area contains the entity type and its higher-level entity types. If you select the Key Can Be Changed; Internal Key Assignment Possible setting Possible setting as the type of key assignment, an additional attribute field to store the temporary key is added to the mapping table.

○

If the entity type is used as a From-entity type in type in relationships (see the “Relationships” section), the technical field replaces the entity type and its higher-level entity types in the corresponding tables.

You also need to assign a number range object in this data model that the system can use to derive the required temporary keys when keys are assigned internally (before the entity is activated). ●

If you want to define texts for an entity type, you can specify the length of the short, medium, and long texts and you can specify whether these texts are to be stored as language-dependent in the database tables.

●

You can enter a more detailed description of the objects in the data model (entity type, attribute, or relationship). For entity types without data elements, the system also uses this description for display in master data maintenance.

●

For entity types with storage and use type 3 type 3 whose whose data elements reference a check table that, in turn, does not reference a text table, you can specify texts for the source field (short text, medium text, and long text). The system uses the text that can be stored in this check table field as the descriptive text of the entity type’s attributes (for example, when formatting the input help).

●

You can specify whether deletion of entity types by means of change requests is permitted.



47

Relationships To map the structure of your master data management in the data model, you define relationships between the individual entity types. The relationship type determines whether one entity type (From-entity type) is at a higher level than another entity type (To-entity type) or whether it is to be copied as an attribute of the other entity type in the check table: ●

Relationship type Leading Leading (P) (P) In this relationship type, the From-entity type is at a higher level than the To-entity type. This means the From-entity type is added as a key field to the database tables of the To-entity type, along with all assigned entity types with storage and use type 4 . The From-entity type from a leading relationship to an entity type with storage and use type 4 is the respective entity type with which you can process the master data of the To-entity type with a change request. You cannot specify a data element. The cardinality 1:N is only permitted for this relationship type when no data element is specified. The cardinality 1:0 is also permitted if:

●

○

The To-entity type has storage and use type 1 type 1 , , no data element, and no additional relationships with the relationship type Leading Leading . .

○

The To-entity type has storage and use type 4 and no additional relationships with the relationship type Qualifying . . Qualifying

Relationship type Qualifying Qualifying (Q) (Q) This relationship type is only relevant for From-entity types with storage and use type 4 . It is used to define additional key fields in the database tables. For entity types of this storage and use type, the system – by default – transfers only the key fields of the From-entity type from the leading relationship. Only the cardinality 1:N is permitted for this relationship type. You cannot specify a data element.

●

Relationship type Referencing Referencing (-) (-) This relationship type declares that the From-entity type is to be used as an attribute of the To-entity type. The description (name) of this type of relationship is inserted as a non-key field in the check table of the Toentity type. The cardinalities 1:N and 0:N are permitted for this relationship type. A data element can be specified in this case. However, this data element must have the same technical properties as the data element assigned to the From-entity type. As an alternative to a referencing relationship with a From-entity type with storage and use type 3 type 3 , , you can also define the attributes for the corresponding To-entity type directly. You configure this setting in Customizing for Master Data Governance under Governance under Ge Gene nera rall Set Setti ting ngss Da Data ta Mod Model elin ing g Ed Edit it Dat Data a Mode Modell in the subdialog Attributes subdialog Attributes . .

Note Whether you use a relationship with the relationship type Referencing Referencing to to define attributes or whether you define these directly (where possible) depends on the settings configured in the data model and on the use type of the attributes. For example, if an attribute is a value to which a unit or currency is to be assigned, you must define this directly. In contrast, if an entity type with storage and use type 3 type 3 that that you can use for attribute definition already exists, you should define a referencing relationship. Which relationship types are permitted depends on the storage and use types of the entity types:

48



Figure 1

Example For an example of the database tables the system generates for entity types with different properties defined in the data model, see Example: Generated Database Tables [external Tables [external document] .

4.1. 4. 1.2 2

Data Da ta Mo Mode dell for for Ma Mast ster er Da Data ta Go Gove vern rnan ance ce fo forr Mat Mater eria iall

The data model for Master Data Governance for Material (MDG-M) is based on the SAP ERP material master. MDG-M supports the entire scope of material classification and many of the material master attributes. The MM model is ERP-specific and resides in the software layer MDG-APPL . The MM data model contains three type 1 entities: MATERIAL (basic data), MKALBASIC , DRADBASIC (basic data for document link), and MATCHGMNG . MATERIAL , MKALBASIC , and DRADBASIC each have one or more type 4 entities that describe it. See below for more detail.

Structure Type 4 Entities for MATERIAL The following are the type 4 entities describing the MATERIAL entity: Table 18 Entity

Description

QMATBASIC

Parameters for Inspection Type



49

Entity

Description

MDMABASIC

MRP Area Basic Data

MBEWMLAC

Material Ledger: Prices

MBEWMLVAL

Material Ledger: Period Totals Records Values

BSCDATTXT

Basic Data Text

CLASSASGN

Class Assignment

INTCMNT

Internal Comment

MARASALES

Material Sales Data

MARAPURCH

Material Purchasing Data

MARAQTMNG

Material Quality Data

MARCWRKSD

Plant Data Work Scheduling

MARCSTORE

Plant Data Storage

MARCSALES

Plant Data Sales

MARCQTMNG

Plant Data Quality Management

MARCPURCH

Plant Data Purchasing

MARCMRPSP

Plant Data MRP Stock Planning ( View Procurement)

MARCMRPPP

Plant Data MRP Production Planning (View Material)

MARCMRPMI

Plant Data MRP Misc (View Manufacturing)

MARCMRPLS

Plant Data MRP Lot Size (View Lot Size)

MARCMRPFC

Plant Data MRP Forecast (View Planning)

MARCFRGTR

Plant Data Foreign Trade

MARCFRCST

Plant Data Forecasting

MARCCSTNG

Plant Data Costing

MARCBASIC

Plant Data Basic Data

MARCATP

Plant Data ATP

MARDMRP

Storage Location MRP Data for Material

MARDSTOR

Storage Location General Data for Material

MBEWACTNG

Material Accounting Data

MBEWVALUA

Material Valuation Data

MBEWCSTNG

Material Costing Data

MEAN_GTIN

International Article Numbers (EANs) for Material

50



Entity

Description

MLANSALES

Tax Classification for Sales

MLANPURCH

Tax Classification for Purchasing

MLGNSTOR

Material Warehouse Management Data

MLGTSTOR

Material Storage Type Data

MRPTXT

Material MRP Text

MPGDPRODG

Material Data for Product Group

MVKESALES

Sales Data

MVKEGRPNG

Sales Grouping

PURCHTXT

Material Purchasing Text

QINSPTXT

Material Quality Inspection Text

SALESTXT

Material Sales Text

UNITOFMSR

Units of Measure for Material

VALUATION

Characteristic Valuation

Type 4 entities for DRADBASIC The following are the type 4 entities describing the DRADBASIC entity: Table 19 Entity

Description

DRADTXT

Document Link Text

Constraints The MDG-M data model does not include further process controlling objects like routing, pricing conditions, or sources list. Forecasting and other process controlling data is not included in the MM data model.

4.1. 4. 1.3 3

Extend Exte ndin ing g the the Da Data ta Mo Mode dell for for Ma Mast ster er Da Data ta Go Gove vern rnan ance ce for Material

You can extend the data model ( MM ) for Master Data Governance for Material (MDGM) with new entity types and attributes. You should extend the ERP material master data model before you extend the MM data model. This document contains information specific to enhancing the data model for MDGM; for more detailed information on the process, see the overall document on extending Master Data Governance content. Governance content.



51

Note There is no need to create a customer access class for the data model MM. The MDGM data model, MM, is preconfigured with one reuse area: MATERIAL . This reuse area points to the access class CL_MDG_BS_MAT_ACCESS , which can handle most fields of the pre-delivered SAP ERP Material Master. The following scenarios for enhancing the MDGM data model are possible: ●

Extend the MDGM data model by adding attributes that already exist as database fields in the pre-delivered or extended SAP ERP material master.

●

Extend the MDGM data model by adding a reuse entity type that already exists as a database table in the predelivered SAP ERP material master.

●

Extend the MDGM data model by adding a reuse entity type that exists as a database table that has been added to the pre-delivered SAP ERP material master.

●

Extend the MDGM data model by adding a flexible entity type that only exists in the database tables in MDG.

Scenarios Scenario: Adding an Attribute to the MDGM Data Model You can extend the MDGM data model by adding an SAP ERP material master database field to an MDGM entity as an attribute. You can only add database fields that are part of the SAP ERP database tables (including customer-created fields); you cannot add customer-created tables that you added to the SAP ERP database. Use the following process to add an attribute to the MDGM data model: 1.

Enhance Enhan ce the MDGM data data model with additional additional attrib attributes. utes. The MDGM MDGM data model is called MM. MM.

2. Gen Generat erate e the mode model-sp l-specif ecific ic struc structur tures. es. 3. Mai Mainta ntain in the mappin mapping g in the Servi Service ce Mappin Mapping g Tool (SMT) (SMT).. 4. Spe Speci cify fy fi field eld pr prope opert rtie ies. s. 5.

Configure the UI. Configure UI. The MDGM applicat application ion configur configuration ation begins with BS_MAT_OVP . It is located in the development package MDG_BS_MAT_UI .

6. Optional Optional step: Create a new new print form. You can use use the existing existing print print form form ( MDG_BS_MAT_PDF_05 ) as a template. 7.

Optional Option al step: step: Enhance Enhance the search. search. Generat Generate e the busine business ss template template MDG_MATERIAL again.

Note This scenario covers the pre-delivered fields belonging to the SAP Material Master database tables and also any customer-defined fields you have added to those tables.

Scenario: Adding a Reuse Entity Type to the MDGM Data Model You can extend the MDGM data model by adding a pre-delivered SAP ERP material master database table to the MDGM data model as an entity type. Use the following process to add a reuse entity type to the MDGM data model: 1.

Enhance the MDGM Enhance MDGM data model model with addition additional al entity types. You You can choose choose the attribu attributes tes belonging belonging to this entity type that you wish to add to the MDGM data model. The MDGM data model is called MM.

2. Gen Generat erate e the mode model-s l-speci pecific fic str struct ucture ures. s. 3.

Create the the mapping mapping in the SMT SMT and assign assign it to the model model specific specific structures structures..

4. Spe Speci cify fy the the fiel field d proper properti ties es..

52



5.

You can can extend extend the the existing existing MDGM applicati application on configur configuration ation ( BS_MAT_OVP ). It is located in the development package MDG_BS_MAT_UI . If necessary you can also create a new application configuration. You can use the existing MDGM application configuration ( BS_MAT_OVP ) as a template.

Note You cannot add fields from a new entity type to an existing UIBB. The new fields must be added to a new UIBB. Multiple UIBBs can be added to a single assignment block. 6. Optional Optional step: Create a new new print form. form. You can can use the the existing existing print print form form ( MDG_BS_MAT_PDF_05 ) as a template. 7.

Optional Option al step: step: Enhance Enhance the search. search. Generat Generate e the busine business ss template template MDG_MATERIAL again.

Note If you have extended the material master tables with customer-defined fields (using the procedure outlined in SAP Note 44410 ), which you want to include into the MDGM Data Model, you need to enhance the following data structures (corresponding to the extended material master table) manually: ●

The structures of the tables in MDG_BS_MAT_S_MAT_DATA having the suffix _X_TAB

●

The structures in MDG_BS_MAT_S_MATERIAL_UI_PROP

This is valid for both scenarios above.

Scenario: Adding a Customer Owned Reuse Entity Type to the MDGM Data Model You can extend the MDGM data model by adding a customer-owned material master database table (Z table) to the MDGM data model as an entity type. Use the following process to add a reuse entity type to the MDGM data model: 1.

Enhance the following Enhance following data structu structures res (correspond (corresponding ing to the new, new, customer-own customer-owned ed material material master table) table) manually: ○

Add table types for the data and _X structure to MDG_BS_MAT_S_MAT_DATA . Use the same design pattern as used in existing table types.

○

Add a table type to the structure MDG_BS_MAT_S_MATERIAL_UI_PROP . Use the same design pattern as used in existing table types.

2. Im Impl plem emen entt the the BA BAdI dI MDG_BS_MAT_API_SEGMENTS_EXT 3.

Enhance the MDGM data Enhance data model with additiona additionall entity types. types. You can choose choose the the attributes attributes belonging belonging to this this entity type that you wish to add to the MDGM data model. The MDGM data model is called MM .

4. Gen Generat erate e the mode model-s l-speci pecific fic stru structu ctures res.. 5.

Create the the mapping mapping in the SMT SMT and assign assign it to the model model specific specific structures structures..

6. Spe Specif cify y the the field field prop proper erti ties es.. 7.

You can can extend extend the existi existing ng MDGM MDGM applicati application on configu configuration ration ( BS_MAT_OVP ). It is located in the development package MDG_BS_MAT_UI . If necessary you can also create a new application configuration. You can use the existing MDGM application configuration ( BS_MAT_OVP ) as a template.

Note You cannot add fields from a new entity type to an existing UIBB. The new fields must be added to a new UIBB. Multiple UIBBs can be added to a single assignment block.



53

8. Optional Optional step: Create a new new print form. You can use use the existing existing print print form form ( MDG_BS_MAT_PDF_05 ) as a template. 9. Optional Optional step: Enhanc Enhance e the search. search. Enhance Enhance the the ERP material material master master search search template template inSAP_APPL . Generate the business template MDG_MATERIAL again and if required, implement the BAdI BADI_SDQ_PP_SEARCH .

Scenario: Adding a Flexible Entity Type to the MDGM Data Model You can extend the MDGM data model by adding a flexible entity type to the MDGM data model. Note that flexible entity types are not supported in Enterprise Search and so attributes from these entities cannot be used as search criteria. Use the following process to add a flexible entity type to the MDGM data model: 1.

Enhance the MDGM data model Enhance model with with additional additional entity types using the theEdit Edit Data Model configuration Model configuration activity. Choose the attributes that you wish to add to the MDGM data model. The MDGM data model is called MM. Assign the reuse area MDG MDG to to your entity types to declare them as flexible entity types.

2.

Optional Option al step: Generat Generate e the model-sp model-specific ecific struc structures tures..

3.

Specify the field properties. You can do this in the Define Field Properties for UI configuration UI configuration activity.

4. In order to see see the new fields fields on the UI you you should should extend the the existing existing MDGM application application configu configuration ration ( BS_MAT_OVP ). It is located in the package MDG_BS_MAT_UI . If necessary you can also create a new application configuration. You can use the existing print form ( MDG_BS_MAT_PDF_05 ) as a template.

Note You cannot add fields from a new entity type to an existing UIBB. The new fields must be added to a new UIBB. Multiple UIBBs can be added to a single assignment block. 5.

Optional step: Create a new Optional new print form. You can use use the existing existing print print form form ( MDG_BS_MAT_PDF_05 ) as a template.

Note You cannot import flexible entities using IDocs, ALE , or the Master Data Import framework.

More Information For more information on extending the material data model see the SAP Community Network ( Network ( scn.sap.com/ docs/DOC-7858#jive_content_id_Material_Data

4.1.4 4. 1.4

).

Tran Tr ansp spor orta tati tion on of Da Data ta Mo Mode dels ls to th the e Tar Targe gett Sys Syste tem m

You can transfer data models for Master Data Governance from your test system to your target system by means of transport requests.

Process To transport an active version of a data model to the target system, proceed as follows:

54



1.

In Cu Cust stom omiz izin ing g fo forr Master Data Governance , Governance , choose Data Model activity. Model activity.

2.

To activate the data model again, select it and choose

Gene Ge nera rall Setti Setting ngss

Data Da ta Mod Model elin ing g and then the Edit

( Activate) Activate) .

A dialog box appears. 3.

Specify the the transport transport request request that you you want to use use to transport transport the active active data model and and save your your entries. entries. The active data model is transported to the target system. Once in the target system, the data model is activated automatically. This can have the following effects on the generated database tables in which the entities are saved: ○

The generated database tables are generated again.

○

The generated database tables are adjusted.

○

If the entity type was removed from the current data model, the generated database tables are deleted.

Note If a deletion of the active data model is transported, the generated database tables are not deleted – with the exception of the hierarchy tables. To transport an inac inactive tive version of a data model to the target system, proceed as follows: 1.

In Cu Cust stom omiz izin ing g fo forr Master Data Governance , Governance , choose Data Model activity. Model activity.

2.

Choose Ta Tabl ble e Vi View ew inactive data model.

Gene Ge nera rall Setti Setting ngss

Data Da ta Mod Model elin ing g and then the Edit

Tran Tr ansp spor ortt and specify the transport request with which you want to transport the

3. Sel Selec ectt the the data data model model and and choos choose e

Proc Pr oces esss

Tran Tr ansp spo ort

Inc In clu lude de in Req Reque uesst .

In the dialog box that appears, specify that all lower-level entries are to be transported and save your entries.

Note You can activate the transported inactive data model in the target system. To do this, in Customizing for Master Data Governance in Governance in the target system, choose Modeling and then the Edit Data Model activity. Model activity. Select the data model and choose

4.1. 4. 1.5 5

Gene Ge nera rall Set Setti ting ngss

Data Da ta

( Activate) Activate) .

Defi De fini ning ng Da Data ta Mo Mode dels ls in th the e Con Confi figu gura rati tion on Wo Work rkbe benc nch h

You can use this Web Dynpro application to define and activate a data model to map master data in the system, along with its properties and relationships. The system uses this data model to generate database tables in which the master data can be stored. You can assign a reuse active area to a data model or to individual entity types of a data model. Then the inactive portion of master data for this data model is stored in the generated tables and the active portion is stored in the database tables specified in the reuse active area.

Note You can also assign a reuse active area on the level of an entity type.



55

Prerequisites You have created any customer-specific data elements you want to use for the entity types in the data model or for their attributes. If you use entity types with internal key assignments, you can define prefixes for internal key assignment. You do this in Customizing for Master Data Governance under Governance under Gen General eral Sett Setting ingss Def Define ine Pref Prefixe ixess for Inter Internal nal Key Key Assignment .

Selecting Data Models or Creating New Ones In the Configuration Workbench screen, Workbench screen, you can select a data model for editing or you can create a new data model. By default, the system displays all data models that are available for processing. For each data model you can see whether an inactive version of the data model exists alongside the active version and whether that version differs from the active version. .

Working with Data Models and their Entity Types After you select a data model for editing or create a new data model in the Configuration Workbench screen, the Data Model screen Model screen opens. In the Data Model screen, Model screen, you can complete the following tasks: ●

Edit data model details

●

Create and customize entity types that belong to a data model.

●

Check the validity of your settings using the Check Check button. button.

●

Activate changes using the Activate the Activate button. button.

●

Enable and disable entity types, attributes, and relationships For more information, see Adapting Standard MDG Content to Your Business Needs

Data Model Details Panel In the Data Model Details panel, Details panel, you can edit the data model description and view details such as version, and activation status

Entity Types Panel You can select an entity type or create a new one in the Entity Types panel. Types panel. You can edit settings for a selected or newly created entity type using the tab pages.

Entity Details Tab Entity Details is divided into the following sections: ●

General Details

You must define a Storage and Use Type for Type for the entity type. In addition, you can provide other data, such as a description and a data element. ●

Hierarchies

You can indicate whether hierarchies are allowed and what properties they are allowed to have. You can only allow a hierarchy to be set up for entity types with storage and use type 1. ●

Key Assignment

You can indicate how keys are assigned to the entity type. ●

56

Enablement Status PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.


You can enable entity types that are relevant to your business and disable entity types that are irrelevant to your business. ●

Reuse

You can specify a reuse active area and references to elements of the data dictionary. ●

Texts

You can specify the fields of the check tables that contain the texts for an entity type. This is only possible for entity types of storage and use type 3.

Attributes Tab Here you define the attributes of each entity type in the data model. Attributes are mapped as non-key fields in the generated database tables of the entity type. You also need to assign an existing data element to each attribute. The data element determines the technical properties of the attribute as well as the field labels and the input help texts on the user interface. Attributes can be defined as required entry fields or as optional fields. You use a currency-supplying attribute or a unit-supplying attribute to assign a currency or unit of measure to the attribute.

Incoming Relationships and Outgoing Relationships Tabs Relationships can be viewed from the perspective of each of the entity types that are involved. For example, the HAS_ADRE relationship between BP_HEADER and ADDRESS can be viewed from the perspective of both entity types. You can view the relationship in the following ways: ●

If you select the BP_HEADER entity type, you can view the relationship in the Outgoing Relationships tab page.

●

If you select the ADDRESS entity type, you can view the relationship in the Incoming Relationships tab page.

For all relationships, you can define properties such as: ●

Relationship Type (leading, Type (leading, referencing, qualifying, or foreign key)

●

Cardinality

●

Fields of foreign key relationships

You can assign the key fields of the from-entity type to the attributes and key fields of the to-entity type.

Example In the PFLI entity type of the SF data model, you model flight scheduling data. For example, you can specify the cities CITYFROM and CITYTO. The GEOCITY entity type has a storage and use type of 3. It acts as a check table for valid cities. If you want to ensure only valid cities are selectable, you create a foreign key relationships between CITYFROM and GEOCITY, and between CITYTO and GEOCITY. To maintain the foreign key attributes for PFLI, you can open the Incoming Relationships tab, Relationships tab, select the relationships CITYFROM and CITYTO, and choose the foreign keys button. You want to define foreign key relationships so that the fields PARTNER_1 and PARTNER_2 at entity type BPREL contain only the values of the field BP_HEADER at entity type BP_HEADER.

Business Object Types Tab You have to assign business object types only for entity types of storage and use type 1 that you want to replicate, or for which you want to generate their own Enterprise Search template. If you have assigned the same business object type to multiple entity types, then you have to specify the entity type to be used for each business object type.



57

You can do this in Customizing for Master Data Governance under Governance under Used for Each Business Object Type

Data Dat a Model Modelling ling

Specif Spe cify y the Ent Entity ity Type Type to Be Be

Hierarchies Tab If you want it to be possible to set up a hierarchy for the entity type, you must specify at least the root node (hierarchy name) for the hierarchy here. To do this, choose one of the available entity types and assign Hierarchy Name as Name as the usage type. You also can specify all entity types that are to be allowed in the hierarchy of the entity type ( No Special Use or Ranges Permitt ed on End Nodes ) Nodes )

4 .2

UI Modeling

The purpose of UI modeling is to define and customize user interfaces with which users process master data.

4.2 .2.1 .1

Man anag agiing of UI Co Con nfi figu gura rati tion ons s

You use the Manage UI Configurations ( Configurations ( USMD_UI_CONFIGURATION ) Web Dynpro application to manage user interfaces in SAP Master Data Governance. Each table row represents a separate user interface and consists of the user interface application and its configuration. You can create a new user interface configuration by copying an existing one. You can also edit the configurations for existing user interfaces. Each link you click opens the relevant screen in the Floorplan Manager (FPM).

Note You can only use this function if Business Function Master Data Governance, Generic Functions 7.0 Feature Pack ( MDG_FOUNDATION_5 ) is active. The previous version of this application only allows management of UI configurations for specific types of single-object processing UIs. If the relevant relevant business function is not active, you can edit the relevant technical technical elements using transaction SE80 . For more information, see the links in this document under Activities Working with a UI Configuration . The documents listed cover editing using transaction SE80 as well as editing using this Web Dynpro application. The most common types of user interface that you can manage are as follows: ●

Single-Object Processing

●

Multiple-Record Multi ple-Record Processing

●

Search

There are many options to change a user interface including customizing, enhancement, context-based adaptation (CBA), and personalization. Some options affect all clients of a system. Other options are client specific. It is even possible to restrict changes to only one user. For more information, see Floorplan Manager for Web Dynpro ABAP [external ABAP [external document] .

58



Prerequisites ●

An active active data data model exists.

●

You have basic knowledge of how to use the FPM and of the configuration of applications and components with Web Dynpro ABAP.

●

To create a new user interface by copying an existing one, the following criteria must be met: ○

You can use an active MDG data model with at least one entity type with storage and use type 1.

○

You have assigned a business object type code (OTC) to this entity type.

○

Before starting the configuration you need to carry out the following steps to ensure the default data model as the data model for which the UI is configured in the following way: 1.

Run Ru n tra trans nsac acti tion on SPERS_MAINT .

2.

Select Edit Objects

3. Fr From om the the displa displaye yed d list, list, choo choose seSAP SAP Master Data Governance - R_FMDM_MODEL R_FMDM_MODEL . . 4. In the the pop-u pop-up, p, set set the the value value of the fie field ldStandard Standard Data Model to Model to the model that you want to use for UI processing. 5. Co Conf nfir irm m an and d sa save ve..

Activities Opening the Web Dynpro Activity in Customizing Path in Customizing for Master Data Governance, Central Governance (transaction Governance (transaction MDGIMG ): Sett Se ttin ings gs UI Mod Model elin ing g Ma Mana nage ge UI Con Confi figu gura rati tion onss

General

Copying a User Interface Configuration 1.

Select Sele ct the the UI config configura uratio tion n you want want to to copy and and choose choose the the Copy Copy button. button.

2. To expand expand confi configur gurable able compo componen nents, ts, choos choose e theConfigurable the Configurable Components button. Components button. 3. In the Copy Copy column, column, select the technical elements you want to copy, and enter appropriate names for the target configurations. 4. Choo oosse the Start Deep-Copy button. Deep-Copy button. 5. Retu Return rn to th the e Manage UI Configurations screen Configurations screen and refresh the table content. The system displays an additional row in the table with the configurations you just created. 6. If the the user user inter interfac face e is compat compatible ible with with the the MDG Communicator , Communicator , the MDG Communicator Status is Status is set to Configuration missing . missing . To make the MDG Communicator available, Communicator available, you must configure it by choosing the Details link. Details link. Subsequent steps depend on the type of user interface you are configuring and the type of configuration you want.

Working with a UI Configuration The following documents provide detailed information on the concept behind the particular types of user interfaces, and instructions on how to create new user interfaces either using the Web Dynpro application USMD_UI_CONFIGURATION or using transaction SE80 :



59

Single-Object Processing ●

Concept: Creating User Interfaces for Single Object Processing [external Processing [external document]

●

Instructions: Creating a Basic Configuration for the Single-Object Processing UI [external UI [external document]

Search ●

Concept: Configuration of the Generic Search [external Search [external document]

●

Instructions: Configuring the Generic Search for a Particular Business Object Type [external Type [external document]

4.2. 4. 2.2 2

Mast Ma ster er Dat Data a Gove Govern rnan ance ce for for Mate Materi rial al UI UI Exte Extens nsib ibil ilit ity y

For more information on extending the Material UI see How To Extend the MDG-M User Interface ( Interface ( scn.sap.com/ docs/DOC-30192

4.2. 4. 2.3 3

).

Conf Co nfig igur urin ing g Web Web Dy Dynp npro ro Pa Page ge an and d Pan Panel el Ti Titl tles es

You can adapt the page and panel titles in the material Web Dynpro applications to include extra information about a displayed material. Specifically, you can change the information shown in the titles of the component configurations S_MAT_OVP_LAYOUT_06 and S_MAT_OVP_LAYOUT_06_H . The extra information is accessed using placeholders that you insert when configuring the titles. This way, descriptive texts, such as Plant ID , ID , and value texts based on screen selections such as PLT002 can be included. The value texts change dynamically based on user selections.

Changing Page Titles To change the page titles of the component configurations BS_MAT_OVP_LAYOUT_06 and BS_MAT_OVP_LAYOUT_06_H, open the component configuration you want to edit in the Component Configuration Editor, and then enter one or more of the placeholders below into the Page Title field. Title field. The following placeholders can be used as part of the page title: Table 20 Placeholder

Description

&TITLE_MATNR&

Material Number

&TITLE_MAT_DESCR&

Material Description

&TITLE_MATNR_DESCR&

Material Number or Material Description if available

&TITLE_PLANT&

Plant ID

&TITLE_VALAREA&

Valuation Area ID

&TITLE_VALAREA_TYPE&

Valuation Area ID and Valuation Type are not initial value

&TITLE_DCHAIN&

Distribution Chain

60



At runtime, the title is constructed from these placeholders in a two-step approach: 1.

The placeholders placeholders are replaced replaced by the descrip descriptive tive texts, texts, which which may contain contain additional additional placeholde placeholders rs for value value texts. For some placeholders, this replacement may depend on the action assigned to an application and on the value of business data. A translatable separator and a space are attached automatically. For language code EN , this separator is a semicolon.

Example Example 1

Placeholder: &TITLE_MAT_DESCR& Action: Create Material Number: 12345678 Result of Replacement: Material: New &MAT_DESCR&; Example 2

Placeholder: &TITLE_MAT_DESCR& Action: Create Material Number: Initial Result of Replacement: Material: New; 2.

The value value text placeholder placeholderss are replaced replaced by current current values values of related key key fields. fields. For&TITLE_MAT_DESCR& this replacement depends on the existence of the material description in the logon language. For &VALUATION& this replacement depends on the valuation area type.

Example Example 1

Descriptive Text: Material: New &MAT_DESCR& Material Number: 12345678 Material Description: Not maintained in logon language Result of Replacement: Material: New 12345678 Example 2

Descriptive Text: Material: New &MAT_DESCR& Material Number: 12345678 Material Description: Mountain bike Result of Replacement: Material: New Mountain bike

Example of Changing Page Titles You have maintained the following page title: &TITLE_MAT_DESCR&&TITLE_PLANT&&TITLE_VALAREA_TYPE&&TITLE_DCHAIN&

The following is the information available for the material and screen: Table 21 Action:


Change


61

Material Number:

12345678

Material Description:

Mountain bike

Plant ID:

ZAPF

Distribution Channel:

01

Sales Organization:

0001

Valuation Area Type:

Plant

Valuation Area ID:

Valuation Type:

ZAPF Initial (header data set)

The page title at runtime displays as follows: Material: Mountain bike; Plant: ZAPF; Valuation Area (Plant): ZAPF; Distribution Chain: 0001/01

Changing Panel Titles You can adjust the panel titles of the Web Dynpro component configurations BS_MAT_OVP_LAYOUT_06 and BS_MAT_OVP_LAYOUT_06_H so that the current key information is included in these texts. To do this, open the UIBB in the Component Configuration Editor and Editor and edit the Title Title field field in the UIBB to include one of the following placeholders: Table 22 Placeholder

Placeholder Description

&MATNR&

Material Number

&MAT_DESCR&

Material Description

&MATNR_DESCR&

Material Number or Material Description if available

&WERKS&

Plant ID

&VKORK&

Sales Organization

&VTWEG&

Distribution Channel

&BWKEY&

Valuation Area ID

&BWTTY&

Valuation Type

&VALUATION&

Valuation Area Type (Company Code or Plant)

At runtime, the panel titles are constructed from these placeholders. The system replaces these placeholders with the current values of the related key fields. For &TITLE_MAT_DESCR& , this replacement depends on the existence of the material description in the logon language. For &VALUATION& this replacement depends on the type of valuation area.

62



Example Table 23 Panel Title as Configured:

Valuation Area (&VALUATION&) &BWKEY&

Valuation Area Type:

Plant

Valuation Area ID:

Result of Replacement:

4.2. 4. 2.4 4

ZAPF Valuation Area (Plant) ZAPF

Proc Pr oces esss-Or Orie ient nted ed and and Hie Hiera rarc rchi hica call Over Overvi view ew Page Pages s

You can use the overview page to view and enter change request data. You can choose between two overview pages in MDG-M: the process-oriented view and the hierarchical view. The application configurations for these pages are BS_MAT_OVP_06 (process-oriented) and BS_MAT_OVP_06H (hierarchical). You can find these application configurations in the Web Dynpro application MDG_BS_MAT_OVP . These pages represent the entire MM data model. If you reduce the governance scope, the fields removed from the data model become read-only on the UI and should be removed if they are not required for reference purposes. You can access the same information in both pages but the process-orientated view displays all material data whereas the hierarchical view compartmentalizes the data so that you see the high-level data initially and can drill down for further detail. The process-oriented overview page is set as the default Create Material UI Material UI where you are more likely to need to access all data at once. The hierarchical page is set as the default Change Material UI Material UI since changes are usually made to specific parts of the material record. To change the assignment of an overview page see the configuration section.

Configuration You can determine which overview page to display for a given logical action using the following Customizing activities: ●

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

●

Link Log. Actions with UI Application and Bus. Activity: Custom Definition

The activities can be found in Customizing under Cross Cross-Applic -Application ation Compo Components nents Proce Processes sses and Tools for Enterp Ent erprise rise App Applica licatio tions ns Mas Master ter Dat Data a Gov Govern ernanc ance, e, Cen Central tral Gov Govern ernanc ance e Gen Genera erall Set Settin tings gs Pro Proces cesss Mod Modeli eling ng Business Activities .

4 .3

Data Quality and Search

The data quality functions of MDG allow you to enrich and validate master data, as well as to prevent the creation of duplicates. The various search capabilities are not only used to find master data that can be processed, but are also used for matching data to prevent the creation of duplicate information. Correct and complete data can be achieved with automatic derivation of attributes and enrichment from external data sources.



63

4.3. 4. 3.11

Sear Se arch ch Pro Provi vide ders rs for for Mas Maste terr Data Data Gov Gover erna nanc nce e

In SAP Master Data Governance you can use the following search providers to search for master data: ●

Enterprise Search [page 64]

●

Database Search [external Search [external document]

●

Business Address Services (BAS)-Based Search [external Search [external document]

●

Searching with Customer-Specific Search Providers [external Providers [external document]

●

SAP HANA Search

Note To configure SAP HANA Search see Configuring SAP HANA-Based Search for MDG [page 66] and 66] and Configuring Drill-Down Search (Optional) [external (Optional) [external document] .

4.3.1.1

Enterprise Search

In SAP Master Data Governance you can use Enterprise Search to search for master data in the staging area and the active area. The standard system contains the following default search application and access class in Customizing for Master Data Governance, Central Governance under Governance under SAP Custom Customizing izing Imple Implementat mentation ion Guide CrossCross-Applic Application ation Compon Com ponent entss Pro Proces cesses ses and and Tools for for Enterpri Enterprise se Applic Applicatio ations ns Mas Master ter Data Data Governan Governance, ce, Centr Central al Governan Governance ce Gene Ge neral ral Set Settin tings gs Da Data ta Qual Quality ity and and Searc Search h De Defi fine ne Searc Search h Applic Applicat atio ions ns : Table 24 Search Application

Access Class

ES

CL_SDQ_USMD_SEARCH_DATA_IMPL

The following additional search options are available for Enterprise Search: ●

Free text search

●

Fuzzy search

When you select the respective checkboxes, two additional fields appear on the Enterprise Search user interface. In the standard system these two checkboxes are selected for search application ES.

Activities Note To use Enterprise Search for SAP Master Data Governance, step one and step two of the procedure must be executed only if you use customer-defined objects. Step three and step four must always be executed. 1.

Searc Se arch h object object con conne nect ctor or temp templat late: e: The standard system contains default search object connector templates for Supplier and Material. However, if you want to use customer-defined objects, the following is required: For every business object type you want to search for, you have to create a search object connector template in Customizing for Master Data Governance, Central Governance under SAP Customizing Implementation

64



Guide Guid e Cr Cros osss-Ap Appl plic icat atio ion n Compo Compone nent ntss Ma Mast ster er Data Data Gove Govern rnan ance ce,, Centra Centrall Gover Governa nanc nce e Data Quality Quality and Search Search Create Searc Search h Object Object Connect Connector or Templates Templates . 2.

Gene Ge neral ral Set Setti ting ngss

You then assign assign your your search object object connector connector templates templates to your your business business object types types in Customiz Customizing ing activity Assign activity Assign Search Object Connector Templates to Object Types . Types . The standard system contains the following default assignments: Table 25 Business Object Type

Search Object Connector Template

986 (Business Partner Relationship Process Control) 194 (Material)

MDG_BUSINESS_PARTNER MDG_MATERIAL

3. Sea Searc rch h obje object ct con conne nect ctor or:: In the Connector Administration Cockpit (transaction ESH_COCKPIT) you must create a search object connector based on the respective search object connector template and software component.

Recommendation On the detailed screen for the search object connector template, go to the Schedules Schedules tab tab page and enable real-time indexing. 4. Sea earrch in index ex:: In the Connector Administration Cockpit you have to execute the following: ○

Initial data load for indexing the data for your search object connector(s).

○

Schedule the delta update of the search index so that the Enterprise Search is regularly updated with the master data that has been changed in the meantime.

The concept of Enterprise Search for SAP Master Data Governance described above is shown in the following figure:

Figure 2: Enterprise Search for SAP Master Data Governance



65

4.3. 4. 3.1. 1.2 2

Crea Cr eati ting ng an and d Ext Exten endi ding ng Se Sear arch ch Pr Prov ovid ider ers s for for Mat Mater eria iall

For information on MDGM-Specific Custom Search Providers see the document Replace Enterprise Search by DB or Alternative Search Provider ( Provider ( scn.sap.com/docs/DOC-44779

).

For more information on enhancing enterprise search for material see Enhancing the Material Search scn.sap.com/docs/DOC-29002

4.3. 4. 3.1. 1.3 3

.

Conf Co nfig igur urin ing g SAP SAP HAN HANAA-Ba Base sed d Sea Searc rch h for for MD MDG G

SAP HANA -based HANA -based search for SAP Master Data Governance enables Governance enables you to perform searches and duplicate checks on master data residing in the SAP HANA database. HANA database. An SAP HANA search HANA search provider is delivered to enable these features. The following data models are supported out-of-the-box forMDG for MDG on HANA : HANA : ●

Flex data models

●

The business partner reuse model ( BP )

●

The material reuse model ( MM )

The access class implementation is not provided for other reuse models. You must implement the access class for SAP HANA search HANA search to use it with the other reuse models. SAP HANA-based search for SAP Master Data Governance can be used for the following MDG applications: ●

Master Data Governance for Custom Objects

●

Master Data Governance for Financials

●

Master Data Governance for Supplier

●

Master Data Governance for Customer

●


Prerequisites You have activated the business functions Master Data Governance, Generic Functions 7.0 ( MDG_FOUNDATION_4 ) and Master Data Governance, Generic Functions 7.0 Feature Pack ( MDG_FOUNDATION_5 ). You have installed the SAP HANA database, HANA database, support package 06. We recommend that you install the highest available version of the SAP HANA database. HANA database. You must have the following permissions to work with search views in SAP HANA : HANA : ●

Permission to create a package and to write objects into packages

●

Permission to create, change and drop attribute views

●

Permission to create, change and drop SQL views

●

Permission to create, execute and drop rule sets

For more details please refer to the SAP HANA HANA security security guide.

66



Process To configure SAP HANA -based HANA -based search for MDG, carry out the steps described below. 1.

Create Database Connection

Run transaction DBCO and create a database connection to the SAP HANA database. HANA database. Table 26 Field

Value

Database Connection Name

Unique name for the SAP HANA database HANA database connection used for search and duplicate check

Database System

SAP HANA database HANA database

Permanent

Yes

User Name

Schema name created in step above

Connection Information

Server: instance number

Connection Limit

0

Optimum Number of Connections

0

Note Deploymentt Options for MDG 7.0 Deploymen

MDG 7.0 can be deployed on an SAP HANA database HANA database or on any database.

2.

○

If you deploy MDG 7.0 on SAP HANA , HANA , then SAP HANA acts HANA acts as the primary database and the creation of the database connection is optional. If the database connection is not maintained then a default connection is derived automatically.

○

If you deploy MDG 7.0 on any other database, then you must maintain the database connection to the schema in the SAP HANA database. HANA database.

Maintain the MDG SAP HANA Database Profile Settings

You must define the MDG landscape settings, such as the connection to the SAP HANA database that is used for the search and duplicate check processes. You can make these setting in Customizing under Master Data Da ta Gove Govern rnan ance ce,, Centr Central al Gove Govern rnan ance ce Ge Gene neral ral Set Setti ting ngss Te Tech chnic nical al Setti Setting ngss for Mas Maste terr Data Data De Defi fine ne MDG MDG Landscape Profile . The use of an SAP Landscape Transformation (SLT) Transformation (SLT) server is optional for MDG data replication. If you use SLT for for replicating the MDG table data to the SAP HANA database HANA database system, then you must also define a connection to an SLT server server as explained below.

Note Deploymentt Options for MDG 7.0 Deploymen ○

If you deploy MDG 7.0 on SAP HANA , HANA , then SAP HANA acts HANA acts as the primary database and no replication is required.

○

If you deploy MDG 7.0 on another database, the MDG data must be replicated to SAP HANA search HANA search schema either by SAP Landscape Transformation (SLT) Transformation (SLT) or by other means. To generate a search view in the target system where search is performed, the MDG table metadata and data must be replicated



67

to the SAP HANA database. HANA database. To enable this initial replication of the data you must carry out the steps described below. 1.

Run Ru n tra trans nsac acti tion on MDGIMG .

2.

Nav avig igat ate e to to Mas Master ter Dat Data a Gover Governan nance, ce, Cen Central tral Gov Govern ernanc ance e Master Mas ter Dat Data a Def Define ine MDG Lan Landsc dscape ape Pro Profile file .

General Gen eral Set Settin tings gs

Technic Tec hnical al Settin Settings gs for for

3. Ent Enter er data data in the the fol followi lowing ng fie fields lds:: Table 27 Field

Value

Database Connection Name for MDG

The SAP HANA database HANA database used for the search and duplicate check processes created in the previous step. This field is optional if MDG 7.0 is deployed on a SAP HANA database. HANA database.

RFC Connecting MDG to SLT System

Optional, only enter data if you use SLT for data replication

SLT Configuration Name

Optional, only enter data if you use SLT for data replication

In the SAP HANA system, HANA system, where the search on MDG data is performed, you must generate the search view. If you deploy MDG on a traditional database, and use SLT for for replication then, when generating the view, before it is created, the system replicates the required table metadata to the SAP HANA database HANA database using the SLT settings. settings. If SAP HANA is HANA is the primary database, it is not mandatory to maintain the database connection name in MDG Landscape Profile customizing. If the name is not maintained the system uses the default database connection. You still have the option of maintaining a different connection name in the MDG Landscape Profile if you do not wish to use the default database connection. 4. In the the SLT system system the SLT SLT user require requiress the author authorizatio ization n object S_DMIS , with the following field values defined for their role: Table 28 Authorization Object

Value

Activity ( Activity ( ACTVT )

02 (Change)

MBT PCL: Scenario ( Scenario ( MBT_PR_ARE )

SLOP (SAP Landscape Transformation

MBT PCL: Processing Role Level ( Level ( MBT_PR_LEV )

PACKAGE (Transfer package level)

5. For Mat Materi erial al Searc Search, h, in tran transac sactio tion n SA38 execute the report MDG_HDB_MAT_MIGRATE_LONGTEXT as a background job. Select the Overwrite target table records checkbox, records checkbox, to perform the initial load of material long texts to the database table MDGHDB_LONGTEXT . This loads the following long text types: Basic Data Text, Sales Text, Purchase Order Text, Inspection Text, Internal Note, and Material Note MRP. 3.

Define Authorization Relevance for Each Entity Type

The authorizations maintained in customizing are considered during search. You can maintain the authorization in Customizing under Master Data Govern Governance, ance, Central Govern Governance ance Gene General ral Settings Settings Data Mode Modeling ling Defin Define e Authoriz Authorization ation Releva Relevance nce per Entity Type . 4. Create Search View Create a search view in the development system and transport it to the test and production systems. The search view must be generated or regenerated in the target (test and production) systems.

68



If you are using the business partner, customer, or supplier domains and have activated the business functions MDG_ERP_CUSTOMER_3 , MDG_ERP_SUPPLIER_4 , or MDG_BUPA_1 , or if you are using material domain and have activated the business function MDG_MATERIAL_5 , then you must assign the template views from these business functions to a customer package in the Create Search View configuration View configuration activity before you can generate and use them. You must also have authorization to create a workbench request. To create a search view, run transaction MDG_HDB_GEN_UI or navigate to Master Data Governance, Central Gove Go vern rnan ance ce Ge Gene nera rall Sett Settin ings gs Da Data ta Qua Quali lity ty and and Sea Searc rch h Se Sear arch ch and and Dup Dupli lica cate te Che Check ck Cr Crea eate te Sea Searc rch h View . The package where you generate the search view must be in the customer namespace. Enter the name of the package during search view creation. When you create the search view and the system generates the SAP HANA view, HANA view, the following search configuration data is automatically updated: ○

Master Mast er Dat Data a Gove Govern rnan ance ce,, Cent Centra rall Gove Govern rnanc ance e Ge Gene neral ral Se Sett ttin ings gs Da Data ta Qua Quali lity ty and and Sear Search ch Se Sear arch ch and Dupl Duplica icate te Check Check Def Define ine Sear Search ch Applic Applicatio ations ns Allo Allocat cation ion of of Search Search Help Help to Sear Search ch Applic Applicatio ations ns

○

Master Mast er Dat Data a Gove Govern rnan ance ce,, Cent Centra rall Gove Govern rnanc ance e Ge Gene neral ral Se Sett ttin ings gs Da Data ta Qua Quali lity ty and and Sear Search ch and Dup Duplica licate te Chec Check k Def Define ine Sea Search rch App Applic licatio ations ns Allo Allocat cation ion of Entit Entities ies to Sear Search ch Help Help

Sear Se arch ch

In SAP HANA attribute views are created on the active and inactive areas. After you create the search view it can be manually edited within SAP HANA Studio to Studio to update the search properties of an attribute. In this case, if the search view is regenerated, the new search view will overwrite the manually updated search view. You can create a search rule set during the search view generation if you want the search to be performed based on search rule sets. If you choose the create ruleset option for a reuse model, a union SQL view is created on the attribute view in SAP HANA. This search rule set can also be manually updated according to the business requirements of the users after it is generated. If the search view is edited at a later date and is regenerated, the search rule set will not be regenerated/overwritten; it has to be manually adjusted. You must manually check out the generated search rule set to the Project Explorer view Explorer view of the SAP HANA Studio Administration Console before Console before it can be edited to change any parameter, such as the fuzzy value or weight of an attribute, and activate it to enable search based on this modified search rule set. You can also copy an existing search view and edit it before generating the search view. If there is a mismatch between the generated search view and the underlying objects, the system recognizes this and updates the status of the generated search view to Outdated. You can edit this outdated search view and regenerate the view. To delete a search view, you must first remove the customizing settings for the search view, and then delete the search view. The status of the view is then set to Marked for Deletion. In transaction SE38 execute the report program MDG_HDB_DELETE_SEARCH_VIEWS to delete the specific view or all views that are marked for deletion, and drop the corresponding objects in SAP HANA. You must set filters in the SAP HANA staging HANA staging views to exclude records that have the obsolete indicator set. Identify all the Obsolete Indicator flags. Indicator flags. The fields corresponding to the obsolete indicator flags in each table of a staging view have the technical naming convention USMD*_OBS_* or USMD*_O_* . Select the obsolete indicator in the Details Details section section of the staging view, right click and select Apply select Apply Filter . Filter . In the Operator Operator field field Not Equal and in the Value select Not Value field field enter X . Table 29 Field Name

Operator

Filter Value

USMD*_OBS_*

Not Equal

X



69

Field Name

Operator

Filter Value

USMD*_O_*

Not Equal

X

For material search you must set filters in the SAP HANA views for the material-related long texts stored in the database table MDGHDB_LONGTEXT . This means that only the appropriate long texts are taken from Content folder folder and navigate to the MDGHDB_LONGTEXT . To do this, in the SAP HANA studio, open the Content package where the search views are created. For reuse entity types, creating a search view generates two views in the SAP HANA system (one each for the active and staging areas), or three if you are using classification data. The views generated for the active area have names similar to searchviewname_Reuse and searchviewname_RINOB . Open the reuse SAP HANA views below. Go to Detail Detail window, window, and select the long text table with the alias you want to update and right-click on the attribute. From the menu choose Apply choose Apply Filter . Filter . From the drop-down menu choose the operator Equal Equal and and maintain the values as specified in the tables below. Basic Text Table 30 Field Name

Filter Value

Table Name (Alias)

BSCDATTXT_TDID

GRUN

BSCDATTXT_MDGHDB_LONGTEXT

BSCDATTXT_TDOBJECT

MATERIAL

BSCDATTXT_MDGHDB_LONGTEXT

Field Name

Filter Value

Table Name (Alias)

SALESTXT_TDID

0001

SALESTXT_MDGHDB_LONGTEXT

SALESTXT_TDOBJECT

MVKE

SALESTXT_MDGHDB_LONGTEXT

Field Name

Filter Value

Table Name (Alias)

QINSPTXT_TDID

PRUE

QINSPTXT_MDGHDB_LONGTEXT

QINSPTXT_TDOBJECT

MATERIAL

QINSPTXT_MDGHDB_LONGTEXT

Field Name

Filter Value

Table Name (Alias)

PURCHTXT_TDID

BEST

PURCHTXT_MDGHDB_LONGTEXT

PURCHTXT_TDOBJECT

MATERIAL

PURCHTXT_MDGHDB_LONGTEXT

Field Name

Filter Value

Table Name (Alias)

MRPTXT_TDID

LTXT

MRPTXT_MDGHDB_LONGTEXT

Sales Text Table 31

Quality Inspection Text Table 32

Purchase Text Table 33

Plant Text Table 34

70



Field Name

Filter Value

Table Name (Alias)

MRPTXT_TDOBJECT

MDTXT

MRPTXT_MDGHDB_LONGTEXT

Field Name

Filter Value

Table Name (Alias)

INTCMNT_TDID

IVER

INTCMNT_MDGHDB_LONGTEXT

INTCMNT_TDOBJECT

MATERIAL

INTCMNT_MDGHDB_LONGTEXT

Internal Comment Text Table 35

5.

Verify Customizing Settings for Search View

After you have created and saved the search view, you must verify that the customizing settings are automatically updated for the newly created search view. To do this, perform the following: 1.


2.

Navigat ate e to to Mas Master ter Dat Data a Gover Governan nance, ce, Cen Centra trall Gover Governanc nance e Gen Genera erall Sett Setting ingss Searc Se arch h Se Searc arch h and and Dupl Duplic icate ate Ch Chec eck k De Defi fine ne Sea Searc rch h Appl Applic icat atio ions ns .

Data Dat a Qualit Quality y and and

3. Selec Selectt the the ro row w wit with h the the Search Mode HA (HANA) . Note that the Fuzzy Fuzzy checkbox checkbox has no impact on SAP HANA search; SAP HANA search is fuzzy by default and this cannot be changed here. 4. Do Dou ubl blee-cl clic ick k on Allocation on Allocation of Search Help to Search Applications . Applications . 5.

Verify that there there is an entry entry for the newly newly created created search search view view in the theIncluded Included Search Help field Help field with the technical name provided during search view creation.

6. Sele Select ct the the row of of the the newly newly create created d search search view view.. 7. Dou Doubl blee-cl clic ick k on on Allocation of Entities to Search Help and Help and verify that the main entity type that you selected during search view creation is updated. 6. Create Match Profile for Duplicate Checks based on SAP HANA Search If you have created a search rule set in the Create Search View step, you can use it to configure the match profile for duplicate checks. 1.


2.

Navigat ate e to to Mas Master ter Dat Data a Gover Governan nance, ce, Cen Centra trall Gover Governanc nance e Gen Genera erall Sett Setting ingss Searc Se arch h Se Searc arch h and and Dupl Duplic icate ate Ch Chec eck k De Defi fine ne Sea Searc rch h Appl Applic icat atio ions ns .

Data Dat a Qualit Quality y and and

3. Se Selec lectt the the ro row w wit with h the the Search Mode HA (HANA). 4. Do Dou ubl blee-cl clic ick k on Match Profile . Profile . 5. For the spe specifi cific c data data model model and the theMatch Match Profile ID for Duplicate Check enter Check enter the name of the search rule set if you generated one in step 4 above, otherwise, leave the field empty. When you enter the search rule set name, the information from the search rule set is used instead of the attribute view while performing search during duplicate checks. 7.

Configure Duplicate Check Based on SAP HANA search

After you have maintained a match profile ID, you can configure the search view for duplicate checks. 1.

Exec Ex ecut ute e tra trans nsac acti tion on MDGIMG .

2.

Navigat ate e to to Mas Master ter Dat Data a Gover Governan nance, ce, Cen Centra trall Gover Governanc nance e Gen Genera erall Sett Setting ingss Dat Data a Qualit Quality y and and Search Sea rch Sea Search rch and Dup Duplic licate ate Che Check ck Con Configu figure re Dupl Duplica icate te Chec Check k for for Entit Entity y Types Types .

3.

Sele lec ct the Data Model and Model and Entity Type for Type for which you want to configure the duplicate check. Select the Search Mode as Mode as HA . Enter the threshold values for the duplicate check. Enter the name of the Match



71

Profile ID and ID and the search view to be used for the duplicate check. Select the Match Profile Based UI if UI if required. 8. Test Search and Duplicate Check 1.

Test Te st th the e SAP SAP HA HANA NA Se Sear arch ch 1.

Launch the SAP NetWeaver Business Client . Client .

2. Sele Select ct the the work work cent center er for for your your data data model. model. 3. La Laun unch ch th the e sear search ch UI UI.. 4. In the Search Method field Method field enter the SAP HANA Search Configuration that Configuration that you have created. 5.

Choose Search Search and and the search results should be returned.

6. In addition, addition, perform perform a freestyle freestyle search search and and an attribute attribute search search and check the the results. results. 2. Te Test st th the e Dup Duplic licate ate Ch Check eck 1.

Create Cre ate a duplic duplicate ate of an an exis existin ting g objec object. t.

2. When When you have have ente entered red data data for for your objec objectt choose chooseCheck Check . . This triggers the duplicate check and the system should indicate that your new object is a potential duplicate.

Result You have now configured your system to use SAP HANA for HANA for MDG search. For drill down search configuration, see Configuring Drill-Down Search (Optional) [external (Optional) [external document] .

4.3.1.3.1

Creating a Search View

Search views are used by the SAP HANA database HANA database to optimize performance when searching. Each search view consists of entities and attributes from the Master Data Governance data model. You can use the Create Search View application View application to create search views for your more common searches and reports. If an existing search view is outdated you can also use this application to update and regenerate it. Regenerating a view overwrites manual modifications to the attribute views made in SAP HANA but HANA but does not overwrite rule set changes.

Process To create a search view follow this process: 1.

Open the Create Search View application. View application.

2.

In the Enter General Data step, Data step, enter a technical name, description, and choose a business object type.

3.

Choose an SAP HANA package HANA package which specifies the folder in the SAP HANA system HANA system where the view is created. You can leave this field blank and fill it in later, before view generation. If you want to search based on rule sets, select the Rule Set checkbox. Set checkbox.

4. Choose Next Next . . 5.

In the Select Entities and Attributes step, Attributes step, select the entities and attributes you want to add to the search view. The entities and attributes displayed are based on the business object you selected in the previous step.

6. Choose Next Next . .

72



7.

In the Review and Generate step, Generate step, confirm the data you entered in the previous steps. Save and transport the data to the target system. In the target system enter the package name if you have not already done so. Choose Generate Generate to to create a search view in the SAP HANA system HANA system under the package you have entered.

Result You have generated a new or updated search view in the SAP HANA system. HANA system.

More Information Configuring SAP HANA-Based Search for MDG [page 66]

4.3.2 4.3 .2

Defini Def initio tion n of Val Valida idatio tions ns an and d Deri Derivat vatio ions ns in BRF BRFplu plus s

You use this Web Dynpro application ( USMD_RULE ) to define validation and derivation rules for a specific data model of Master Data Governance. Derivation rules are designed to simplify the entry of master data, whereas validation rules ensure consistency of the master data entered.

Integration After you specify a data model, the Web Dynpro application launches the Business Rule Framework plus ( BRFplus) application. For more information, see Business Rule Framework plus [external plus [external document] (available in English only).

Prerequisites You have created the data model for which you want to define derivations and validations. Trigger Functions

You can assign trigger trigger functions to the following events to validate master data changes: ●

CHECK_ENTITY (Check entity): The system executes the function assigned to this event when entity values

are validated during single or collective processing, when mass changes are made, or during the upload process. ●

executes the function assigned to this event CHECK_CHANGE_REQUEST CHECK_CHANGE_REQUEST (Check change request): The system executes the when the change request is checked. It also executes the function prior to the final check of the change request.

●

CHECK_EDITION (Check edition): The system executes the function assigned to this event before an edition

is released. ●

CHECK_ENTITY_HRY (Check hierarchy information of an entity): The system executes the function assigned

to this event after the hierarchy of an entity type is changed.



73

●

CHECK_CHANGE_REQUEST_HRY (Check hierarchy information of a change request): The system executes the

function assigned to this event at the same time as CHECK_CHANGE_REQUEST . The function assigned to the CHECK_CHANGE_REQUEST_HRY event is used to check the hierarchy information. ●

CHECK_EDITION_HRY (Check hierarchy information of an edition): The system executes the function

assigned to this event at the same time as CHECK_EDITION . The function assigned to the CHECK_EDITION_HRY event is used to check the hierarchy information. ●

DERIVATION (Derivation): The system executes the function assigned to this event when data is entered

during single processing or the upload process. When defining rules for CHECK events, you can define an action for issuing a message and control further processing in Master Data Governance based on which message type you select. When defining rules for the DERIVATION event, you can use the Change Context action Context action to change the attribute values of the entity type. You can also trigger other actions (for example, by means of a static method) and include additional information in the computation. For each entity type of the data model with storage and use type 1 or 4, the system generates a structure-type data object when you start this Web Dynpro application for the first time. Each time you subsequently activate a change to the data model, the system again generates the data objects the next time the user starts the Web Dynpro application. BRFplus Structure Generation

If entity type 1 and entity type 4 have the cardinality 1:N, the BRFplus catalog generation does not add the fields of entity type 4 to the fields of entity type 1. If entity type 1 and entity type 4 have the cardinality 1:1, the structure generation and the derivation function in BRFplus treat entity type 4 as an extension of entity type 1. If entity type 1 and entity type 4 have the cardinality 1:1, the BRFplus catalog generation adds the fields of entity type 4 to the fields of entity type 1.

Note If entity type 1 and entity type 4 have the cardinality 1:1, instead of calling the derivation function of entity type 4, the system calls the derivation function of entity type 1. Naming Conventions

The following naming conventions apply to the relevant nodes, objects, applications, and catalogs: ●

Trigger function nodes in the catalog structure The naming convention for validation-based trigger function nodes of a catalog structure is: CHECK_, for example, CHECK_ACCOUNT . The naming convention for derivation-based trigger function nodes of a catalog structure is DERIVE_, for example, DERIVE_ACCOUNT .

Note These naming conventions apply only to the naming of the trigger function nodes of a catalog structure. They do not apply to the naming of the trigger functions linked to the nodes. Each entity type should have a maximum of one trigger function per event. The nodes of the respective function branch of the trigger function represent the corresponding application options. ●

74

Data objects PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.


Data objects are automatically generated from the data model definition. The structure-type data objects have the same names as their respective entity types.

Note The naming conventions valid for SAP enhancement package 4 are still supported. However, we recommend that you discontinue their use. The standard system features the following predefined data objects, which you can use within rules and functions, as additional input parameters: ○

SAPFMDM_CREQUEST_TYPE : Change of change request type ID

○

SAPFMDM_CREQUEST : Change of change request ID

○

SAPFMDM_EDITION_TYPE : Edition type ID

○

SAPFMDM_EDITION : Edition ID

○

SAPFMDM_PROCESS : Business activity

○

SAPFMDM_CREQUEST_STEP : Change request step

○

SAPFMDM_CREQUEST_INDEX : Change request index

○

SAPFMDM_WORKITEM_ID : Work item

○

SAPFMDM_HRY_DELTA : Deep structure consisting of a hierarchy relationship (or an associated pair of

objects) for validation This must be used in the hierarchy-based validation events CHECK_ENTITY_HRY , CHECK_CREQUEST_HRY , and CHECK_EDITION_HRY .

Note If a trigger function contains the predefined data objects only, it is executed once during the validation. ○

BRFplus application and catalog The system creates the BRFplus application [external application [external document] and catalog structure automatically for each data model when you define validations or derivations.

Note Use the namespace for the system-generated BRFplus application and catalog structure to create your own applications and catalogs. The system uses the syntax FMDM_MODEL_, for example, FMDM_MODEL_0G for data model 0G . Enhancement Enhancem ent for Validation and Derivation

The Business Add-In (BAdI) Define Validations/Derivations is Validations/Derivations is provided as an enhancement implementation of this Web Dynpro application. This enables you to define validations and derivations using alternative code. To call the BAdI, in Customizing for Master Data Governance, Central Governance choose Governance choose General Settings Data Quality and Search and choose the Customizing activity BAdI: Define Validations/Derivations . Validations/Derivations . If entity type 1 and entity type 4 have the cardinality 1:N, in the derivation function of the entity type 4 you have read access to the values of entity type 1 for determining entity type 4. In the derivation function of entity type 1, you do not have read access to the values of entity type 4.



75

Activities To start this Web Dynpro application, in Customizing for Master Data Governance, Central Governance choose Governance choose Genera Gen erall Sett Settings ings Dat Data a Qualit Quality y and and Searc Search h and choose the Customizing activity Define Validation and Derivation Rules . Rules .

Example Creating BRFplus functions for derivations of entities with storage and use type 4 The following table shows an example of the different cardinalities, which are described in the BRFplus Structure Generation section. Table 36 Entities

Entity Type

CARR

1

Attributes

CURRCODE CARR_DELTA

4 with 1:1 cardinality URL

COUNTER

4 with 1:N cardinality COUNTNUM AIRPORT C_URL

This example contains the entity CARR with storage and use type 1 along with the dependent entities CARR_DELTA and COUNTER, which have storage and use type 4. CARR_DELTA has the cardinality 1:1 and COUNTER has the cardinality 1:N. The third column shows the attributes of the entities. Generated BRFplus Structures Table 37 Entities

Attributes of the Generated BRFplus Structures

CARR CARR CURRCODE URL CARR_DELTA URL COUNTER CARR COUNT_NUM AIRPORT

76



Entities

Attributes of the Generated BRFplus Structures

C_URL

In the data model, the entities with storage and use type 4 have their own attributes. In contrast, in generated BRFplus structures, the system adds the attributes of the entities with storage and use type 4 with cardinality 1:1 to the attributes of entity type 1. For this reason, the CARR structure has the additional URL attribute. ●

Derivations for entities with cardinality 1:1 ○

UIs based on Web Dynpro application USMD_ENTITY_VALUE2 If you want to create a derivation for CARR_DELTA in BRFplus, you can execute this only with the function DERIVE_CARR, but not with the DERIVE_CARR_DELTA function. When entities have the cardinality 1:1, in BRFplus you access derivations using the entity type 1.

○

UIs based on the Convenience API CL_USMD_CONV_SOM_GOV_API If you want to create a derivation for CARR_DELTA in BRFplus, you can execute this only with the function DERIVE_CARR_DELTA, but not with the DERIVE_CARR function.

●

The generated BRFplus structure of the entity type 1 contains the attributes of the entity type 4 with cardinality 1:1. If you specify the signature for the BRFplus function, you must use the structure of the type-1 entity CARR.

●

In contrast, to access access an entity type 4 with cardinality 1:N (for example, COUNTER), you call the DERIVE_COUNTER function.

●

The signature of the BRFplus function DE RIVE_COUNTER is the COUNTER structure.

4.3. 4. 3.3 3

Chec Ch ecks ks an and d Der Deriv ivat atio ions ns fo forr Mat Mater eria iall

For information on validations and derivations for material see Checks and Derivations scn.sap.com/docs/ DOC-14915

.

4.3. 4. 3.4 4

Data Da ta Qua Quali lity ty Rem Remed edia iati tion on Con Confi figu gura rati tion on Gui Guide de

This document describes the necessary configuration steps you have to process to use the data quality remediation in Master Data Governance.

Prerequisites 1.

You have have insta installed lled a data data qualit quality y tool in in your your system system lands landscape cape..

2.

You have installed installed a data data quality connecto connectorr in the MDG system. system. The The data quality quality connector connector consists consists of an ABAP class that implements the interface IF_MDG_DQR_DQ_SERVICE and, optionally, an implementation of the BAdI Event Handling for Data Quality Remediation . Remediation . For more information, see the documentation of this BAdI under Ge Gene nera rall Set Settin tings gs Da Data ta Qua Qualit lity y and and Sea Searc rch h Bu Busi sine ness ss Ad Addd-In Inss .



77

Process Configuration Process

1.

You need to execu execute te the the Custo Customiz mizing ing act activit ivity y Define Data Quality Service . Service . For more information, see the documentation of this customizing activity under Ge Gene neral ral Se Sett ttin ings gs Da Data ta Qu Qual ality ity and Se Sear arch ch Da Data ta Qu Quali ality ty Remediation .

2.

Copy the Floor Plan Manag Manager er (FPM) (FPM) Config Configuration uration Templat Templates es 1.

In the package package MDG_DQR MDG_DQR_GENERA _GENERAL L select Web Dynpro Dynpro Application Application configur configuration ation MDG_DQR_ MDG_DQR_OVP OVP and choose Start Configurator . Configurator .

2.

In the Editor for the Web Dynpro ABAP Application Configuration select Configuration select Continue in Display Mode . Mode .

3.

In the Application Application Configu Configuration ration MDG_DQR_ MDG_DQR_OVP OVP select select the configura configuration tion name MDG_DQR MDG_DQR_OVP _OVP of the the component FPM_OVP_COMPONENT.

4. In the the Component Component Confi Configurati guration on of compone component nt MDG_DQR_ MDG_DQR_OVP OVP select select Additional Functions Copy . 5.

Deep

Choose Configurable Components to Components to expand the list of configurations. To create a copy of the Application Configuration MDG_DQR_OVP, the Overview Page Floorplan MDG_DQR_OVP Floorplan MDG_DQR_OVP and at least of the component configuration MDG_DQR_FAILED_REC_LIST_UIBB, set the according flags in the column Copy and Copy and enter appropriate names in the column Target Configuration . Configuration . Then choose Deep-Copy Deep-Copy . .

Note The technical names of target configurations should reflect the business object type and the data quality service. 6. Cho Choose ose a packag package e for the the copied copied config configura uration tions. s. 3. Adap Adaptt the Copi Copied ed Confi Configur gurati ations ons of of the the FPM 1.

Select Sele ct the the name of of the copie copied d applicat application ion confi configur guratio ation. n.

2.

Select Edit Edit and and enter the ID of the data quality service defined in step 1 in the parameter MDG_DQR_DQS_ID and save.

3.

Select the copied copied config configuration uration of the the componen componentt MDG_DQR_O MDG_DQR_OVP. VP.

4. Change Change the copy of the the configuration configuration MDG_DQR_ MDG_DQR_FAILE FAILED_REC_ D_REC_LIST_U LIST_UIBB IBB by the selectin selecting g the respective UIBB and choosing Configure UIBB . UIBB . 5.

Choose General Settings and Settings and then Feeder Class Parameters and enter the Business Object Type for Type for which you want to configure data quality remediation and save your entries.

6. Confi Configure gure the the List List UIBB UIBB according according to the selected selected busines businesss object type. 4. Con Config figure ure Chan Change ge Reques Requestt Proces Processs for for DQR Create a business activity for the business object type with logical action CHANGE_DQR in customizing activity Create Business Activity and Activity and assign it to a change request type in Customizing activity Create Change Request Type . Type . 5.

To provide the the DQR function function to your your users add add the Web Dynpro Dynpro application application MDG_DQR_OVP MDG_DQR_OVP with with the copy copy of the configuration MDG_DQR_OVP to the role menu.

With the description above you configure the DQR application to include the UI of the data quality tool. The URL to this UI is defined in the Customizing activity Define Data Quality Service . Service . To filter the displayed objects with errors the UI of the data quality tool can raise events that are provided to the DQR application with the implementation of the BAdI Event Handling for Data Quality Remediation . Remediation . This filtering can also be done with dropdown lists. The configuration template for this variant is provided in the application configuration MDG_DQR_OVP_FILTER and component configuration MDG_DQR_FILTER_UIBB. To co nfigure this variant go through this configuration

78



process and use application configuration MDG_DQR_OVP_FILTER instead of MDG_DQR_OVP in step 2. In this case you need to copy and adapt the component configuration MDG_DQR_FILTER_UIBB by setting the feeder class parameter to the data quality service ID you want to use for your DQR process.

4 .4

Process Mo Modeling

The configuration of governance scope, change requests, and workflow offers you flexible ways to model the desired governance process.

4.4 4. 4.1

Def efiini nin ng a Gov over ern nanc nce e Sc Sco ope

You can determine a governance scope based on your business needs. Ungoverned fields are read-only in change requests, unless you remove them from the user interface.

Example In the material application, you can for example, remove sales grouping data from the governance scope.

Prerequisites You have identified the data models whose governance scope you want to change, as well as the content within each data model that you want to govern. You are aware of the consequences of changing the governance scope. See the help document in Customizing for Master Data Governance under Governance under Ge Gene nera rall Setti Setting ngss Pro Proce cess ss Mod Model elin ing g De Defi fine ne Gov Gover ernan nance ce Sco Scope pe

Procedure 1.

In Cu Cust stom omiz izin ing g fo forr Master Data Governance under Governance under Governance Scope . Scope .

Genera Gen erall Set Setting tingss

Proces Pro cesss Mod Modeli eling ng , choose Define

2.

In the Data Models view, Models view, select the data model whose governance scope you want to define.

3. Ma Make ke nece necess ssar ary y chan change gess to the the Governed Governed settings settings of entity types, attributes, and referencing relationships. If there are dependencies, a pop-up informs you of these dependencies and proposes required changes. You can apply required required changes or cancel. The following changes to governance scope are not possible: ○

Changes to the Governed Governed setting setting for entity types with types with a storage a storage and use type of type of 1. These entity types are shown in the Customizing activity, to enable navigation to attributes.

○

Changes the Governed Governed setting setting of attributes that are key fields. These attributes are not shown in the Customizing activity.

○

Changes to attributes for which the Required Field setting Field setting is set to Yes Yes in in the data model. These attributes attributes are not shown in the Customizing activity. activity.



79

Result You have defined a governance scope for the data model. You can keep ungoverned data model elements on the user interface for information purposes. If the elements are not informative to your users, we recommend that you remove them. For more information, see Managing of UI Configurations [page 58] . 58] .

4.4. 4. 4.2 2

Sett Se ttin ing g Up Up New New Bu Busi sine ness ss Ac Acti tivi viti ties es

You need to carry out the following steps if you want to enable users to create a single entity without having to create a change request beforehand in a separate step. As a result, the user also no longer needs to select the data model, the entity type, or the change request type. These are predefined automatically as part of the configuration settings described in this documentation.

Procedure 1.

Create Cre ate a new new busine business ss activ activity ity in the the custo customer mer names namespace pace.. In Customizing for Master Data Governance, Central Governance , Governance , choose Mode Mo deli ling ng Ch Chan ange ge Re Requ ques ests ts Cre Create ate Bu Busin sines esss Ac Activ tivit ity y .

2.

Gene Ge nera rall Se Setti tting ngss

Proce Pro cess ss

Assign Assig n the new new business business activity activity to to a change change request request type for for single single objects. objects. In Customizing for Master Data Governance, Central Governance , Governance , choose Modeli Mode ling ng Ch Chan ange ge Req Reque uest stss Cr Crea eate te Cha Chang nge e Requ Reques estt Type Type .

4.4. 4. 4.3 3


Proce Pro cess ss

Conf Co nfig igur urat atio ion n of of the the Ch Chan ange ge Re Requ ques estt Pro Proce cess ss

When configuring the change request process you need to define the following: ●

Processing steps and their processors

●

Possible actions of processors

●

Process flow between steps

●

Change request status in each step

Additionally, you can use editions to schedule changes and you can define when the data replication should happen. For more information, see Using Editions to Schedule Changes [external Changes [external document] . You must configure the following elements: ●

Change Request Type

The change request type defines which data can be processed. The change request type is assigned to one MDG data model and lists the possible entity types that the change request can contain. SAP Business Workflow is used to process change requests in SAP Master Data Governance. To define the process proce ss flow of the change request you can use standard workflow templates or custom custom workflow templates when defining a change request type. For more information on SAP Business Workflow, see the Customizing activities under SA SAP P Ne NetW tWea eave verr Ap Appli plica cati tion on Se Serve rverr Bu Busin sines esss Ma Mana nage geme ment nt SA SAP P Bu Busi sine ness ss Wo Work rkflo flow w .

80



Alternatively, you can use the MDG rule-based workflow template when defining a change request type. In this case, the content of Business Rule Framework plus (BRFplus) [external (BRFplus) [external document] decision tables defines the process flow of the change request. For more information, see the Customizing activity Create Change Request Type under Type under Proce Pro cess ss Mode Modelin ling g Ch Chang ange e Reque Request stss . ●

General Settings

Change Request Step

Each change request process consists of a number of change request steps that can be either dialog steps or background steps. For each dialog change request step, you can do the following: ○

Assign processors

○

Configure validations and data enrichments

○

Assign UIs

The processing sequence of the steps is based on the processors' decision and other criteria that are evaluated by the workflow assigned to the change request type. If you are not using the rule-based workflow, the workflow template defines the available change request steps. Every change request type using this workflow template can only have the available steps. For more information, see Customizing activity Define Change Request Step Types and Assign Actions under Actions under General Sett Se ttin ings gs Pr Proc oces esss Mo Mode deli ling ng Wor orkf kflo low w . If you are using the rule-based workflow, the Customizing settings and the content of the BRFplus decision tables define the available steps. Every change request type using the rule-based workflow can have different change request steps although all change request types are using the same rule-based workflow template. For more information, see Customizing activity Define Change Request Steps for Rule-Based Workflow under Workflow under Gene Ge nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wo Work rkfl flow ow . ●

Change Request Step Type and Change Request Action

The change request step type defines the possible actions that a processor of a change request step can use. We deliver a number of change request step types, for example Approve example Approve Change Request with Request with the possible actions Approve actions Approve and and Reject Reject . . The change request step type of each change request step is determined at runtime. You can configure a change request step that allows the actions Approve actions Approve and and Reject Reject in in one case, while allowing Finalize Processing and Processing and Send for Revision in Revision in another case. For more information, see Customizing activity Define Change Request Step Types and Assign Actions Actions under under Gene Ge nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow . ●

Change Request Status

The change request status informs the user about the processing status and determines the possible changes to the change request and the contained data. We deliver a set of status control attributes: ○

no processing

○

objects can be added or removed

○

data changes are allowed

The following statuses that finalize the change request and stop further processing: Final Check Approved and Final Check Rejected . Rejected . In all other statuses, including any custom statuses, the change request is still open and interlocks the contained data to protect it from processing with other change requests. For more information, see Customizing activity Edit Statuses of Change Requests under Requests under Ge Gene nera rall Se Setti tting ngss Pr Proc oces esss Mode Mo delin ling g Ch Chan ange ge Re Requ ques ests ts . The change request status is set by the workflow. Either the task Set Status of Change Request is Request is used to set the status or, if the rule-based workflow is used, the decision tables are used. For more information, see Customizing activity Configure Workflow Tasks under Tasks under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow .



81

4.4. 4. 4.3. 3.11

Desi De sign gnin ing g the the Ch Chan ange ge Re Requ ques estt Pro Proce cess ss

For the design of the change request process and its configuration, it is useful to create a diagram that comprises all change request steps and their connections. The recommended process is as follows:

Process 1.

Start with Start with step step 00 and an appropr appropriat iate e descript description ion,, for example exampleRequest . Provide a name for the group of users that are allowed to create change requests of this type, for example Requester .

Figure 3: Change Request Step: 00/Request. Change Request Type: Requester

Note You control which users can create change requests of a certain type with the authorization object see Authorization Objects and Roles Used by USMD_CREQ . For further information on authorizations, see Authorization Master Data Governance [external Governance [external document] . Also, add a step 99 to represent the end of the process.

Figure 4: Change Request Step: 99/Complete

2.

Add a step for each each task that that a user needs needs to perform. perform. Assign Assign a step number number that is unique unique for the the process and choose an appropriate description. Name the group of users that shall perform the task. Select a step type in Customizing activity Define Change Request Step Types and Assign Actions Actions under under General Sett Se ttin ings gs Pr Proc oces esss Mod Mode eli ling ng Wor orkf kflo low w that fits to the task and includes the actions the processor should be able to choose. Add the step type and the possible actions as outcomes to the diagram like shown below.

Figure 5: Dialog Step 90/Approve: With Expert as Processor, Approve Change Request as Step Type, and Approve and Reject as Possible Actions

82



3.

Add a step for each each background background task. task. Assign Assign a step number number and a description. description. Add Add this information information togeth together er with the description of the background task to the diagram. Also, include all possible outcomes of the task on which you want to react in the process. Some important standard tasks of MDG to work with the change request are the following: ○

ACTIVATE CHANGE REQUEST (TS60808002)

○

DISCARD CHANGE REQUEST (TS75707936)

○

CHANGE REQUEST REPLICATION (TS60807976) (TS60807976)

Figure 6: Background Step 91/Activate: To Activate All Data of the Change Request with Task Activate Change Request and Two Outcomes to Handle Successful and Unsuccessful Completion of the Task

4. Connect Connect each step step with an arrow arrow that originates originates from from the respective respective outcome outcome of the the previous previous step and ends ends at the step that should follow. For each arrow, add the new status that the change request shall have, when the process proceeds from one step to the next.

Figure 7: If the expert chooses to approve the change request, the status shall be set to 02/Change 02/Changess to be Executed, and the system shall activate the change request.

More Information For more information, see Creating a Basic Change Request Process [page 93] and 93] and Add User-Agent Steps [page 96] for 96] for examples to configure the rule-based workflow.



83

4.4. 4. 4.3. 3.2 2

Conf Co nfig igur urat atio ion n of th the e Wo Work rkfl flow ow

SAP Business Workflow is used to process change requests in Master Data Governance (MDG). You have the option to use standard or custom workflow templates when defining a change request type. If you choose standard templates you can customize predefined change request process flows. If you choose custom templates you can create your own process with the workflow builder of SAP Business Workflow. Alternatively, you can use the MDG rule-based workflow, which is based on one generic workflow template. You can configure your particular change request process with BRFplus decision tables. Using the rule-based workflow you can add or remove a change request step or change the order of the steps without the need to change anything in the workflow template by adapting the BRFplus decision tables.

Prerequisites You have performed the basic workflow setup as described in the document Workflow Set-Up.

Activities Standard Workflow Template

1.

Choose Cho ose an approp appropriat riate e template template by examin examining ing its its document documentatio ation. n.

2.

Create the change change request request type and and enter the chosen chosen workflo workflow w template. template.

3.

Perform further Perform further configuration configuration according according to the requiremen requirements ts of the template, template, for example, assign assign processors processors to the change request steps.

Custom Workflow Template

1.

Crea Cr eate te th the e wor workf kflo low w tem templa plate te..

2.

Define the change change reques requestt steps steps in the MDG MDG Customiz Customizing. ing.

3.

Create the change change request request type and and enter your custom custom workflo workflow w template. template.

4. Perform Perform further further configuration configuration,, according to the the requirements requirements of the template, template, for example example assign processor processorss to the change request steps. Rule-based workflow

1.

Crea Cr eate te the the cha chang nge e requ reques estt type type..

2. Def Define ine chang change e request request steps steps in in MDG Custo Customiz mizing ing.. 3. Cr Crea eate te de decis cision ion ta table bles. s.

4.4.3.2.1

Workflow Set-Up

You use this process to define the mandatory Customizing settings that are needed to enable SAP Business Workflow for the change request process in Master Data Governance.

84



Prerequisites You have defined the necessary settings for SAP Business Workflow and defined the organizational plan in Customizing under SA SAP P Ne NetW tWea eave verr Ap Appl plic icati ation on Se Serv rver er Bu Busi sine ness ss Ma Mana nage geme ment nt SA SAP P Bu Busin sines esss Wo Work rkfl flow ow .

Process 1.

The workf The workflow low sys syste tem m user user (typi (typical cally ly WF-BATCH ) processes background tasks of MDG. Therefore, this user needs to have the required MDG authorizations. Assign the PFCG role SAP_MDG_WF_ADM to the workflow system user in transaction SU01 . For more information, see SAP Note 1650993

.

2. Create Create event event type type linkag linkages es for the the busine business ss object object BUS2250 (MDG Change Request) as described in Customizing activity Activate activity Activate Type Linkage under Linkage under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow . 3.

To assign assign processors processors to change change request request types and and change request request steps, steps, decide decide on the possible possible agents agents of the MDG workflow tasks in general. In Customizing activity Configure Workflow Tasks under Tasks under General Sett Se ttin ings gs Pr Proc oces esss Mo Mode deli ling ng Wor orkf kflo low w assign specific agents from your organizational plan to each dialog task. In the attributes pop-up of each dialog task, select to whom processors may forward a respective work item. Instead of assigning specific possible agents to a dialog task, you can also classify a dialog task as general task, so that a work item can be executed by any user. All users in the list of possible agents that are also assigned as processors of a change request step, are selected as the agents at runtime and will receive the work item. Make the settings for all dialog tasks of the application component CA-MDG-AF and the respective components of the MDG application that you use.

Note If you assign a processor to a change request step that is not assigned as possible agent, the workflow will end in an error at runtime unless you have classified the task as general task.

4.4.3.2.2

Rule-Based Workflow

Instead of building your own workflow template, you can use the MDG rule-based workflow. Using the rule-based workflow, you can configure any kind of change request process without the need to create and adapt a workflow template. You can define different change request processes in decision tables of the Business Rules Framework plus (BRFplus), which are maintained in Customizing for each change request type. At runtime, the current step, the user interactions, and other parameters in the decision tables determine the process flow of the change request. When you adapt the decision tables in BRFplus, you can add or remove a change request step or change the order of the steps without changes in the workflow template. The rule-based workflow uses BRFplus to determine the change request status, the next change request step, and expected agent(s). To make this information available, the system uses the current step, the last action, the priority of the change request, and, where appropriate, the reason of rejection as input parameters. You access the BRFplus application to determine how change requests are processed for a particular change change request type request type in Customizing activity Configure Rule-Based Workflow under Workflow under Ge Gene nera rall Se Sett ttin ings gs Pr Proc oces esss Mo Mode deli ling ng Ch Chan ange ge Requ Re ques ests ts Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wo Work rkfl flow ow . If you process this Customizing activity for a change request type for the first time the system generates a BRFplus application for each change request type. Each application contains functions, rule-sets, and decision tables. The content of the decision tables defines the change request process.



85

Three decision tables are available for each change request type: ●

Single Value Decision Table

The Single Value Decision Table DT_SINGLE_VAL_ defines the process flow between the change request steps. Based on the previous step, the action, and other parameters, this table returns the next step and other result parameters. The most important result parameter is the condition alias that links to the other decision tables. This decision table has the following condition columns: ○

CR Previous Step This parameter contains the previously processed change request step.

○

Previous Action This parameter contains the result of the previous system or previous user action.

○

Chng. Req. Priority This parameter contains the current priority of the change request.

○

Chng. Req. Reason This parameter contains the reason for this change request.

○

CR Rejection Reason This parameter contains the reason for rejection of this change request.

○

CR Parent Step and Step and Parallel Agt Grp No. These columns are used for parallel processing and are considered by the rule-based workflow to find the next step in the relevant subprocess. The system identifies the relevant subprocess by referring to the values in CR Parent Step and Step and Parallel Agt Grp No. . No. . For more information, see Parallel Processing [page 98] . 98] .

Based on the data from these condition columns, the system takes the actions and sets the statuses outlined in the result columns. This decision table has the following result columns: ○

Condition Alias The condition alias references the other decision tables. Each condition alias must be handled using at least one row in either the User Agent Decision Table or Table or the Non-User Agent Decision Table . Table .

○

New Chng. Req. Step This parameter parameter contains the next next step in the process.

○

New CR Status This parameter contains the new status for the change request.

○

Hours to Completion After the expected completion time in hours has passed, without any of the agents having processed the work item, the system automatically sends a notification.

○

Merge Type and Type and Merge Parameter In parallel processing, the merge type and the merge parameter define how the results of the subprocesses are merged back into the higher-level process. The system only supports the merge type B calling a BAdI method. The filter value for the BAdI is determined by the merge parameter. For more information, see Parallel Processing [page 98] . 98] .

○

Dyn Agt Sel Service The service name is used so select an implementation of BAdI: Dynamic Selection of Agent in Rule-Based Workflow in Workflow in MDG Customizing under Ge Gene nera rall Sett Settin ings gs Pr Proc oce ess Mod Model elin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Work Wo rkfl flow ow Bu Busin sines esss Ad Addd-In Inss . The implementation can overwrite various result values and determine the user agent groups. You can use this BadI, for example, to determine the processors at runtime based

86



on data in the change request. For more information, see the documentation of BAdI: Dynamic Selection of Agent in Rule-Based Workflow . Workflow . ●

User Agent Decision Table

The User Agent Decision Table DT_USER_AGT_GRP_ determines the processors of the change request step that was returned as the next step by the Single Value Decision Table . Table . It also determines the change request step type that defines the possible actions the processors can execute. This table has the following condition column: ○

Condition Alias The condition alias links the row in this table with corresponding rows in the Single Value Decision Table . Table .

This decision table has the following result columns: ○

User Agt Grp No. Enter an arbitrary value in the column User Agt Grp No. and No. and enter the processors in the column User Agent Value . Value . If you need more than one entry for User Agent Value to Value to define the processors, enter the same value for User Agent Group and Group and Condition Alias in Alias in each row to create one user agent group. You configure parallel processing of the change request step by entering different values for User Agent Grp No. and No. and the same condition alias. For each value in User Agent Grp No. , No. , a separate subprocess is started. For more information, see Parallel Processing [page 98] . 98] .

○

Step Type The step type defines the possible actions for the processor in the change request step.

○

User Agent Type and User Agent Value Identifies what kind of agent receives the work item in a change request. It can be a single user, an organizational unit, a role, a job, a position, or a special user. The user agent value defines the agents a work item can be sent to. It can be a user ID, or a user group ID. It can also point to rather than directly identify the user agent – for example, with user agent type SU (single user), user agent value LAST specifies the last processor and user agent value INIT specifies the requester of the change request.

●

Non-User Agent Decision Table

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

Condition Alias The condition alias links the row in this table with corresponding rows in the Single Value Decision Table . Table .

This decision table has the following result columns: ○

Agent Group Enter an arbitrary value in this column to execute the operation in column Process Pattern in Pattern in the background. If you are using parallel processing, create a row for each process pattern that should be executed in a separate subprocess. Choose a different value in this column for each row. For more information, see Parallel Processing [page 98] . 98] .

○

Process Pattern The Process Pattern controls Pattern controls the flow of the process and to define what the system shall perform in this change request step. Frequently used values are:



87

○

05 Activation (do not bypass snapshot)

Activates the change request, for example, after final approval. ○

08 Roll Back Change Request

Removes all inactive data, for example, after the change request was rejected. ○

99 Complete (Sub-)Workflow

Completes a workflow or a subworkflow. This process pattern is used, for example, in the last step to end the change request process. See Process Pattern [page 92] for 92] for a complete list of available process patterns. ○

Service Name The meaning of this parameter depends on the process pattern. For example, it contains the workflow template when creating a sub-workflow with process pattern 03 Call Sub-Workflow . Sub-Workflow .

More Information For information on how to create and enhance your rule-based workflow, see Creating a Basic Change Request Process [page 93] and 93] and Add User-Agent Steps [page 96] . 96] . Application specific information on rule-based workflow is available inRule-Based in Rule-Based Workflows for Material [page 101] . 101] .

4.4.3.2.2.1 4.4.3 .2.2.1 Conf Configuri iguring ng the Rule Rule-Base -Based d Workfl Workflow ow This document explains how to configure the rule-based workflow for a change request process that you have described using a process diagram as explained in Designing the Change Request Process [page 82] . 82] .

Prerequisites ●

You have completed the Customizing settings as described in Workflow Set-Up [page 84] . 84] .

●

You have created a diagram of the change request process that you want to configure as described in Designing the Change Request Process [page 82] . 82] .

Process ●

Enhance Process Diagram

Enhance the process diagram with further information required by the rule-based workflow. For each nonuser agent change request step, determine the appropriate Process Pattern [page 92] and 92] and add the information to the diagram.

88



Figure 8: To activate the change request, you need to use the process pattern 06/Activation.

For each arrow pointing pointing to a change request step, choose choose a 3 digit identifier for the condition alias. It is common to use abbreviations of the step’s meaning for better readability, for example APP for an approval step.

Figure 9: The arrow pointing to the change request step Activate is labeled with the condition alias ACT.

For information about an example of a process diagram that is enhanced for the rule-based workflow, see Add User-Agent Steps [page 96] . 96] . ●

Create Change Request Type

In Customizing activity Create Change Request Type under Type under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mo Mode deli ling ng Ch Chan ange ge Requests , create the change request type for which you want to define the process flow. Assign the rulebased workflow template WS60800086 to the change request type. ●

Define Change Request Steps



89

In Customizing activity Define Change Request Steps for Rule-Based Workflow under Workflow under General Settings Proc Pr oces esss Model Modelin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wor Workf kflo low w , define the process steps that are used in the process diagram of your change request type. ●

Service Names

In the case of a complex workflow scenario, for example, when using a handler to merge the results of parallel processing, you need to define service names for the BAdI implementations that you need to use. For more information, see the documentation documentation of Customizing activity Define Service Names for Rule-Based Workflow under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wo Work rkfl flow ow . ●

Build Decision Tables

Start Customizing activity Configure Rule-Based Workflow under Workflow under Ge Gene nera rall Settin Settings gs Pr Proc oces esss Model Modelin ing g Work Wo rkfl flow ow Ru Rule le-B -Bas ased ed Wor Workf kflo low w and enter your change request type to open the BRFplus workbench and to enter the values for the decision tables.

Note If you perform this activity the first time for this change request type, the BRFplus application is generated. Depending on the settings of the client, you are asked to assign a transport request and a software component. 1.

For each each arro arrow w in your your proce process ss diagr diagram, am, enter enter a row row in the theSingle Single Value Decision Table DT_SINGLE_VAL_ . Use the step numbers on each end of the arrow as the values for CR Previous Step and Step and New Chng. Req. Step . Step . The action code of the previous step that triggers this connection is the value for Previous Action . Action . The labels on the arrow provide the values for Condition Alias and New CR Status . Status .

Figure 10: The arrow of this diagram leads to the following values in the decision table: CR Previous Step = 90. New Chng. Req. Step. = 91. Previous Action = 03. Condition Alias = ACT. New CR Status = 02.

Note You can use the condition columns Chng. Req. Priority , Priority , Chng. Req. Reason , Reason , CR Rejection Reason , Reason , CR Parent Step , Step , and Parallel Agt Grp No. as No. as additional parameters to make the process flow more specific. You can enter a time limit for the processors of the next change request step in Hours to Completion . Completion . This uses the feature of the requested end deadline end deadline monitoring of the SAP Business Workflow. The rulebased workflow will send a notification to all processors of this change request step as a reminder to complete this task. The result columns Merge Type and Type and Merge Parameter are Parameter are used for parallel processing. For further information, see Parallel Processing [page 98] . 98] .

90



Instead of providing values for the result columns in the decision table, you can provide a service name in Dyn Agt Sel Service to Service to link to an implementation of BAdI: Dynamic Selection of Agent in Rule-Based Workflow . . For more information, see the documentation of BAdI: Dynamic Selection of Agent in RuleWorkflow Based Workflow in Workflow in MDG Customizing under Ge Gen ner eral al Se Sett ttin ings gs Pr Proc oce ess Mo Mode deli lin ng Wo Work rkfl flow ow Ru Rule le-Base Ba sed d Work Workfl flow ow Bu Busin sines esss Add-I Add-Ins ns . 2.

For each each user user agent agent step in your your process process diagram, diagram, enter enter a row row in the the User Agent Decision Table DT_USER_AGT_GRP_ . If you followed the recommendation in Designing the Change Request Process [page 82] to 82] to use the same condition alias for all arrows that point to a change request step, use this value for the column Condition Alias . Alias . If you use different aliases, you need to create multiple rows, one for each alias. Transfer the values for Step Type , Type , User Agent Type , Type , and User Agent Value from Value from the diagram into the table. The valid values for User Agent Type and Type and User Agent Value are Value are defined by your organizational structure (for example, see Customizing activity Edit Organizational Plan ) Plan ) and identify an organizational object, for example, the purchasing department. If you use SU for User Agent Type you Type you can use INIT (Initiator) as User Agent Value to Value to select the requester of the change request as processor. Furthermore, the value LAST for User Agent Value selects Value selects the processor of the previous step as the processor. If the overall group of processors for the change request step consists of multiple organizational objects, create a row for each object. In this case and unless you want to configure parallel processing of the change request step, use the same value for User Agt Grp No . No . for this condition alias. You configure parallel processing of the change request step by using different values for User Agt Grp No. for No. for the same condition alias. For further information, see Parallel Processing [page 98] . 98] .

Figure 11: The information from this diagram leads to the following values in the decision table: Condition Alias = APP. User Agt Grp No. = 001 (arbitrary value). Step Type = 02. User Agent Type = AG. User Agent Value = MD Experts (assuming there is a PFCG role named MD Experts and all users assigned to this role should be processors).

3.

For each each background background step step in your your process process diagram, enter a row in the theNon-User Non-User Agent Decision Table DT_NON_USER_AGT_GRP_ . If you followed the recommendation in Designing the Change Request Process [page 82] to 82] to use the same condition alias for all arrows that point to a change request step, use this value for the column Condition Alias . . If you use different aliases, you need to create multiple rows, one for each alias. Alias Transfer the value for Process Pattern from Pattern from the diagram into the table. If required by the chosen process pattern, specify the Service Name . Name . Unless you want to configure parallel processing in this change request step, choose any value for Agent for Agent Group , Group , for example 001 . For more information, see Parallel Processing [page 98] . 98] .



91

Figure 12: The information from this diagram leads to the following values in the decision table: Condition Alias = ACT. Process Pattern = 06. Service Name = . Agent Group = 001 (arbitrary value).

Caution The decision tables are processed in sequence Therefore, the table entries should be arranged starting with the most specific ones, followed by more general ones.

More Information For information about examples of process diagrams related to the rule-based workflow, see Creating a Basic Change Request Process [page 93] and 93] and Add User-Agent Steps [page 96] . 96] .

4.4.3.2. 4.4.3. 2.2. 2.2 2 Pr Proc oces ess s Patt Patte ern The rule-based workflow groups several workflow steps together to form basic operations that are called Process Patterns . . These patterns are used to control the flow of the change request process or to define which Patterns background task the system will perform in a change request step. Technically, the rule-based workflow runs in a loop. In each repetition of the loop, one out of several process patterns is executed. The workflow continues to run in this loop until the change request process is ended with the process pattern 99 Complete (Sub-)Workflow . (Sub-)Workflow . If the current change request step is a user-agent step, the used process pattern is 01 UI Dialog . Dialog . For non-user agent steps, the column Process Pattern in Pattern in the Non-User Agent Decision Table DT_NON_USER_AGT_GRP_ is used to determine the pattern. The possible process patterns are: ●

01 UI Dialog

This process pattern is used by the system for user-agent change request steps and should not be entered by you in the Non-User Agent Decision Table . Table . It is a special process pattern that is always automatically selected if a user agent has been found in the user agent decision table. This process pattern uses the dialog task Dialog Processing TS60807954 . ●

92

02 Call Synchronous Method



You can use this process pattern to include operations that are not provided from SAP. This process pattern uses the background task Synch. System Method TS60807949 . For more information, see BAdI: Calling of System Method for Rule-Based Workflow in Workflow in MDG Customizing under Ge Gene neral ral Se Sett tting ingss Pro Proce cess ss Mod Mo del elin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wor Workf kflo low w Bu Busi sine ness ss AddAdd-In Inss . ●

03 Call Sub-Workflow

You can use this process pattern to start a sub-workflow. The background task Subworkflow for Single Step Workflow TS60807994 starts a sub-workflow with the workflow template ID that is read from the column Service Name of Name of the non-user agent decision table. ●

04 Call Data Replication

You can use this process pattern to start the replication of the master data after the change request has been activated. This process pattern uses the background task Change Request Replication TS60807976 and the method DISTRIBUTE of the object type MDG Change Request BUS2250 to replicate the object using the data replication framework (DRF). ●

05 Activation (do not bypass snapshot)

You can use this process pattern to activate the data in the change request. This process pattern uses the background task Activate task Activate Change Request TS60808002 with the indicator IGNORE_SNAPSHOT_DIFF not set. The value of Previous Action is Action is updated with the result of the operation enabling you to handle error situations. If there have been conflicting changes to the data in the standard master data tables while the change request was in process the activation fails. In this case, Previous Action is Action is set to 33 Activation failed for Snapshot . Snapshot . If the activation was successful Previous Action is Action is set to 31 Activation Successful . Successful . In all other cases, Previous Action is Action is set to 32 Activation failed . failed . ●

06 Activation (bypass snapshot)

You can use this process pattern to activate the data in the change request, even if the data has been changed in the backend since the change request was created. The system ignores these potential changes and overwrites them. This process pattern uses the background task Activate task Activate Change Request TS60808002 with the indicator IGNORE_SNAPSHOT_DIFF set. ●

07 Validate Change Request

You can use this process pattern to validate the change request data. The results are written to the application log. The process pattern uses the background task Check Change Request TS75707952 . ●

08 Roll Back Change Request

You can use this process pattern to remove the inactive data of the change request from the staging area if the change request should not be activated. This process pattern also provides the information when and by whom the change request was released and sets the change request status to 06 Final Check Rejected . Rejected . The process pattern uses the background task Discard Change Request TS75707936 . ●

98 Error

You can use this process pattern to handle errors and exceptions. The process pattern uses the background task Error Handler TS60807951 . ●

99 Complete (Sub-)Workflow

You can use this process pattern to end the rule-based workflow instead of looping back.

4.4.3.2.2.3 4.4.3 .2.2.3 Creat Creating ing a Basic Basic Change Change Request Request Process Process This document describes how to enable a basic change request process using the MDG rule-based workflow. This basic change request process only activates the change request after it was submitted. The process does not



93

include any dialog step. To provide data governance capabilities, you need to enhance the process adding further change request steps such as approving the change request. The figure in this document shows a complete process.

Figure 13: Basic MDG Change Request Process

The process starts with step 00 when the requester submits the change request. The next step 91 is the activation of the change request. If the change request is successfully activated, its status is set to Final Check Approved and Approved and the process ends with step 99. If the activation fails, the change request is rolled back in step 92, the change request status is set to Final Check Rejected , Rejected , and the process ends.

Prerequisites You have created a change request type and you have entered the template for rule-based workflow WS60800086 in Customizing activity Create Change Request Type under Type under Ge Gene nera rall Se Setti tting ngss Pr Proc oces esss Mode Mo delin ling g Ch Chan ange ge Re Requ ques ests ts . In the following example configuration, the change request type CR_TYPE is used.

Process You need to perform the following steps in order to configure the rule-based workflow for the basic change request process: 1.

Create Cre ate nec necess essary ary chan change ge requ request est ste steps. ps. Define the change request steps 00, 91, 92, and 99 as shown in the figure in Customizing activity Define Change Request Steps for Rule-Based Workflow under Workflow under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow Rule-Based Workflow .

94



Table 38 Change Request Type

Change Request Step

Description of Change Request Step

CR_TYPE

00

Request

CR_TYPE

91

Activation

CR_TYPE

92

Roll Back

CR_TYPE

99

Complete

2. Def Defin ine e dec decis isio ion n ta table bles. s. For every change request type, there is a separate set of BRFplus decision tables that contain the configuration of the change request process. You can start the configuration of the rule-based workflow in Customizing activity Configure Rule-Based Workflow under Workflow under Gen Genera erall Set Setting tingss Pro Proces cesss Mod Modeli eling ng Work Wo rkfl flow ow Ru Rule le-B -Bas ased ed Wor Workf kflo low w . In the Single Value table Value table of change request type CR_TYPE , you define the sequence of the steps. If a column is not mentioned in the tables below it is not relevant for this process configuration. You have to add a row in the Single Value table Value table for each arrow in the figure to connect two change request steps and use the following information from the figure: ○

Previous Change Request Step

○

New Change Request Step

○

Change Request Status

○

Change Request Action

○

Condition Alias

The first row of the Single Value table Value table corresponds to the arrow from step 00 to step 91 in the figure: The column CR Previous Step contains Step contains 00 and the column New CR Step contains Step contains 91. Since the first change request step is the request step that produces no action result, the column CR Previous Action is Action is left empty. The column New CR Status contains Status contains 02 as the status of the change request in step 91. Finally, the column Condition Alias contains Alias contains the identifier ACT that you need to assign and that is used to connect this row with rows in the other decision tables. Single Value table Value table Table 39 CR Previous Step

CR Previous Action

Condition Alias

New CR Step

New CR Status

00

n.a.

ACT

91

02

91

31

END

99

05

91

31

RB

92

02

92

n.a.

END

99

06

The basic process contains only steps with background steps. Therefore, you only have to configure the Non User Agent table Agent table and the User Agent table Agent table is left empty. In the figure all arrows pointing to the same change request step have identical condition aliases. These condition aliases have been chosen to match the process pattern of this step. You have to add a row in the Non User Agent table Agent table for each change request step and use the following information from the figure: ○

Condition Alias

○

Process Pattern



95

Note The column Agent column Agent Group is Group is only relevant for parallel processing. Use the value 001 to create one work item for a change request step. If you look at the arrow with condition alias ACT from step 00 to step 91 with process pattern 05, the first row in the Non User Agent table Agent table contains the condition alias ACT , agent group 001 and process pattern 05. The following rows are needed in the Non User Agent table Agent table for the configuration of the complete basic process: Table 40 Condition Alias

Agent Group

Process Pattern

ACT

001

05

RB

001

08

END

001

99

After you have saved and activated the new entries for the Single Value table Value table and the Non User Agent table, Agent table, you can use the new change request type.

4.4.3.2.2.4 4.4.3 .2.2.4 Add UserUser-Agen Agentt Steps Steps This document describes how to enhance the basic change request process with a user agent step. In the basic process, a change request is immediately activated after the requester submits the change request without further involvement of another user. In this enhanced process, a second user checks the change request in an additional user-agent step. If this user decides to approve the change request, the activation is started with change request step 91. Otherwise, the roll back of the change request is started with change request step 92. The other change request steps are not changed.

Note The terms dialog step and step and user agent step are step are used as synonyms in MDG. To enhance the basic process from the document Creating a Basic Change Request Process [page 93] to 93] to the enhanced process described in this document, the new step 90 Final Check with Check with step type 2 Approve 2 Approve Change Request is Request is added. The user symbol next to the step type indicates that this is a user-agent step. The arrow from change request step 00 now points to the new change request step 90. The condition alias of this arrow was chosen as FC FC to to abbreviate Final Check . Check . The arrow, depicting that the user has accepted the change request with action 03, points to the change request step 91. The condition alias ACT for the change request step 91 is added to the arrow. The arrow, depicting that the user has rejected the change request with action 04, points to the change request step 92. The condition alias RB for the change request step 92 is added to the arrow.

96



Figure 14: Change Request Process Including a User Agent Step

Prerequisites You have configured the rule-based workflow for the basic change request process, as described in Creating a Basic Change Request Process [page 93] . 93] . In the following example process, the change request type CR_TYPE and the user FINAL_CHECK_USER are used.

Process You need to process the following steps in order to extend the basic workflow with a user step: 1.

Crea Cr eate te the the new cha chang nge e reque request st ste step. p. The new change request step for the user dialog is defined in Customizing activity Define Change Request Steps for Ruled-Based Workflow under Workflow under Ge Gene nera rall Se Sett ttin ings gs Pr Proc oces esss Mo Mode deli ling ng Wo Work rkfl flow ow Ru Rule ledd-Ba Base sed d Workflow . Workflow Step Numbers Table 41 Type of Chg. Request CR Step

Keys

Validation

Description

CR_TYPE

n.a.

n.a.

Final Check

90

2. Adap Adaptt and and add lin lines es to to decisi decision on table tables. s. Comparing the figure Change Request Process Including Dialog Tasks with Tasks with the figure Basic MDG Change Request Process of Process of the basic rule-based workflow you can see that you have to add new rows to the decision table and also change existing rows of the decision table, because the first arrow from change request step 00 to step 91 in figure Basic MDG Change Request Process has Process has changed. In the figure Change Request Process Including Dialog Tasks , Tasks , the arrow points to the new change request step 90. The Single Value table Value table row with the previous change request step 00 has changed to the following:



97

Table 42 CR Previous Step

CR Previous Action

Condition Alias

New CR Step

New CR Status

00

n.a.

FC

90

02

After this change, you have to add a new row to the Singe Value table Value table for every arrow that is depicted in the figure Change Request Process Including Dialog Tasks and Tasks and not depicted in the figure Basic MDG Change Request Process . Process . You have to add the following rows to configure the new sequence of steps: Table 43 CR Previous Step

CR Previous Action

Condition Alias

New CR Step

New CR Status

90

03

ACT

91

02

90

04

RB

92

02

In the basic rule-based workflow, only background tasks are used. In the enhanced workflow described in this document, a dialog task is used. In the User Agent table, Agent table, you have to configure the user agent group, the change request step type, the user agent and the user agent value for the new change request step 90. The following line with the condition alias FC for the new change request step is required: Table 44 Condition Alias

User Agt Group

Step Type

User Agent Type

User Agent Value

FC

001

02

US (User)

FINAL_CHECK_USER

4.4.3. 4.4 .3.2.2 2.2.5 .5 Par Parall allel el Pro Proces cessin sing g The rule-based workflow allows the parallel processing of a change request for processors belonging to more than one agent group. For example, you can define an approval step in which both one processor of the controlling department and one processor of the purchasing department need to approve the change request. Both groups of users will receive a work item for the processing of the change request at the same time and can complete their work independent of each other. Parent Step

The step from which parallel processing starts is called parent step. In contrast to regular change request steps, you assign multiple agent groups to a parent step. For each assigned agent group, a subprocess is started that is executed in parallel. The first step of each subprocess has the same step number as the parent step. Therefore, the step number of the parent step and the agent group number of the subprocess are additionally used to uniquely identify each step in subprocesses. The process that is started initially after the change request was submitted is called root process. Process Flow in Sub-Processes

Each subprocess is an instance of the rule-based workflow. Subprocesses provide the information of their parent step and the agent group for which they were started. This information is used during the evaluation of the single value decision table for determining the next change request step. Using these parameters in the single value decision table, you separate the configuration of the process flow in the initial process from the process flow in the subprocesses. Ending of SubProcesses

Subprocesses have to be ended by using a change request step with the process pattern 99 Complete (Sub-)Process . . (Sub-)Process

98



When all subprocesses have ended, processing continues in the parent step by evaluating the action results of the subprocesses. This is done by a result handler. For example, if any user of the two departments chooses to reject the change request in a subprocess that the overall result of the parent step rejects the change request. Result handlers are implementations of BAdI: Handling of Parallel Results in Rule-Based Workflow in Workflow in MDG Customizing under Ge Gene nera rall Se Sett ttin ings gs Pr Proc oces esss Mo Mode deli ling ng Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wo Work rkfl flow ow Bu Busi sine ness ss Ad Addd-In Inss and referenced by their service name. For more information, see the documentation of BAdI: Handling of Parallel Results in Rule-Based Workflow . Workflow . Using the actions and steps returned by the subprocesses, the result handler returns a merge step and merge action that are used in the next loop of the rule-based workflow to evaluate the single value decision table. You need to specify the result handler in the row of the single value decision table that leads to the parent step of the subprocesses. This is done by providing the value B in column Merge Type and Type and the service name of the result handler in column Merge Parameter . Parameter . Agent Groups

Agent groups are assigned to change request steps through the condition alias of the single value decision table. User agent groups are defined in the user agent decision table for dialog steps. Non-user agent groups are defined in the non-user agent decision table for background steps. Both types of groups are uniquely identified by their group number and the condition alias. User Agent Groups

A user agent group specifies the assigned processors of a change request step and the step type of the dialog step. All users assigned to a user agent group will receive a workitem to process the change request step. You can use multiple organizational objects to specify the members of the user agent group. In this case, you need to create a row for each organizational object in the user agent decision table and use the same value in the columns Condition Alias and Alias and User Agent Grp No. . No. . This defines a user agent group with multiple rows. You configure the parallel processing of a change request step by entering different values for User Agent Grp No. and the same condition alias. For each value in User Agent Grp No. , No. , a separate subprocess is started. It is not allowed to have rows with the same condition alias and the same user agent group, but different step type, because a change request step can only have one change request step type. However, it is possible to configure parallel steps that have different change request step types. Non-User Agent Groups

A non-user agent group specifies the process pattern that should be executed in the background in a change request step. A non-user agent group is defined by entering the condition alias, the agent group, and the process pattern in the non-user agent group decision table. You configure parallel processing of a change request step by entering different values for the agent group and the same condition alias. For each value in the agent group, a separate subprocess is started to execute the respective process pattern. It is not allowed to have more than one row with the same values for the condition alias and the agent group, because only one process pattern can be executed in each change request step. However, you can define parallel background steps, in which process patterns are executed in parallel. It is not allowed to have a row in the non-user agent decision table that has the same values for condition alias and agent group as a row on the user agent decision table, because a change request step can only be either a dialog or a background step. However, you can define two parallel steps, one as a dialog step and the other as a background step. Phases of Parallel Processing

The phases in which the rule-based workflow handles parallel processing are as follows: 1.

After having having evaluat evaluated ed the decision decision tables, tables, it is is checked checked whether whether there there is more than than one agent group group assigned to the change request step.



99

2.

For each agent agent group, group, a new instance instance of the rule-based rule-based workflow workflow is started. started. The The already determined determined agent agent group and the step number of the parent step are passed to the instance. In the parent step, the processing is suspended until every subprocess has ended.

3.

In the initial initial loop of the rule-bas rule-based ed workflow, workflow, the agent agent group is already already known known and processing processing can can directly directly continue by creating the workitem for the dialog step or executing the process pattern in case of a background step. After that, a new loop is started.

4. In the second second loop, the action action result result of the previous previous step, step, the informat information ion of the parent parent step, and and the agent agent group of this sub-process are used to find a matching row in the single value decision table and to find the assigned condition alias in the user agent decision tables and non-user Agent decision tables. 5. If a ste step p with with proc proces esss patt patter ern n 99 End (Sub-)Process is (Sub-)Process is found, the workflow ends and control returns to the parent step. If there are further steps defined for the subprocess they are processed in further loops of the subworkflow. 6. After all subproce subprocesses sses have have ended, the the result handler handler is called. called. It uses uses the action action results' results' return return and the change request step numbers' return by the subprocesses to determine a merge step and merge action. Both values are used in the next loop of the rule-based workflow to query the decision tables and processing continues until the root process is ended as well.

More Information Rule-Based Workflow: Technical Details [page 100]

4.4.3.2.2.6 4.4.3 .2.2.6 Rule Rule-Base -Based d Workflow: Workflow: Technical Technical Details Details This document explains how the rule-based workflow works by describing the workflow template of the rule-based workflow and how this workflow template of the rule-based workflow uses the BRFplus application of a particular change request type. We deliver the standard workflow template WS60800086 for the rule-based workflow. This workflow template consists of the following steps: 1.

Start Workflow

An instance of the rule-based workflow template is started when a user submits a change request of a type that has the rule-based workflow template assigned. The same workflow template is also used to create subworkflow instances for parallel processing. 2.

Determine Change Request Type

The system determines the change request type; for example, Create Material or Material or Change Material and Material and stores the change request type in the workflow container. 3.

Check Assignment of Processor to Workflow

The system checks whether a processor is already assigned to the workflow, for example, the current workflow instance is a sub-workflow that was started for parallel processing. If a processor is not yet assigned, the system launches BRFplus. The BRFplus decision tables for the change request type are used to find the next step, the process pattern, and the agents, based on the previous step and action. If the current workflow instance is the main workflow, the system also refreshes the status of the change request. 4. Determine Whether Single Processing or Parallel Processing is Configured

100



The system determines the number of configured agent groups of the current change request step. An agent group can consist of a single user or multiple users. For example, it might be necessary that users in the purchasing department and users in the accounting department should able to approve the change request in parallel. If more than one agent group is found, parallel processing is configured and the system proceeds as follows: 1.

The syst system em creates creates mult multiple iple work workflo flow w instan instances ces of the WS60800086 template: one for each agent group. These sub-workflows run in parallel.

2. As soon soon as as all subw subworkf orkflows lows are compl complete eted, d, the the BAdI: Handling of Parallel Results in Rule-Based Workflow in MDG Customizing under Ge Gene nera rall Set Setti ting ngss Pr Proc oces esss Mod Model elin ing g Wo Work rkfl flow ow Ru Rule le-B -Bas ased ed Wo Work rkfl flow ow Business Add-Ins is called in order to merge the results of the parallel subworkflows into one result and, based on those results, determines the next step of the change request process. 5.

Branch by Process Pattern

Based on the determined process pattern, the workflow branches into one out of several basic operations of the rule-based workflow. For more information, see Process Pattern [page 92] 6. Check Workflow Completion The system checks whether the process pattern was 99 Complete (Sub-)Workflow . (Sub-)Workflow . ○

If this is the case the system completes the workflow.

○

If this is not the case the system returns to step 3 and starts again.

4.4. 4. 4.3. 3.2. 2.3 3

BRF+ BR F+ De Deci cisi sion on Ta Tabl ble e Con Conte tent nt fo forr Mat Mater eria iall

You can use the Business Rule Framework plus (BRFplus) plus (BRFplus) tool to create your own rule-based workflows for material master data governance. The BRFplus BRFplus tool tool is accessed through the Customizing activity Configure RuleBased Workflows . Workflows . SAP delivers a number of preconfigured workflows that you can use for your governance process. You can adapt these preconfigured workflows or choose to create your own with the BRFplus tool. The following text outlines the fields and settings for the preconfigured workflow Create Material (Change Material (Change Request type MAT01 ). The other workflows use similar process patterns and steps and therefore are not explained here.

Structure Decision Tables The Create Material workflow Material workflow uses the following decision tables to direct the creation process: ●

Single Value Decision Table ( DT_SINGLE_VAL_MAT01 ) This is the master workflow table for material creation. This table lists the workflow steps and references the other two tables when necessary.

●

Non-User Agent Decision Table ( DT_NON_USER_AGT_GRP_MAT01 ) This decision table contains a list of system tasks. The tasks can be referenced by the DT_SINGLE_VAL_MAT01 decision table when it requires a system action.

●

User Agent Decision Table ( DT_USER_AGT_GRP_MAT01 )



101

This decision table contains a list of user assignments to workflow tasks. This information here is also referenced by the DT_SINGLE_VAL_MAT01 decision table when it requires user action.

Fields in Decision Table DT_SINGLE_VAL_MAT01 The table has two areas: the first area lists the expected start values leading into each step and the second area lists the actions to be taken if those values are set. The table below explains the fields: Table 45 Field

Field Type

Description

CR Previous Step

Start Value

This field links this line with a workflow step above it. The system takes the information from the New Chng. Req. Step field Step field below and searches for values matching that in the CR Previous Step fields of workflow steps below it.

Previous Action

Start Value

Contains the code for the system or user action if there was an action. The actions are maintained in customizing.

Chng. Req. Priority

Start Value

Contains the current priority of the change request

Chng. Req. Reason

Start Value

Contains the reason for the change request. The reasons are maintained in customizing.

CR Rejection Reason

Start Value

Contains the reason for rejection of a change request. The reasons for rejection are defined in customizing.

CR Parent Step

Start Value

Parent step number (Only used in parallel processing).

Parallel Agt Grp No.

Start Value

Parallel agent group number (Only used in parallel processing)

Condition Alias

Action

References the other two tables. An entry here specifies an action for the system or a user. Every Condition Alias needs to be handled at least once by either a User Agent or a Non-User Agent activity

New Chng. Req. Step

Action

Contains the next step in the workflow

New CR Status

Action

Displays the new status for the change request. The statuses are defined in customizing.

Hours to Completion

Action

Expected completion time in hours

Merge Type

Action

Parallel merge type (used in parallel processing)

102



Field

Field Type

Description

Merge Parameters

Action

Parallel merge parameter (used in parallel processing)

Dyn Agt Sel Service

Action

Dynamic agent selection service

Fields in Decision Table DT_NON_USER_AGT_GRP_MAT01 This table contains a list of system tasks that is referenced by the DT_SINGLE_VAL_MAT01 workflow table when one of the workflow steps requires a system action. The table defines the action to be taken by the system. For a list of the predefined values see Configuring Master Data Governance for Material [page 13] . 13] . Table 46 Field

Description

Condition Alias

This is a reference for the main workflow table. If this condition alias is set as a value in the

DT_SINGLE_VAL_MAT01 table then the system will read this line to see what actions are to be taken. Agent Group

User agent group number

Process Pattern

This line displays the background task the system performs. These tasks are preset and cannot be changed

Service Name

This is a filter for BAdI execution. The BAdI Rule-Based Workflow - Call System Method must Method must be implemented for process pattern 2 to work.

Fields in Decision Table DT_USER_AGT_GRP_MAT01 DT_USER_AGT_GRP_MAT01 This table contains a list of agents (usually users) that is referenced by the DT_SINGLE_VAL_MAT01 workflow table when one of the workflow steps requires user participation. For a list of the predefined values see Configuring Master Data Governance for Material [page 13] . 13] . You can use the following Configuration activities to define your own actions and step types: ●

Master Mast er Dat Data a Gove Govern rnan ance ce,, Cent Centra rall Gove Govern rnan ance ce Actions for Change Request UIs

Gene Ge nera rall Sett Settin ings gs

Proc Pr oces esss Mode Modeli ling ng

Work Wo rkfl flow ow

Defi De fine ne

●

Master Mast er Dat Data a Gove Govern rnan ance ce,, Cent Centra rall Gove Govern rnan ance ce Step Types and Assign Actions

Gene Ge nera rall Sett Settin ings gs

Proc Pr oces esss Mode Modeli ling ng

Work Wo rkfl flow ow

Defi De fine ne

Table 47 Field

Description

Condition Alias

This is a reference for the main workflow table. If this condition alias is set as a value in the

DT_SINGLE_VAL_MAT01 table then the system will read this line to see what actions are to be taken. User Agt Grp No.

Non-user agent group number

Step Type

Defines the user interface and buttons that appear for the user when they click on the workflow task they receive.



103

Field

Description

User Agent Type

Indicates the agent type, defining if it is a user, organizational unit, role, job, position, or special user.

User Agent Value

Defines the name of the agent to be sent this workflow task

Example Steps in the Create Material Rule-Based Workflow The following steps make up the pre-delivered rule-based workflow for creating a new material. The workflow involves two users, a business user who creates the change request, and a Master Data Steward who is tasked with reviewing and approving the change request. If a field is not mentioned in the tables below it is not relevant for the workflow step. The order of the steps below is not important as the order in which they occur is based on the field values. The intention of this workflow is to provide a simple workflow for change requests for material creation. The change request is sent for review, reviewed, then is either rejected, or is accepted and sent for a technical check. If the technical check is successful the material is created and the workflow ends, if the technical check is not successful then the change request is sent back for rework.

Change Request Step: The system puts the new change request into the worklist of the Master Data Steward. This is the first step in the create material workflow. The change request has been created and the step tells the system to place it in the worklist for the Master Data Steward. The settings in the user table determine the user interface to be displayed when opening the worklist item. The Master Data Steward has the choice to either approve or reject the change request. Table 48 Field

Field Value

Explanation of Field Value

CR Previous Step

00

This is the first step and no previous values exist.

Condition Alias

1

This value points to condition alias 1 from user table

DT_USER_AGT_GRP_MAT01 . This line tells the system to put the workflow task to the Master Data Steward. New Chng. Req. Step

90

This tells the system to check the lines with step 90 as the value for CR Previous Step next. Step next.

New CR Status

02

This sets the change request status to value 02: Changes to be Executed . Executed .

104



Change Request Step: The Master Data Steward opens the change request and activates it. The change request is sent for technical validation. This step is triggered when the Master Data Steward reviews the change request and approves it. The step tells the system to send the change request for technical validation where the data will be checked for validity and completeness. Table 49 Field

Field Value


CR Previous Step

90

Identifies this step and links it to the previous step.

Previous Action

9

Indicates that the user action was

Final Check Approved (The user chose the Activate the Activate button) button) and that the change request is to be activated. Condition Alias

2

Instructs the system to check the other workflow tables for condition alias 2. In this case the Master Data Steward choose the Activate the Activate button button and the workflow chooses the activation pattern.

New Chng. Req. Step

91

This tells the system to check the line with step 91 as the value for CR Previous Step next. Step next.

New CR Status

02

The status remains unchanged.

Change Request Step: The Master Data Steward opens the change request and rejects it. This step triggers the roll back for the change request and sends it back to the business user for revision. This step is triggered if the Master Data Steward chooses to reject the change request. The step instructs the system to roll back the change request and send the change request back to the business user for revision. Table 50 Field

Field Value


CR Previous Step

90


Previous Action

04

Indicates that the user previous action was Reject Reject (The (The Master Data Steward choose the Reject Reject button) button) and that the Master Data Steward sent the change request back to be revised.

Condition Alias

3

This value tells the system to refer to table DT_USER_AGT_GRP_MAT01 .

New Chng. Req. Step

95




105

Field

Field Value


New CR Status

10

This sets the change request status to value 10 value 10 : : To Revise: Perform Changes

Change Request Step: The activation was successful and the workflow is completed. This step is triggered following reviewer approval of the change request and a successful technical check. This step completes the workflow. Table 51 Field

Field Value


CR Previous Step

91

Identifies this step and links it to the previous step

Previous Action

31

The background action was

Activation Successful Condition Alias

4

This value tells the system to refer to table

DT_NON_USER_AGT_GRP_MAT01 . The task the value points to completes the workflow. New Chng. Req. Step

99

This field value indicates the end of the process.

New CR Status

05

This sets the change request status to value 5: Final Check Approved . Approved .

Change Request Step: The activation failed due to data errors. The change request is sent back to the Master Data Steward. This step is triggered following the Master Data Steward’s approval of the change request and a failed activation. The activation failed for technical reasons and the change request is sent back to the Master Data Steward to resolve the issues. Table 52 Field

Field Value


CR Previous Step

91

Identifies this step and links it to the previous step

Previous Action

< > 31

Indicates that the action was not

Activation Successful Condition Alias

5

This value tells the system to refer to table DT_USER_AGT_GRP_MAT01 . The change request is sent back to Master Data Steward to deal with the technical errors.

106



Field

Field Value


New Chng. Req. Step

90


New CR Status

11

Sets the status to value 11: Process Errors After Activation . Activation .

Change Request Step: The business user canceled the change request and triggered the roll back of the data and the completion of the workflow. This step is triggered if the Master Data Steward rejected the change request and the business user decided to cancel the change request rather than make updates to it. This step completes the workflow. Table 53 Field

Field Value


CR Previous Step

92


Previous Action

Blank

Condition Alias

6

This value tells the system to refer to table

DT_NON_USER_AGT_GRP_MAT01 . The task it points to completes the workflow. New Chng. Req. Step

99

This field value indicates the end of the process.

New CR Status

06

This sets the change request status to value 06: Final Check Rejected . Rejected .

Change Request Step: The business user opens the change request and chooses the Request button. The system performs a technical check of the change request. This step is triggered when the business user revises the change request and sends it again for approval. This step instructs the system to perform a technical check on the data contained within the change request. Table 54 Field

Field Value


CR Previous Step

95


Previous Action

07

Indicates that the user action was 07 Resubmit

Condition Alias

7

Instructs the system to check the other workflow tables for condition alias 7. This line tells the system to put the workflow task back to the Master Data Steward.



107

Field

Field Value


New Chng. Req. Step

90


New CR Status

02


Change Request Step: The business user reviews the change request and decides to cancel it. The Master Data Steward has sent back the change request for revision and the business user decides to cancel the change request rather than make changes to it. Table 55 Field

Field Value


CR Previous Step

95


Previous Action

08

Indicates that the user action was 08 Withdraw

Condition Alias

08

Instructs the system to check the other workflow tables for condition alias 8. In this case this is a system task to roll back the change request.

New Chng. Req. Step

92


New CR Status

02


More Information For more information on material workflows see the following guides: scn.sap.com/docs/ DOC-7858#jive_content_id_Material_Data

4.4. 4. 4.4 4

.

Scop Sc ope e fo forr Hi Hier erar arch chyy-Sp Spec ecif ific ic Ch Chan ange ges s

You can determine the extent to which users can make parallel changes to a hierarchy that belongs to a particular hierarchy type. A change to a hierarchy can comprise adding a node, moving a node, removing a node, changing the attributes of a node, or creating a hierarchy. After a change to a hierarchy is saved to a change request, changes to interlocked nodes must be saved to the same change request. The system determines which nodes are interlocked by referring to the Interlocking Interlocking setting setting in Customizing for the relevant hierarchy type. Hierarchy nodes that represent business objects are technically distinct from the business objects themselves. Interlocking affects the parallel processing of hierarchy nodes only.

108



The Interlocking Setting You can define the scope of interlocking in Customizing for Master Data Governance under Governance under Hierarc Hie rarchie hiess Def Define ine Sco Scope pe for Cha Change ngess

Process Modeling

The Interlocking Interlocking setting setting applies to a Hierarchy Type and Type and specifies which nodes besides the node being changed are interlocked while a hierarchy-specific change is in process. The setting is described in the table below: Table 56 Interlocking S Se etting

Interlocked Nodes

Loose

Nodes assigned to the parent node of the node being changed.

Strict

Interlocking propagates upwards and downwards from the parent node of the node being changed: ●

Upwards interlocking interlocks the parent node and

its assigned nodes, the parent node of the parent node and its assigned nodes, and so on up to the root node. ●

Downwards interlocking interlocks child nodes of the

parent node, their child nodes, and so on down to the end nodes. This comprises a subhierarchy of interlocked nodes with the parent node at its root.

When applying the Interlocking Interlocking setting, setting, be aware of the following: ●

Choosing the scope for hierarchy-specific changes involves striking a balance between centralized control and process efficiency.

●

The Interlocking setting also defines the locking of nodes to avoid competing changes by multiple users who work on the hierarchy at the same time.

Prerequisites To minimize business disruption, we recommend that you define the scope for changes to a hierarchy type when you define the hierarchy type within a data model. You can only change the scope for changes to a hierarchy type when no pending change requests exist for any hierarchy of this type. If you must change the scope after you have defined the hierarchy type and you must then transport your changes, ensure that no pending changes exist for the affected hierarchies in the target system.

Example The hierarchy called Global consists of continents, countries, cities, and teams. A change request to add Rome as a child node to Italy as the parent node is pending. No other hierarchy-relevant change requests are pending. If you want to change nodes that are specified as Interlocked Interlocked in in the figures and descriptions below, you must use the pending change request that assigns Rome to Italy. For changes to other nodes, you can use separate change requests.

Interlocking – Loose The figure below shows how the Interlocking Interlocking setting setting of Loose Loose affects affects a hierarchy in the scenario where Rome is added to Italy.



109

Figure 15: Interlocking – Loose

Loose interlocking affects all nodes that are assigned to the parent node of the node being changed . The node being changed is Rome and its parent node is Italy. Only the direct child nodes of Italy - Rome and Milan - are interlocked with the pending change request.

Interlocking – Strict The figure below shows how the Interlocking Interlocking setting setting of Strict Strict affects affects a hierarchy in the scenario where Rome is assigned to Italy in a pending change request.

110



Figure 16: Interlocking - Strict

Upwards Interlocking All nodes in the path from Italy to Global are interlocked. The child nodes of these nodes are also interlocked. Affected nodes include the following: ●

Italy (parent node), Rome and Milan (child nodes)

●

Europe (parent node of parent node), France and Italy (child nodes)

●

Global (root node), Asia and Europe (child nodes)

Downwards Interlocking All nodes in the subhierarchy below Italy are interlocked. Affected nodes include the following: ●

Cities Rome and Milan, which are below country Italy (Also covered by upwards interlocking)

●

Teams I and J, which are below city Rome

●

Teams K and L, which are below city Milan

●

Any other nodes that might be added in the future to any nodes descending from Italy

4.4. 4. 4.5 5

Navi Na viga gati tion on to th the e Use Userr Int Inter erfa face ce

In SAP Master Data Governance, you can navigate to user interfaces in the following ways: ●

Roles and Navigation [external Navigation [external document] You use menu nodes provided in SAP NetWeaver Business Client to directly navigate to an application. The menu is defined using a PFCG role.

●

Object-and-Action Based Navigation [page 112] You navigate in this way to display or start the processing of master data objects.



111

●

Change-Request Based Navigation [page 113] You navigate in this way to display a change request that contains one or more master data objects that are being processed.

4.4. 4. 4.5. 5.11

Obje Ob ject ct-a -and nd-A -Act ctio ion n Bas Based ed Na Navi viga gati tion on

You use object-and-action based navigation to display or to start the processing of master data objects. The typical navigation sequence for the user is as follows: 1.

Launch Lau nch the sea search rch appl applicat ication ion fro from m the the SAP NetWeaver Business Client (transaction Client (transaction NWBC ). To do this, you can choose an entry from the role menu, click a link from the service map, or click a link from the home page.

2. Se Sear arch ch fo forr an an obj objec ect. t. You search for a business object of interest and display the object in a new window. By clicking the link to display the business object, you initiate a logical action. Another possibility is choosing the New New button. button. In all cases, the system opens a new window with the target UI. 3. Pro Proces cesss the objec objectt in the the target target user user inter interfac face. e. Sometimes you can directly edit the object in the target user interface and sometimes you must choose the Edit button Edit button first. Choosing the Edit Edit button button triggers another logical action.

Features Navigation from NWBC to the Generic Search Application The Web Dynpro application Generic Search ( Search ( USMD_SEARCH ) is available in the menu. The USMD_SEARCH node of the menu can include the object-independent configuration USMD_SEARCH or an object-specific configuration. With the generic configuration, you can set default values for the data model and for the entity type, by specifying the following parameters in the menu node: ●

USMD_MODEL

●

USMD_ENTITY

The user can still override the defaults you set by selecting different options on the user interface. If you specify a Business Object Type with Type with the parameter USMD_OTC , users can no longer change the data model and the entity type. For more information on the required parameters, see Configuration of the Generic Search [external document] .

Navigation to the Target UI

Note In the following description, the Generic Search is Search is used as an example of the Current UI . UI . If you do not specify the USMD_OTC parameter for the USMD_SEARCH Web Dynpro application, the system derives an Business Object Type for Type for the data model and entity type based on Customizing. The relevant settings are as follows:

112



●

Governance (transaction MDGIMG ) under Activity: Customizing for Master Data Governance, Central Governance (transaction Gene Ge nera rall Sett Settin ings gs

●

Data Da ta Mo Mode deli ling ng

Edit Ed it Dat Data a Mod Model el

View: Business Object Type

When a user clicks a link to a business object, the system triggers logical action DISPLAY . Further logical actions are possible, for example CREATE . The availability of logical actions (defined in Customizing for Master Data Governance under Governance under Pr Proc oces esss Mode Modeli ling ng Bu Busi sine ness ss Act Activ iviti ities es De Defin fine e Logi Logica call Acti Action onss ) depends on the UI, the UI configuration, and the state of the chosen business object type. To determine the target user interface, the system considers the current user interface and its configuration, the logical action, and the Business Object Type of Type of the selected business object. Relevant settings are available in the following Customizing activities: ●

Governance (transaction MDGIMG ) Standard Definition: Customizing for Master Data Governance, Central Governance (transaction under Ge Gene neral ral Set Setti ting ngss Pr Proc oces esss Mode Modelin ling g Bus. Act.: Standard Definition

●

Busi Bu sine ness ss Act Activ iviti ities es

Link Lin k Log. Log. Actio Actions ns with with UI UI Applic Applicat atio ion n and

Custom Definition (Overrides Standard Definition): Customizing for Master Data Governance, Central Governance (transaction Governance (transaction MDGIMG ) under Ge Gene nera rall Se Sett ttin ings gs Pr Proc oces esss Mo Mode deli ling ng Bu Busi sine ness ss Ac Acti tivi viti ties es Li Link nk

Log. Actions with UI Application and Bus. Act.: Custom Definition

Navigation from Other Search Applications You can use other search applications than USMD_SEARCH . In particular, the initial page of the single-object processing UI USMD_OVP_GEN can provide an object-specific search. The logic for determining a target UI is the same for other search applications as it is for the generic search.

Navigation from the Initial Step of a Change Request If a logical action triggers the creation of a change request, the system gives precedence to the logic of the change-request-based navigation (see Change-Request Based Navigation [page 113] ) 113] ) over object-and-action based navigation for the initial change request step 00 . If you have defined a target UI for the change request step Governance under 00 , the system uses that UI. (Path: Customizing for Master Data Governance, Central Governance under Gene Ge neral ral Se Sett tting ingss Pro Proce cess ss Mo Mode delin ling g Ch Chan ange ge Re Requ ques ests ts Configure Properties of Change Request Step ). If you have not defined a target UI, the system uses the logic for object-and-action based navigation to determine a target UI.

Note If the current UI application is the generic single-object processing UI USMD_OVP_GEN and the same UI is also the target UI application, the system ignores the value of Configuration ID from ID from the view User Interface per Change Request Step . Step . Instead, USMD_OVP_GEN uses its current configuration for the initial change request step.

4.4. 4. 4.5. 5.2 2

Chan Ch ange ge-R -Req eque uest st Bas Based ed Nav Navig igat atio ion n

Change-request based navigation occurs when you start processing a change request. Navigation possibilities include the following: ●

Opening the relevant work item from the inbox.

●

Searching for and selecting a change request in My Change Requests . Requests .

●

Searching for a business object and clicking the Pending Change Requests icon. Requests icon.



113

Features Navigation Based on Change Request Steps The system selects a target user interface for the change request type and the current change step based on the User Interface per Change Request Step view Step view of the following activity in Customizing for Master Data Governance, Central Governance : Governance : Ge Gene neral ral Se Sett ttin ings gs Pr Proc oces esss Mod Model eling ing Ch Chan ange ge Re Requ ques ests ts Co Conf nfig igur ure e Pro Prope pert rtie iess of of Cha Chang nge e Request Step If a target UI is found, it is used.

Object-and-Action Based Navigation for Single-Object Change Requests If the system cannot identify a target UI for the current change request step and the indicator Single Object of Object of the change request request type is set (Customizing for Master Data Governance, Central Governance under Governance under General Settings Pro Proce cess ss Mod Model eling ing Ch Chang ange e Requ Reques ests ts Cr Crea eate te Cha Chang nge e Requ Reques estt Type Type ), the system uses object-andobject-andaction based navigation. The system performs the following actions: 1.

Determines Determi nes the busine business ss activit activity y for for the the change change reques requestt type. type. Governance under Path: Customizing for Master Data Governance, Central Governance under Mode Mo deli ling ng Ch Chan ange ge Re Requ ques ests ts Cre Create ate Ch Chan ange ge Re Requ ques estt Typ Type e


Proce Pro cess ss

2. Det Determi ermines nes the log logical ical act action ion and andBusiness Business Object Type based Type based on the business activity settings. Governance under Path: Customizing for Master Data Governance, Central Governance under Mode Mo deli ling ng Bu Busi sine ness ss Ac Activ tiviti ities es Cr Crea eate te Bu Busi sine ness ss Ac Acti tivit vity y 3.


Proce Pro cess ss

Determines the Determines the target target UI based based on the business business activi activity, ty, logical logical action, action, and and Business Object Type according Type according to the logic of object-and-action based navigation (See Object-and-Action Based Navigation [page 112] ) 112] )

Note If the system cannot determine a target UI based on the logic described above, the target UI is the obsolete single-object processing UI USMD_ENTITY_VALUE2 . In this case, the system determines the application configuration ID for USMD_ENTITY_VALUE2 in the Entity Types view Types view of the following activity in Customizing for Master Data Governance, Central Governance : Governance : Gen ene era rall Set Setti ting ngss Pro roce cess ss Mode Modelin ling g Ch Chang ange e Reque Request stss Create Change Request Type .

Multiple-Object Change Requests If the system cannot determine a target UI for the current change request step and the Single Object setting Object setting of the change request type is not applied (Path: Customizing for Master Data Governance, Central Governance under Governance under Gene Ge neral ral Se Sett tting ingss Pro Proce cess ss Mo Mode delin ling g Ch Chang ange e Re Requ ques ests ts Cr Crea eate te Ch Chan ange ge Re Requ ques estt Typ Type e ), the target UI is application USMD_CREQUEST_PROCESS .

4.4. 4. 4.6 6

Enab En abli ling ng Det Detai aile led d Anal Analys ysis is of of Chan Change ge Req Reque uest sts s

You can apply system settings that allow you to monitor in detail how effectively your organization processes change requests. You can analyze the statuses of change requests in your organization, the processing times of change requests in your organization, and the nature of change requests involving you. For more information, see Analysis of Change Requests [external Requests [external document] .

114



Procedure Enabling the detailed analysis of change requests involves completing the following tasks: 1.

Config Con figuri uring ng Oper Operati ationa onall Data Data Provis Provisioni ioning ng

2.

Activating Activa ting Busine Business ss Informati Information on (BI) (BI) Content Content in Maste Masterr Data Governa Governance nce

3. Sett Setting ing up the the busines businesss contex contextt viewer viewer 4. As Assi sign gnin ing g role roless to you yourr user user 5. Cha Changi nging ng aut author horizat ization ion obje objects cts 6. Int Integr egratin ating g SAP Busine BusinessO ssObjec bjects ts Dashbo Dashboards ards 7.

(Option (Op tional) al) Defin Defining ing a serv service ice-lev -level el agreem agreement ent

Configuring Operational Data Provisioning For more information, see Operational Data Provisioning [external Provisioning [external document] .

Activating BI Content in Master Data Governance You use Business Information (BI) content to analyze change requests. To activate the content, proceed as follows: 1.

Run Ru n tra tran nsa sact ctio ion n BSANLY_BI_ACTIVATION .

2.

Choo oosse the 0MDG_ANLY_CR_PROCESS content bundle.

3.

Optional Step: If you Optional you want to identify identify and fix fix the errors errors that would would occur if you activate activated d the content content bundle, bundle, choose the Simulate Activation button. Activation button.

4. To activ activate ate the the conte content nt bundl bundle, e, choos choose e the Activate the Activate button. button.

Setting Up the Business Context Viewer You must activate the business context viewer to be able to access side panels for the following Web Dynpro applications that are used in the analysis of change requests: ●

Processing Time (List View) (MDG_MONITOR_CR_PROCESTIME) .

●

My Change Requests (USMD_EDITION_CREQUEST)

You can refer to the following documents: ●

For instructions on how to activate the business context viewer, see Business Context Viewer in Single Processing [external Processing [external document] .

●

For more information about the business context viewer, see Business Context Viewer (BCV) [external (BCV) [external document] .

●

For more information about side panels, see Side Panel [external Panel [external document] .

You can only access the side panels after you change the authorization object Business Context Viewer Execute Side Panel ( BCV_SPANEL ). Instructions on how to do this are provided in the Changing Authorization Objects section Objects section of this document.

Note After you activate the business context viewer, you can configure a side panel for any Web Dynpro application.



115

Assigning Roles to Your User You need to assign roles to your user. For more information, see . Authorization . Authorization Concept in Business Context Viewer (BCV) [external (BCV) [external document]

Roles to Access Web Dynpro Applications Investigate if the role or roles you already have allow you to access the following Web Dynpro applications: Table 57 Web Dynpro Application

Description

MDG_MONITOR_CR_PROCESTIME

Used for the analysis of the status of change requests or the processing time of change requests. Used to display the reasons why change requests were

MDG_ANLY_CR_REJ_REASON

rejected. Used to display change requests involving you.

USMD_EDITION_CREQUEST

Note You can view and edit roles using transaction PFCG . The Menu Menu tabbed tabbed page shows Web Dynpro applications. Often, existing roles that use the required Web Dynpro applications have technical names with suffixes of *_MENU . If you do not have the required roles, consider the following options: ●

Assign the Master Data Governance: Analytics ( SAP_MDGA_MENU ) role to your user. This role only contains the relevant Web Dynpro applications.

●

Create your own role and add the Web Dynpro applications to that role. If you do this, you can control the placement of Web Dynpro applications on the menu in the user interface.

Changing Authorization Objects You must modify authorization objects to accomplish the following: ●

Specify the change request types to be analyzed and the level of access required

●

Specify the Web Dynpro applications requiring a side panel.

For every role associated with the relevant Web Dynpro applications, proceed as follows: 1.

Call Ca ll up tr tran ansa sact ctio ion n PFCG .

2.

Enter the name of the role and choose the

3.

Open the Authorizations Authorizations tab tab page and, in Maintain Authorization Data and Generate Profiles section, Profiles section, choose the

(Change Change)) icon.

(Change)) icon. (Change

4. Chang Change e the relevant relevant authori authorization zation objects objects as as shown in the followin following g table: Table 58 Authorization Object

SAP Master Data

Purpose

Parameter

Settings

Specify the types of change

Change Request Type

Specify the level of the

requests users are allowed

access allowed to each the

Change Request

to analyze and the level of

change request types

( USMD_CREQ )

access allowed.

specified under Activities under Activities . .

Gov over erna nanc nce e

Typ Ty pe of

As a minimum, choose

116



Authorization Object

Purpose

Parameter

Settings

Display . . Choose other Display options, if required. Activities

Specify which change request types can be accessed. You can use the * symbol as a wildcard for the entire technical name or for part of the technical name of the change request type.

Caution Be careful when using wildcards; you do not want to accidentally provide access to incorrect change request types. Business Context View Vi ewer er

Exec Ex ecut ute e Si Side de

Panel ( BCV_SPANEL )

Specify the Web Dynpro applications requiring a side panel.

Context Key

Enter the following context keys: ●

MDGAF_MYCR The application is the Application Framework ( MDGAF ) and the object is My Change Requests ( Requests ( MYCR ). Specifying this context key enables a side panel for the My Change Request screen.

●

MDGAF_ANLY The application is the Application Framework ( MDGAF ) and the object is ( ANLY ). Specifying this context key enables a side panel for the Status (Graphic View) screen, View) screen, which is used to analyze the status of change requests.



117

Authorization Object

Purpose

Parameter

Settings

Activity

Specify an activity of 16 , which allows you to execute the side panel.

RSXCLSID

Front End Integration

Authorization for working

Xcelsius Dashboard

with SAP BusinessObjects

of the dashboard:

( S_RS_XCLS )

Dashboards.

0XC_MDG_MONITOR_CR . Activities

Specify the technical name

Specify the level of the access allowed to dashboards. As a minimum, choose Display Display . . Choose other options, if required.

RSZOWNER

Specify the owner of the dashboard for a reporting comment. We recommend a value of “*” to provide universal ownership.

5.

Save the authorization profile and choose the

(Generate Authorization Profile) Profile) icon.

Integrating Dashboards For an overview of how to integrate dashboards, see Xcelsius see Xcelsius Enterprise Integration [external Integration [external document] SAP Business Objects dashboards only work if a BI Java server is enabled. For more information, see SAP Note 1450981

(Optional) (Optiona l) Defining Defining a Service-Level Agreement A change request is late if it exceeds its due date (an optional field of the change request) or if it violates a Service Level Agreement (SLA). You can define the SLA in Customizing for priorities of change request types. To define a service level agreement for each priority of a change request type, proceed as follows: 1.

In Cu Cust stom omiz izin ing g fo forr Master Data Governance, Central Governance , Governance , choose Mode Mo deli ling ng Ch Chan ange ge Re Requ ques ests ts Cre Create ate Ch Chan ange ge Re Requ ques estt Typ Type e


Proce Pro cess ss

2.

In the Type of Change Request view, Request view, choose a Change Request Type

3.

In the Service Level Agreement view, Agreement view, define a target number of days and hours for each Priority Priority . . When specifying hours, you can only specify 4 hours, which is a half day.

Result After completing this procedure, it is possible to access meaningful analytical information about change requests.

118



4 .5

Data Replication

You use this function to make the necessary settings for data replication within the Data Replication Framework (DRF). Data is replicated to business systems that are assigned to outbound implementations of replication models (see graphic below).

Figure 17: Replication Models, Outbound Implementation Implementations, s, and Business Systems

SAP supplies most of the objects and assignments as standard, such as the following: ●

Business objects

●

Filter objects

●

Outbound implementations

●

Service operations

Note You can view the objects and assignments that SAP supplies as standard in Customizing. More information is available in Customizing for Master Data Governance, Central Governance under Governance under Ge Gene nera rall Set Setti ting ngss Da Data ta Replication . However, you must configure your replication model. This involves the following: ●

Definition of replication model Define your replication model and enter a description.

●

Definition of the receiving systems of your replication model Enter one or more systems in which you want to replicate the data.

Caution When you transfer your Customizing settings to the production system, you must subsequently check and adjust the assignment of the replication model to the receiving systems. ●

Assignment of outbound implementations



119

You assign the desired outbound implementations to your replication model. The outbound implementation specifies how business object data is transferred to a replication model. This means, for example, which data is to be transferred and which communication channel is to be used.

Note The following communication channels are available for data replication purposes: ○

RFC

○

IDoc

○

Enterprise Services

○

File download

Ensure that you use only those communication channels that are supported by your replication model. One or more outbound implementations can be used for each replication model. This means that different data can be transferred in different ways for a certain replication model. This depends on the attributes of the outbound implementations that are assigned to the replication model. ●

Definition of additional parameters per outbound implementation You can define technical parameters for parallel processing or specify the number of business objects per bulk message, for example.

●

Assignment Assig nment of languages You can specify which languages the system is to take into account for language-dependent texts in the outbound implementation.

Activities You configure your replication model in Customizing for Master Data Governance, Central Governance under Governance under Gene Ge neral ral Set Settin tings gs Da Data ta Repl Replic icat atio ion n De Defi fine ne Cust Custom om Sett Setting ingss for Data Data Repl Replic icat atio ion n Co Conf nfigu igure re Repl Replic icati ation on Models . For further prerequisites for data replication, see Customizing for Master Data Governance, Central Governance under Ge Gene nera rall Set Settin tings gs Da Data ta Re Repl plic icat atio ion n Ov Over eral alll Inf Infor orma matio tion n .

4.6

Value Ma Mapping

You can use value mapping to map the code values for customizing elements that are represented in the system to the code values of a named external list. The external list can be a global code list or a system-specific code list.

Prerequisites ●

You understand the meaning of the code values in the various systems and have agreed mappings with business users.

●

You have determined whether to use a global code list or a system-specific code list. ○

120

We recommend you use a global code list if you are using Enterprise Service Oriented Architecture (ESOA) communications or if target systems support value mapping. PUBLIC © Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.


○

You must use a system-specific code list if you are using Application Link Enabling (ALE) communications or if target systems do not support value mapping.

SAP target systems in releases EHP4 and below and non-SAP target systems can only support value mapping with the help of SAP NetWeaver Process Integration (PI) tools or other middleware tools. When implementing value mapping, you have the following options: ●

Use of a Global Code List (see Prerequisites section) For more information, see Value Mapping: Use of Global Code Lists [page 121] . 121] .

●

Use of a System-Specific Code List (see Prerequisites section) For more information, see Value Mapping: Use of System-Specific Code Lists [page 123] . 123] .

4.6. 4. 6.11

Valu Va lue e Map Mappi ping ng:: Use Use of Gl Glob obal al Co Code de Li List sts s

You use this process to implement value mapping using global code lists. We recommend you use a global code list for inbound and outbound mapping to target systems if you are using enterprise service-oriented architecture (eSOA) communications or if target systems support value mapping.

Process The following steps describe value mapping for a selected value when you use a global code list. The selected value is the Company form of address. 1.

Outbound Processing on the MDG Hub

When the MDG hub sends a message that contains the Company form of address, the system converts the internal code defined for the MDG hub (0004) to the code defined for the message (0003). See graphic below.

Figure 18: Use of a Global List: – MDG Hub Configuration

The value mapping configuration information shown in the graphic is summarized in the table below.



121

Table 59 Values in the Message ●

Internal Values (MDG Hub)

Values come from one of the global code lists for the

data element is associated with the AD_TITLE

This code list has a list agency ID of MDG_GLOBAL

domain. ●

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

●

Values come from the AD_TITLE data element. This

Global Data Type (GDT) FormOfAddressCode . and a list version ID of 1 . ●

●

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

●

Values are mapped to the values described in the Values in the Message column.

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

2.

Inbound Processing on the Target System

When the target system receives a message that contains the Company form of address, the system converts the internal code defined for the MDG hub (0003) to the code defined for the message (0003). In this case, the values are the same. See graphic below.

Figure 19: Use of a Global List: – Target System Configuration

The value mapping configuration information shown in the graphic is summarized in the table below. Table 60 Values in the Message ●


Values come from the AD_TITLE data element. This data element is associated with the AD_TITLE


domain. ●

Values are mapped to the values described in the



●

●


Internal Values (Target System)

●


Internal Values (Target System) column.

122



4.6. 4. 6.2 2

Valu Va lue e Mapp Mappin ing: g: Use Use of of Syst System em-S -Spe peci cifi fic c Code Code Lis Lists ts

You use this process to implement value mapping using system-specific code lists. You must use a systemspecific code list if you are using Application Link Enabling (ALE) communications or if target systems do not support value mapping.

Process The following steps describe value mapping for a selected value when you use a system-specific code list. The selected value is the Company form of address. 1.

Outbound Processing on the MDG Hub

When the MDG hub sends a message that contains the Company form of address, the system converts the internal code defined for the MDG hub (0004) to the code defined for the message (0003). See graphic below.

Figure 20: Value Mapping: System-Specific Code Lists

The value mapping configuration information shown in the graphic is summarized in the table below. Table 61 Values in the Message ●


Values come from the AD_TITLE data element. This data element is associated with the AD_TITLE


domain. ●


●

●


Internal Values (MDG Hub)

Values are mapped to the values described in the


●


Internal Values (MDG Hub) column.

2.

Inbound Processing on the Target System

When the target system receives a message that contains the Company form of address, the system accepts the values as they are without doing any conversion.



123

4.6 .6..3

Define Value Mapping

The elements for possible value mapping are predelivered. If required, you can define value mapping for elements such as, UoM, industry sector, material type, and others in Customizing for Master Data Governance, Central Governance under Governance under Ge Gene nera rall Setti Setting ngss Va Valu lue e Mapp Mappin ing g . Material-specific key and value mapping Customizing activities can be found in Customizing for Master Data Governance, Central Governance under Governance under Master Data Governance for Material

4.7

Key Mapping

Customizing for key mapping under Ge Gene nera rall Set Settin tings gs Ke Key y Map Mappin ping g is recommended but not mandatory. You can use key mapping instantly, without doing any Customizing. The use cases for Customizing key mapping are as follows: ●

Changing Default Key Mapping Settings

●

Extending Key Mapping Settings for Existing Business Objects

Typically, you extend existing key mapping settings by adding new object IDs. ●

Extending Key Mapping Settings for New Business Objects

The Customizing activities you use to extend key mapping do not enable key mapping. After you define elements such as object IDs, you must implement them in code. You can refer to the code for existing key mapping entries to implement new key mapping entries.

4.7. 4. 7.11

Defi De fine ne Ke Key y Ma Mapp ppin ing g for for Ma Mate teri rial al Nu Numb mber ers s

If you are working with multiple connected systems and did not consolidate the material keys during the initial load phase, key mapping may be required. You can define the system-specific mappings for the key value of the supplier in Customizing for Master Data Governance, Central Governance under Governance under Ge Gene nera rall Set Settin tings gs Ke Key y Map Mappi ping ng . Material-specific key and value mapping Customizing activities can be found in Customizing for Master Data Governance, Central Governance under Master Data Governance for Material The mapping definitions of the key mappings are conducted by any authorized user using the business transaction from the portal or the corresponding back-end transaction. Customizing for Key Mapping

If you are working with multiple connected systems you may want to define or configure the key mapping between the MDG Hub and the client systems. Use the following steps to determine if the client system and hub system need to be key mapped or harmonized: 1.

Enter transaction DRFIMG and navigate to navigate to Business Systems .

Define Techn Technical ical Settin Settings gs

Define Techn Technical ical Settin Settings gs for

2. Sele Select ct a bus busine iness ss sys system tem and cho choose ose Define Bus. Systems. BOs . BOs . 3.

Select BO Type 194 . 194 .

4. Choose Define Bus. Systems. BOs, Communication Channel . Channel .

124



5.

In the Key Harm column, Harm column, check if the channel uses harmonized IDs or key mapping. If nothing is selected you may choose to set up key mapping if required.

Note Key and value mapping must be performed once for each connected system where data is being replicated from MDG Hub system.

4.7 4. 7.2

Def efiine Key Map appi pin ng fo for Oth Other er ID IDs s

The elements for key mapping are pre-delivered. If required, you can maintain key mapping for elements such as Plant , , Sales Organization , Plant Organization , and others in the Material Governance work Governance work center. To maintain the mapping in the Material Governance work Governance work center, in the Data Exchange section Exchange section open the Data Replication workset, Replication workset, and select Create and Edit Key Mapping . Mapping .

4.7. 4. 7.3 3

Cust Cu stom omiz izin ing g for for AL ALE E Aud Audit it (O (Opt ptio iona nal) l)

You can configure your client and hub systems so that your client systems send confirmation of replicated materials back to the MDG hub. Use the following steps to set up this confirmation process. In the client system make the following settings: 1.

Selec Sel ectt Di Dist stri ribu buti tion on Mo Mode dell 1.

Run Ru n tra tran nsa sact ctio ion n BD64 and choose Change/Display Change/Display . .

2.

Select the distri distribution bution model you created above and choose choose Add Message Type . Type .

3.

In the Add Message Type screen Type screen enter the following: ○

In the Sender Sender field, field, enter the logical system from which the acknowledgement is sent (The client system).

○

In the Receiver Receiver field, field, enter the logical system to which the acknowledgement is sent (The hub system).

○

ALEAUD . In the Message Type field, Type field, enter ALEAUD

4. Choose Ok Ok . . 2. Sel Selec ectt Pa Part rtne nerr Pr Prof ofile ile 1.

Run tra Run tran nsa sact ctio ion n SALE and choose Part Partner ner Prof Profiles iles Gen Genera erate te Partn Partner er Prof Profile iless . Alternatively, run transaction BD82 (Generate Partner Profiles).

2. Sele Select ct the the distr distribu ibution tion mode modell and in the thePartner Partner System field, System field, enter the hub logical system name. 3.

Enter the ALE-User ALE-User (the (the default value is ALEREMOTE ) and the following values. Table 62 Field

Value

Version

3

PackSize

100



125

Field

Value

Output Mode

Transfer IDoc Immediately


Trigger Immediately

4. Cli lic ck on on th the Execute Execute button. button. The log for partner profile generation appears showing the new sender and receiver systems 5. To verif verify y your your settin settings, gs, run run trans transact action ion WE20 and from the Partner Profiles menu, Profiles menu, choose Partner Type LS . . Verify that Partner type LS is LS LS is the logical destination system. 6. In the the detai detaill screen screen,, the the messag message e type, type, ALEAUD must appear. 7.

In the Inbound Options tab, Options tab, in the Process Code field Code field enter AUD2 .

8. Sele lec ct the Cancel Processing After Syntax Error checkbox. Error checkbox. 9. In the Processing by Function Module section, Module section, select the Trigger Immediately radio Immediately radio button. 10.. Ch 10 Choo oose se Save Save . . 11.. Run 11 Run tran transa sact ction ion BD64 . Select the model view and select Hub system and click OK OK . .

Ed i t

Model Vi View

Distribute . Select the

In the hub system make the following settings: 1.

Disstr Di trib ibu uti tion on Mod Model el Run Ru n tra trans nsac acti tion on BD64 and check that the same Distribution Model View with View with partner profile was created.

1.

2. Pa Part rtne nerr Pro Profi file le 1.

Run tra Run trans nsac acti tion on WE20 and check that the partner profile with logical name of the receiver system (Hub system) exists below the Partner Type LS folder. LS folder.

2.

Select Receiver Logical System (Hub System (Hub system) and choose Change Change . .

3.

Choose Create Outbound Parameter . Parameter .

4. In the Message Type field Type field enter ALEAUD . 5.

In the Outbound Options tab, Options tab, in Receiver Port field, Port field, enter the logical system name for the client from which the status information is to be received.

6. In the Output Mode list, Mode list, select Transfer IDoc Immediately . Immediately . 7.

In the Basic Type field Type field enter ALEAUD01 .

8. Sele lec ct the Cancel Processing After Syntax Error checkbox. Error checkbox. 9. Choose Save Save . . 3. Co Conf nfig igur ure e DRF DRF Cust Custom omiz izin ing g 1.

Run Ru n tra trans nsac acti tion on DRFIMG .

2.

Nav avig igat ate e to to Dat Data a Replic Replicatio ation n for Business Systems .

3.

Select the receiver receiver syste system m (Hub (Hub system) system) and double-c double-click lick on on Define Bus. Systems, BOs, Communication Channel . . Channel

Define Def ine Cust Custom om Sett Setting ingss for Data Data Replic Replicatio ation n

Define Def ine Tech Technic nical al Settin Settings gs

4. En Ente terr the the busi busine ness ss obje object ct type type 194 and choose OK OK . . 5. Se Sele lect ct th the e che check ckbo boxx Upd.KM Upd.KM . . 6. Choose Save Save . .

Note The inbound IDoc in the target system always accepts the material number sent in the IDoc, independent of the number range settings for the material type. Without additional coding it is not possible to force the target

126



systems to create new material numbers. You can do this coding in enhancement spot ES_SAPLMV02 in function module IDOC_INPUT_MATMAS01 .

4.8 4. 8

Gove Go vern rnan ance ce App Appli lica cati tion on Pr Prog ogra ramm mmin ing g Inte Interf rfac ace e

For greater flexibility you want to be able to develop new UIs that enhance your Master Data Governance applications and are consistent with the existing software. A number of developments in the Master Data Governance Application Framework (MDGAF) allow you greater freedom to build UIs for applications. ●

Governance API

●

Convenience API

●

Application Context API

●

Communicator

●

Change Request UI Building Block (CRUIBB)

The configuration of components is shown below:

Figure 21

All interactions between applications and MDGAF are now handled by either the Governance API or the Convenience API. It is not possible to use the Convenience API and the Governance API at the same time for the same model. This restriction is introduced to prevent misuse of the both APIs. Governance API

The Governance API covers the entire governance process, handling processes that are not UI-related, and background services such services such as master data load and data replication.



127

The Governance API is designed to handle multiple change requests simultaneously. At any time, one instance of the Governance API can exist in the system per data model. The Governance API also provides services to the convenience API. There is less grouping of functions than in the Convenience API so that you can combine a greater range of individual methods to meet the needs of the application. The Governance API also provides services for UI issues, but the applications access these services through the Convenience API, which then calls the Governance API. The Governance API Class ID is CL_USMD_GOV_API (IF_USMD_GOV_API) . Convenience API

The Convenience API provides the functionality needed for an application to work with a change request. It can handle one change request for a single data model at a given time. The Convenience API takes over all governance-relevant logic such as managing change request data, handling change requests, and routing change requests to the Governance API. The Convenience API groups together some of the methods of the Governance API ensuring tighter control of the change request-handling capability available to the applications, and simplifying the use of UI services for applications. The application manages only the application data. The Convenience API Class ID is CL_USMD_CONV_SOM_GOV_API (IF_USMD_CONV_SOM_GOV_API) . Application Context API

The Application Context API stores context-specific runtime information at a central point so that this information is accessible for other parts of the application and can be used to control the program-flow. Previously the system did not provide application context information such as what change request is being processed and whether the master data object is to be created or updated. The Application Context API provides a consistent, reliable solution to this problem. The following context information is available: ●

Data model

●

Business activity

●

Workflow information

●

○

Change request

○

Change request type

○

Change request step

○

Change request index (relevant for parallel processing)

○

Workflow item

Application parameter data (stored in the Workflow Container, not accessed by MDG)

The Application Context API offers the following advantages: ●

Allows existing UIs to access the application context without using the complete Governance API

●

Keeps existing interfaces stable

●

Increases flexibility. While, for example, the Governance API or Convenience API can only be instantiated for a data model, the Context API is directly available to MDGAF components such as a UI application or background process.

●

Manages application-specific context data Application-specific context data is stored within the workflow container. This enables you to provide application-specific context data throughout the workflow.

The Application Context API Class ID is CL_USMD_APP_CONTEXT . Communicator

The Communicator allows the user to work with the change request and ensures consistency of change request handling prerequisites, such as change request type, change request ID, and work item ID. When a user begins

128



working with a change request, the Communicator recognizes missing parameters and initiates user interaction accordingly, for example, requesting the user to specify a change request type if none has yet been specified. Change Request UI Building Block (CRUIBB)

This UI component is included in application-specific UIs and handles the presentation of change request data in Web Dynpro applications, ensuring a consistent UI layout for change request data across all applications. The CRUIBB contains data such as CR description, priority, reason for CR, notes, and attachments. Applications need to manage the application data only.



129

Typographic Conventions

Table 63 Example

Description

Angle brackets indicate that you replace these words or characters with appropriate entries

to make entries in the system, for example, “Enter your ”. Exam Ex ampl ple e

Exa Ex amp mple le

Arrows separating the parts of a navigation path, for example, menu options

Example

Emphasized words or expressions

Example

Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com

Textual cross-references to an internet address

/example

Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Example

Hyperlink to an SAP Note, for example, SAP Note 123456 ●

Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

Example

●

Cross-references to other documentation or published works

●

Output on the screen following a user action, for example, messages

●

Source code or syntax quoted directly from a program

●

File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE

Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE

130

Keys on the keyboard


Master Data Governance for Material Typographic Conventions



131

www.sap.com

© Copyright 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

MDG Config Mat 80 SP00

Recommend Documents