Config Mdg Co 70 01

SAP Library

Configuring Master Data Governance for Custom Objects 1

Configuring Master Data Governance for Custom Objects

PUBLIC

SAP Library


Copyright © Copyright 2013 SAP AG. All rights reserved. SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

SAP Library


Icons in Body Text Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles. EXAMPLE TEXT Technical names of system objects. These include report names, program

names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

SAP Library


Configuring Master Data Governance for Custom Objects

1. Data Model

The basis for the configuration of your custom master data governance process is a data model. This document describes how you can derive the required Master Data Governance (MDG) entity types [External] and relationships from an entity relationship model. The SAP Flight Data Model is used as an example. This example shows the basic steps in Customizing, which are a prerequisite for all subsequent steps, such as the UI configuration [External].

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

need to assign the values for the authorization field USMD_MODEL Data Model

(for example MM, BP, or 0G) and the values for the authorization activity

ACTVT Activity (for example 01:Create or generate, or 02: Change).

Instead of creating your own data model, you can also add entity types to the delivered MDG data models 0G, BP, or MM.

1. MDG Data Model: Details

This section describes the entity types and the relationship types used in the MDG Application Framework (MDGAF).

1. Entity Types

An MDG data model consists of the following entity types:

Entity Type with Storage and Use Type 1 (Type–1 Entity Type)

Storage and use type 1 must be used for entity types that can be processed in MDGAF. They have the following characteristics:

They represent root objects that are subject to governance.

More than one type–1 entity type is possible in one data model.

Data storage is generated (edition [External] dependent and staging area [External]).

SAP Library


They are used for modeling attributes and relationships.

They are processed in the first step of the change requests [External]

Non-assignment of data elements is optional.

Input help is linked to a generated check table.


Storage and use type 2 must be used for entity types that cannot be processed with MDG and which are not available in the system. They have the following characteristics:

They model lists of values and descriptions that can be uploaded.

They model key enhancements for type-1 and type-4 entity types.

Data storage is generated (no edition, no staging area).

No further modeling is possible (only check tables and text tables generated).

No processing in change requests is possible.

They require an assignment of a data element.

Check table values of data elements are ignored.

Input help is linked to a generated check table.


Storage and use type 3 must be used for entity types that should not be processed by MDG, but are available in the system. They have the following characteristics:

They model external entities used in the data model.

They model additional primary keys for the tables of type-1 and type-4 entity types.

No data storage is generated

No further modeling is possible.

No processing in MDG is possible at all.

They require an assignment of a data element.

Check tables and domain fixed values are used.

Input help is linked to a check text table and a domain fixed value of data elements; only key fields are processed in check tables.

SAP Library



Storage and use type 4 must be used for entity types that can be processed in MDG within the context of other entity types. They have the following characteristics:

They represent dependent nodes of objects to structure object data.

Entity type 4 must be processed on the UI together with required leading type-1 entity types.

Data storage is generated (edition dependent and staging area).

They model attributes and relationships.

No assignments of data elements are possible.

2. Relationship Types

An MDG data model consists of the following relationship types:

Leading Relationships

Type-1 entity type can lead type-1 entity types and type–4 entity types.

Type-4 entity types must be linked to a leading type-1 entity type.

A type-1 entity type can have a leading type-1 entity type [External].

Qualifying Relationships [External]

Entity types are qualified using additional key attributes.

Type-2 and type-3 entity types can enhance the keys of type-1 and type-4 entity types.

The key of an type-4 entity type must be enhanced by at least one type–1, type–2, or type–3 entity type.

Referencing Relationships [External]

The key of a referenced entity type becomes an attribute of the referencing entity type.

2. Example: Flight Customers

This example shows how a governance process for flight customers is defined. The SFLIGHT example defines three related database tables: SCUSTOM, SBUSPART and STRAVELAG. For more information, see Flight Model [External].

Although the tables in this data model use the SAP namespace, the steps and requirements necessary for bringing the tables under governance are the same as those used in the customer namespace. The names of your entity types must be in the customer namespace. In this example, the table SBUSPART represents entity type ZSBUSPART. Since the governance

SAP Library


process should be based on airline partners (table SBUSPART), ZSBUSPART shall be the entity type of storage and usage type 1. During this process, airline partners and travel agencies are created as well. Therefore, entity types need to be created. Since they are created only together with airline partners, these entity types need to have storage and usage type 4.

A key of the SCUSTOM table is the field ID. The field ID uses the check table SBUSPART. Therefore, ZSCUSTOM is defined as an entity type with storage and usage type 4 with a leading relationship to ZSBUSPART.

A key field of the table STRAVELAG is the field AGENCYNUM. The AGENCYNUM field uses the check table SBUSPART. Therefore, ZSTRAVLAG is defined as an entity type with storage and usage type 4 with a leading relationship to ZSBUSPART.

SCUSTOM : Flight Customers

Field Data Element

MANDT S_MANDT

ID S_CUSTOMER

NAME S_CUSTNAME

FORM S_FORM

STREET S_STREET

POSTBOX S_POSTBOX

POSTCODE POSTCODE

CITY CITY

COUNTRY S_COUNTRY

REGION S_REGION

TELEPHONE S_PHONENO

CUSTTYPE S_CUSTTYPE

DISCOUNT S_DISCOUNT

LANGU SPRAS

EMAIL S_EMAIL

WEBUSER S_WEBNAME

SBUSPART: Airline Partner

Field Data Element

MANDANT S_MANDT

BUSPARTNUM S_BUSPANUM

CONTACT S_CONTACT

CONTPHONO S_CPHONENO

SAP Library


BUSPATYP S_BUSPATYP

STRAVELAG: Travel Agency

Field Data Element

MANDT S_MANDT

AGENCYNUM S_AGNCYNUM

NAME S_AGNCYNAM

STREET S_STREET

POSTBOX S_POSTBOX

POSTCODE POSTCODE

CITY CITY

COUNTRY S_COUNTRY

REGION S_REGION

TELEPHONE S_PHONENO

URL S_URL

LANGU SPRAS

CURRENCY S_CURR_AG

Data Modeling

In this process, you create entity types for SBUSPART, SCUSTOM, and STRAVELAG, their attributes, and the relationships between the entity types.

3. Create Data Model

Define the data model in Customizing for Master Data Governance under

General Settings Data Modeling Edit Data Model .

Select the Data Models view, choose New Entries, and enter a new data model called YZ with the description Airline Business Partner.

4. Create Entity Types

Select the Entity Types view, choose New Entries, and make the following entries for the entity type ZSBUSPART :

Fields Entries Comment

Storage/Use Type

Changeable via Change Request; Generated Database Tables

Type-1 Entity Type

Validity of Entity No Edition n.a.

Data Element S_BUSPANUM Defines the key of the entity type and the field labels

Hierarchies No Hierarchies n.a

SAP Library


Validity/Hierarchy Hierarchy is Not Edition Dependent n.a.

Key Assignment Key Cannot Be Changed; No Internal Key Assignment

User needs to provide the key when creating new entities

Deletion Deletion Allowed n.a.

Description Airline Partner n.a.

Leave all other fields of the entity type blank, which is the default.

Create a new entry for the type-4 entity type ZSCUSTOM


Storage/Use Type

Changeable via Other Entity Type; Generated Database Tables

Type-4 Entity Type


Data Element <BLANK> Left blank for ZSCUSTOM as the key will be derived from the relationship to the leading entity type ZSBUSPART (see below)


Validity/Hierarchy Hierarchy is Not Edition Dependent

n.a.




Description Flight Customers n.a.

Create a new entry for the type-4 entity type ZSTRAVLAG


Storage/Use Type

Changeable via Other Entity Type; Generated Database Tables

Type-4 entity type


Data Element <BLANK> Left blank for ZSTRAVLAG as the key will be derived from the relationship to the leading entity type ZSBUSPART (see below).


Validity/Hierarchy Hierarchy is Not Edition Dependent

n.a.



SAP Library



Description Travel Agencies n.a.

If you save your data at this point, the check log shows various errors, which you can ignore at this time.

Enter the attributes of the entity types ZSBUSPART, ZSTRAVLAG, and ZSCUSTOM. Select the entity type you want to process and navigate to the Attributes view.

Choose New Entries and enter the following attributes and data elements for entity type ZSBUSPART:

Attribute Data Element

BUSPATYP S_BUSPATYP

CONTACT S_CONTACT

CONTPHONO S_CPHONENO

Leave all other fields of the attributes blank, which is the default.

Data in MDG is always client dependent. Therefore, the MANDT field is not modeled as an attribute.

Choose New Entries and enter the following attributes and data elements for the entity type ZSTRAVLAG:


CITY CITY

COUNTRY S_COUNTRY

CURRENCY S_CURR_AG

NAME S_AGNCYNAM

POSTBOX S_POSTBOX

POSTCODE POSTCODE

REGION S_REGION

STREET S_STREET

TELEPHONE S_PHONENO

URL S_URL

ZLANGU SPRAST

SAP Library


MDG uses the value table of the domain as defined in the data element of the attribute. This lets you perform checks and call up input help in the user interface.

In transaction SE11, you can see that the attribute LANGU with the data element SPRAS is used in the data dictionary (DDIC) table STRAVELAG. This cannot be reflected in the MDG data model. The attribute name LANGU cannot be used. Therefore, the name ZLANGU is used. The data element SPRAS cannot be used as well, but it can be replaced by SPRAST. The attribute names MANDT, SID, TXTLG, TXTMI, and TXTSH cannot be used as well.

Choose New Entries and enter the following attributes and data elements for the entity type ZSCUSTOM:


SCITY CITY

SCOUNTRY S_COUNTRY

SCUSTTYPE S_CUSTTYPE

SDISCOUNT S_DISCOUNT

SEMAIL S_EMAIL

SFORM S_FORM

SLANGU SPRAST

SPOSTBOX S_POSTBOX

SREGION S_REGION

SSTREET S_STREET

STELEPHON S_PHONENO

SWEBUSER S_WEBNAME

Attributes such as CITY can only be assigned once to a type-1 entity type. Therefore, you have to rename the attributes of entity type ZSCUSTOM. This is also true for indirect assignments that involve leading type-4 entity types. When renaming, insert an S as the prefix.

5. Create Relationships

Select the Relationships view, choose New Entries, and enter the following relationship details:

From-Entity Type Relationship To-Entity-Type Relationship Type Cardinality

ZSBUSPART BUSP2CUST ZSCUSTOM Leading 1:1

ZSBUSPART BUSP2TRAV ZSTRAVLAG Leading 1:1

Leave all other fields of the relationships blank, which is the default.

6. Save and Activate the Data Model

SAP Library


First, you need to save the data model. This will automatically perform a check. For the data in this example data the warning messages, which are related to change documents. Now activate the data model.

You can choose Visualize Data Model to display an overview.

2. UI Configuration

You need to create a UI configuration to display or change data as part of the change request process.

Start the UI configuration in Customizing for Master Data Governance under

General Settings UI Modeling Edit UI Configuration .

Choose Create to create a new UI configuration.

Rename the Target Configuration ID entries to YZ_MDG_APPL (for Application Configuration), YZ_MDG_IDR (for Identification Region), and YZ_MDG_OIF (for Object Instance Floorplan). Then choose Start Deep Copy.

If you want to transport the UI configuration, assign a package and a transport request, otherwise choose Local Object and OK. When the copy is finished, the system displays a message confirming the successful creation of the deep copy.

Select the target configuration ID YZ_MDG_APPL of the application configuration.

The UI configuration needs to be linked to the data model. Choose Change and go to the Application Parameter and enter the data model YZ in the field USMD_MODEL.

Save your entries and select the configuration name YZ_MDG_OIF in the section Assign Web Dynpro Component.

You create a simple UI layout that displays the three entity types ZSBUSPART, ZSTRAVLAG, and ZSCUSTOM on one screen.

If the section Navigation is not displayed, choose pushbutton Navigation.

In the section Navigation choose New Variant . For the variant ID select ZSBUSPART from the value help and choose OK.

The component configuration contains a dummy variant. This entry needs to be deleted.

Select the line VariantMust Be Deleted and choose the Delete pushbutton.

Select the variant ZSBUSPART

Not only the attributes of ZSBUSPART will be available in the UI configuration of this variant, but also the attributes of the entity types ZSTRAVLAG and ZSCUSTOM. This is because there is a 1:1 relationship to these entity types from ZSBUSPART.

Choose UIBB and select Form Component (GL1.1). The default values for Component and View appear. Provide a new configuration name.

Since the component configuration contains a default UIBB that you are not going to use, delete this UIBB. In the Hierarchy section, select other UIBB and choose Delete.

Choose Save and ignore the error message stating that the configuration ID does not yet exist. You are going to create this configuration ID in the next step. Select UIBB and choose Configure UIBB.

Choose New to create the new configuration ID. Provide a description for the configuration.

SAP Library


If you want to transport the component configuration, assign a package and a transport request, otherwise choose Local Object and OK.

In the next window, Edit Parameters, choose OK.

Choose Add Group.

Enter Airline Business Partner in the Text attribute of the group.

Choose Configure Group.

Drag the following fields from the Available Fields section to the Displayed Fields section so that they appear on the UI.

o BUSPATYP

o BUSPATYP_DESCRIPTION

o CONTACT

o CONTPHONO

Choose OK to display the added fields in the preview.

Select the description Business Partner ID Number and change the attribute Display Type to Text View.

Choose Save.

The UI configuration can now be used for the change request process.

In this example, we only created a very simple configuration with a small number of fields. For more information on UI configuration features, see Managing of UI Configurations [External].

Process

1. Process Modeling

1. Create Business Activity

Create a business activity in Customizing for Master Data Governance under

General Settings Process Modeling Change Requests Create

Business Activity .

Choose New Entries and enter the following:

Bus. Activity Description Data Model

YZBP Process Airline Business Partner YZ

Choose Save and create a transport request or select an existing transport request.

2. Create Change Request Type

Create a change request type in Customizing for Master Data Governance

under General Settings Process Modeling Change Requests Create

Change Request Type .

Choose New Entries and enter a new change request type as follows:

Type of Data Description Objects Single Main Entity Type

SAP Library


Change request

Model Required Object Workflow

YZBP01 YZ Process Airline Business Partner

No Yes ZSBUSPART WS75700040

Choose Entity Types and select New Entries. Enter entity type ZSBUSPART. Enter UI Configuration YZ_MDG_APPL. Choose Business Activities. Choose New Entries and enter YZBP.


3. Define Workflow

The standard workflow template WS75700040 will be used for the change

request process. This template provides workflow step numbers, which need

to be entered in Customizing for Master Data Governance under General

Settings Process Modeling Workflow Other MDG Workflows Define

Workflow Step Numbers .

In case the following entries do not exist already, choose New Entries and enter the following.

Workflow Step Number Description Keys Suc.Val.Req'd

WS75700040 1 Processing Yes No

WS75700040 2 Final Check No Yes

WS75700040 3 Revision No No


4. Setup of Organizational Structure

The system uses organizational structures to assign processors to the workflow steps of the change request. Create 2 positions and 1

organizational unit for this assignment. You can use transaction PPOMW to

create these structures and also to assign users to these structures. This configuration description assumes an organizational structure as follows:

Organizational Unit Position User

Flight Alliance Inc. (Code: FAI, ID: O 50001125)

Flight Application Process Expert (Code: FLAPPEXPERT, ID: S 50001127)

FLAPPEXPERT

Flight Operations Manager (Code: FLOPMAN, ID: S 50001128)

FLOPMAN

Organizational Unit: Flight Alliance Inc. (Code: FAI, ID: O 50001125) -- Position: Flight Application Process Expert (Code: FLAPPEXPERT, ID: S

SAP Library


50001127) ---- User: FLAPPEXPERT -- Position: Flight Operations Manager (Code: FLOPMAN, ID: S 50001128) ---- User: FLOPMAN

You use the column configuration to display the codes and IDs of the objects. You will need the IDs in the Assign Processors activity. The system will generate the IDs. These IDs will be different than the example data in your settings.

You can use the same user and assign it to each position. This enables you to use the change request process with a single logon. In order to demonstrate the segregation of tasks, we recommend that you use a dedicated user for each position, whereas one user, for example FLPRODMAN, is not assigned to a position and the users FLAPPEXPERT and FLOPMAN are assigned to positions.

5. Assign Processors

Assign processors to the workflow step numbers in Customizing for Master

Data Governance under General Settings Process Modeling Workflow

Other MDG Workflows Assign Processor to Workflow Step Number

(Simple Workflow) .

Choose New Entries and enter the following:

Type of Change request

Step Description Ob Agent ID Complete Name

YZBP01 1 Processing S 50001127 Flight Application Process Expert

YZBP01 2 Final Check S 50001128 Flight Operations Manager


You do not assign a processor to step number 3 (Revision), since the workflow template automatically determines the processor.

6. Create Role

In order to provide a menu and authorizations for the users, create a role using transaction PFCG.

Create a menu entry with the following settings:

Web Dypro Application USMD_ENTITY_SEARCH

Description Process Airline Business Partner

Parameter

Name Value

PROCESS YZBP

SAP Library


On the Authorizations tab, create a profile with the following authorizations:

Authorization Object USMD_CREQ (Type of Change Request)

Activity All Activities

Type of Change Request YZBP01

Authorization Object USMD_UI2 (UI Configuration)

Activity Execute

Configuration Identification YZ_MDG_APPL

Authorization Object USMD_MDAT (Master Data)

Activity All Activities

Data Model YZ

Assign this role to the users in the organizational structure of activity Setup of Organizational Structure.

In this example, we only add the search Web Dynpro application (WDA) of Master Data Governance (MDG) to the menu. For more information on other WDAs of MDG, see Master Data Processing [External].

1. Execute Process

After implementing all configuration settings, you can now execute this example process. For this process, you use the users you assigned to the organizational structures earlier.

1. Create Change Request

Log on with the user assigned to position Flight Product Manager. Choose Process Airline Business Partner. Search for airline partners to change one of these airline partners. Select an airline partner to change an existing airline partner and choose Change. To create a new airline partner choose Create and, on the next screen, enter an airline partner ID and choose Start.

Enter a description for the change request and provide the data for the attributes of the airline partner. Choose Submit to create the change request and send it to the next processor.

2. Process Change Request

Log on with the user assigned to position Flight Application Process Expert. Select SAP Business Workplace (transaction SBWP). Select Inbox to display your workflow items. Double-click the work item belonging to the change request you just created. Now you can review and change the data of the airline business partner. Choose Finalize Processing to send it to the next processor. Alternatively, choose Send for Revision to send it back to the requestor.

3. Approve Change Request

Log on with the user assigned to position Flight Operations Manager. Select SAP Business Workplace (transaction SBWP). Select Inbox to display your workflow items. Double-click the work item belonging to the change request. You can now finally approve or reject the change request. The final approval will activate the data.

SAP Library


Now, when you search for the updated airline business partner, the system lists the one that has been activated.

Configuring Data Replication

You can replicate master data stored within MDG as well as reference data, stored in configuration tables. The replication process is slightly different in each case.

MDG offers the following options to store active master data (data that has been approved):

The reuse option used by MDG-M and MDG-S stores data in the SAP ERP tables

such as MARA or LFA1.

The flex option used by MDG-F and MDG for Custom Objects stores data in generated tables.

In both options, inactive master data (data that has not yet been approved) is stored in the generated tables.

Data that the MDG system replicates to target systems is always active data. The MDG system takes the active data from the SAP ERP tables or from the generated tables depending on the option in use (reuse option or flex option).

MDG applications such as MDG-M, MDG-S, and MDG-F include standard implementations of the Data Replication Framework (DRF) that read the data and send the messages to the target system. The standard implementations support key mapping and value mapping.

About the Configuration of Reference Data

Reference data, which is stored in Customizing tables, is typically stable and available for use across an organization. Currency codes, for example, may be stored as reference data. You can model reference data in MDG data models, govern changes, and replicate changes.

Once configured, the replication process for reference data is as follows:

Replication from the MDG hub to Customizing tables in one or more target systems.

Creation and release of transport request in target system.

Prerequisites for Data Replication

At least one data model, with entity types, attributes, and relationships is defined using the flex model. The user interface, workflow, and processors are defined.

Prerequisites for the replication of Reference data are as follows:

1. The target system of replication is a development system.

2. The logged user for which replication is being done has the same ID in the source system and the target system.

3. If replication is scheduled to occur on activation of the change request as part of the workflow, the logged user is WF-BATCH. The logged user has the authorization for the RFC destination of the target system. To obtain this authorization, you can contact a system administrator.

4. After getting authorization for the RFC destination, you have run transaction SM59 and applied the following settings for the RFC destination of the target system for the logged user:

1. Under Logon & Security, you have selected Trust Relationship.

2. Logon & Security Logon Procedure , you have selected Current User.

SAP Library


Steps for Replicating Data

1. Define mapping contexts across clients for the Unified Key Mapping Service (UKMS).

o Path: Customizing for Key Mapping (transaction IDMIMG) underDefine a

Mapping Context for UKMSDefine Mapping Contexts.

o Instructions: Copy the default Main Context to a new table and give the new mapping context a prefix of Z. The system generates a set of tables based on the standard tables. The Z prefix indicates that the objects in those tables belong to the Customer namespace.

o Example: Copy table UKMDB_AGC00000 to ZUKMDB_AGCZZSF0.

2. Define the business object types to be replicated using outbound implementations and assign the defined business object types to a main context ID that is defined within the UKMS (Unified Key Mapping Service).

Business object types used in data replication are based on entity types with a storage and use type of 1 within data models.

1. Define business object types to be replicated.

Path: Customizing for Key Mapping (transaction IDMIMG) under Define

Business Objects

Example: Specify business object type ZZSF, which is for the customer

implementation of SFLIGHT (Flex).

2. Assign the business object types you defined to the mapping context for key mapping.

Path: Customizing for Key Mapping (transaction IDMIMG) under Enhance

Key Mapping ContentAssign Business Objects to the Main Context

Example: Assign business object type ZZSF to the main context (defined in

the previous step.)

3. If multiple object identifier types that already belong to the same business object type must belong to the same mapping group, define an object node type. Then assign the object node type to the object identifier types.

0. Define an object node type.

Path: Customizing for Data Replication (transaction DRFIMG) under

Enhance Default Settings for Outbound Implementation Define Business

Objects and Object Identifiers Define Business Object Nodes

1. Specify the object node type in the definitions of the object identifier types.

Path: Customizing for Key Mapping under Enhance Key Mapping Content

Define Object Identifiers.

Row for Business Partner Number

Business Object Type: 147

Business Object Node Type: 368

Business Object ID Type: 888

SAP Library


Constant Name for Business Object ID Type:

BPARTNER_UUID.

Row for Business Partner UUID

Same as above, except for the following:

Business Object ID Type: 889

Constant Name for Business Object ID Type:

BPARTNER_UUID.

1. Define business object identifier types so it is possible to differentiate an identifier of a business object from other identifiers of the same business object. Assign the business object identifiers types to the relevant business object types.

1. Create business object identifier types.


Key Mapping Context Define Object Identifiers

Example: Object ID Type = ZZSF; Description of Object ID Type = SFLIGHT

- Airline Code; BO Type = ZZSF; Ob ID Constant Name =

ZZSF_AIRLCODE; Object Node Type = ZZSF

2. Assign the business object identifier types to the definition of the business object types.


Key Mapping Context Define Business Objects

Example: Business Object Type = ZZSF; Description = SFLIGHT (Flex

Option); Constant Name = ZZSF_AIRLCODE; Object Identifier Type for Key

Structure Access = ZZSF

2. Create a package in preparation for the generation of data model-specific structures in the ABAP Dictionary. Generate the structures for each entity type that you want to replicate. Verify that the system generated the structures correctly.

1. Run transaction SE80 and create a package.

Example: Object Name = ZZ_DRF, Description = Custom Object SFLIGHT Data Replication

2. Generate the data model-specific structures.

Path: Customizing for Master Data Governance (transaction MDGIMG) under

Data Modeling Generate Data Model-Specific Structures

Example: Data Type = ZXX_S_ZZ_ZDRF_CARR, Where Used = DRF

Structures, Prefix / Namespace = ZXX, Name of Structure = ZDRF_CARR

3. Run transaction SE11 and check the structures for the generated data model-

specific structure. Whenever MDG generates structures, it activates them, so the word Active displays beside the structure name.

Example: Data Type = ZXX_S_ZZ_ZDRF_CARR

3. Assign a key structure to the object identifier types so the key mapping functions can break down concatenated keys into their constituent parts.

SAP Library


Path: Customizing for Data Replication (transaction DRFIMG) under Enhance

Default Settings for Outbound Implementation Define Business Objects and Object

Identifiers Assign Key Structures to Object Identifiers

Example: Business Object Type = ZZSF; Key Structure = ZXX_S_ZZ_ZDRF_CARR.

4. Assign an entity type within a data model to a business object type, generate the data model, and verify that the confirmation message returns no errors.

Path: Customizing for Master Data Governance (transaction MDGIMG) under

General Settings Data Modeling Edit Data Model In the Inactive Data Models view, select a data model. In the Entity Types view, select an entity type. In the Business Object Type view, enter the business object type for the entity type. Then generate the data model.

Example: In the Inactive Data Models view,: select CARR. In the Entity Types view,

select ZZ. In the Business Object Types view, enter the following details:Business

Object Type = ZZSF. Choose the Generate Data Model button.

5. Prepare for the creation of an outbound interface model by creating a package that contains a function group.

1. Run transaction SE80.

2. Create a package.

Example: Package = Z_ZZ_PACKAGE. Short Description = Package for

Outbound Implementation for ZFLIGHT (ZZ). Software Component

= HOME. Transport Layer = ZZNE. Package Type = Not a Main Package.

3. Create a function group for the package.

Example: Function Group = Z_ZZ_FUNC_GROUP. Short Text = Function Group for Outbound Sflight (ZZ)

6. Generate an outbound interface model that contains the entities and attributes from a data model that you want to replicate from the Master Data Governance hub to one or more target systems. This model also generates interfaces (RFCs and service interfaces) that can be used for such a data replication. After creating the outbound interface model, you can view the generated function module in transaction SE80.

Path: Transaction OIF_MAINTAIN or Customizing for Data Replication (transaction

DRFIMG) under Enhance Default Settings for Outbound Implementation Define

Outbound Interface Models

Example: Complete the following steps:

1. Wizard step: Enter Header Data.

Specify and describe an identifier for the interface model, an object type code, a package name, a name for the outbound interface model, and a description for the interface model. If you want to replicate reference data, so triggering the generation of a function module enabling the replication of such data, select the Configuration Data checkbox.

You can adjust the generated function module according to your needs, for example, in the case of reference data, you can omit the release of the transport request in order to enable data enrichment. The user can then release the transports manually.

SAP Library


Example

Select the CARR entity type and all of its attributes. Choose the Name ABAP

Dictionary Objects button. Enter the following details for the new structure:

Interface Model ID = ZZ_SFLIGHT

Interface Model Description = SFlight Outbound Model (ZZ)

Object Type Code = ZZSF

Package Name = Z_ZZ_FUNC_GROUP

Name = ZZ_SFLIGHT

Description = Generated RFC for SFlight Outbound Model (ZZ)

2. Wizard step: Select Entity Types and Attributes. Select entity types and attributes you want to include in the interface model. Then enter names for the resulting dictionary objects, by choosing the Name ABAP Dictionary Objects button.

Example: Select the CARR entity type and all of its attributes. Choose the

Name ABAP Dictionary Objects button. Enter the following details for the new structure:

Structure Name = ZZSF_S_CARR

Structure Description = Structure for CARR

Table Type Name = ZZSF_T_CARR

Table Type Description = ZZSF_T_CARR

3. Wizard Step: Review and Submit. Review and submit your work. Create a transport request or assign an existing transport request. You can use the same transport to transfer the function module to the target system later on.

4. Wizard Step: Check Application Log. Check the application log that displays after you review your submitted work..

5. Review the code of the function module. Run transaction SE80. Open the Repository Browser and browse by the Function Group you created earlier. Open the Function Modules folder, and review the system-generated function module for the outbound interface model.

The outbound implementation you define in the data replication framework calls this function module to replicate the data.

7. Create an outbound implementation to define how specific business object data is replicated. The creation of the outbound implementation involves specifying business object data to be transmitted, a class that retrieves and sends the data, and a communication channel.

When defining an outbound implementation, use the generic outbound

implementation class (CL_MDG_OIF_DRF_OUTBOUND_IMPL). You can copy this

class to allow additional capabilities that are not supported by default such as key mapping and value mapping. For more information, you can refer to the standard outbound implementations that SAP delivers for other objects.

SAP Library



Default Settings for Outbound Implementation Define Outbound Implementations .

Example:Outbound Implementation = ZZSF_01; Outbound Implementation Class =

CL_MDG_OIF_DRF_OUTBOUND_IMPL; Communication Channel = 4 Replication

via iDoc; Business Object Type = ZZSF; Outbound Interface Model ID =

ZZ_SFLIGHT.

8. Create a filter object to restrict the data can be selected and transferred to a target system during data replication through the use of filters. Define filters for the filter object.


Default Settings for Outbound Implementation Define Filter Objects .

1. Enter data in the Define Filter Objects

view and select the relevant row.

Example: Filter Object = ZZSF_FROOT; Description = Filter SFlight

(ZZ) - Root. Leave the Table Name field blank.

A complex filter such as the one in the example does not require a table name. The system only requires table names for simple filters. Such filters are only available for standard applications that are built using the reuse option.

2. Define the filters for the filter object in the Assign Filters subview.

If required, you can define your own structure to include all relevant fields from the generated table. In the Assign Filters view, apply the following settings.

3. For the Filter field, use codes between 80 and 99. This range is assigned to the customer namespace.

4. Specify a filter class. Example: Use the generic Filter Class

CL_MDG_OIF_DRF_FILTER.

9. Assign a filter object to a business object type (specific filtering) or to an outbound implementation.

o Assignment of a filter object to a business object type (specific filtering).

Path: Customizing for Data Replication (transaction MDGIMG) under

Enhance Default Settings for Outbound Implementations Define

Business Objects and Object Identifiers Assign Filter Objects to Business

Objects

o Assignment of a filter object to an outbound implementation:

Path: Customizing for Data Replication (transaction MDGIMG) under

Enhance Default Settings for Outbound Implementations Define

Outbound Implementations

Example: Business Object Type = ZZSF; Filter Object = ZZSF_FR00T;

Outbound Interface Model ID = ZZ_SFLIGHT

SAP Library


10. Create a filter to indicate precisely what data you want to replicate.

0. Run transaction DRFF.

1. Select the Business Object for which you want to define filter criteria.

Example: SFLIGHT (Flex Option).

2. Define a filter.

Example: Under Filter Criteria to Include Business Objects, choose Airline

local currency is EUR.

11. Create a replication model, assign the outbound implementation to the replication model, and assign the business systems that act as target systems for replication to the combination of the outbound implementation and the replication model. Each replication model specifies one or more outbound implementations.

0. Create a replication model.

Client-Specific Path: Customizing for Data Replication (transaction MDGIMG)

under Define Custom Settings for Outbound Implementations Define

Replication Models

Example:

In the Define Replication Model view, create a new entry with the following settings:

Replication Model = ZZSF; Description = Replication Model for

SFLIGHT; Log -Days: 15.

Select the new entry.

1. Assign an outbound implementation to the replication model.

Example: In the Assign Outbound Implementation view, apply the following

settings: Outbound Implementation = ZZSF_01; Communication Channel = 4

Replication via RFC; Replication via RFC; Filter Time = 2 Filter

After Change Analysis.

Select the assigned Outbound Implementation.

2. Assign the business system or business systems to which you want to replicate data using the combination of the replication model and the outbound implementation.

Example: Open the Assign Receiver Systems view, and enter the following

value: Business System = QV5_410

3. Activate the replication model.

Choose the Activate Replication Model pushbutton.

Additional Steps for the Replication of Reference Data

1. Generate an outbound interface model that contains the entities and attributes from a data model that you want to replicate from the Master Data Governance hub to one or more target systems. This model also generates interfaces (RFCs and service interfaces) that can be used for such a data replication. After creating the outbound

interface model, you can view the generated function module in transaction SE80.

SAP Library


Path: Transaction OIF_MAINTAIN or Customizing for Data Replication (transaction

DRFIMG) under Enhance Default Settings for Outbound Implementation Define

Outbound Interface Models

Example: Complete the wizard as follows:

1. Wizard step: Enter Header Data.

Specify and describe an identifier for the interface model, an object type code, a package name, a name for the outbound interface model, and a description for the interface model. To trigger the generation of a function module enabling the replication of such data, select the Configuration Data checkbox.

You can adjust the generated function module according to your needs, for example you can omit the release of the transport request in order to enable data enrichment. The user can then release the transports manually.

Example

Select the CARR entity type and all of its attributes. Choose the Name ABAP

Dictionary Objects button. Enter the following details for the new structure:

Interface Model ID = ZZ_SFLIGHT

Interface Model Description = SFlight Outbound Model (ZZ)

Object Type Code = ZZSF

Package Name = Z_ZZ_FUNC_GROUP

Name = ZZ_SFLIGHT

Description = Generated RFC for SFlight Outbound Model (ZZ)

2. Wizard step: Select Entity Types and Attributes. Select entity types and attributes you want to include in the interface model. Then enter names for the resulting dictionary objects, by choosing the Name ABAP Dictionary Objects button.

Example: Select the CARR entity type and all of its attributes. Choose the

Name ABAP Dictionary Objects pushbutton. Enter the following details for the new structure:

Structure Name = ZZSF_S_CARR

Structure Description = Structure for CARR

Table Type Name = ZZSF_T_CARR

Table Type Description = ZZSF_T_CARR

3. Wizard Step: Review and Submit. Review and submit your work. Create a transport request or assign an existing transport request. You can use the same transport to transfer the function module to the target system later on.

SAP Library


4. Wizard Step: Check Application Log. Check the application log that displays after you review your submitted work.

5. Review the code of the function module. Run transaction SE80. Open the

Repository Browser and browse by the Function Group you created earlier. Open the Function Modules folder, and review the system-generated function module for the outbound interface model.

The outbound implementation you define in the data replication framework calls this function module to replicate the data.

2. Create a mapping using the service mapping tool to map data from the staging area in the source system to the reuse table in the target system.

Ensure the following:

o The source structure is the data model-specific structure for the outbound interface model.

o The source structure uses the flex option and the target structure uses the reuse option.

Path: Customizing for Master Data Governance (transaction MDGIMG) under Data

Modeling Generate Data Model-Specific Structures

3. Maintain a mapping table to map the tables to the objects.

Run transaction SM30.

Example:

o Table Name: ZFX_S_ZT024E.

Specified when you created an outbound interface model.

o Object: V_T024E

The target business object stored in Customizing.

o Type: view.

o SMT_Mapping: ZF_PO_MAP.

Created previously in the Service Mapping Tool (SMT).

1 Master Data Governance for Custom Objects: Example Description

You can use this example to explore the main capabilities of SAP Master Data Governance. The scenario is based on the Flight Data Model demonstration and education content.

Prerequisites

You have activated the Master Data Governance, Generic Functions 7.0

(MDG_FOUNDATION_4) business function.

In order to enable the scenario, see Master Data Governance for Custom Objects: Example Configuration [Page 26].

SAP Library


Process

The business processes run as follows:

1. Process Airlines of the Flight Data Model.

2. Process Flight Connections of the Flight Data Model.

3. Analyze Change Request Process.

2 Master Data Governance for Custom Objects: Example Configuration Description

This description provides the information to setup the example scenario of Master Data Governance for Custom Objects. At the end you will be able to execute all processes of the example scenario as described in Master Data Governance for Custom Objects: Example Description [Page 25].

Prerequisites

You have activated the business function Master Data Governance, Generic Functions 7.0

(MDG_FOUNDATION_4).

Process

1. Setup of the Organizational Structure

The assignment of processors to the workflow steps of the change request is done by using organizational structures. This structure needs to be available before the activation of the BC-Set in one of the next steps. Create 2 positions, and 1 organizational unit for this assignment. The identification numbers are generated by the system and are different in each client. You can use transaction PPOC to create these structures and also to assign users to these structures.

This configuration description assumes an organizational structure as depicted below.

Organizational Unit: Flight Alliance Inc. (Code: FAI)

o Position: Flight Application Process Expert (Code: FLAPPEXPERT)

o User: FLAPPEXPERT

o Position: Flight Operations Manager (Code: FLOPMAN)

o User: FLOPMAN

You can display the codes and IDs of the objects by using the Column Configuration. You need the IDs when activating the BC-Set containing the change request types.

You can use the same user and assign it to each position. This will allow you to go through the change request process with one single logon and therefore be easier to use. However, in order to properly demonstrate the segregation of tasks, it is recommended to use a dedicated user for each of the positions.

SAP Library


2. Client Independent Configuration, Part 1 – Data Model

With transaction SCPR20 Business Configuration Sets: Activation you can activate the BC-Set CA-MDG-AF-FS_SFLIGHT_DATA_MDL_02. You can ignore warning messages that change documents are not available.

3. Client Independent Configuration, Part 2

In this step the configuration for business activities, settings for structure generation and the assignment of entity types to business object type codes are performed. Use transaction SCPR20 Business Configuration Sets: Activation and activate the set of BC-Sets CA-MDG-AF-FS_SFLIGHT_CROSS_02 to perform this. Skip the dialog that asks for a development package by not entering anything and ignore the related error message that this is not a valid development class.

4. Client Specific Configuration

This configuration will be done by activating a set of BC Sets as well. The BC Sets assume a configuration of priorities for change requests. Use the Customizing-activity

Define Priorities for Change Requests under General Settings Process Modeling

to check whether there are priorities 1 (High), 2 (Medium), and 3 (Low) defined. If this is not the case, these priorities have to be created before activating the BC Set. You can activate BC Set CA-MDG-AF-FS_SFLIGHT_CR_PRIOS for this.

Use transaction SCPR20 Business Configuration Sets: Activation and activate the set of BC-Sets CA-MDG-AF-FS_SFLIGHT_CLIENT_02. During the activation the system prompts you to enter the IDs of the organization structures you want to use for agent determination. The values that you need to enter depend on how you have set up the organizational structure in step 1. Using the example values from step 1, you would have to enter the following values:

o Agents: Flight Operations Manager — 50001128

o Agents: Flight Application Process Expert — 50001127

You can perform the activation of this BC Set in multiple clients to be able to execute the scenarios independent in each client.

In case the system raises errors during the activation of BC Sets that come from other configuration data (e.g. from change request types that are not contained in the BC Set), the activation fails. You first need to repair the error in the respective Customizing-activity.

o Assign the Role to Users

Assign the role SAP_MDGX_FND_SAMPLE_SF_04 (or a copy of it) to the users that should be able to execute the scenario. These are the same users that you assigned to the organizational structure in step 1.

Result

The users that you assigned to the organizational structure in step 1 are able to execute the Master Data Governance for Custom Objects Example .

SAP Library


You can execute the report SAPBC_DATA_GENERATOR to populate the Flight Data Model with example data, like airlines, airports, or cities. This example data will give you a better impression of the example.

3 Creating User Interfaces for Single Object Processing

For single object processing a Web Dynpro application is used that implements the overview page (OVP) of the Floorplan Manager (FPM). The user interface building blocks (UIBBs) of the OVP are used to display and enter the data of the business object during the processing of the change request. The generic application controller USMD_OVP_GEN interacts with these UIBBs and integrates the change request UIBB.

WebDynpro

F loorplanmanager

R

BOL

GeniL

R

R

BOL Feeder

R

Convenience API

Data Base

R

GUIBB

Buffer

Major Building Blocks for the UI Framework

User Interface

The UIs for MDG are based on ABAP Web Dynpro. They are built with FPM using the Business Object Layer (BOL)/generic interaction layer (genIL) technology. This technology offers the following characteristics:

Loose coupling of the UIs to the MDG specific processes

Flexible UI creation

The amount of fields to be displayed is split into small UIBBs. UIBBs support lists and forms as well as pop-ups, search input, and search results.

SAP Library


Possibility to create object-specific user interfaces to create a consistent layout and a similarity of the MDG user interfaces to the SAP GUI transactions

Reuse of the tables, structures and fields (including their names) generated by MDG during user interface creation

Generic Interaction Layer (genIL)

GenIL is required for the MDG UIs. It consists of a genIL data model and one or more genIL implementation classes for the data model. We provide the genIL data models for MDG and the implementation class CL_USMD_GENERIC_GENIL_ADAPTER. To view the data model call transaction GENIL_MODEL_BROWSER in the SAP backend.

A genIL data model consists of objects and relations with the following characteristics:

Objects consist of attributes. Each attribute reflects a usable field on the UI.

Relations connect one object to another. They also define the cardinality of objects in a relation. Relations are reflected on the UI by the wires (connections) from one UIBB to another. The UIBB hierarchy in the OVP must be consistent with the genIL object hierarchy as defined by the relations.

The genIL data models in MDG are dynamic. Any manual change to a genIL data model is strictly forbidden. The genIL data model is generated by its implementation class according to the runtime information of the MDG data model with the following characteristics:

Each entity type of storage and use type 1 of the data model is transferred to a genIL root object.

Each entity type of storage and use type 4 of the data model is transferred to a genIL dependent object.

Relations are determined and transferred into genIL relations.

For example, between entity types of storage and use type 1 and entity type of storage and use type 1 or between entity type of storage and use type 1 and entity type of storage and use type 4.

Each entity type of storage and use type 1 retrieves additional genIL queries and query result objects to support the search.

If an entity type of storage and use type 1 supports multi-lingual texts, a dependent object is created in genIL to enable the text processing within a table.

If an entity type of storage and use type 1 supports attachments, two dependent objects are created in genIL to enable attachment processing within a table and processing of related pop-ups.

The generated structures belonging to an entity are used for the genIL key and attribute structures. This ensures that all fields of the MDG data model are available for the creation of the related user interfaces. Attribute structures are used by FPM to build the field catalog that is available during user interface creation.

Enhancements of the MDG data model are reflected immediately after activation of the data model in the genIL component. A manual change or enhancement of the genIL component MDG is strictly forbidden. If enhancements in genIL are required, all changes have to be implemented in a related genIL implementation class. It is mandatory that this class inherits data from the SAP class CL_USMD_GENERIC_GENIL_ADAPTER.

Context-Based Adaptations

SAP Library


A context-based adaptation (CBA) is an FPM concept that allows you to change the UI in a flexible way based upon values (for example application parameters and user input). CBA consists of an adaptation schema made up of one or more adaptation dimensions as follows:

The predefined adaptation schema for MDG is USMD_GEN.

The adaptation schema includes the following adaptation dimensions:

o USMD_OTC: Usable for adaptations according to the current business object type code

o ACTION: Usable for adaptations according to the current logical action as, for example, Create or Mark for Deletion

o CRTYPE: Usable for adaptations according to the current change request type

o WFSTEP: Usable for adaptations according to the current workflow step

Using both the adaptation schema and its dimensions, you can create various adaptations of the UI (for example, a different layout of an OVP, or additional/removed row actions within a list UIBB). You can combine several dimensions to create a very specific adaptation. The CBA concept is based on the common FPM event handling. You can trigger one or more CBA events that are handled by the event loop processing from FPM.

FPM handles multiple CBA events one after the other. It does not cumulate the dimension information within each event, which means that the final CBA event is the valid event.

3.1 Creating Forms

You can use the MDG form feeder to create and edit forms. This document describes the MDG form feeder and its configuration for an entity type.

The Web Dynpro application for single object processing typically uses at least one form

GUIBB, for example FPM_FORM_UIBB_GL2, to display and process the data of a business

object.

MDG delivers the feeder class CL_MDG_BS_GUIBB_FORM for form GUIBBs.

The feeder class gets the attributes of the entity type for which the form can be configured. This way you can configure the layout of the form. During runtime it reads, writes, and checks the data of the entity that is currently being processed.

For information on assigning UI fields for each entity type, see the Generic Interaction Layer (genIL) section in Creating User Interfaces for Single Object Processing [Page 28].

Prerequisites

Before starting the configuration you need to set the default MDG data model in your user parameters. The form feeder uses the MDG data model to provide you with a list of the entity types that can be configured.

SAP Library


Process

Set the default data model as the data model for the UI as follows:

1. Run the transaction SPERS_MAINT.

2. Select Edit Objects.

3. Search for the entry SAP Master Data Governance - R_FMDM_MODEL in the displayed list. Double-click on the related line.

4. In the pop-up set the value of the field Standard Data Model to the data model that you want to use for the UI processing.

5. Confirm and save.

6. Then select Edit Parameters and make the settings for the following fields:

o Component

You can use the genIL component for the objects to be configured on the form. Always enter MDG in this field, which is the genIL component that has been generated automatically.

o Object Name

Enter an entity type for which you want the form to be configured.

o Editable

Select the Edit checkbox.

3.2 Creating Lists

You can use the MDG list feeder to create and edit lists. This document describes the MDG list feeder and its configuration for an entity type.

To process multiple entity types of storage and use type 4 in a table, a list GUIBB can be

used, for example FPM_LIST_UIBB_ATS. MDG delivers the feeder class

CL_MDG_BS_GUIBB_LIST for list GUIBBs.

The feeder class gets the attributes of the entity type for which the list shall be configured. This way you can configure the layout of the list. During runtime it reads, writes, and checks the data of the entity that is currently being processed.

For information on assigning UI fields for each entity type, see the Generic Interaction Layer (genIL) section in Creating User Interfaces for Single Object Processing [Page 28].

Prerequisites

Before starting the configuration you need to set the default MDG data model in your user parameters. The form feeder uses the MDG data model to provide you with a list of the entity types that can be configured.

Process



SAP Library






6. Then select Edit Parameters and make the settings for the following fields:

o Component

You can use the genIL component for the objects to be configured on the form. Always enter MDG in this field, which is the genIL component that has been generated automatically.

o Object Name

Enter an entity type for which you want the form to be configured.

o Editable


3.3 Creating Attachments

This document describes how to provide a UI for handling attachments of entities with the MDG Web Dynpro application USMD_OVP_GEN.

Entity types with storage and use type 1 can be configured in the MDG data model to store attachments. If the indicator Attachments is selected, you can store attachments (for example, Microsoft Word or Adobe PDF files) to entities that belong to this entity type. The system automatically provides a data store for this. The existing attachments can be displayed on the UI in a list and new attachments can be created with a dialog box.

Attachments are included in the example configuration USMD_SF_OVP_CARR of the generic

MDG Web Dynpro application USMD_OVP_GEN in package

MDG_FND_SAMPLE_IMPLEMENTATIONS.

Prerequisites

Before starting the configuration make sure you have processed the following steps:

1. There is an entity type with indicator Attachments selected.

2. You need to set the default MDG data model in your user parameters.





SAP Library




3. There is a configuration of the generic MDG Web Dynpro application USMD_OVP_GEN

that includes a configuration of the FPM overview page FPM_OVP_COMPONENT to

which you can add the attachment list. You can open and edit the configuration of this page in the FPM editor. Alternatively, you can create Customizing for this configuration. For more information, see Configuration Editor for Floor Plan Manager [External].

Process

Attachment List

The following numbered list describes how to add the attachment list to the UI.

1. Create a new configuration for the list component FPM_LIST_UIBB_ATS by copying

the template USMD_SF_CARR_ATTACHMENT_LIST from package


2. In the configuration of the list component enter the following values for the parameters of the feeder class CL_USMD_ATTACHMENT_LIST:

o Component

Always enter MDG in this field. This is the generic GenIL component for MDG and provides access to the entity types defined in the MDG data model.

o Object Name:

Enter AtthEntity Type in this field. Replace Entity Type with the name of the entity type for which you want to configure attachments. Atth stands for attachment header.

o Editable


3. Add the list component to the FPM OVP on which the entity attachments should be displayed.

4. In the wiring of the page, create a wire for the attachment list using the connector

class CL_MDG_BS_CONNECTOR_BOL_REL and the following parameters:

o Source Component/Source Config Name

o Port Type/Port Identifier: Lead Selection/Standard

The component displays the entity for which the attachment list should be shown. This could be a form component on the page, for example.

When you have entered the source component and port, the parameter for Relation Name should be automatically set to ENTITY_TYPE2AtthENTITY_TYPERel.

5. In the toolbar schema of the FPM OVP, add the following buttons for the attachment list UIBB:

Text Image Source Tooltip FPM Event ID

Edit ~Icon/Edit Edit FPM_LOCAL_EDIT

SAP Library


Delete ~Icon/Delete Delete Attachment ATT_DELETE

File ~Icon/AddFile Add File ATT_FILE_ADD

Link ~Icon/AddLink Add Link ATT_LINK_ADD

Dialog Boxes to Add File Attachments

The following numbered list describes how to add a dialog box to the page so that attachments of type file can be added.

1. Create a new configuration for the form component FPM_FORM_UIBB_GL2 by

copying the template USMD_SF_CARR_ATT_FILE from package


2. In the configuration of the form component enter the following values for the

parameters of the feeder class CL_USMD_ENTITY_ATTACHMENT:

o Component


o Object Name:

Enter AttcEntity Type in this field. Replace Entity Type with the name of the entity type for which you want to configure attachments. Attc stands for attachment content.

o Editable


3. Add a dialog box to the FPM OVP on which the entity attachments should be displayed with page ID USMD_ENTITY_ATT_FILE and description Add File.

4. For the attributes of the dialog box, enter the following values: Button Sets: OK and Cancel (OK is default button) Width: 400 (choose a value that suits your page layout)

o Button Sets

OK (default value) and Cancel

o Width

400 (choose a value that suits your page layout)

5. Add the form component created in step 1 to the dialog box.

Dialog Boxes to Add Link Attachments

The following numbered list describes how to add a dialog box to the page so that attachments of type link can be added.

1. Create a new configuration for the form component FPM_FORM_UIBB_GL2 by

copying the template USMD_SF_CARR_ATT_LINK from package


2. In the configuration of the form component enter the following values for the parameters of the feeder class CL_USMD_ENTITY_ATT_LINK:

o Component

SAP Library



o Object Name:

Enter AtthEntity Type in this field. Replace Entity Type with the name of the entity type for which you want to configure attachments. Atth stands for attachment header.

o Editable


3. Add a dialog box to the FPM OVP on which the entity attachments should be displayed with page ID USMD_ENTITY_ATT_LINK and description Add Link.

4. For the attributes of the dialog box, enter the following values: Button Sets: OK and Cancel (OK is default button) Width: 400 (choose a value that suits your page layout)

o Button Sets

OK (default value) and Cancel

o Width

400 (choose a value that suits your page layout)

5. Add the form component created in step 1 to the dialog box.

4 Data Quality Remediation Configuration Guide

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 installed a data quality tool in your system landscape.

2. You have installed a data quality connector in the MDG system. The data quality connector consists of an ABAP class that implements the interface IF_MDG_DQR_DQ_SERVICE and, optionally, an implementation of the BAdI Event Handling for Data Quality Remediation. For more information, see the documentation

of this BAdI under General Settings Data Quality and Search Business Add-Ins

.

Process

Configuration Process

1. You need to execute the Customizing activity Define Data Quality Service. For more

information, see the documentation of this customizing activity under General

Settings Data Quality and Search Data Quality Remediation .

2. Copy the Floor Plan Manager (FPM) Configuration Templates

1. In the package MDG_DQR_GENERAL select Web Dynpro Application configuration MDG_DQR_OVP and choose Start Configurator.

SAP Library


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

3. In the Application Configuration MDG_DQR_OVP select the configuration name MDG_DQR_OVP of the component FPM_OVP_COMPONENT.

4. In the Component Configuration of component MDG_DQR_OVP select

Additional Functions Deep Copy .

5. e. Choose Configurable 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 and at least of the component configuration MDG_DQR_FAILED_REC_LIST_UIBB, set the according flags in the column Copy and enter appropriate names in the column Target Configuration. Then choose Deep-Copy.

The technical names of target configurations should reflect the business object type and the data quality service.

6. Choose a package for the copied configurations.

3. Adapt the Copied Configurations of the FPM

1. Select the name of the copied application configuration.

2. Select Edit 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 configuration of the component MDG_DQR_OVP.

4. Change the copy of the configuration MDG_DQR_FAILED_REC_LIST_UIBB by the selecting the respective UIBB and choosing Configure UIBB.

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

6. Configure the List UIBB according to the selected business object type.

4. Configure Change Request Process for DQR

Create a business activity for the business object type with logical action CHANGE_DQR in customizing activity Create Business Activity and assign it to a change request type in Customizing activity Create Change Request Type.

5. To provide the DQR function to your users add the Web Dynpro application MDG_DQR_OVP with the 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. 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. 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 configure this variant go through this configuration process and use application configuration MDG_DQR_OVP_FILTER instead of MDG_DQR_OVP in step 2. In this case you need to

SAP Library


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.

Config Mdg Co 70 01

Documents

sap products

sap library documentation

version of sap library

sap group products

example text keys

example text output

master data governance

express permission of