Quantcast
Channel: SCN : Document List - SAP Master Data Governance
Viewing all 300 articles
Browse latest View live

R11 130 error while approver finalize the CR in MDGS

$
0
0

Issue:

 

When the approver finalize the CR # 26061 in MDGS for the Vendor Master # 12345 block the change are not flown to MP1. Based on this we have

verified the logs in SLG1 the error message as "An address with GUID 53D942C0341D3580E10080010A785401 does not exist for business partner

12345" and the Message no. R11130.

 

Also we have verified the table BUT000 for the BP # 12345 and found that it has mapped to GUIID: 5106D20CF5951020E10080000A785429. When we

try to search the GUIID: 53D942C0341D3580E10080010A785401 in table BUT000. No entry found.

 

Solution:

 

Based on this we have found the OSS # 1550109 and implemented and aalso make sure you execute the report MDG_BS_BP_ADDRESS_GUID_2STA this will adjust the staging table data and resolved my issue.

 

Hope this might be useful.

 

Regards,

Sada


MDG Vendor master Block / Deltion not flowing to ECC afteractivation

$
0
0

Issue:

 

Whenever the users update the Block indicator in MDG by CR # XXXXX the data had not flown to ECC after activation of the change requests.  Based on this we verified the log details in T-code MDS_PPO2 we are able to see the error message as “ Vendor 12345 already exists for function VN” . The error message number is F2 631.

 

Solution :

 

We  have start investigate the issue and found few things.

 

Whenever if we want to block the vendor master for all company code and purchase org then only we need to select  as below (screen shot: 1) , else we need to select the specific company code (screen shot : 2) for  our testing purpose we have selected the Co. code 1085 and 1089 of vendor # 1234 in Company code data tab  and created the CR # 12345.

 

After the activation of CR # 12345 the company code block data has flown to ECC successfully (screen shot: 3) and the same way it is worked for Posting Block for all company codes and Purchasing organization in MDG to ECC. Hence the check box should not be selected in both /all the tabs (Supplier General Data and Co.Code (or) Supplier General Data and purchasing organization).

 

FYI, per standard whenever all the tabs  (posting block for all company code and purchasing org, Company code and purchasing org posting block) are maintained the data is not flowing from MDG to ECC.

 

Screen shot : 1

 

1.png

 

Screen shot : 2

 

2.png

Screen Shot : 3

 

3.png

4.png

Hope this will be useful those who are new to MDGS.

 

Regards,

Sada

SAP MDM Vs MDG - Kousik Mukherjee

$
0
0
SAP Master Data Management (MDM)SAP Master Data Governance (MDG)
Server / SoftwareNetWeaver MDM 7.1 - SP1 to SP10                                                                                                                                                                                                                                                                                                                               NetWeaver 7.0, CE 7.1, CE 7.2, NetWeaver 7.3                                                                                                                                                                                                                                                                                                                                          NetWeaver PI 7.1, 7.3MDG -  EHP5, EHP6, 6.1, 7.0                                                                                                                                                                                                                                                                                                        BRFplus                                                                                                                                                                                                                                                                                                                                                 
Data ModelingMDM ConsoleMDG - Data Modeling
Data ProcessingMDM Data ManagerMDG - Data Processing
Data ImportMDM Import ManagerMDG - Data Transfer Framework - Import
Data ExportMDM SyndicatorMDG - Data Transfer Framework - Export
UI ModelingDone directly in PortalMDG - UI Modeling
Value MappingMDM Import Manager - Value MappingMDG - Value Mapping
Key MappingMDM Import Manager - Field MappingMDG - Key Mapping
SearchMDM Data Manager - SearchMDG - Data Quality and Search
Duplicate CheckMDM Data Manager - Matching ModeMDG - Data Quality and Search
ValidationMDM Data Manager - ValidationsValidation Rules (BRF+)
WorkflowNetWeaver BPMABAP Workflow
Rule Based WorkflowNetWeaver BPM with BRMABAP Workflow with BRF+
User InterfaceJava Web Dynpro with MDM Java APIABAP Web Dynpro with FPM
Master Data Integration with other systemsMDM Import Server (MDIS) with PI - Inbound                                                                                                                                                                                                                                                                                                                  MDM Syndication Server (MDSS) with PI  - OutboundMDG - Data Replication Framework
Out-of-the-Box Data ModelsProduct, Material, Vendor, Customer, Business Partner, Employee0G - Financials, MM - Material, BP - Business Partner
Supported Data Exchange formatsFlat Files, XML, Web ServicesEnterprise Services, ALE, IDocs

How to control toolbar buttons in Entity search for MDG custom objects

$
0
0

This document explains how to control tool bar buttons for e.g. Hiding/Adding buttons in Entity search applications provided for custom objects by SAP by using BADI USMD_SEARCH.

 

For custom objects or custom data models , SAP has provided following search applications.

 

USMD_ENTITY_SEARCH(Till MDG 6.1):



10-17-2014 10-19-43 PM.jpg

 

  USMD_SEARCH(From MDG 7.0):


USMD_SEARCH.jpg

 

The above mentioned applications could be generically used for searching the data of all the entities defined in a custom data model.

 

In both the applications , certain tool bar buttons are pre delivered by SAP.

 

Sometimes it might be necessary to hide some of the buttons for e.g. Mass Change for all or certain entities of a data model . It might also be needed to add some additional tool bar buttons.

 

This could be achieved by creating implementation of BADI  USMD_SEARCH and by implementing necessary coding in the method Initialize and Process_Event of the implementing class.

 

First step is to create an implementation of BADI USMD_SEARCH. The custom data model should be set as a filter criteria

 

filte.jpg

 

  1. Hiding standard tool bar buttons:

 

       Hiding tool bar buttons could be achieved manipulating exporting parameter ET_STANDARD_EVENT of method INITIALIZE.

 

       The tool bar button to be hidden should be passed to field EVENT_ID.  For USMD_ENTITY_SEARCH and USMD_SEARCH , event ids are different.

 

      Following are the list of standard event ids available for USMD_ENTITY_SEARCH.

    • ALV_FCT_CREATE(Create Button)
    • ALV_FCT_CHANGE(Change Button)
    • ALV_FCT_COPY(Copy Button)
    • ALV_FCT_MASSCHANGE(Mass Change Button)
    • ALV_FCT_CNGDOCS(Change Documents Button)
    • ALV_FCT_WHEREUSED(Where Used Button)

 

      Following are the list of standard event ids available for USMD_SEARCH

    • NEW(Create Button)
    • COPY(Copy Button)
    • MASS_CHANGE(Mass Change Button)
    • MULTI(Multi-Processing button)
    • CHANGE_DOCS( Change Documents button)
    • REPL_STATUS ( Replication Status button)
    • REPLICATE( Replicate button)

 

    Visibility could be controlled by passing the following values to field VISIBILITY

 

    • cl_wd_uielement=>e_visible-none(01)
    • cl_wd_uielement=>e_visible-visible(02)


    Example implementation:

 

example_impl.jpg

 

      With this implementation , tool bar button Mass change would be hidden

 

      USMD_ENTITY_SEARCH

   

    hidden_old.jpg

 

        USMD_SEARCH

  

     hidden_new.jpg


    2.  Adding new  tool bar buttons:

   

        New tool bar buttons could be added by manipulating parameter ET_ADDITIONAL_EVENT of method INITIALIZE.

 

        new_add.jpg

          get_d.jpg

 

           Handling of the event triggered by this button could be done in method PROCESS_EVENT

            process.jpg

Corporate Reference Master Data Governance using SAP MDG

$
0
0

     Most of us are already well versed with the concepts of Master data and Transactional data. But there is another kind called Reference Master Data which        many are not aware of. This article would explain about the concept of reference master data and the need of governing it.

 

  What is Corporate Reference Master Data?

 

  Corporate Reference master data is the master data which is used across the organization by various departments. The data itself is reference data also known as look-up data.

 

Following are the typical characteristics of the Reference Master Data

 

      • Simpler structure, rarely changed and less volume of data
      • Centrally maintained
      • Frequently used across several types of master data
      • Harmonized definition and values across corporate group
      • May be defined in external standards
      • Supports Business processes

 

 

Examples of such data are codes for countries/languages, material type, currency code, plant, location, payment conditions, commodity codes, Country allocation hierarchy etc.,

 

An organization could also have a specific reference master data objects based on its typical process

     Need to Govern Corporate Reference Data

 

Given its wide use across the organization it is vital that the reference master data is kept accurate and complete.

 

 

Classic example of Country code changes

Image source: SAP SDN

 

  The above example shows that it is very much possible to have

    • Different ISO code / same country
      • Codes change over time but are not maintained synchronously in all clients
      • New countries with preliminary codes
    • Systems treat countries differently
      • Separate country or
      • part of another country (e.g. Hong Kong)

 

 

Based on the above example, it can be inferred that it is essential to have a governed and harmonized reference master data across a corporate group to avoid breakdowns across distributed business processes, impart corporate best-practice and enable trusted company-wide reporting.

 

This can be achieved by

 

    • Making one person/organization responsible (per „reference data type“)
    • Having a well-defined , central maintenance process
    • Distributing same values for use across all business processes

 

   SAP Master Data Governance

 

       Identifying the right tool

 

     To manage the reference master data, a right tool which provides the following features should be used by an organization

 

    • Central storage of the reference master data in order to allow enterprise-wide access to the data through a single and central point via the tool.
    • Synchronization and distribution of reference data updates including additions across all systems storing or referencing the reference master data.
    • Workflows to help standardize and manage the process of data updates/additions and monitor the status i.e. who is the next person to do something with the data.

 

SAP Master Data Governance, an Add-on by SAP provides all the above features

SAP Master Data Governance is a natural extension of the business processes running in SAP Business Suite, providing domain-specific master data governance to centrally create, change, and distribute master data.


 

                                 Image source SAP AG


SAP Master Data Governance enables users to create necessary data classes in Data model and helps in bringing front end governance and control to the Reference master data maintenance process with a simple implementation effort.

    

       

Fig 1.Data model


       It also provides a Floor plan manager based tool for the UI modeling

       

          Fig 2. UI modeling


It provides Rule based Workflows to help standardize and manage the process of data updates/additions and monitor the status i.e. who is the next person to do something with the data. SAP MDG is integrated with SAP Business Rules Framework. This enables customers to define derivation and validation rules in a simple way.


       Fig 3. Rule based workflow



SAP MDG allows replicating the data via Web services. As a result of this, it is possible to replicate the data to both SAP and Non-SAP systems. It also allows auditing and history storage to enable tracking and recording of changes made to the reference data over a period of time. This would help in meeting the regulatory requirements.


The data maintenance screen could be accessed via portal or Netweaver business client

        

 

        To summarize SAP MDG is an excellent tool which an organization could use to govern and centrally maintain Reference Master data thus resulting in fostering corporate best practices and to avoid disruptions in business processes

 

   Sources: SAP AG,SAP SCN Community

How to Create a G/L Account in SAP Master Data Governance for Financial Data

$
0
0

Video tutorial showing the process of creating a G/L account in SAP Master Data Governance

View this Demo

Customizing Synchronization between MDG and ERP (Guide)

$
0
0

In most cases SAP customers implementing SAP Master Data Governance (SAP MDG) need to think about the synchronization of customizing across at least two systems in order to keep consistent business processes that span multiple systems. This in particular is true if the SAP customer follows the SAP MDG Hub approach (MDG deployed on a different system than the operational ERP system). 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.

View this Document

How To - MDGM: Checks and Derivations

$
0
0

The processes in Master Data Governance for Material are workflow-driven and can include several approval and revision phases, and the collaboration of all users participating in the master data maintenance. To support these processes, check and derivation rules can be created for the MM data model. Checks ensure that the master data is consistent. You can use derivations to calculate values for attributes from other resolved attributes, thereby simplifying data entry. This How-To Guide gives an overview of the checks used in MDG-M and gives examples for Checks and Derivations built in BRF+.

View this Document


How To-MDGM: Using Data Replication Framework

$
0
0

This guide provides background information about the Data Replication Framework (DRF). It  also describes how to set up the system to enable immediate distribution of changes in the material master during activation of the material.

View this Document

How To-MDGM: Maintenance for Multiple Materials

$
0
0

The following guide provides some insights on the applicability of the features to create or change multiple materials, also with respect of boundary conditions and possible limitations.

View this Document

How to... MDG-M: Use the Data Import Framework

$
0
0

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.

View this Document

Featured Content in SAP Master Data Governance

$
0
0

SAP Master Data Governance for Enterprise Asset Management

Read this blog to find out about SAP Master Data Governance, Enterprise Asset Management Extension by Utopia. 16 December 2014

 

It's the Customer's Voice that Counts

Read this blog to find out why it is often better to speak about solutions rather than describing functions. 3 November 2014

 

Effective Information Governance for the Networked Economy

SAP Thought Leadership Paper outlines what information governance means in the networked economy. 24 October 2014


SAP Master Data Governance - Updated Product Roadmap

To find out about SAP MDG today, planned innovations and future vision, read Markus Ganser's blog. 30 September 2014

 

What is SAP Master Data Governance?

To get a good understanding of SAP Master Data Governance, watch this 2014 webinar recording. 26 September 2014

 

Benefit from Innovations in SAP Master Data Governance 7.0 SP02 (Feature Pack)

SAP Master Data Governance 7.0 is generally available with Support Package 2 (Feature Pack). Read Markus Kuppe's blog to find out what the feature pack has in it for you; for information on the SAP MDG 7.0 core release, read this blog26 September 2014

 

Extensibility and Configuration Options for SAP Master Data Governance

Find extensibility and configuration options for SAP Master Data Governanceat one spot. Includes recent updates. 26 September 2014

 

SAP Fiori and SAP MDG

To find out how SAP Fiori apps can extend the reach of SAP Master Data Governance, read Markus Ganser's blog. 5 June 2014

 

SAP Ranked Leader in Forrester WAVE for MDM

Recent Forrester Wave™ on master data management (MDM) ranks SAP as a leader. Read more in this blog. 14 February 2014

 

System Landscape Recommendations for SAP Master Data Governance 7.0

Read this brand new document that outlines deployment recommendations for SAP Master Data Governance 7.0. 28 January 2014

How To... Master Data Governance for Material Extend MDG-M User Interface (EhP6 on)

$
0
0

SAP Master Data Governance for Material (MDG-M) provides business processes to find, create, change, and mark material master data for deletion. It supports governance of material master data on a central hub and 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. In EhP6 MDG-M addresses only descriptive data for the Material.  This guide describes how to adapt the UI of Master Data Governance for Material from EhP6 on.

View this SAP How-to Guide

Configuration and Enhancement of SAP Master Data Governance

$
0
0

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

 

Domain Specific Areas

Application Framework including Custom Objects

Title
Description and Documents
Valid-From
Valid-To
Smart Business

New May 2014

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 (Feature Pack)
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
HANA-based Search - Implementation of the Access Class Interface for the Reuse
Model

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.0MDG7.0 (Feature Pack)

Joining Text Tables to Replace Technical Names with Descriptions in the HANA View for Drilldown Search

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.0MDG7.0 (Feature Pack)
BI Content

Activating BI Content for Analysis of Change Requests

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:

  • Processing times (for example, view a graphic indicating what proportion of change requests violate Service Level Agreements)
  • Statuses (for example, view a graphic indicating what proportion of change requests are in process)
  • Change requests involving you
EhP6MDG7.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.1MDG7.0 (Feature Pack)

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.1MDG7.0 (Feature Pack)
Creating a UI Configuration and Integrating it with the MDG CommunicatorYou 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.1MDG7.0 (Feature Pack)
Customizing Navigation for Change Request Steps in the User Interface for Single-Object ProcessingDuring 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.1MDG7.0 (Feature Pack)
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.EhP5MDG7.0 (Feature Pack)
Hiding Fields in the Change Request User InterfaceYou 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 RequestsIn 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.EhP6MDG7.0 (Feature Pack)
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.EhP6MDG7.0 (Feature Pack)

New December 2014Default
Values in MDG Single Object Maintenance UIs based on FPM BOL Feeder Classes

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)MDG7.0 (Feature Pack)
API
Updated January 2014 Application Programming Interface Customizing GuideDepending on the software release, MDG offers different APIs for consumption with different functional scopes. This guide describes the Application Programming Interfaces for each release.EhP5MDG7.0 (Feature Pack)

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.EhP5MDG7.0 (Feature Pack)
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.EhP5MDG7.0 (Feature Pack)
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 (Feature Pack)
BADI USMD_SSW_RULE_CONTEXT_PREPARE
EhP5
MDG7.0 (Feature Pack)
Rule Based Workflow: Enhancement for parallel workitemsBADI USMD_SSW_PARA_RESULT_HANDLER
EhP5
MDG7.0 (Feature Pack)
Rule Based Workflow: Enhancement for Flexible User DeterminationBADI USMD_SSW_DYNAMIC_AGENT_SELECT
EhP5
MDG7.0 (Feature Pack)
BADI USMD_SSW_SYSTEM_METHOD_CALLER
EhP5
MDG7.0 (Feature Pack)
Sending an E-mail notification from the rules-based workflow
EhP5
MDG7.0 (Feature Pack)
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 (Feature Pack)
How to add an additional task to the inboxYou create own workflow definitions with new workflow tasks and want to see the corresponding workitems in the MDG inbox.
EhP5
MDG7.0 (Feature Pack)
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.
EhP5MDG7.0 (Feature Pack)
Extensibility
Description how to extend new attributes for entity type
EhP5MDG7.0 (Feature Pack)
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.EhP5MDG7.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
MDG7.0 (Feature Pack)
Enrichment of Master Data in MDG – Generic Guide and Sample ImplementationYou 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)MDG7.0 (Feature Pack)
Checking for non-existent objects in the object list of a change requestSAP 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 objectsEhP6MDG7.0 (Feature Pack)
Value Mapping
You want to maintain mass value mapping (customizing mapping) via file export/import.
EhP5
MDG7.0 (Feature Pack)
Data Replication
You want to replicate data from your customer-specific data model to target systems (using flex option).
EhP5
MDG7.0 (Feature Pack)

Financial Data

Title
Description and Documents
Valid-From
Valid-To

Data Model Metadata

A zip file containing a spreadsheet for the Financials data model.MDG7.0MDG7.0 (Feature Pack)
Updated May 2014 SAP How-To Guide for MDG-F - OverviewThis guide provides you with foundation knowledge about financial data and its related governance solution financial governance (MDG-F).MDG7.0MDG7.0 (Feature Pack)
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)MDG7.0 (Feature Pack)
New May 2014 Enable Changeable IDs in MDG-FExplains 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)MDG7.0 (Feature Pack)
New May 2014 Enable multi-copy of Accounts in Company Code in MDG-FExplains 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)MDG7.0 (Feature Pack)
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)MDG7.0 (Feature Pack)
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)MDG7.0 (Feature Pack)

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.EhP5MDG7.0 (Feature Pack)

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.0MDG7.0 (Feature Pack)

Updated May 2014

Extending the Data Model by New Fields in MDG-F

Foundation knowledge to extend the MDG-F data model by new fields.MDG7.0MDG7.0 (Feature Pack)

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.0MDG7.0 (Feature Pack)
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.
EhP5MDG6.1
Remote Where-Used List: Example ImplementationThis 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.EhP6MDG6.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.EhP6MDG6.1

Material Data

Title/Group
Description and Documents
Valid-From
Valid-To
Extensibility
Best Practice for Maintenance StatusThis guide provides background information about the maintenance statuses for the material master and the use of the maintenance statuses in MDG for Material.allall
Maintenance for Multiple MaterialsThe guide provides some insights on the applicability of the features to create or change multiple materials, also with respect of boundary conditions and limitations.allall
Set Up Parallel Change Requests for MaterialChange 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.0MDG7.0 (Feature Pack)
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.0MDG7.0 (Feature Pack)
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 (Feature Pack)
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 (Feature Pack)
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 (Feature Pack)

Extend MDG-M Data Model by

Custom 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 (Feature Pack)
This guide describes how to extend the UI of Master Data Governance for Material to display additional data.
EhP6
MDG7.0 (Feature Pack)
Adjust
MDG-M Homepage
This guide describes how to extend the Homepage of Master Data Governance for Material to display additional linksEhP6MDG7.0 (Feature Pack)
Create Custom Print FormsThis guide shows you how to create a custom print form to support different layouts and custom fields.MDG7.0MDG7.0 (Feature Pack)
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.EhP5MDG7.0 (Feature Pack)
Central guide for SAP MDG-M extensibilityIncludes topics such as field extensions, table extensions, UI adaptation, etc.EhP5EhP5
This guide describes how to adapt the generic UI of Master Data Governance for Material in EhP5.
EhP5EhP5
File Up and DownloadThis How To Guide shows how the CSV file download and upload functionality can be used for MDG materials.EhP5EhP5
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
MDG7.0 (Feature Pack)
Workflow
Enable Dynamic Parallel Approval for Company Code Data in Rule-based WorkflowThis document shows you how to create parallel approval workflow steps using a rule-based workflow when the parallel number is determined dynamically.MDG6.1MDG7.0 (Feature Pack)
Follow-up Work Item to Maintain Material Related ObjectsThis guide describes how to integrate follow-up work items for material related objects into the MDG Change Request process.MDG6.1MDG7.0 (Feature Pack)
Rule Based Workflow with Partial ActivationWhen 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 (Feature Pack)
BADI USMD_SSW_RULE_CONTEXT_PREPARE
EhP5
MDG7.0 (Feature Pack)
Rule Based Workflow: Enhancement for parallel workitemsBADI USMD_SSW_PARA_RESULT_HANDLER
EhP5
MDG7.0 (Feature Pack)
Rule Based Workflow: Enhancement for Flexible User DeterminationBADI USMD_SSW_DYNAMIC_AGENT_SELECT
EhP5
MDG7.0 (Feature Pack)
BADI USMD_SSW_SYSTEM_METHOD_CALLER
EhP5
MDG7.0 (Feature Pack)
Sending an E-mail notification from the rules-based workflow
EhP5
MDG7.0 (Feature Pack)
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 (Feature Pack)
Performance
Performance TweaksBesides 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.1MDG7.0 (Feature Pack)
Performance TweaksBesides 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.EhP6EhP6

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.
EhP5MDG7.0 (Feature Pack)
Search
Enhance the Material Search (EhP5)Adding extra fields to the search templateEhP5EhP5
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 (Feature Pack)
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
MDG7.0 (Feature Pack)
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.EhP6MDG7.0 (Feature Pack)
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).

EhP6MDG7.0 (Feature Pack)
Using Enterprise Material Services (SOA)This guide explains how to enhance the asynchronous SAP Material Enterprise Services MaterialERPBulkReplicateRequest_InMDG6.1MDG7.0 (Feature Pack)

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 SP3MDG 7.0
Extending SAP Master Data Governance for Supplier - Part 1Data Model ExtensionsEhP5
EhP5
Extending SAP Master Data Governance for Supplier - Part 2User Interface ExtensionEhP5EhP5
SAP How-To Guide: Extend the MDG Business Partner - OverviewThis 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).EhP6MDG7.0 (Feature Pack)
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.
EhP6MDG7.0 (Feature Pack)
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.
EhP6MDG7.0 (Feature Pack)
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).
EhP6MDG7.0 (Feature Pack)
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).
EhP6MDG7.0 (Feature Pack)
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.
EhP6MDG7.0 (Feature Pack)
SAP How-To Guide: Extend the MDG BP – Ensure Auto-creation of ERP Vendors with MDG-SYou 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.
EhP6MDG7.0 (Feature Pack)
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).
EhP6MDG7.0 (Feature Pack)
Installing, Configuring, and Using the Excel Upload for Business PartnerYou 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.EhP6MDG7.0 (Feature Pack)
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:
  • The data model
  • Related backend data
  • iDocs
  • Services
EhP6MDG7.0 (Feature Pack)

Integration Scenarios

Title
Description and Documents
Valid-From
Valid-To
New December 2013Using
Enhanced Integration of CRM with MDG for Customers (MDG-C) in a CRM/ERP Data
Exchange
This guide describes how to use enhanced integration of CRM with MDG for Customers in a CRM / ERP Data Exchange Scenario.EhP6MDG7.0 (Feature Pack)
A cross-system master data process for supplierImplementation 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.EhP5MDG7.0 (Feature Pack)
Customizing Integration Between MDG and ERPThe 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.EhP6MDG7.0 (Feature Pack)

MDG-M: Replace Enterprise Search by DB or Alternative Search Provider

$
0
0

For the standard delivery scope, MDG-M requires a fully configured Enterprise Search. As of MDG 7.0 SP02 it is also possible to use SAP HANA as alternative search provider. This guide describes how to adapt MDG-M so that another search provider can be used. The example focuses on integrating a database search, but other search providers can be supported in a similar way.

View this Document


How to Add Custom attributes of MDG-F Entities to Search application

$
0
0

It is a very common requirement of many customers to extend the MDG data models based on their specific requirements.A document is already available in SCN which gives detailed information about extending the MDG-F data models and extending the single processing UI with the custom attributes.

 

However , it is often also needed to extend the entity search application as well with the custom attributes so that the users can search the data based on these custom attributes.As the MDG-F UIBBs are modelled and not generic , any custom attribute has to be added via customizing

 

This document explains the steps to add the custom attributes to the entity search applications of MDG-F entities in MDG 7.0  SP02 version using the Customizing option.

 

Type 1 Entity CELEM(Cost element) is used for example in this document. It is already extended by a custom attribute YYACTVATD.

pastedImage_0.png

 

1. Finding the configurations related to search application

 

          The first step is to know the configuration for search application. The UI configurations related to various entities could be found by executing the activity   Manage UI Configurations in MDGIMG.

 

pastedImage_1.png

 

pastedImage_3.png

 

 

The corresponding component configuration MDGF_0G_CELEM_OVP contains the pages for Search application and single processing UI

pastedImage_4.png

 

The search applications related to all MDG-F entities could be found in a similar way.

 

2. Extending the search criteria

 

  • Go to SE80 , select Webdynpro component FPM_SEARCH_UIBB and open the corresponding search configuration by clicking on Display configuration

 

pastedImage_3.png

 

  • Create customizing as shown below

pastedImage_4.png

 

  • In the next screen , add the custom field in the Search criteria

pastedImage_9.png

 

pastedImage_10.png

 

 

3. Extending the Result list

 

  • The result list can be extended by customizing the corresponding list configuration by following similar steps mentioned above

 

pastedImage_13.png

 

 

pastedImage_14.png

After performing the above steps , the custom attributes could be seen in the search application.

 

 

pastedImage_0.png

How to-Master Data Governance for Material: Enhance the Material Search

$
0
0

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 to connected operational and business intelligence systems. 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.

View this SAP How-to Guide

SAP MDG Fiori Extensibility Guide

$
0
0

This document covers the extensibility concept for SAP Fiori MDG applications. The document contains references to the documentation for extension of other layers.

View this Document

SAP Master Data Governance: enhanced hierarchy management and enhancements in SAP MDG, Financials

$
0
0

Session recording featuring the enhanced hierarchy management and enhancements in SAP MDG, Financials coming with MDG 8.0.

View this Demo

How to Extend Content in MDGM with Customer Fields from Existing Tables

$
0
0

SAP 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. In addition, SAP Master Data Governance provides the flexibility to customize the solution, in cases where the pre-delivered content does not fully match customer requirements. This guide describes how to extend the preconfigured content of MDG-M with customer z-fields from the existing backend tables.

View this Document

Viewing all 300 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>