This page provides domain-specific information on how to add fields or capabilities to your solution, reconfigure your solution, or integrate your solution within your software landscape. The documents are typically enriched with screenshots, instructions, and - where necessary - sample code.
The documents cover different releases from EhP5 to MDG 8.0; their exact validity is mentioned for the individual document.
Disclaimer
SAP code or application samples and tutorials are NOT FOR PRODUCTION USE . You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| Fiori | |||
| This document covers the extensibility concept for SAP Fiori MDG applications. The document contains references to the documentation for extension of other layers. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) | |
| SAP HANA-based Analytics | |||
| New guide for Smart Business and SAP HANA-based analytics covering features available after SAP Master Data Governance 7.0 (SP05). Complements the next guide on the list. This guide shows how you can analyse change request data as well as additional data that is directly linked to the change request data. | MDG7.0 (SP05) | MDG 8.0 | |
| SAP HANA-based Analytics for SAP Master Data Governance 9.0 | This guide explains how the change analysis of critical attributes of master data objects can be used for analytical scenarios in the master data governance process. | MDG 9.0 | |
Configuration and Use of Smart Business for SAP Master Data Governance | SAP Smart Business applications provide insight into the real-time operations of your business by collecting and displaying KPIs directly in your browser. To do this, SAP Smart Business combines the data and analytical power of SAP HANA with the integration and the interface components of SAP Business Suite. To enable the implementation of SAP Smart Business applications in SAP Master Data Governance, this guide describes the tasks and concepts necessary for initial setup and configuration of all components in the SAP Smart Business system landscape. | MDG7.0 (Feature Pack) | MDG7.0 SP04 |
Extending SAP HANA-based Analytics for SAP Master Data Governance - Integrating Object Counters | This guide shows how you can analyse change request data as well as additional data that is directly linked to the change request data. | MDG7.0 (SP05) | MDG 8.0 |
This document explains how to build HANA-based calculation views that can be used to analyse whether data replication occurs in accordance with agreed KPIs. | MDG7.0 (Feature Pack) | MDG 8.0 | |
| HANA | |||
| The SAP HANA-based search of master data is one of several ways of searching master data that reside in SAP HANA. You can create a HANA view and configure it to explore the master data or to perform a drilldown search. This guide describes how you can flexibly extend the drilldown application with custom buttons and hyperlinks that enable navigation to other UIs. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) | |
SAP | You can use this document to implement the access class interface for your reuse model so that the HANA-based search of master data can retrieve both active data and inactive data. | MDG7.0 | MDG7.0 (Feature Pack) |
| The SAP HANA-based search of master data is one of several ways of searching master data that reside in SAP HANA. You can create a HANA view and configure it to explore the master data or to perform a drilldown search. If the HANA view contains attributes with technical keys (such as Country Keys or Region Codes), the drilldown search results display technical keys instead of text descriptions. To ensure that text descriptions display in the browser panes and result sets of the drilldown search, you must manually modify your generated SAP HANA views in SAP HANA Studio by adding text joins to the corresponding text tables. | MDG7.0 | MDG7.0 (Feature Pack) | |
| BI Content | |||
With MDG 6.0 EHP6, SAP supports BI Content; reports and functions that analyze how effectively change requests are processed in your organization. You must activate the content first, as described in this document. You can analyze change requests from the following perspectives:
| EhP6 | MDG7.0 (Feature Pack) | |
| User Interface | |||
How to use a customer specific UIBB in MDG application 'Create Change Request' | This tutorial describes how to use a customer specific UIBB in the MDG application 'Create Change Request' (WebDynproApplication usmd_crequest_create). | MDG6.1 | MDG 8.0 |
Customizing Navigation for Change Request Steps in the User Interface for Multi-Record Processing | In multi-record processing, you can define different user interfaces for the same change request step. For example, you can make the initial step appear different to the approval step or the processing step. | MDG6.1 | MDG7.0 (Feature Pack) |
| Creating a UI Configuration and Integrating it with the MDG Communicator | You can copy an existing UI Configuration and adapt it to your needs. As an example, we copy the Component Configuration of the Overview Floorplan (OVP) USMD_SF_CARR_OVP and delete the attachment User Interface Building Block (UIBB). | MDG6.1 | MDG 8.0 |
| Customizing Navigation for Change Request Steps in the User Interface for Single-Object Processing | During Single Object Processing, you want to define different User Interfaces for individual Change Request steps. For example, in a Supplier Scenario you might want one step to make the general data visible, and, in another step you might want only the purchasing organization data to be visible. | MDG6.1 | MDG 8.0 |
| How to Add Fields to the Change Request UI (MDG EhP6) | This article describes how you can do this with the new UI technologies that are used by the domain specific Web Dynpro applications for material and supplier with enhancement package 6. | EhP5 | MDG 8.0 |
| Hiding Fields in the Change Request User Interface | You want to hide fields of the change request UI. For example you do not want to allow users to enter a due date when submitting a change request. | EhP5 | MDG6.1 |
| Enhancement of the User Interface Building Block for Change Requests | In this example, you require an extra parameter to control the process and the workflow for change requests - Requesting Business Area. You do not model this parameter is as part of the MDG data model because it is not part of the business context. Instead, you store the parameter together with the change request number in a Z-table. In addition, you place the parameter on the change request UIBB on the tab for the general data. The user can select from business areas defined in Customizing. (The relevant data element is GSBER and the relevant table is TGSB). When a user opens the change request for display, the Requesting Business Area parameter is displayed and cannot be changed. | EhP6 | MDG 8.0 |
| Video tutorial on how to create a lean request step with a role-specific UI and less strict data validations in MDG for Custom Objects. | EhP6 | MDG 8.0 | |
Default | This document describes how to initialize fields of the Single Object Maintenance UI with default values. Different techniques for custom UIs and SAP-owned UIs are discussed. | MDG7.0 (Feature Pack) | MDG 8.0 |
| API | |||
| Updated January 2014 Application Programming Interface Customizing Guide | Depending on the software release, MDG offers different APIs for consumption with different functional scopes. This guide describes the Application Programming Interfaces for each release. | EhP5 | MDG 8.0 |
Updated June 2014How to Read Approval Info for Master Data by Calling MDG API | This document applies for all MDG master data. It is especially useful for the G/L Account because of the SOX (Sarbanes-Oxley Act) compliance. In the G/L Account area, MDG-F is also known for its SOX compliance. SOX requires thorough tracking of changes with approval processes. This document shows you how to get relevant approval information for the G/L Account by calling all MDG APIs. | EhP5 | MDG 8.0 |
Workflow | |||
| How-to handle Entities with type 4 in BRF+ | This article explains how entity types 4 with 1:1 and 1:N cardinality are handled in BRF+ by an small example. | EhP5 | MDG 8.0 |
| How to Check or Derive an Attribute Value in MDG Using BRFPlus | With SAP Master Data Governance you can use BRFplus to define rules for checking attribute values or to derive them. This step-by-step guide shows you how to create such a rule. This procedure can be applied to any MDG application or data model. The MDG for Custom Objects Example Scenario is used as an easy to understand basis for this how to document. | EhP5 | MDG 8.0 |
BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | MDG 8.0 | |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | MDG 8.0 |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | MDG 8.0 |
BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 | MDG 8.0 | |
Sending an E-mail notification from the rules-based workflow | EhP5 | MDG 8.0 | |
Setting up extended workflow notifications in order to send out e-mails when new workflow items are generated (also allows you to include a link to the workflow inbox in the generated e-mail). | EhP5 | MDG 8.0 | |
| How to add an additional task to the inbox | You create own workflow definitions with new workflow tasks and want to see the corresponding workitems in the MDG inbox. | EhP5 | MDG 8.0 |
Description how to trigger an Email to all users involved once a change request is finally approved. The Email contains a protocol of the change request incl. changes and associated metadata. | EhP5 | MDG 8.0 | |
| Extensibility | |||
Description how to extend new attributes for entity type | EhP5 | MDG 6.1 | |
| SAP How-To Guide Develop a Custom Master Data Object in SAP Master Data Governance (ERP 6 EhP5 and EhP6) | Many companies want to manage custom object in a central Master data system to be able to harmonize this information across the landscape. Custom objects can be individual defined object such as assets or locations. Custom objects are typically less complex master data object with a small and simple data model. | EhP5 | MDG7.0 (Feature Pack) |
| This tutorial describes how to create an enrichment spot implementation with user interaction in Master Data Governance. The implementation is called when executing Checking for non-existent objects in the object list of a change requesta consistency check in the Single Processing UI (WebDynpro Application usmd_entity_value2). | EhP6 | MDG 8.0 | |
| Enrichment of Master Data in MDG – Generic Guide and Sample Implementation | You can use the enrichment framework to enrich the MDG data with external services or with internal logic. The enrichment framework also supports embedding of specific UIs for enrichment. The first section of this guide provides a generic overview of how enrichment works. The second section provides an example of address validation. | MDG7.0 (Feature Pack) | MDG 8.0 |
| Checking for non-existent objects in the object list of a change request | SAP Master Data Governance offers the feature to include the keys of objects that do not yet exist in the object list of a change request. Rather than waiting until all data is ready before specifying changes, you can work simultaneously on object creation and the processing of the change request. This document shows how to implement BAdIs that provide warnings and errors about non-existent objects | EhP6 | MDG 8.0 |
| Value Mapping | |||
You want to maintain mass value mapping (customizing mapping) via file export/import. | EhP5 | MDG 8.0 | |
| Data Replication | |||
You want to replicate data from your customer-specific data model to target systems (using flex option). | EhP5 | MDG 8.0 |