MDG70SP02CO

SAP Library

Configuring Master Data Governance for Custom Objects 1

Configuring Master Data Governance for Custom Objects

CUSTOMERDocument Version: 19.05.2014

SAP Library


Copyright Copyright 2014 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 purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors. National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies (SAP Group) forinformational purposes only, without representation or warranty of any kind, and SAP Groupshall not be liable for errors or omissions with respect to the materials. The only warranties forSAP Group products and services are those that are set forth in the express warranty statementsaccompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark foradditional trademark information and notices.

SAP Library


Icons in Body TextIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Helpo General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic ConventionsType Style DescriptionExample 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 programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.

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 ofinstallation, upgrade and database tools.

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

Variable user entry. Angle brackets indicate that you replace these words andcharacters 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 CustomObjects

1. Data Model

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

Before you activate the business functions, ensure that you have theadministration authorization for MDG. The required authorization objects aredelivered with the authorization role SAP_MDG_ADMIN. In transaction PFCG,we recommend creating a copy of this role and assigning the relevantauthorization values. For the authorization object USMD_DM Data Model youneed to assign the values for the authorization field USMD_MODEL Data Model(for example MM, BP, or 0G) and the values for the authorization activityACTVT Activity (for example 01:Create or generate, or 02: Change).

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

1. MDG Data Model: Details

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

1. Entity Types

An MDG data model consists of the following entity types:

Entity Type with Storage and Use Type 1 (Type1 EntityType)

Storage and use type 1 must be used for entity types thatcan be processed in MDGAF. They have the followingcharacteristics:

They represent root objects that are subject togovernance.

More than one type1 entity type is possible in onedata model.

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

SAP Library


They are used for modeling attributes andrelationships.

They are processed in the first step of the changerequests [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 thatcannot be processed with MDG and which are not availablein the system. They have the following characteristics:

They model lists of values and descriptions that canbe uploaded.

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

Data storage is generated (no edition, no stagingarea).

No further modeling is possible (only check tablesand 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 thatshould not be processed by MDG, but are available in thesystem. They have the following characteristics:

They model external entities used in the data model.

They model additional primary keys for the tables oftype-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 adomain fixed value of data elements; only key fieldsare processed in check tables.

SAP Library



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

They represent dependent nodes of objects tostructure object data.

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

Data storage is generated (edition dependent andstaging 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 andtype4 entity types.

Type-4 entity types must be linked to aleading 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 keyattributes.

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

The key of an type-4 entity type must be enhancedby at least one type1, type2, or type3 entity type.

Referencing Relationships [External]

The key of a referenced entity type becomes anattribute of the referencing entity type.

2. Example: Flight Customers

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

Although the tables in this data model use the SAP namespace, the stepsand requirements necessary for bringing the tables under governance are thesame as those used in the customer namespace. The names of your entitytypes must be in the customer namespace. In this example, the tableSBUSPART 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 thisprocess, airline partners and travel agencies are created as well. Therefore,entity types need to be created. Since they are created only together withairline 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 tableSBUSPART. Therefore, ZSCUSTOM is defined as an entity type with storageand usage type 4 with a leading relationship to ZSBUSPART.

A key field of the table STRAVELAG is the field AGENCYNUM. TheAGENCYNUM field uses the check table SBUSPART. Therefore,ZSTRAVLAG is defined as an entity type with storage and usage type 4 witha 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, andSTRAVELAG, their attributes, and the relationships between the entity types.

3. Create Data Model

Define the data model in Customizing for Master Data Governance underGeneral Settings Data Modeling Edit Data Model .

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

4. Create Entity Types

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

Fields Entries Comment

Storage/UseType

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 typeand 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 InternalKey Assignment

User needs to provide the keywhen 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/UseType

Changeable via OtherEntity Type; GeneratedDatabase Tables

Type-4 Entity Type


Data Element Left blank for ZSCUSTOM as the key will bederived from the relationship to the leadingentity type ZSBUSPART (see below)


Validity/Hierarchy Hierarchy is Not EditionDependent

n.a.

Key Assignment Key Cannot Be Changed;No Internal KeyAssignment

User needs to provide the key whencreating new entities


Description Flight Customers n.a.

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


Storage/UseType

Changeable via OtherEntity Type; GeneratedDatabase Tables

Type-4 entity type


Data Element Left blank for ZSTRAVLAG as the key willbe derived from the relationship to theleading entity type ZSBUSPART (seebelow).


Validity/Hierarchy Hierarchy is Not EditionDependent

n.a.

Key Assignment Key Cannot Be Changed;No Internal KeyAssignment

User needs to provide the key when creatingnew entities

SAP Library



Description Travel Agencies n.a.

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

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

Choose New Entries and enter the following attributes and dataelements 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 MANDTfield 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 dataelement of the attribute. This lets you perform checks and call upinput help in the user interface.

In transaction SE11, you can see that the attribute LANGU with thedata element SPRAS is used in the data dictionary (DDIC) tableSTRAVELAG. This cannot be reflected in the MDG data model. Theattribute name LANGU cannot be used. Therefore, the nameZLANGU 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 dataelements 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 entitytype. Therefore, you have to rename the attributes of entity typeZSCUSTOM. This is also true for indirect assignments that involveleading 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 followingrelationship 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 acheck. For the data in this example data the warning messages, which arerelated 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 changerequest process.

Start the UI configuration in Customizing for Master Data Governance underGeneral 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 ApplicationConfiguration), YZ_MDG_IDR (for Identification Region), and YZ_MDG_OIF (forObject Instance Floorplan). Then choose Start Deep Copy.

If you want to transport the UI configuration, assign a package and a transportrequest, otherwise choose Local Object and OK. When the copy is finished, thesystem 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 tothe 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 sectionAssign 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 selectZSBUSPART from the value help and choose OK.

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

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 thisvariant, but also the attributes of the entity types ZSTRAVLAG and ZSCUSTOM. Thisis because there is a 1:1 relationship to these entity types from ZSBUSPART.

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

Since the component configuration contains a default UIBB that you are not going touse, 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 notyet exist. You are going to create this configuration ID in the next step. Select UIBBand choose Configure UIBB.

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

SAP Library


If you want to transport the component configuration, assign a package and atransport 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 Fieldssection so that they appear on the UI.

o BUSPATYP

o BUSPATYP_DESCRIPTIONo CONTACT

o CONTPHONOChoose OK to display the added fields in the preview.

Select the description Business Partner ID Number and change the attribute DisplayType 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 offields. For more information on UI configuration features, see Managing of UIConfigurations [External].

Process1. Process Modeling

1. Create Business Activity

Create a business activity in Customizing for Master Data Governance underGeneral 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 transportrequest.

2. Create Change Request Type

Create a change request type in Customizing for Master Data Governanceunder General Settings Process Modeling Change Requests CreateChange 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


Changerequest

Model Required Object Workflow

YZBP01 YZ ProcessAirlineBusinessPartner

No Yes ZSBUSPART WS75700040

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


3. Define Workflow

The standard workflow template WS75700040 will be used for the changerequest process. This template provides workflow step numbers, which needto be entered in Customizing for Master Data Governance under GeneralSettings Process Modeling Workflow Other MDG Workflows DefineWorkflow Step Numbers .

In case the following entries do not exist already, choose New Entries andenter 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 theworkflow steps of the change request. Create 2 positions and 1organizational unit for this assignment. You can use transaction PPOMW tocreate these structures and also to assign users to these structures. Thisconfiguration 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 theobjects. You will need the IDs in the Assign Processors activity. Thesystem will generate the IDs. These IDs will be different than theexample data in your settings.

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

5. Assign Processors

Assign processors to the workflow step numbers in Customizing for MasterData 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 Changerequest

Step Description Ob Agent ID Complete Name

YZBP01 1 Processing S 50001127 Flight Application ProcessExpert

YZBP01 2 Final Check S 50001128 Flight Operations Manager


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

6. Create Role

In order to provide a menu and authorizations for the users, create a roleusing 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 ofOrganizational Structure.

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

1. Execute Process

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

1. Create Change Request

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

Enter a description for the change request and provide the data for theattributes of the airline partner. Choose Submit to create the change requestand 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 displayyour workflow items. Double-click the work item belonging to the changerequest you just created. Now you can review and change the data of theairline business partner. Choose Finalize Processing to send it to the nextprocessor. Alternatively, choose Send for Revision to send it back to therequestor.

3. Approve Change Request

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

SAP Library


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

Configuring Data ReplicationYou can replicate master data stored within MDG as well as reference data, stored inconfiguration 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):

x The reuse option used by MDG-M and MDG-S stores data in the SAP ERP tablessuch as MARA or LFA1.

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

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

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

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

About the Configuration of Reference DataReference data, which is stored in Customizing tables, is typically stable and available for useacross an organization. Currency codes, for example, may be stored as reference data. Youcan model reference data in MDG data models, govern changes, and replicate changes.

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

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

x Creation and release of transport request in target system.

Prerequisites for Data ReplicationAt least one data model, with entity types, attributes, and relationships is defined using theflex 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 user who replicates the data has the same ID in the source system and in thetarget system.

3. The RFC destination for the target system has the following settings:

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

2. Under Logon & Security Logon Procedure , you have selected CurrentUser.

4. In the target system, the user who replicates the data is added to the list of RFCUsers authorized to execute RFC calls in trusted systems.

Steps for Replicating Data1. Define mapping contexts across clients for the Unified Key Mapping Service (UKMS).

SAP Library


o Path: Customizing for Key Mapping (transaction IDMIMG) underDefine aMapping Context for UKMSDefine Mapping Contexts.

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

o Example: Copy table UKMDB_AGC00000 to ZUKMDB_AGCZZSF0.

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

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

1. Define business object types to be replicated.

Path: Customizing for Key Mapping (transaction IDMIMG) under DefineBusiness Objects

Example: Specify business object type ZZSF, which is for the customerimplementation of SFLIGHT (Flex).

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

Path: Customizing for Key Mapping (transaction IDMIMG) under EnhanceKey Mapping ContentAssign Business Objects to the Main Context

Example: Assign business object type ZZSF to the main context (defined inthe previous step.)

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

0. Define an object node type.

Path: Customizing for Data Replication (transaction DRFIMG) underEnhance 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

Constant Name for Business Object ID Type:BPARTNER_UUID.

Row for Business Partner UUID

SAP Library


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 abusiness object from other identifiers of the same business object. Assign thebusiness object identifiers types to the relevant business object types.

1. Create business object identifier types.

Path: Customizing for Key Mapping (transaction IDMIMG) under EnhanceKey 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 businessobject types.

Path: Customizing for Key Mapping (transaction IDMIMG) under EnhanceKey Mapping Context Define Business Objects

Example: Business Object Type = ZZSF; Description = SFLIGHT (FlexOption); Constant Name = ZZSF_AIRLCODE; Object Identifier Type for KeyStructure Access = ZZSF

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

1. Run transaction SE80 and create a package.

Example: Object Name = ZZ_DRF, Description = Custom Object SFLIGHTData Replication

2. Generate the data model-specific structures.

Path: Customizing for Master Data Governance (transaction MDGIMG) underData Modeling Generate Data Model-Specific Structures

Example: Data Type = ZXX_S_ZZ_ZDRF_CARR, Where Used = DRFStructures, 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, sothe 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 canbreak down concatenated keys into their constituent parts.

Path: Customizing for Data Replication (transaction DRFIMG) under EnhanceDefault Settings for Outbound Implementation Define Business Objects and ObjectIdentifiers Assign Key Structures to Object Identifiers

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

SAP Library


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

Path: Customizing for Master Data Governance (transaction MDGIMG) underGeneral 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 theBusiness Object Type view, enter the business object type for the entity type. Thengenerate 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:BusinessObject Type = ZZSF. Choose the Generate Data Model button.

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

1. Run transaction SE80.

2. Create a package.

Example: Package = Z_ZZ_PACKAGE. Short Description = Package forOutbound 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 = FunctionGroup for Outbound Sflight (ZZ)

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

Path: Transaction OIF_MAINTAIN or Customizing for Data Replication (transactionDRFIMG) under Enhance Default Settings for Outbound Implementation DefineOutbound Interface Models

Example: Complete the following steps:

1. Wizard step: Enter Header Data.

Specify and describe an identifier for the interface model, an object typecode, a package name, a name for the outbound interface model, and adescription for the interface model. If you want to replicate reference data, sotriggering the generation of a function module enabling the replication of suchdata, select the Configuration Data checkbox.

You can adjust the generated function module according to yourneeds, for example, in the case of reference data, you can omit therelease 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 ABAPDictionary Objects button. Enter the following details for the new structure:

SAP Library


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 andattributes you want to include in the interface model. Then enter names forthe resulting dictionary objects, by choosing the Name ABAP DictionaryObjects button.

Example: Select the CARR entity type and all of its attributes. Choose theName ABAP Dictionary Objects button. Enter the following details for the newstructure:

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 atransport request or assign an existing transport request. You can use thesame transport to transfer the function module to the target system later on.

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

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

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

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

When defining an outbound implementation, use the generic outboundimplementation class (CL_MDG_OIF_DRF_OUTBOUND_IMPL). You can copy thisclass to allow additional capabilities that are not supported by default such as keymapping and value mapping. For more information, you can refer to the standardoutbound implementations that SAP delivers for other objects.

Path: Customizing for Data Replication (transaction DRFIMG) under EnhanceDefault 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

SAP Library


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 targetsystem during data replication through the use of filters. Define filters for the filterobject.

Path: Customizing for Data Replication (transaction DRFIMG) under EnhanceDefault 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 atable name. The system only requires table names for simple filters.Such filters are only available for standard applications that are builtusing 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 fieldsfrom the generated table. In the Assign Filters view, apply the followingsettings.

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

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

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

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

Path: Customizing for Data Replication (transaction MDGIMG) underEnhance Default Settings for Outbound Implementations Define

Business Objects and Object Identifiers Assign Filter Objects to BusinessObjects

o Assignment of a filter object to an outbound implementation:

Path: Customizing for Data Replication (transaction MDGIMG) underEnhance Default Settings for Outbound Implementations Define

Outbound Implementations

Example: Business Object Type = ZZSF; Filter Object = ZZSF_FR00T;Outbound Interface Model ID = ZZ_SFLIGHT

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.

SAP Library


Example: SFLIGHT (Flex Option).

2. Define a filter.

Example: Under Filter Criteria to Include Business Objects, choose Airlinelocal currency is EUR.

11. Create a replication model, assign the outbound implementation to the replicationmodel, and assign the business systems that act as target systems for replication tothe combination of the outbound implementation and the replication model. Eachreplication 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 DefineReplication Models

Example:

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

Replication Model = ZZSF; Description = Replication Model forSFLIGHT; 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 followingsettings: Outbound Implementation = ZZSF_01; Communication Channel = 4Replication via RFC; Replication via RFC; Filter Time = 2 FilterAfter Change Analysis.

Select the assigned Outbound Implementation.

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

Example: Open the Assign Receiver Systems view, and enter the followingvalue: Business System = QV5_410

3. Activate the replication model.

Choose the Activate Replication Model pushbutton.

Additional Steps for the Replication of Reference Data1. 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 ormore target systems. This model also generates interfaces (RFCs and serviceinterfaces) that can be used for such a data replication. After creating the outboundinterface model, you can view the generated function module in transaction SE80.

Path: Transaction OIF_MAINTAIN or Customizing for Data Replication (transactionDRFIMG) under Enhance Default Settings for Outbound Implementation DefineOutbound Interface Models

Example: Complete the wizard as follows:

SAP Library


1. Wizard step: Enter Header Data.

Specify and describe an identifier for the interface model, an object typecode, a package name, a name for the outbound interface model, and adescription for the interface model. To trigger the generation of a functionmodule enabling the replication of such data, select the Configuration Datacheckbox.

You can adjust the generated function module according to yourneeds, for example you can omit the release of the transport requestin order to enable data enrichment. The user can then release thetransports manually.

Example

Select the CARR entity type and all of its attributes. Choose the Name ABAPDictionary 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 andattributes you want to include in the interface model. Then enter names forthe resulting dictionary objects, by choosing the Name ABAP DictionaryObjects button.

Example: Select the CARR entity type and all of its attributes. Choose theName ABAP Dictionary Objects pushbutton. Enter the following details for thenew 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 atransport request or assign an existing transport request. You can use thesame transport to transfer the function module to the target system later on.

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

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

SAP Library


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

2. Create a mapping using the service mapping tool to map data from the staging areain 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 outboundinterface model.

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

Path: Customizing for Master Data Governance (transaction MDGIMG) under DataModeling 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.This example is based on the Flight Data Model demonstration and education content.

PrerequisitesYou have activated the Master Data Governance, Generic Functions 7.0(MDG_FOUNDATION_4) business function.

In order to enable the example, see Master Data Governance for Custom Objects: ExampleConfiguration [Page 26].

ProcessThe business processes run as follows:

1. Process Airlines of the Flight Data Model.

2. Process Flight Connections of the Flight Data Model.

SAP Library


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 DataGovernance for Custom Objects. At the end you will be able to execute all processes of theexample scenario as described in Master Data Governance for Custom Objects: ExampleDescription [Page 25].

PrerequisitesYou have activated the business function Master Data Governance, Generic Functions 7.0(MDG_FOUNDATION_4).

Process1. Setup of the Organizational Structure

The assignment of processors to the workflow steps of the change request is done byusing organizational structures. This structure needs to be available before theactivation of the BC-Set in one of the next steps. Create 2 positions, and 1organizational unit for this assignment. The identification numbers are generated bythe system and are different in each client. You can use transaction PPOC to createthese 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 theColumn Configuration. You need the IDs when activating the BC-Setcontaining the change request types.

You can use the same user and assign it to each position. This willallow you to go through the change request process with one singlelogon and therefore be easier to use. However, in order to properlydemonstrate the segregation of tasks, it is recommended to use adedicated user for each of the positions.

2. Client Independent Configuration, Part 1 Data Model

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

3. Client Independent Configuration, Part 2

SAP Library


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

4. Client Specific Configuration

This configuration will be done by activating a set of BC Sets. Dependent on thebusiness function you have activated, you need to apply the following:

o If you have activated MDG_FOUNDATION_4 use transaction SCPR20 andactivate the set of BC Sets CA-MDG-AF-FS_SFLIGHT_CLIENT_02 MDGFoundation Example SFLIGHT Client-Specif Customizing 7.0

o If you have activated MDG_FOUNDATION_5, available with MDG 7.0 SP02and higher, and want to use the function highlight changes in the example,use transaction SCPR20 and activate the set of BC Sets CA-MDG-AF-FS_SFLIGHT_CLIENT_03 MDG Foundation Example SFLIGHT Client-Specif Cust 7.0 SP02.

The BC Sets assume a configuration of priorities for change requests. Use theCustomizing activity Define Priorities for Change Requests under GeneralSettings Process Modeling to check whether there are defined the priorities 1(High), 2 (Medium), and 3 (Low). If this is not the case, these priorities have to becreated before activating the BC Set. You can activate the BC Set CA-MDG-AF-FS_SFLIGHT_CR_PRIOS to define the priorities.

During the activation the system prompts you to enter the IDs of the organizationstructures you want to use for agent determination. The values that you need to enterdepend on how you have set up the organizational structure in step 1. Using theexample 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 toexecute the scenarios independent in each client.

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

5. Assign the Role to Users

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

SAP Library


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

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

3Navigation to User Interfaces

In SAP Master Data Governance, you can navigate to user interfaces in the following ways:

x Object-and-Action Based Navigation [Page 29]

You navigate in this way to display or start the processing of master data objects.

x Change-Request Based Navigation [Page 31]

You navigate in this way to display a change request that contains one or moremaster data objects that are being processed.

SAP Library


3.1Object-and-Action Based Navigation

You use object-and-action based navigation to display or to start the processing of masterdata objects.

The typical navigation sequence for the user is as follows:

1. Launch the search application from the SAP NetWeaver Business Client (transactionNWBC).

To do this, you can choose an entry from the role menu, click a link from the servicemap, or click a link from the home page.

2. Search for an object.

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. Anotherpossibility is choosing the New button. In all cases, the system opens a new windowwith the target UI.

3. Process the object in the target user interface.

Sometimes you can directly edit the object in the target user interface and sometimesyou must choose the Edit button first. Choosing the Edit button triggers anotherlogical action.

SAP Library


FeaturesNavigation from NWBC to the Generic Search ApplicationThe Web Dynpro application Generic Search (USMD_SEARCH) is available in the menu. TheUSMD_SEARCH node of the menu can include the object-independent configurationUSMD_SEARCH or an object-specific configuration. With the generic configuration, you can setdefault values for the data model and for the entity type, by specifying the followingparameters in the menu node:

x USMD_MODEL

x USMD_ENTITY

The user can still override the defaults you set by selecting different options on the userinterface.

If you specify a Business Object Type with the parameter USMD_OTC, users can no longerchange the data model and the entity type. For more information on the required parameters,see Configuration of the Generic Search [Page 33].

Navigation to the Target UI

In the following description, the Generic Search is used as an example of the CurrentUI.

If you do not specify the USMD_OTC parameter for the USMD_SEARCH Web Dynproapplication, the system derives an Business Object Type for the data model and entity typebased on Customizing.

The relevant settings are as follows:

x Activity: Customizing for Master Data Governance (transaction MDGIMG) underGeneral Settings Data Modeling Edit Data Model

x 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 Process Modeling BusinessActivities Define Logical Actions ) depends on the UI, the UI configuration, and the state ofthe chosen business object type.

To determine the target user interface, the system considers the current user interface and itsconfiguration, the logical action, and the Business Object Type of the selected businessobject. Relevant settings are available in the following Customizing activities:

x Standard Definition: Customizing for Master Data Governance (transaction MDGIMG)under General Settings Process Modeling Business Activities Link Log.Actions with UI Application and Bus. Act.: Standard Definition

x Custom Definition (Overrides Standard Definition): Customizing for Master DataGovernance (transaction MDGIMG) under General Settings Process ModelingBusiness Activities Link Log. Actions with UI Application and Bus. Act.: CustomDefinition

SAP Library


Navigation from Other Search ApplicationsYou can use other search applications than USMD_SEARCH. In particular, the initial page ofthe single-object processing UI USMD_OVP_GEN can provide an object-specific search. Thelogic for determining a target UI is the same for other search applications as it is for thegeneric search.

Navigation from the Initial Step of a Change RequestIf a logical action triggers the creation of a change request, the system gives precedence tothe logic of the change-request-based navigation (see Change-Request Based Navigation[Page 31]) over object-and-action based navigation for the initial change request step 00. Ifyou have defined a target UI for the change request step 00, the system uses that UI. (Path:Customizing for Master Data Governance under General Settings Process ModelingChange Requests Configure Properties of Change Request Step ). If you have not defineda target UI, the system uses the logic for object-and-action based navigation to determine atarget UI.

If the current UI application is the generic single-object processing UIUSMD_OVP_GEN and the same UI is also the target UI application, the system ignoresthe value of Configuration ID from the view User Interface per Change Request Step .Instead, USMD_OVP_GEN uses its current configuration for the initial change requeststep.

3.2

SAP Library


Change-Request Based Navigation

Change-request based navigation occurs when you start processing a change request.Navigation possibilities include the following:

x Opening the relevant work item from the inbox.

x Searching for and selecting a change request in My Change Requests.

x Searching for a business object and clicking the Pending Change Requests icon.

FeaturesNavigation Based on Change Request StepsThe system selects a target user interface for the change request type and the currentchange step based on the User Interface per Change Request Step view of the followingactivity in Customizing for Master Data Governance: General Settings Process Modeling Change Requests Configure Properties of Change Request Step If a target UI is found,

it is used.

Object-and-Action Based Navigation for Single-Object Change RequestsIf the system cannot identify a target UI for the current change request step and the indicatorSingle Object of the change request type is set (Customizing for Master Data Governanceunder General Settings Process Modeling Change Requests Create Change RequestType ), the system uses object-and-action based navigation.

The system performs the following actions:

1. Determines the business activity for the change request type.

Path: Customizing for Master Data Governance under General Settings ProcessModeling Change Requests Create Change Request Type

2. Determines the logical action and Business Object Type based on the businessactivity settings.

Path: Customizing for Master Data Governance under General Settings ProcessModeling Business Activities Create Business Activity

3. Determines the target UI based on the business activity, logical action, and BusinessObject Type according to the logic of object-and-action based navigation (See Object-and-Action Based Navigation [Page 29])

If the system cannot determine a target UI based on the logic described above, the targetUI is the obsolete single-object processing UI USMD_ENTITY_VALUE2. In this case, thesystem determines the application configuration ID for USMD_ENTITY_VALUE2 in theEntity Types view of the following activity in Customizing for Master Data Governance:

General Settings Process Modeling Change Requests Create Change RequestType .

Multiple-Object Change RequestsIf the system cannot determine a target UI for the current change request step and the SingleObject setting of the change request type is not applied (Path: Customizing for Master Data

SAP Library


Governance under General Settings Process Modeling Change Requests CreateChange Request Type ), the target UI is application USMD_CREQUEST_PROCESS.

4 Configuration of the Generic Search

The Generic Search (USMD_SEARCH) service enables you to search for and display instancesof business objects based on specified criteria. For more information, see Search BusinessObject. [External]

FeaturesThe user interface is divided into the following areas, each of which you can customize:

x Search control

x Search criteria

x Search results

If the generic search application is too generic for you, you can create a restricted search withits own user interface, (for example, a search that returns airline partners only) by copyingand changing the generic configurations.

The technical objects that you can copy and change to create your own custom searchapplication are as follows:

x Application: USMD_SEARCH

x (Mandatory) Application Configuration: USMD_SEARCH

x Component Configurations:

o (Mandatory) USMD_SEARCH_OVP

Specifies the layout of the search application. Defines the user interfacebuilding blocks (UIBBs) for the search criteria and the results list.

o (Depends on the area of the UI that you want to customize) Area-SpecificConfigurations

Search control

MDG_BS_SEARCH_CONTROL

Feeder Class: CL_MDG_BS_SEARCH_SWITCH_FEEDER specifieswhat appears in the drop-down lists within the search control area ofthe user interface.

Search criteria

USMD_SEARCH_DQUERY

Specifies the configuration of the search criteria block. Defines whichsearch attributes can be used.

Search results

USMD_SEARCH_RESULT

SAP Library


Specifies how search results display. Determines which columnsdisplay in which order.

o (Mandatory) USMD_SEARCH

Specifies the configuration of the MDG communicator framework. Must havea name that matches the application configuration. At runtime, thiscomponent specifies the selection block indicating which data model, entitytype, and search method are used.

4.1 Configuring the Generic Search for aParticular Business Object

You can configure the user interface of the Generic Search (USMD_SEARCH) Web Dynproapplication so that only business objects for a particular entity type and data model can besearched. With this configuration, users do not have to select data models or entity types fromdropdown lists in the search control area. You can also configure which fields display in whichorder in the search results.

You can create this example configuration in the following ways:

x Using the Manage UI Configurations Web Dynpro application in Customizing

For more information, see Managing of UI Configurations [External]

This feature is available with business function Master Data Governance,Generic Functions 7.0 Feature Pack (MDG_FOUNDATION_5). This businessfunction is available with support package 02 and higher support packages ofMDG 7.0.

x Editing the technical objects in transaction SE80

If you have not activated business function Master Data Governance, GenericFunctions 7.0 Feature Pack (MDG_FOUNDATION_5), implement SAP Note 1984862before implementing this example using transaction SE80. If you have activated thebusiness function, use the Manage UI Configuration Web Dynpro application inCustomizing instead.

Both techniques are described in this document. Some steps provide separate navigationoptions for each technique.

PrerequisitesYou have set the standard data model to the data model for the entity type for which you areconfiguring the generic search by completing the following steps:

1. In transaction SPERS_MAINT, you have chosen the Edit objects button.

2. You have double-clicked the SAP Master Data Governance row.

3. In the popup, you have entered the standard data model and you have saved yourchanges.

SAP Library


ProcedureCopy UI Configuration

1. To start copying the UI configuration, choose from the following options:

o Manage UI Configurations

In Customizing for Master Data Governance, go to General Settings UIModeling Manage UI Configurations .

In the table, select the row with the following attributes and choose the Copybutton:

Application:USMD_SEARCH

Application Configuration:USMD_SEARCH_TEMPLATE

o Transaction SE80

Open Component Configuration USMD_SEARCH_OVP_TEMPLATE. UnderAdditional Functions, choose the Deep Copy button.

2. In the Floorplan Manager: Application Hierarchy screen, enter target configuration IDsfor the application configuration, the UI configuration (also known as the OVPconfiguration), and the UIBB configurations. Then choose the Start Deep Copybutton.

Application Configuration: Specify Parameters1. To open the copied application configuration, choose from the following options:


Return to the Manage UI Configurations screen and choose the Refresh link.An extra row displays in the table for the copied configuration. Click the linkfor the application configuration.

o Transaction SE80

Navigate to and open the application configuration you copied.

2. Enter the following parameters:

o USMD_MODEL: The data model

o USMD_ENTITY: The entity type

o USMD_OTC: The business object type

3. (Optional Step) To make the most commonly used search application appear as thedefault search application in the dropdown list, enter the search application in theUSMD_SEARCH_MODE parameter. If appropriate, enter the search help in theUSMD_SEARCH_HELP parameter.

4. Save the application configuration.

UI Configuration: Configure Search Criteria1. Open the copied UI configuration. Choose from the following options:


SAP Library


Return to the Manage UI Configurations screen and click the link for the UIconfiguration.

o Transaction SE80

Navigate to and open the UI configuration you copied.

2. Choose the Continue in Change Mode button.

3. In the Overview Page Schema, select the row for the Search Criteria UIBB. Thenchoose the Configure UIBB button.

4. Enter the following values for the CL_USMD_SEARCH_GUIBB_DQUERY feeder class:

Parameter Required Value

Component Yes MDG

Dyn QueryName

Yes GenSearchQuery

For example GenSearchQueryPFLI for the Flight entity type

SearchMode

Yes The search application. You can find the definition of searchapplications in use in Customizing for Master Data Governanceunder General Settings Data Quality and Search Searchand Duplicate Check Define Search Applications

InclSearchHelp

No (Optional) The search help for the search application. You can findthe definition of search helps allocated to the search application inCustomizing for Master Data Governance under GeneralSettings Data Quality and Search Search and Duplicate Check Define Search Applications .

5. In the Search UIBB Schema, add search attributes by using the Search Criteriabutton. Use the Up and Down buttons to change the order of the search attributes.You can change the number of search attributes that display in General Settings, byselecting a value for Number of Search Rows on Open. It might be necessary torestart the application before the search attributes of the entity type specified by theDyn Query Name are made available.

6. (Conditional Step) If the entity type is edition-based, add a search attribute so that theuser can select the validity timeframe for the returned instances of the businessobjects. If you add search attribute Valid On (USMD_VALID_AT), the user can selectthe validity timeframe directly. If you add search attribute Edition (USMD_EDITION),the user can select an edition that determines the validity timeframe. In the lattercase, set parameter USMD_SEARCH_EDITION_MODE to X in the copied applicationconfiguration.

Save the Search UIBB Schema configuration and return to the UI configuration.

UI Configuration: Configure Search Results1. In the Overview Page Schema, select the row for the Search Results UIBB. Then

choose the Configure UIBB button.

2. Enter the following values for the CL_USMD_SEARCH_GUIBB_RESULT feeder class:

Parameter Value

Component MDG

SAP Library


Object Name QRes

For example QResPFLI for the Flight entity type

3. In the List UIBB Schema, add search result attributes by using the Column button.Use the Up and Down buttons to change the order of the result attributes.

To enable navigation from the search results to the inactive data of abusiness object, add column CREQUEST_PENDING and set its display type toImage. To enable navigation from the search results to the active data of abusiness object, set the display type of the column representing the objectkey to Link To Action.

4. (Conditional step) If the entity type is edition-based, add the required result attributesthat describe the validity of the displayed instances of business objects. You candisplay result attributes for time-related validity and for edition-related validity.

o Time-related validity For a date-specific edition type, add attributes Valid From

(USMD_VDATE_FROM) and Valid To (USMD_VDATE_TO).

For a period-specific edition type, add attributes Period/Fiscal YearFrom (USMD_VPER_FROM) and Period/Fiscal Year To(USMD_VPER_TO).

You can identify whether an edition-based entity type uses dates orperiods in Customizing for Master Data Governance under GeneralSettings Process Modelling Create Edition Type . The Validity ofEntity field can have a value of Date-Specific or Period-Specific.

o Edition-related validityTo display validity in terms of editions, add attributes From Edition(USMD_EDITION) and To Edition (USMD_EDITION_TO).

5. In the Toolbar Schema, add required toolbar elements (or buttons) and save theconfiguration.

MDG Communicator: Configure MDG CommunicatorConfigure Using Manage UI Configurations

1. Return to the Manage UI Configurations screen.

2. Click the Details link in the Communicator Status column to create the necessarycomponent configuration for the MDG Communicator.

3. (Optional) To provide the search screen with a Search Method dropdown list thatoffers all available search applications and search helps instead of just the searchapplications and search help specified in the application configuration, select theincludeSearchControl checkbox of the settings context element.

4. Save the configuration and click the Refresh link. The Communicator Status field isset to Configuration available.

SAP Library


Configure Using Transcation SE801. Create a component configuration for Web Dynpro component

MDG_BS_GOV_COMMUNICATOR and give it exactly the same name as the applicationconfiguration you created previously.

2. (Optional) To provide the search screen with a Search Method dropdown list thatoffers all available search applications and search helps instead of just the searchapplications and search help specified in the application configuration, select theincludeSearchControl checkbox of the settings context element.

3. Save the configuration.

ResultTo test the application you created, open the copied application configuration and choose theTest button.

5 Creating User Interfaces for Single ObjectProcessing

In a complete UI configuration for single object processing, several components work togetherand need to be configured accordingly as shown in the figure MDG UI Configuration forSingle-Object Processing below.

One of these components is the generic MDG Web Dynpro application USMD_OVP_GENwith its application configurations. Each application configuration is specific for an object typeand this object type is defined with the parameter USMD_OTC.

This Web Dynpro application implements an adaptable overview page (OVP) component ofthe Floorplan Manager (FPM): FPM_ADAPTABLE_OVP. This OVP component is a wrapperthat contains an FPM overview page component (FPM_OVP_COMPONENT). Theconfiguration of the adaptable OVP references the adaptation scheme for creating contextbased adaptations (CBA) of the included OVP component and of its sub-components.

For more information, see Generic Context-Based Adaptation Scheme [Page 52].

The configuration of the OVP contains at least one page. At least one section of the pagecontains user interface building blocks (UIBBs). Most UIBBs enable the processing ofbusiness object data on the UI. The UIBBs are configured for all entity types that belong tothe business object. Usually, theres more than one entity type.

The MDG framework provides the following UIBBs:

x The change request UIBB (CRUIBB) displaying the change request properties, suchas description, due date, notes, and attachments

x The validity UIBB displaying the time validity for edition-based entities

These UIBBs are no explicit parts of the configuration of the Web Dynpro application, but areadded at runtime by the MDG communicator, which has overall responsibility for the changerequest process. The MDG communicator controls the availability of change request actions,which are represented as buttons in the global toolbar. The settings that the MDGcommunicator uses are stored in its component configuration.

You can also include the CRUIBB explicitly in the OVP configuration.

SAP Library


If you want to have an object-specific search, the OVP can include an initial screen with anFPM search UIBB to enter search criteria and a list UIBB to display search results.

MDG UI Configuration for Single-Object ProcessingApplication Configuration for USMD_OVP_GEN

Component Configuration for Adaptable OVPComponent Configuration for OVP

Further Pages (optional)for example edit pages, dialog boxes

Main Page of the OVPPage Section (can be multiple)

Change Request UIBBValidity UIBBEntity UIBBs (Forms, Lists)

Initial page of the OVP (optional)Page Section

Search UIBBResult List UIBB

Configuration of the MDG Communicator Settings

MDG UI Configuration for Single-Object Processing

MDG Data Model

The UI configuration is based on the active version of an MDG data model. At design-time,when you create the configuration of a UI or customize a UI, the relevant data model isdetermined by the standard data model from your user profile. You set the standard datamodel in the following way:

1. Run transaction SPERS_MAINT.

2. Select Edit Objects.

3. From the displayed list, choose SAP Master Data Governance - R_FMDM_MODEL.

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

5. Confirm and save.

SAP Library


At run-time, when the UI is used to process data, the MDG data model is determined by thebusiness object type code given in the parameter USMD_OTC of the configuration of the WebDynpro application USMD_OVP_GEN.

Business Object Type Code

Every configuration of the Web Dynpro application USMD_OVP_GEN contains the parameterUSMD_OTC that must be set to the business object type code (OTC) of the object that the UIshould be used for. The OTC is defined in Customizing for Master Data Governance under

General Settings Data Replication Enhance Default Settings for OutboundImplementations Define Business Objects and Object Identifiers Define Business Objects

. At least the columns BO Type, which contains the OTC, and Description need to be filled.You need to assign the OTC to the data model and the entity type in the view BusinessObject Type in the Customizing activity Edit Data Model under General Settings DataModeling . You also need to set the indicator Root in the same view. Additionally, you needto assign the data model and the entity type to the OTC in the Customizing activity DefineEntity Type to Be Used by Business Object Type under General Settings Data Modeling

.

Data Model-Specific Structures

The UI components of MDG require several DDIC structures that are specific to the datamodel used for the UI configuration. Initially and also after every change to the data model,these structures need to be generated. Use the Customizing activity Generate Data Model-Specific Structures under General Settings Data Modeling for all entity types that youuse in the UI configuration to generate the required structures for the following entries of thecolumn Where Used:

x 3 - Mapping of Reuse Active Area

x 6 - Field Control for Attributes

x 7 - Field Properties for Attributes and Key Fields

x 8 - Key Fields of an Entity Type

Mandatory Naming Convention for the MDG Communicator

The application configuration ID must be the same as the configuration ID for the MDGcommunicator settings. Otherwise, the application cannot determine which settings to useand the integration with the MDG framework will not work.

Possible symptoms of a mismatch between configuration IDs at runtime are as follows:

x No CRUIBB is displayed after choosing Edit in one of the UIBBs.

x No change request ID is generated.

x No change request action buttons are displayed in the main toolbar.

Recommended Naming Conventions for Other Configurations

x Application Configuration __OVP_

Example: USMD_SF_OVP_CARR

x Component Configurations ___

Examples:

SAP Library


o USMD_SF_CARR_OVP for the configuration of the OVP component for theentity type CARR in data model SF

o USMD_SF_CARR_FORM for the configuration of a form component for theentity type CARR in data model SF

Highlight Changes

You can set the colors and the activation of the highlight changes function in the configurationof the used MDG Web Dynpro application, for example USMD_OVP_GEN, using theparameters MDG_HC_DISABLE, MDG_HC_COLOR_SAVED, andMDG_HC_COLOR_UNSAVED. For more information, see Highlight Changes [External].

5.1 Creating a Basic Configuration for the Single-Object Processing UI

This document describes how to configure the generic MDG single-object processing userinterface that is provided by the MDG Web Dynpro application USMD_OVP_GEN.

PrerequisitesYou have completed the following:

1. You can use an active MDG data model with at least one entity type with storage anduse type 1. You have assigned a business object type code (OTC) to this entity type.

2. You have generated the required structures in the Customizing activity GenerateData Model-Specific Structures under General Settings Data Modeling .

3. You have set the standard data model in your user profile.

For more information, see Creating User Interfaces for Single Object Processing [Page 38].

Process

Instead of using transaction SE80 for the processes described below, you can alsouse the Customizing activity Manage UI Configurations under General SettingsUI Modeling for the deep-copy of application configurations and the creation ofMDG communicator settings. For more information, see Managing of UIConfigurations [External].

Deep-Copy of Application Configuration

This section describes how to configure the MDG Web Dynpro application USMD_OVP_GENcreating a deep-copy of the template USMD_OVP_GEN_TEMPLATE.

1. Start transaction SE80 and display the Web Dynpro application configurationUSMD_OVP_GEN_TEMPLATE from the package USMD_GENERIC_BOLUI.

2. Choose Display Configuration. Then choose the application configuration nameUSMD_GEN_OVP_TEMPLATE of the component FPM_OVP_COMPONENT.

3. Choose Additional Functions Deep Copy .

SAP Library


4. Open Configurable Components and enter the target configuration IDs for theapplication configuration, the context-based adaptation FPM_ADAPTABLE_OVP,and the overview page (OVP) floorplan FPM_OVP_COMPONENT. Then chooseStart Deep-Copy.

Replace in the configuration IDs with the combination of an MDG datamodel and the main entity type using meaningful names. For example,Z_USMD_OVP_SF_CARR for the application configuration andZ_USMD_SF_CARR_OVP for the OVP configuration.

5. Open the new application configuration and change the parameter USMD_OTC tothe object type code of the business object that you want to process with thisconfiguration as mentioned in step 1 of the Prerequisites section of this document.

Create MDG Communicator Settings

For the integration of the new application configuration with the MDG framework the systemrequires the configuration of the MDG communicator.

In this configuration activity you will create MDG communicator settings from atemplate that contains dummy entries for the UIBB of the main entity and the page IDof the OVP. After you have added this UIBB to the OVP component, remember toreplace these dummy entries with the actual IDs that you have chosen.

To create this configuration perform the following steps:

1. Start transaction SE80 and display the Web Dynpro component configurationMDG_BS_GOV_COMMUNICATOR_TEMPLATE from the packageUSMD_GENERIC_BOLUI.

2. Choose Start Configurator.

3. Choose Copy Configuration .

4. Enter the same configuration ID for the MDG communicator settings that you havechosen for the configuration ID of the MDG application USMD_OVP_GEN when youhave created the deep-copy. For example, Z_USMD_OVP_SF_CARR.

The two configuration IDs need to match exactly. Otherwise, the applicationis unable to determine the settings for the MDG communicator.

5. The settings of the MDG communicator must be completed in a later step, after youhave configured the UIBB that displays the main entity on the OVP. Only then youknow which values need to be entered here. To complete this step, open the copiedconfiguration of the MDG communicator. In the table Configuration Context, navigateto Context Settings crWires (MAIN) and enter the following values: :

o Page Id

ID of the page in the OVP that contains the UIBB with the main entity

o Source Component

SAP Library


The UIBB that contains the main entity

o Source Config Name

The UIBB that contains the main entity

6.

7. If you make a mistake in the configuration of the MDG communicator, theintegration with the MDG framework will not work.

8. Possible symptoms at runtime are:

o There is no change request UIBB displayed after choosing Edit in one ofthe UIBBs

o No change request ID is generated

o There are no change request action buttons displayed in the main toolbar

5.2 Creating Forms

This document describes how to configure a Floorplan Manager (FPM) form for a userinterface building block (UIBB) to process data with the MDG Web Dynpro applicationUSMD_OVP_GEN. You can use this configuration description for implementations of thefollowing form UIBBs:

x FPM form GUIBB GL2: FPM_FORM_UIBB_GL2

x FPM form GUIBB: FPM_FORM_UIBB

The FPM form GUIBB has been replaced by the new FPM form GUIBB GL2.

MDG delivers the feeder class CL_MDG_BS_GUIBB_FORM which you can use in such aconfiguration. The feeder class retrieves the attributes of the entity type for which the form isconfigured. With this you can configure the layout of the form. During runtime the feeder classreads, writes, and checks the data of the entity that is currently being processed.

An FPM form GUIBB GL2 is included in the example configurationUSMD_SF_OVP_CARR. This example configuration is located in the generic MDGWeb Dynpro application USMD_OVP_GEN in packageMDG_FND_SAMPLE_IMPLEMENTATIONS.

For information on assigning UI fields for each entity type, see the Generic Interaction Layer(genIL) section in Building Blocks for the UI Framework [Page 53].

PrerequisitesYou have completed the following:

1. You can use an active MDG data model with at least one entity type with storage anduse type 1. You have assigned a business object type code (OTC) to this entity type.

SAP Library


2. You have generated the required structures in the Customizing activity GenerateData Model-Specific Structures under General Settings Data Modeling .

3. You have set the standard data model in your user profile.

4. You can use a configuration of the generic MDG Web Dynpro applicationUSMD_OVP_GEN that includes an FPM overview page (OVP) FPM_OVP_COMPONENTto which you can add the UIBB. You can open and edit the configuration of this pagein the FPM editor. Alternatively, you can create Customizing for this configuration. Formore information, see Configuration Editor for Floor Plan Manager [External].

For more information, see Creating User Interfaces for Single Object Processing [Page 38].

ProcessConfiguration of a FPM Form GUIBB

Follow these steps to create a new configuration of a FPM f

MDG70SP02CO

Documents

Transcript of MDG70SP02CO