Master Data Governance provides an out-of-the box solution for the central management of various master data objects such as financial objects, supplier and material. But SAP Master Data Governance also provides the flexibility to customize the solution, in cases where the pre-delivered content does not fully match customer requirements. You can use this guide to extend the MDG-M data model by a new entity. The attribute values of the new entity type will be copied to the corresponding ERP tables (reuse option) after activation of the change request.
↧
SAP How-To Guide: Extend MDG-M Data Model by a New Entity Type (ERP Table, Reuse Option)
↧
SAP Master Data Governance: Copying of Materials in Multi-Record Processing
This recording shows how to apply the copy materials feature in multi-records processing (available as of release 8.0).
↧
↧
Solving Performance Problems in Transactional Fiori Applications
This blog contains some of the points that can be considered to improve performance of complex Fiori applications. Complex here refers to too many fields on the Fiori UI which indirectly means an oData service with more than 20 entities and each entity having more than 10 attributes. We are talking about services which have more than 300 attributes. The concepts mentioned here are based on the experience which we had during our developments in such complex applications
Master Detail Screen: One of the templates available in Fiori is the master detail template. Application built using this would contain a Master list on the left hand side and a detail screen on the right.
Master List
Any Fiori application is launched via the Launchpad tile. Hence the Initial load time is the time taken by the application to render its initial page once we click on the tile. In a master detail screen this would mean time taken for getting the master list + time taken for fetching the details of the lead selected record
- Evaluate whether time taken for fetching the list takes more time in case it does then we can consider pagination of the list. Thus instead of fetching 100 records we can fetch 10 records at a time which is supported using the $top and $skip options within the oData services
- In case it ends up that even fetching 10 records takes more time then we can fetch only the first record and in parallel execute the two queries: fetch of data on the right hand side and fetch the remaining records in the first 10 records. Parallel execution is possible by using jquery deferred concepts.
Example coding:
// create a deferred object var deferLoad = jQuery.Deferred();
// tell the deferred object what to do after a task which might be async is done deferLoad.then(function(s2Controller){ s2Controller.loadInitialAppData(s2Controller.aSorter, s2Controller.aFilter); })
// Resolve would trigger the then deferLoad.resolve(s2Controller);
Detail Screen
oData services in some cases will not be modelled from scratch we could as well take any existing model (Genil Model or any other model) and then build the oData model from this. Thus the hierarchy or the relationships are cascaded from these models.
- Re-implement $expand you would have already read in several blogs that the default implementation of $expand is not performance friendly in most cases especially when you have a complex oData model with hundreds of attributes. Hence the first option to consider is to re-implement the $expand as per the application needs.
Re-implementation of $expand would have generally two aspects
1. Building the static structure in line with the entities that are queried
2.Providing data to this deep or nested structure
- When we talk about 300 attributes it is important to see how we distribute or segment this data in different pages within the application. You would not want to load all the information in the first click itself in that case you will probably have a flat service with one entity and 300 attributes within them which is never the case. Hence bring in the lazy load concept in the UI so that only the needed information is fetched at all time from the backend to the UI.
- The UI design should balance the number of click that the end user has to perform to read the complete data. This should take precedence over designing the UI to improve performance implicitly.
- Modelling of description fields there are two options that could come to mind in modelling the description fields.
1. Add another attribute for every description field within the entity
2. Add a common entity which would have navigations from the entity which needs description. This entity could have key, text attributes
The first option fits for display applications as here we always have only a single description associated to a key as this would reduce the number of queries. Whereas the second option could be better in case of create or change application where we can also query for the value helps. Based on the application needs we can decide to have both or choose one of the options
- Asynchronous calls help in improving the performance and if not used in an apt manner can consume more time. Let us assume that in the detail screen we have 5 tabs and once the initial tab is loaded we have an option to make all the calls for the remaining 4 tabs to fetch the data asynchronously. This has the advantage that if we take some time to go through the data in initial tab then the remaining tabs are populated with data during this time. Hence the subsequent click on any tab would be faster. Now when we load the backend with 4 queries in parallel we have to be careful on how many request can be handled by backend. Sometimes it might so happen that loading data on click would be better than making such asynchronous calls. Hence a thorough analysis needs to be done before the usage of asynchronous calls. If used wisely they help in bringing down the performance.
- Tradeoff between asynchronous calls and batch calls. The advantage of batch call is that the number of roundtrips are reduced but the result comes only once all the queries are executed however the time taken would be the maximum time taken by one of the queries within the batch whereas in case of asynchronous calls roundtrips are more but the result comes as an when the individual queries finishes execution. Based on the UI design we can use option which is more apt.
↧
SAP How-To Guide for MDG-F Overview
This guide provides you with the foundation knowledge you need to know about financial data and its related governance solution financial governance (MDG-F).
↧
Extending the MDG Track My Request Fiori Application to get Change Requests from multiple backend system
In order to extend the Track my request Fiori application to fetch the change requests from multiple backend system we need to do two things:-
=>In backend configure the OData service using gateway configuration to accept data from more than one backend system.
=>Extend the track my request Fiori application to refer to the new service URL by appending ;mo to the existing service.
Backend Changes: Gateway provides configurations to connect any OData service to multiple backend system. This can be done in the gateway system using the /iwfnd/maint_service transaction. Here you can add multiple system aliases for which you want to establish connections. One of the aliases can be selected as default. More information on this can as well be found in the SAP help(https://help.sap.com/saphelp_nw74/helpdata/en/bc/f72651c294256ee10000000a445394/content.htm)
Frontend changes: In order to use the gateway multi origin feature in the extended application we need to point the URLs to the new url by appending ;mo to the existing standard service/extended Z service. The tile also shows the count of change request this also can be changed all the configuration for the new tile so that the count from one or more backend system is provided.
In order to extend the application the following steps are needed:-
=>Create a new extension project in Webide which points to the backend BSP application. Follow the standard Fiori extensions for doing this.
=>Add the below code in the config of the default generated code. Modify the service name in case the service is extended with the new Z service.
"sap.ca.serviceConfigs": [
{ name: "MDG_MYCR_SRV",
serviceUrl: "/sap/opu/odata/sap/MDG_MYCR_SRV;mo/",
isDefault: true, mockedDataSource: "./model/metadata.xml"
} ]
Create a new tile in the Launchpad. Here modify the URL to fetch the change request count in tile. The service URL should be changed to /sap/opu/odata/sap/mdg_mycr_srv;mo/ChangeRequests/$count?$filter=(( ChangeRequestStatusFlag eq 'I' ) and (NoOfDays eq '30')
Once the configuration changes are done to support multi origin and the app is pointed to the service with multi origin support as mentioned above. The tile should launch the application by showing change request from multiple backend. Refer to the document(http://scn.sap.com/docs/DOC-62495) for further details on MDG Fiori extensibility.
↧
↧
Extend MDG-M by a New Entity Type (Flex)
This guide describes how to extend the preconfigured content of Master Data Governance for Material (using the data model MM) with a new entity type, where records stay in the generated tables (flex option). Here the active area and the staging area are identical and generated by MDG.
↧
SAP Master Data Governance, Consolidation
With release 8.0, SAP Master Data Governance has evolved from central governance to consolidation scenarios, too. With SAP MDG 8.0, the consolidation capability is available for Business Partner, Supplier and Customer master data. MDG, Consolidation can be operated stand-alone, or in conjunction with MDG, Central Governance.
↧
SAP Master Data Governance: Integration with SAP Simple Finance
SAP Simple Finance can be a distribution target for master data managed under central governance by SAP MDG. Central Finance as deployment scenario can additionally leverage MDG's key mapping capability for aligned postings.
↧
Data quality check in customer tables for MDG Customer reporting purpose
The document is about a report for displaying the corresponding customer details using a simple ABAP program with ALV display, using input file that have BP numbers.
It consist of multiple select conditions that will fetch and display the BP number, GUID, Customer number, address details of customer , company code details of the customer, and sales area data. Also a check box is available if the program need to select the customer credit details as well. The program is executed in live system for data quality check and to identify the missing mandatory fields in ERP tables.
Steps are given below
- Prepare the input file with BP numbers in a notepad
2. The program is using GUI_Upload for fetching data from input file and the file is to be placed in local system
3. It will collect corresponding business partner GUID from BUT000
4. Using the busness partner GUID it will fetch the corresponding customer from CVI_CUST_LINK
5. Using customer number get the details from KNA1, KNB1 and KNVV for customer general, company code and sales area details
6. The reports selects those fields which are mandatory for my system and this needs to be modified according to the mandatory/ custom fields in system
7. If the check box is checked for customer credit then it will fetch the fields from KNKK table as well
8. After giving input and execute, an ALV display is available with BP number, GUID, customer number, customer company code , and sales area details and customer credit details
↧
↧
SAP Master Data Governance: What’s New with MDG 8.0 – Overview
Session recording featuring an overview of the enhancements included in MDG 8.0.
↧
SAP Master Data Governance: What’s New with MDG 8.0 – MDG, Consolidation
Session recording featuring the new consolidation capabilities coming with MDG 8.0.
↧
SAP How-To Guide: Extend MDG-M Data Model by a New Entity Type (ERP Table, Reuse Option)
Master Data Governance provides an out-of-the box solution for the central management of various master data objects such as financial objects, supplier and material. But SAP Master Data Governance also provides the flexibility to customize the solution, in cases where the pre-delivered content does not fully match customer requirements. You can use this guide to extend the MDG-M data model by a new entity. The attribute values of the new entity type will be copied to the corresponding ERP tables (reuse option) after activation of the change request.
↧
SAP How-To Guide for MDG-F Overview
This guide provides you with the foundation knowledge you need to know about financial data and its related governance solution financial governance (MDG-F).
↧
↧
Configuration and Enhancement of SAP Master Data Governance
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 are valid for releases EhP5 to MDG.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.
Domain Specific Areas
Application Framework including Custom Objects
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| Fiori | |||
New March 2015 | 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 May 2014 | 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 |
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 |
New May 2015: 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 |
New June 2015 | 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 | |||
New May 2014 HANA Drill Down: Extensibility Guide | 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 | |
New December 2014Default | 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 |
Financial Data
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| A zip file containing a spreadsheet for the Financials data model. | MDG7.0 | MDG 8.0 | |
New October 2015 MDG Financials Validations | A zip file containing a spreadsheet with an overview of SAP pre-defined validations that are executed by the system when validating data. | MDG7.0 | MDG 8.0 |
| Updated October 2015 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 | MDG 8.0 |
| New May 2014 Entity Derivation in MDG-F | Explains how to implement a custom cross-entity derivation for MDG-F entity types. It covers the key concepts and implementation details in general and includes a real-life example of the MDG-F data model 0G. | MDG7.0 (Feature Pack) | MDG 8.0 |
| New May 2014 Enable Changeable IDs in MDG-F | Explains how to enable the new functionality of changeable IDs for MDG-F entities. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG 8.0 |
| New May 2014 Enable multi-copy of Accounts in Company Code in MDG-F | Explains how to enable the new functionality for copying a single Account in Company Code to multiple target Accounts in Company Code. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG 8.0 |
| New May 2014 Enable HANA Search in MDG-F | Explains how to enable the new functionality for HANA search. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG 8.0 |
| New May 2014 Enable Primary Cost Elements for Accounts in MDG-F | Explains how to enable the new functionality for the one-step creation of Primary Cost Elements for Accounts. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG 8.0 |
New May 2014 Enable Dynamic Parallel Approval for Company Code Data in Rule-based Workflow (Available since EhP5.) | Shows you how to create parallel approval workflow steps using a rule-based workflow when the parallel number is determined dynamically. | EhP5 | MDG 8.0 |
Using the Master Data Management Generic Extractor (MDMGX) 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 | MDG 8.0 |
Updated May 2014 | Foundation knowledge to extend the MDG-F data model by new fields. | MDG7.0 | MDG 8.0 |
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 | MDG 8.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
allTitle/Group | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
Extensibility | |||
| Best Practice for Maintenance Status | This guide provides background information about the maintenance statuses for the material master and the use of the maintenance statuses in MDG for Material. | all | all |
| Maintenance for Multiple Materials | The guide provides some insights on the applicability of the features to create or change multiple materials, also with respect of boundary conditions and limitations. | all | all |
| Set Up Parallel Change Requests for Material | Change Request in parallel for a single Business Object enables you to activate or reject a change request independently from the processing results of other change requests for the same business object. This guide gives some background information and explanation for setting up Parallel Change Requests for the Business Object Material. | MDG7.0 | all |
| 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 | all |
| You can use this guide to extend MDG-M by new attributes. The system copies the attribute values to the corresponding customer Z-fields in standard ERP table (reuse) after activation of the change request. (MARA extension example) | EhP6 | all | |
| Extend MDG-M by a New Entity Type for standard ERP Tables (Reuse) | You can use this guide to extend MDG-M by a new entity type. The attribute values of the new entity type are copied to the corresponding standard ERP tables (reuse) after activation of the change request. (YMARC example) For additional information about how to extend the UI, see : | EhP6 | all |
Extend MDG-M by a New Entity Type for custom Z-tables (Reuse) | You can use this guide to extend MDG-M by a new entity type. The attribute values of the new entity type are copied to the corresponding Z-backend tables after activation of the change request. | EhP6 | all |
| Extend MDG-M by a New Entity Type (Flex) | You can use this guide to extend MDG-M with a new entity type, where records stay in the generated tables (flex option). Here the active area and the staging area are identical and generated by MDG. | EhP6 | all |
This guide describes how to extend the UI of Master Data Governance for Material to display additional data. | EhP6 | all | |
| Adjust MDG-M Homepage | This guide describes how to extend the Homepage of Master Data Governance for Material to display additional links | EhP6 | all |
| Create Custom Print Forms | This guide shows you how to create a custom print form to support different layouts and custom fields. | MDG7.0 | all |
| 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 | all |
| 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 |
Checks and Derivations | |||
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 | all | |
Workflow | |||
| Enable Dynamic Parallel Approval for Company Code Data in Rule-based Workflow | This document shows you how to create parallel approval workflow steps using a rule-based workflow when the parallel number is determined dynamically. | MDG6.1 | all |
| Follow-up Work Item to Maintain Material Related Objects | This guide describes how to integrate follow-up work items for material related objects into the MDG Change Request process. | MDG6.1 | all |
| 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 | all |
BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | all | |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | all |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | all |
BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 | all | |
Sending an E-mail notification from the rules-based workflow | EhP5 | all | |
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 | all | |
| 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 | all |
| 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. | EhP6 | EhP6 |
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. | all | all |
| 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 | all |
| Enhance the Material Search (EhP6 on) | With MDG for Material master data it is possible to extend the data model MM. If you want to search also with these new fields you have to extend the search too. | EhP6 | all |
| Data Import/Data Replication | |||
| Using Data Import Framework (DIF) | You can use the Import Master Data service to import files containing material and classification data to the MDG system. This guide provides background information about the Data Import Framework (DIF) and describes how to use the DIF to upload material data from a CSV file using a BAdI for the file conversion. | EhP6 | all |
| Using Data Replication Framework (DRF) | This guide provides background information about the Data Replication Framework (DRF). The guide also describes how to set up the system to enable immediate distribution of changes in the material master during activation of the material (SAP Note 1764329). | EhP6 | all |
| Using Enterprise Material Services (SOA) | This guide explains how to enhance the asynchronous SAP Material Enterprise Services MaterialERPBulkReplicateRequest_In | MDG6.1 | all |
Customer / Supplier Data
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| New January 2015Copying of Business Partners (SAP Note 2020896) | Refer to the SAP Note linked to here. A how to guide for using the BOL entity cloner is attached to the Note. The BOL entity cloner.allows you to clone almost arbitrary BOL entities visible on a UI. Make sure you read the disclaimer in the attachment to the note before proceeding. | MDG 7.0 SP3 | MDG 8.0 |
| 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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | MDG 8.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 | 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 | EhP6 |
| Data Models | |||
A zip file containing separate spreadsheets for Business Partner, Supplier, and Customer. Each spreadsheet contains information about the following:
| EhP6 | MDG 8.0 |
Integration Scenarios
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
Updated July 2015 Using | This guide describes how to use enhanced integration of CRM with MDG for Customers in a CRM / ERP Data Exchange Scenario. | EhP6 | MDG 8.0 |
| 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 | MDG 8.0 |
| Updated February 2015Customizing Synchronization 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.1 | MDG 8.0 |
Updated November 2015 Rapid-Deployment Solution package for data remediation (SMP login required) | Data remediation based on integration of SAP Information Steward with SAP MDG | See RDS document | See RDS document |
↧
Audio Files about SAP Master Data Governance
This page provides audio files about global trends in master data management as well as business benefits, basic functions, and integration aspects of SAP Master Data Governance.
SAP Master Data Governance: Podcasts
Title | Description | Published |
|---|---|---|
General introduction into MDG's prebuilt scenarios for centralized governance of master data domains and MDG's capabilities to customize and extend these scenarios including replication (Duration: 7:32 min.) | Mar 2015 | |
Introduction into business networks, mobile apps, and the cloud as examples of major current strategic trends in master data management (Duration: 2:14 min.) | Mar 2015 | |
Introduction into the joint value proposition of MDG in combination with hybris PCM in the context of master data enrichment for e-commerce purposes (Duration: 2:32 min.) | Mar 2015 | |
| Introduction to the MDG Workflow | Introduction into the MDG workflow describing the MDG change request process and its elements change request type, step, status, activation, and the rule-based workflow (Duration: 8:51 min.) | Mar 2015 |
| SAP Master Data Governance Product Roadmap Part 1 of 3: Today | Interview with Chief Solution Architect Markus Kuppe about the current MDG release as it is available today (MDG 7.0 Feature Pack) (Duration: 9:33 min.) | Mar 2015 |
| SAP Master Data Governance Product Roadmap Part 2 of 3: Planned Innovations | Interview with Chief Solution Architect Markus Kuppe about the MDG development team's plans to extend the functional scope beyond central master data management, increase the use of SAP Fiori, and improve the MDG application foundation's flexibility. (Duration: 6:59 min.) | Mar 2015 |
| SAP Master Data Governance Product Roadmap Part 3 of 3: Future Direction | Interview with Chief Solution Architect Markus Kuppe about the long-term future direction of MDG(Duration: 9:27 min.) | May 2015 |
| Coming soon | What's New in SAP MDG - Consolidation (Duration: 2:30 min.) | Nov 2015 |
↧
How-To Videos for SAP Master Data Governance
This page provides domain-specific videos showing how to use basic functions of SAP Master Data Governance.
Videos about processing tasks by master data domain:
Title | Description | Valid From | Valid To |
|---|---|---|---|
Master Data Governance for Financials | |||
July 2014 | Tutorial showing how to create an edition. An edition is an obligatory container for creating or changing master data in SAP MDG for Financials. Editions are used to specify validity periods and schedule changes for specific master data objects (2:48 min.) | MDG 7.0 (Feature Pack) | MDG 7.0 (Feature Pack) |
July 2014 | Tutorial showing the process of creating a profit center in SAP MDG (3:16 min.) | MDG 7.0 (Feature Pack) | MDG 7.0 (Feature Pack) |
July 2014 Change Request Processing for Single Objects and Multiple Objects | Tutorial focusing on user interaction (and UIs) in single and multiple object processing; uses the creation of a cost center and the creation of objects for a cost center group hierarchy as examples (6:02 min.) | MDG 7.0 (Feature Pack) | MDG 7.0 (Feature Pack) |
October 2014 | Tutorial showing the process of creating a G/L account in SAP MDG (3:24 min.) | MDG 7.0 (Feature Pack) | MDG 7.0 (Feature Pack) |
Master Data Governance for Material | |||
August 2015 | Tutorial showing the process of copying materials in SAP Master Data Governance for Material using a new function in multi-record processing. (3:59 min.) | MDG 8.0 | MDG 8.0 |
Master Data Governance HANA-Based Analytics | |||
May 2015 Leverage SAP Smart Business for Realtime Insights in MDG Analytics: How to Configure a KPI Tile | Tutorial showing how to configure a KPI tile in the context of SAP HANA-based analytics leveraged in SAP MDG (8:43 min.) | MDG 7.0 (Feature Pack) | MDG 7.0 (Feature Pack) |
Videos and learning material about basic functions of SAP Master Data Governance:
Title | Description | Published |
|---|---|---|
Recording from SAP TechEd && d-code 2014: | Jan 2015 | |
Building Processes for Your Own Master Data with SAP Master Data Governance | Recording from SAP TechEd && d-code 2014: | Jan 2015 |
Presentation: Note: Information on system access for live exercises, provided in the original script, is not applicable. | Jan 2015 | |
| Audio Files for Quick Learning | Compilation of podcasts about about global trends in master data management as well as business benefits, basic functions, and integration aspects of SAP MDG. | Mar 2015 |
↧
Featured Content in SAP Master Data Governance
SAP TechEd 2015: Reap the harvest and recap SAP Master Data Governance sessions
Attendees of SAP TechEd 2015 can recap various sessions. To find out how, read this SCN blog by Markus Ganser. 25 November 2015
Innovations with SAP Master Data Governance 8.0
To find out about the innovations that have come with SAP MDG, release 8.0, read the SCN blog by Markus Kuppe and the complementary blog by Steffen Ulmer.For quick insight into what SAP Master Data Governance is all about, watch thenew animated 3-minute videos25 November 2015
Extensibility and Configuration Options for SAP Master Data Governance
Find extensibility and configuration options for SAP Master Data Governanceat one spot. Includes recent updates. 11 May 2015
Landscape Recommendations for SAP Master Data Governance 8.0
Find out about deployment recommendations for SAP Master Data Governance 8.0.3 September 2015
SAP Master Data Governance - Updated Product Roadmap
To find out about SAP MDG today, planned innovations and future vision, read Markus Ganser's blog. updated 28 July 2015
SAP Master Data Governance and SAP Simple Finance
Find out how SAP MDG integrates with SAP Simple Finance. 28 July 2015
↧
↧
Calculating best record in SAP MDG, Consolidation
Tutorial showing the process of calculating the best record in SAP MDG, Consolidation.
↧
What's new in SAP MDG 8.0?
What's new in SAP Master Data Governance 8.0?
↧
Extending the Search Result List for MDG for Business Partner
This document explains how to extend the search result list for the SAP MDG domain Business Partner with specific information that is relevant for Customer and Supplier data.
↧