Class Items in BOMs

8/12/2019 Class Items in BOMs

http://slidepdf.com/reader/full/class-items-in-boms 1/18

SAP Library

Configuring Master Data Governance for Custom Objects 1

Configuring Master Data Governance for Custom Objects

Document Version: 18.02.2013



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 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.

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






SAP Library


Icons in Body TextIcon Meaning

Caution

Example

NoteRecommendation

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 Help 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.

<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 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] .

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 (Type –1 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 type –1 entity type is possible in onedata model.

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

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.

Entity Type with Storage and Use Type 2 (Type –2 Entity

Type)



SAP Library


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 a

domain fixed value of data elements; only key fieldsare processed in check tables.


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.



SAP Library


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 andtype –4 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 type –1, type –2, or type –3 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 the

same 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 governanceprocess 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. The AGENCYNUM field uses the check table SBUSPART. Therefore,



SAP Library


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 SPRASEMAIL S_EMAIL

WEBUSER S_WEBNAME

SBUSPART: Airline Partner

Field Data Element

MANDANT S_MANDT

BUSPARTNUM S_BUSPANUM

CONTACT S_CONTACT

CONTPHONO S_CPHONENO

BUSPATYP S_BUSPATYP

STRAVELAG: Travel Agency

Field Data Element

MANDT S_MANDT

AGENCYNUM S_AGNCYNUM

NAME S_AGNCYNAM





SAP Library


Fields Entries Comment

Storage/UseType

Changeable via Other EntityType; Generated DatabaseTables

Type-4 Entity Type

Validity of Entity No Edition n.a.

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

Hierarchies No Hierarchies n.a

Validity/Hierarchy Hierarchy is Not EditionDependent

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 Flight Customers n.a.

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

Fields Entries Comment

Storage/UseType

Changeable via OtherEntity Type; GeneratedDatabase Tables

Type-4 entity type

Validity of Entity No Edition n.a.

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

Hierarchies No Hierarchies n.a

Validity/Hierarchy Hierarchy is Not EditionDependent

n.a.

Key Assignment Key Cannot Be Changed;No Internal Key

Assignment

User needs to provide the key when creatingnew entities

Deletion Deletion Allowed n.a.

Description Travel Agencies n.a.

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



SAP Library


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

Choose New Entries and enter the following attributes anddata 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 thedefault.

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

Choose New Entries and enter the following attributes and dataelements 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

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.



SAP Library


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

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 .



SAP Library


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 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 push button 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 Variant Must Be Deleted and choose the Delete push button.

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.

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 Fields section so that they appear on the UI.



SAP Library


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 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 Governance under General Settings Process Modeling Change Requests CreateChange Request Type .

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

Type ofChangerequest

DataModel

Description ObjectsRequired

SingleObject

Main Entity TypeWorkflow

YZBP01 YZ Process AirlineBusinessPartner

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 .




SAP Library


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 Define

Workflow 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 three positions, organizationalunits, or jobs for this assignment. You can use transaction PPOMW to createthese 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 Product Manager (Code:FLPRODMAN, ID: S 50001126)

FLPRODMAN

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 Product Manager (Code: FLPRODMAN, ID: S 50001126) ----User: FLPRODMAN -- Position: Flight Application Process Expert (Code:FLAPPEXPERT, ID: S 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. The



SAP Library


system 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 that

you use a dedicated user for each position.

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 the

workflow 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

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

Author iza t ion Objec t USMD_CREQ (Type of Ch ange Request)

Activity All Activities

Type of Change Request YZBP01

Author iza t ion Objec t USMD_UI2 (UI Configuratio n)



SAP Library


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 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 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.

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



SAP Library


1 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.

Prerequisites1. 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 qualityconnector consists of an ABAP class that implements the interfaceIF_MDG_DQR_DQ_SERVICE and, optionally, an implementation of the BAdI EventHandling for Data Quality Remediation . For more information, see the documentationof this BAdI under General Settings Data Quality and Search Business Add-Ins

.

ProcessConfiguration Process

1. You need to execute the Customizing activity Define Data Quality Service . For moreinformation, see the documentation of this customizing activity under GeneralSettings 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 Applicationconfiguration MDG_DQR_OVP and choose Start Configurator .

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. Tocreate a copy of the Application Configuration MDG_DQR_OVP, theOverview Page Floorplan MDG_DQR_OVP and at least of the componentconfiguration MDG_DQR_FAILED_REC_LIST_UIBB, set the according flagsin the column Copy and enter appropriate names in the column TargetConfiguration . Then choose Deep-Copy .

The technical names of target configurations should reflect thebusiness 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 theparameter MDG_DQR_DQS_ID and save.



SAP Library

18

3. Select the copied configuration of the component MDG_DQR_OVP.

4. Change the copy of the configuration MDG_DQR_FAILED_REC_LIST_UIBBby 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 qualityremediation 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 actionCHANGE_DQR in customizing activity Create Business Activity and assign it to achange request type in Customizing activity Create Change Request Type .

5. To provide the DQR function to your users add the Web Dynpro applicationMDG_DQR_OVP with the copy of the configuration MDG_DQR_OVP to the rolemenu.

With the description above you configure the DQR application to include the UI of the dataquality tool. The URL to this UI is defined in the Customizing activity Define Data QualityService . To filter the displayed objects with errors the UI of the data quality tool can raiseevents that are provided to the DQR application with the implementation of the BAdI EventHandling for Data Quality Remediation . This filtering can also be done with dropdown lists.The configuration template for this variant is provided in the application configurationMDG_DQR_OVP_FILTER and component configuration MDG_DQR_FILTER_UIBB. Toconfigure this variant go through this configuration process and use application configurationMDG_DQR_OVP_FILTER instead of MDG_DQR_OVP in step 2. In this case you need tocopy and adapt the component configuration MDG_DQR_FILTER_UIBB by setting the feederclass parameter to the data quality service ID you want to use for your DQR process.

Documents

Class Items in BOMs