For Releases EhP5 to MDG7.0
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.
Application Framework including Custom Objects
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| HANA | |||
New November 2013 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 |
New November 2013 | 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 |
| BI Content | |||
New November 2013 | 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 |
| User Interface | |||
New November 2013 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 | MDG7.0 |
New November 2013 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 |
| New November 2013 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 | MDG7.0 |
| New November 2013Customizing 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 | MDG7.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 | MDG7.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 | MDG7.0 |
| 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 | MDG7.0 |
| A demo of how to remove a field from the user interface and remove the corresponding validations. | EhP6 | MDG7.0 | |
| API | |||
| Updated November 2013 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 | MDG7.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 | MDG7.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 | MDG7.0 |
BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | MDG7.0 | |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | MDG7.0 |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | MDG7.0 |
BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 | MDG7.0 | |
Sending an E-mail notification from the rules-based workflow | EhP5 | MDG7.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 | MDG7.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 | MDG7.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 | MDG7.0 | |
| Extensibility | |||
Description how to extend new attributes for entity type | EhP5 | MDG7.0 | |
| SAP How-To Guide Develop a Custom Master Data Object in SAP Master Data Governance (ERP 6 EhP5 amd 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 |
| 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 | MDG7.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 | MDG7.0 |
| Value Mapping | |||
You want to maintain mass value mapping (customizing mapping) via file export/import. | EhP5 | MDG7.0 | |
| Data Replication | |||
You want to replicate data from your customer-specific data model to target systems (using flex option). | EhP5 | MDG7.0 |
Financial Data
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| New November 2013 SAP How-To Guide for MDG-F - Overview | This guide provides you with foundation knowledge about financial data and its related governance solution financial governance (MDG-F). | MDG7.0 | MDG7.0 |
New November 2013 Using the Master Data Management Generic Extractor for Initial Load in MDG-F
| Foundation knowledge to perform an initial load of master data into the financial governance (MDG-F) data model. | MDG7.0 | MDG7.0 |
New November 2013 Extending the Data Model by New Fields in MDG-F
| Foundation knowledge to extend the MDG-F data model by new fields. | MDG7.0 | MDG7.0 |
New November 2013 ALE Replication from MDG Hub to ERP Using the Same Client in MDG-F
| Foundation knowledge for setting up an ALE scenario for the replication of MDG_F entities into the same physical client system. (MDG hub and ERP system share the same client.) | MDG7.0 | MDG7.0 |
| Enhancing the change request user interface in MDG-F | Example how to display an additional account form in the create change request application only when the A-segment account is processed in the change request. | EhP5 | MDG6.1 |
| Remote Where-Used List: Example Implementation | This guide demonstrates how to use the remote where-used-list in MDG. The standard delivery includes a generic user interface and an example Business Add-In (BAdI) implementation for the ACCOUNT entity type of the 0G data model. In this document, we use the default implementation as an example of all implementations. | EhP6 | MDG6.1 |
| In this article we look at two different approaches for extending the 0G data model of MDG-F. In the first section, we extend the 0G model directly. In the second section, we extend a copy of 0G. Finally, we compare the advantages and disadvantages of the two approaches. | EhP6 | MDG6.1 |
Material Data
Title/Group | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
Extensibility | |||
| New November 2013 Create new User Interfaces for Multiple-Record Processing | Multiple-Record Processing offers a streamlined process, with a UI that enables you to create change requests for multiple records with greater efficiency. This guide shows how to create new configurations for material. | MDG7.0 | MDG7.0 |
You use this guide to extend the MDG-M data model by a new entity type. The attribute values of the new entity type will be copied to the corresponding ERP tables (reuse option) after activation of the change request. | EhP6 | MDG7.0 | |
| Extend MDG-M Data Model by a New Entity Type (Standard-ERP Table, Reuse Option) | You can use this guide to extend the MDG-M data model by a new entity type. The attribute values of the new entity type are copied to the corresponding ERP tables (reuse option) after activation of the change request. For additional information about how to extend the UI, see : | EhP6 | MDG7.0 |
| You can use this guide to extend the MDG-M data model by a new field. The system copies attribute values of the new field to the corresponding ERP table (reuse option) after activation of the change request. | EhP6 | MDG7.0 | |
| Extend MDG-M Data Model with Customer Z-Fields from Existing Tables | This guide describes how to extend the preconfigured content of MDG-M with customer z-fields from the existing backend tables. | EhP6 | MDG7.0 |
This guide describes how to extend the UI of Master Data Governance for Material to display additional data. | EhP6 | MDG7.0 | |
| Adjust MDG-M Homepage | This guide describes how to extend the Homepage of Master Data Governance for Material to display additional links | EhP6 | MDG7.0 |
| Extend Model with Complex Backend Data (e.g. MLAN) | This guide describes how to extend the preconfigured content of Master Data Governance for Material, contained in the data model MM, with Tax Data. | EhP5 | MDG7.0 |
| Central guide for SAP MDG-M extensibility | Includes topics such as field extensions, table extensions, UI adaptation, etc. | EhP5 | EhP5 |
This guide describes how to adapt the generic UI of Master Data Governance for Material in EhP5. | EhP5 | EhP5 | |
| File Up and Download | This How To Guide shows how the CSV file download and upload functionality can be used for MDG materials. | EhP5 | EhP5 |
BRF+ | |||
This how-to guide gives an overview of the checks which are used in MDG-M and gives examples for checks and derivations built in BRF+. | EhP5 | MDG7.0 | |
Workflow | |||
| Rule Based Workflow with Partial Activation | When using the rule-based workflow, the process pattern '06 Activation (Bypass Snapshot)' means that the material is activated, even if the material record was changed in the backend system since the change request was created. Any backend changes are lost upon activation. You can adjust this behavior with SAP Note 1797009. | MDG6.1 | MDG7.0 |
| Distribute Material Immediately | This guide describes how to set up the system to enable immediate distribution of changes in the material master during activation of the material, which is descripted in SAP Note 1764329. | EhP6 | MDG7.0 |
BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | MDG7.0 | |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | MDG7.0 |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | MDG7.0 |
BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 | MDG7.0 | |
Sending an E-mail notification from the rules-based workflow | EhP5 | MDG7.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 | MDG7.0 | |
| Performance | |||
| Performance Tweaks | Besides the official sizing guide for customer system landscapes, this guide focuses on the MDGM application and how it can be accelerated. The findings are based on the “Create Material” scenario but can also be applied to the “Change Material” scenario. | MDG6.1 | MDG7.0 |
Data Models | |||
| Data Model Metadata | A zip file containing a spreadsheet for the Material data model. This spreadsheet contains information about the data model, the MaterialERPBulkReplicateRequest and related backend data. | EhP5 | MDG7.0 |
| Search | |||
| Enhance the Material Search (EhP5) | Adding extra fields to the search template | EhP5 | EhP5 |
| Replace Enterprise Search by DB or alternative search provider | For the standard delivery scope, MDG-M requires a fully configured Enterprise Search (ES). To mitigate this dependency, this guide describes how to adapt MDG-M so that another search provider can be used. The example focuses on integrating a Database base search (DB search), but other search providers can be supported in a similar way. | MDG6.1 | MDG7.0 |
| Enhance the Material Search (EhP6 on) | In EhP6 MDG for Material master data domain addresses only Basic, Descriptive data & Classification data of the Material but it is possible to extend the data model. If you want to search also with these new fields you have to extend the search too. | EhP6 | MDG7.0 |
| Data Import | |||
| Use the Data Import Framework with a CSV File | You can use the Import Master Data service to import files containing material and classification data to the Master Data Governance system. The data from these files can update existing master data records or create new ones using the options available in the Import Master Data service. This guide describes how to use the Data Import Framework to upload material data from a CSV-file using a BAdI for the file conversion. | EhP6 | MDG7.0 |
Customer / Supplier Data
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| Extending SAP Master Data Governance for Supplier - Part 1 | Data Model Extensions | EhP5 | EhP5 |
| Extending SAP Master Data Governance for Supplier – Part 2 | User Interface Extension | EhP5 | EhP5 |
| SAP How-To Guide: Extend the MDG Business Partner - Overview | This guide provides you with the foundation knowledge you need to extend business partner data and its related governance solutions: customer governance (MDG-C) and supplier governance (MDG-S). | EhP6 | MDG7.0 |
| You can use this guide to extend the MDG Business Partner (including MDG-C and MDG-S) by creating and registering a custom handler class. | EhP6 | MDG7.0 | |
| SAP How-To Guide: Extend the MDG Business Partner - Create or Redefine a UI Feeder Class | You can use this guide to extend the MDG Business Partner by creating or redefining a feeder class for the user interface. | EhP6 | MDG7.0 |
| SAP How-To Guide: Extend MDG-S Data Model by a new Entity Type (Flex Option) | You can use this guide to extend the MDG-S /MDG-C data model by a new entity type. The attributes of the new entity type only exist in the MDG context and not in the ERP data models (flex option). | EhP6 | MDG7.0 |
| SAP How-To Guide: Extend MDG-S Data Model by a New Field (Reuse Option) | You can use this guide to extend the MDG-S data model or the MDG-C data model by adding attributes that already exist as database fields in the appropriate customer include of the SAP Business Partner / Vendor / Customer (MDG reuse option). | EhP6 | MDG7.0 |
| SAP How-To Guide: Extend the MDG Business Partner – Node Extension (Reuse Option) | You can use this guide to extend the data model for supplier governance (MDG-S) or for customer governance (MDG-S) by creating a new node, using the reuse entity type. | EhP6 | MDG7.0 |
| SAP How-To Guide: Extend the MDG BP – Ensure Auto-creation of ERP Vendors with MDG-S | You can use this guide to extend supplier governance (MDG-S) by ensuring that every time a user creates a supplier using the main user interface for supplier governance, the solution always creates an ERP vendor record. | EhP6 | MDG7.0 |
You can use this guide to extend the customer governance and supplier governance so that MDG users who are only interested in the environment of their local business system only get to see entries for this local business system (such as company codes and payment terms). | EhP6 | MDG7.0 | |
| Installing, Configuring, and Using the Excel Upload for Business Partner | You can upload business Partner data in batch to MDG-S from a .csv file. This document provides the installation and configuration instructions, a link to the relevant source code and excel file, and instructions on how to use the excel upload. | EhP6 | MDG7.0 |
| Archived Guides | |||
| SAP How-To Guide: Extend MDG-S / MDG-C Data Model by a New Field (Reuse Option) | You can use this guide to extend the MDG-S data model or the MDG-C data model by adding attributes that already exist as database fields in the appropriate customer include of the SAP Business Partner / Vendor / Customer (MDG reuse option). | EhP6 | |
| SAP How-To Guide: Extend MDG-S / MDG-C Data Model by a New Entity Type (Flex Option) | You can use this guide to extend the MDG-S /MDG-C data model by a new Entity Type. The attributes of the new entity only exist in the MDG context and not in the ERP data models (flex option). Note: This is not the right guide for you if you need an extension where the data is stored in tables outside of MDG (i.e. Partner Functions). | EhP6 | |
| Data Models | |||
A zip file containing separate spreadsheets for Business Partner, Supplier, and Customer. Each spreadsheet contains information about the following:
| EhP6 | MDG7.0 |
Integration Scenarios
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| A cross-system master data process for supplier | Implementation details for a simplified cross system Supplier On-boarding scenario leveraging SAP's Enterprise Master Data Management portfolio consisting of SAP NetWeaver Master Data and SAP Master Data Governance. The overarching process is modeled using SAP NetWeaver Business Process Management. | EhP5 | MDG7.0 |
| Customizing Integration Between MDG and ERP | The intention of this document is to support SAP MDG implementation projects with general guidelines, templates and links to documentation that can be a basis for the synchronization process – including lists of customizing objects that might be affected. | EhP6 | MDG7.0 |