how to master data governance for material adjust mdg...

SAP

How-To Guide

Master Data Governance

for Material

How To...

Master Data Governance for Material

Adjust MDG Homepage

Applicable Releases:

EhP6, MDG 6.1

Version 1.0

October 2013

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained

herein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

Document History

Document Version Description

1.00 First official release of this guide

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly as

they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

Table of Contents

1. Business Scenario ............................................................................................................... 1

2. Background Information ..................................................................................................... 1

3. More Information ................................................................................................................. 1

4. Adjust the Homepage for MDG .......................................................................................... 2

4.1 Users Can Personalize Their Own Homepages ........................................................... 2

4.2 Customize the Homepage – For All Users of the Role ................................................ 3

4.3 Add a new folder with new entries ................................................................................ 8

4.3.1 Create the Folder with the Services ................................................................. 8

4.3.2 1st version: Enhancement of the Homepage only ............................................ 8

4.3.3 2nd

Altenative: Enhancement of Catalog and Homepage .............................. 12

4.3.4 Adjusting the Homepage ................................................................................ 15

4.4 Offer Additional Content using CHIPs for The Users to Choose ................................ 16

4.4.1 Alternative Link List CHIP .............................................................................. 16

4.4.2 Add Analytic Reports ..................................................................................... 18

4.5 Create New Roles for Menus with New Homepages ................................................. 18

4.6 Technical Background – How PFCG, Homepage, Catalog, and Launchpad are

linked .......................................................................................................................... 21

4.6.1 Launchpad ..................................................................................................... 21

4.6.2 Information: Elements Used to Control the Homepage for the MDG Domain22

4.6.3 Catalog Page ................................................................................................. 24

4.6.4 Troubleshooting tip ........................................................................................ 24

EhP5 How To... MDG-M: Extend MDG-M UI (EhP6 on)

1. Business Scenario

SAP Master Data Governance for Material (MDG-M) provides business processes to find, create,

change, and mark material master data for deletion. It supports the governance of material master

data on a central hub and the distribution of material master data to connected operational and

business intelligence systems.

The processes are workflow-driven and can include several approval and revision phases, including

collaboration between all users participating in master data maintenance.

This guide describes how to extend the Homepage of Master Data Governance for Material to display

additional links.

2. Background Information

EHP6 Application Help (incl. configuration documentation):

http://help.sap.com/erp2005_ehp_06/helpdata/en/7c/a94fabb8274d738d994c2bc1c4cf7a/frameset.htm

MDG 6.1 Help: http://help.sap.com/mdg61

3. More Information

Enhancement of Master Data Governance Content in EHP6:

http://help.sap.com/erp2005_ehp_06/helpdata/EN/ab/05f68761744157b40f81af8689b700/frameset.htm

MDG Extensibility Guides on SDN:

http://scn.sap.com/docs/DOC-7858

How to Create, Enhance, and Adapt Floorplan Manager Applications (FPM):


http://help.sap.com/erp2005_ehp_06/helpdata/en/7c/a94fabb8274d738d994c2bc1c4cf7a/frameset.htm

http://help.sap.com/mdg61

http://help.sap.com/erp2005_ehp_06/helpdata/EN/ab/05f68761744157b40f81af8689b700/frameset.htm




4. Adjust the Homepage for MDG

Homepages are part of every MDG role by default. They are included using the (menu) role definition

in transaction PFCG. They can be adjusted to your needs like other parts of the UI using WebDynpro.

Technically the ABAP Page Builder is used to implement the homepage.

You can adjust the UI on the following levels:

The possibilities for Configuration and Customizing are almost the same, both are transportable, but

you need to be careful with configuration and you should follow the enhancement guides in order not

to run into conflicts with future upgrades. Therefore it is recommended in our example when working

on the homepages to use the Customizing option. This does not require developer authorization and is

also fully transportable.

Technical Hint: The configuration using the Page Builder is similar but not identical to the configuration

using the Floor Plan Manager (FPM).

4.1 Users Can Personalize Their Own Homepages

If new common changes have been introduced it is possible to reset the personalization to the

common standard settings:


4.2 Customize the Homepage – For All Users of the

Role

Until MDG EhP6 the structure of the user menu was displayed in CHIPs (Collaborative Human

Interface Part). Technically these were PFCG CHIPs with links to PFCG folders through aliases. In

MDG 6.1 we developed a more flexible concept that allows an administrator to better control the

personalization options.

In addition, the concept allows publishing the menu and homepage in an SAP Enterprise Portal

environment.


We now deliver 3 parts that are linked together:

Homepage

Catalogpage

CHIPCatalog

Launchpad

BCV

Some more background information on how SAP set up and linked those structures can be found in

the last chapter. In brief:

You can customize and configure the catalog page based on the central CHIP catalog

You can customize and configure the homepage based on the available CHIPs from the catalog page

You define the available content of the CHIPs using the launchpad

Changes in the Launchpad are immediately visible on the homepage

Any changes on the homepage itself can be reset to standard

Use case:

You want to add one special change request type for all users of a role to an existing CHIP as an

additional link.

Example:

Add a “Special Create Material” entry that links to the Change Request type: “ZRMAT01”

Step-by-step instruction:

1. Customize the Launchpad that exists for the domain: for the governance data model “MM” it is

the role “MDG_MAT” with instance “HOME”. You can find out this key information by starting

customizing and opening the “Define Link List”. The ‘Role’ and ‘Instance’ contains the name of

the Launchpad to be enhanced using the transaction LPD_CUST.


2. Start Tx LPD_CUST and navigate to the change mode of role “MDG_MAT”, instance “HOME”:


3. Mark an entry and use the right mouse button to copy and paste the entry:

4. Now change the text of the copied entry and show the advanced parameters:


5. Open the BI parameters and add and set the parameter for the CR type:

6. The supported parameters can be found out using the drop-down help for a WebDynpro

Application in transaction PFCG.

7. Save the Launchpad.

If you now refresh your homepage for Material, the new entry is available immediately:


4.3 Add a new folder with new entries

Use case:

You want to add a new section with new links to launch additional transactions directly from the

homepage.

Example:

Add a “Special processing” that links to the required change request types, for example, one per

material type.

Step-by-step instruction:

Use transaction LPD_CUST to view the Launchpad for the domain: for governance model “MM” it is

role “MDG_MAT” with instance “HOME”

4.3.1 Create the Folder with the Services

Add a new folder “MATTYPE Processing” on the left.

For a quick start we copy the created “special create” from previous chapter, copy it a second time,

and rename the two entries. In the example we do not adjust the parameters.

This new folder is not yet reflected after the refresh of the homepage for material since they require

new CHIPs. You must bring them into the catalog and then from there onto the homepage using

customizing.

Under certain circumstances the entries are displayed after the refresh since the page builder mixes

and merges the existing entries of the Launchpad.

4.3.2 1st

version: Enhancement of the Homepage only

You drop another LPD CHIP on the homepage and adapt the link to point to the newly added folder.

The disadvantage of this solution is that the catalog page doesn’t contain the new CHIP. If the CHIP is

deleted by mistake from the homepage, its configuration has to be done again, instead of copying it

from the catalog page.


1. Start the customizing of the homepage and open the CHIP Catalog. You cannot see your new

“Special Processing” folder there:

2. Drag and drop any of the LPD CHIPs from the catalog to the homepage:


3. Open in the tray menu the “Define Link List” and search for the created folder:

4. Accept the changed Folder ID and change the Title text:


5. Save your changes:

6. Refresh your brower window displaying the homepage or click on the SAP Icon. You can now see

the changes on the homepage (for all users):


If the LPD CHIP was deleted by mistake from the homepage it cannot be restored easily from the

catalog page. The previously described setup has to be done again. Therefore the 2nd

alternative

below is preferred.

4.3.3 2nd

Altenative: Enhancement of Catalog and Homepage

If you want the users to choose from a number of CHIPs from the catalog instead of going through the

first alternative, you can use the customizing of the catalog in order to enhance the available CHIP

catalog.

The easiest way to reach the catalog for changes is to add menu favorite for a Web Dynpro

Application:


You can also find those component configurations using the WD component WDR_CHIP_PAGE.

Open transaction SE80, open the WDC, and navigate in the component configuration folder to the

following entries:

MDG_BS_MAT_HOME_PFCG_03 represents the homepage that is included in the PFCG role

MDG_BS_MAT_HOME_CATALOG_03 is the MDG specific catalog page.

1. Start the customizing for the catalog page:


2. Open the CHIP catalog. The CHIP catalog contains all installed CHIPs (resp. CHIP provider)

provided by SAP. Open the branch “Web Dynpro CHIPs” and navigate to “Launchpad Link List”:

3. Drag and Drop to the left, Define Link List, add parameters, and change Title according to the direct

change described above:


4.3.4 Adjusting the Homepage

Start the homepage, switch to customizing mode and follow one of the following options:

Start the role using NWBC and use the customizing option described above:

Stay in transaction PFCG on the “Home” node and using the “Execute Node” button from the menu open the homepage in the browser without the NWBC surrounding:

Here you can start configuration, customizing, or personalization as from the NWBC homepage.

Note:

Based on your authorizations you also can switch between the three options: personalization,

customizing, and configuration:

In the customizing mode you can arrange, adjust, and configure the single parts of the homepage.

Open the CHIP Catalog for a list of the available CHIPs. This list is based on the definition of the

catalog page (here MDG_BS_MAT_HOME_CATALOG_03), changed in the previous step:


You can adjust individual parts using the tray menu with context-specific options for every CHIP.

You can also change attributes such as size, behavior, and layout using right-mouse button and

choosing “Settings for current configuration”.

4.4 Offer Additional Content using CHIPs for The Users

to Choose

4.4.1 Alternative Link List CHIP

The “Launchpad Link List” CHIP can be used for the homepage with both the NWBC and the Portal.

The configuration, that is, the list of visible links, of this type of CHIP doesn’t adapt automatically to the

current PFCG role.

Instead of the “Launchpad Link List” CHIP you can use the “PFCG Link List” CHIP (also listed in the

folder Web Dynpro CHIPs). It doesn’t work in the context of the Portal. It directly reflects the definition

of a folder of the PFCG role. The displayed lists and their sequence is the same as in the menu of the

PFCG role.


The “PFCG Link List” is assigned with the PFCG Alias (written as tag: “{PBA=<alias>}”) to a folder of a

PFCG role:

The PFCG role contains this tag in the attribute ‘Application Alias’:

The homepage and the referenced PFCG folder have to be part of the same PFCG role.


4.4.2 Add Analytic Reports

Use case:

You want to offer the users additional graphical reports that they can include on their homepage.

Example:

Add the “All Change Request” query with default parameters.

Step-by-step instructions:

1. Start to enhance the catalog page as described above: Start the catalog page and switch to

customizing mode.

2. Open the CHIP Catalog.

3. Open the folder “Business Context Viewer CHIPs” and place the CHIP “My Change Request”

on the catalog page using Drag & Drop.

4. Change the title to “All Change Requests” and set the parameters as shown below:

Depending on other applications using the Business Context Viewer (BCV), the list of available CHIPs

can be larger. Every BCV CHIPs represents a query view, displaying a BCV query. How to configure

and – if necessary – to implement own BCV query is described in the corresponding documentation.

Now the (power) user can start the customizing mode of the homepage and select the newly added

CHIPs from the catalog.

4.5 Create New Roles for Menus with New Homepages

If you want different roles to have different homepages there are two options:

If there are smaller differences in the menus, you can use the “PFCG Link List” CHIP instead of the “Launchpad Link List” CHIP. In this case the homepage cannot be used within the Portal

If there are larger differences you have to create a homepage for each PFCG role. Dependent on the differences between the PFCG roles, you can create separate folders in the Launchpad role (in standard MDG_MAT) for smaller differences or create separate Launchpad roles for each PFCG role for larger differences.


From a functional point of view is there no difference. The method influences only the complexity of maintenance.

1. To create a new homepage, copy the delivered one.

2. Start transaction SE80, select the Web Dynpro Configuration WDR_CHIP_PAGE, and

navigate to the component configuration MDG_BS_MAT_HOME_PFCG_03 (or

MDG_BS_MAT_HOME_CATALOG_03 to copy the catalog).

3. Double click on the configuration, press the button “Display Configuration” and copy it:

The new homepage references the standard homepage.

4. If the new homepages should reference a new catalog page, you must copy the catalog page.


For each homepage you have to create an application configuration. Use the delivered one as an

example or copy it if needed. The application configuration uses in standard the same name as the

component configuration: MDG_BS_MAT_HOME_PFC_03.

To change the reference to the homepage call transaction SE80, select the Web Dynpro Configuration

WDR_CHIP_PAGE and navigate to the Web Dynpro Application ‘wdr_chip_page’ and the Application

Configuration “MDG_BS_MAT_HOME_PFCG_03”.

Here you can change the referenced catalog page.


4.6 Technical Background – How PFCG, Homepage,

Catalog, and Launchpad are linked

4.6.1 Launchpad

If you want to find out which is the proper Launchpad, you have to start the customizing mode for your

homepage and use the option “Define Link List” of the tray menu. The fields “Role” and “Instance”

contain the name of the Launchpad:


4.6.2 Information: Elements Used to Control the Homepage

for the MDG Domain

1. The PFCG Menu Role contains a node „Home“ that links to the WebDynpro Application WDR_CHIP_PAGE with the Application Configuration MDG_BS_MAT_HOME_PFCG_03:

From here you have 3 options for navigation:

Since all of them are Configurations, you could now start to change standard SAP entries.

Therefore it is not recommended to make changes here in this configuration but use the Page

Builder Customizing as described previously.


2. You can start the Application Configuration from within PFCG node details. You can see that the WDR_CHIP_PAGE has a sub-node CHIP_CATALOG that is delivered with the component configuration MDG_BS_MAT_HOME_CATALOG_USAGE_03:

Using the two links you can navigate to their component configurations:

The first link leads to component configuration MDG_BS_MAT_HOME_PFCG_03. You see the defined structure of the page itself (like the frame to include the links and graphics):

The second link leads to the component configuration specifying the catalog page to use.

The configuration context contains a context-selection-parameter PAGE_CONFIG with the value MDG_BS_MAT_HOME_CATALOG_03 this is the SAP-delivered catalog of allowed services:


4.6.3 Catalog Page

The catalog page is intended to allow the administrator to restrict the CHIPs available for MDG. The

homepage can be maintained by a small set of super users depending on business needs.

The homepage references the catalog page. Only CHIPs contained at the catalog page are available

to configure the homepage. The layout of the catalog page itself is completely independent from the

homepage.

If the CHIPs are moved with drag and drop from the catalog to the homepage, they are copied with

their configuration to the homepage. A later change of the CHIP configuration at the catalog page is

not reflected by the copies of the CHIP at the homepage.

The catalog page can contain several configurations of the same type of CHIP (For example,

“Launchpad Link List”).

If a CHIP is removed from the catalog, it is not automatically removed from the homepage. This has to

be done manually in a second step. The same catalog page can be referenced by several

homepages. Any homepage can have only a single catalog page.

The catalog of the catalog page is the central unrestricted catalog of CHIPs.

If it is necessary, this reference list of catalogs can be cascaded, that is you can define a company

catalog page of CHIPs that are used by department catalog pages, which are in turn used by

homepages as catalog.

4.6.4 Troubleshooting tip

If you change the configuration you might get warnings that the customizing is outdated (but see recommendation on the top to user customizing preferably). To clear these messages choose option “Reset to Default” after starting the customizing mode:

If changes of the Launchpad do not affect the users homepage: Call transaction LPD_CUST, navigate to the problematic Launchpad, and use from the ‘Extras’ menu choose the function ‘Delete End-User Launchpad’.

how to master data governance for material adjust mdg...

Documents