1 2 3 6 Previous Next

SAP Master Data Governance

80 Posts

Business Requirement


SAP Master Data Governance helps organizations govern master data from its creation in a business application,through  step by step enrichment by different roles in the organization, to its replication to target applications to ensure data quality and regulatory compliance across the enterprise. SAP master data governance can be used for multiple master data domains like customer, material, supplier, articles , finance etc. As you probably are already aware, SAP MDG  process are centered around the concept of Change Requests. Any request for creation or change of an object is handled via change request. The change request work items any user receives, as part of the governance process, are visible in his workflow inbox. In a typical business day, the user would log into his workflow inbox and start processing one work item after another. The workitem inbox in its standard  view shows only the field information from the change request header


In the retail industry we very often come across a requirement in article governance process , where the category manager or the purchasing manager likes to make a decision based on certain attributes on the article master data .  These could be for example, based on the Purchasing Group decide if he is the one to process or should this be picked up by another colleague in the team  or based on the price decide if he wants to include the article in his assortment therefore move the article to the next step for further enrichment  etc


Especially during the early steps in the governance process the category manager might not want to click on the change request item and go into the details, But rather might want to make the decision on how the workitem should be processed right from the inbox.


The category manager is looking for a view where he can look at some important fields on the article data  in a single glance and make decisions on multiple articles right from the inbox without going into the detailed view screen



In this blog we will walk you through the steps required to enhance a standard MDG inbox to include additional fields.


Pre Requisites


We will enhance the inbox with the purchasing group field. The MDG for Article data model already has the field Purchasing group and hence we need not extend it. But if you want some other field as additional column in the MDG Inbox for any data model, then that respective field has  to be first extended in the Data Model



  • Create a class zcl_usmd_crequest_powl which is an inheritance from super class cl_usmd_crequest_powl.
  • Copy the structure usmd_s_crequest_powl into your own Z structure. This is nothing but your inbox structure. Now add the additional field to this structure.
  • Reimplement the method SET_MV_RESULTSTRUCTURE in your Z class and provide this structure name over there.

        Now you have your own structure which will be displayed in your inbox. In order to pass value to this field,

  • Redefine the method  IF_POWL_FEEDER~GET_OBJECTS. Call the super method first and then have your part of coding:




data: : it_wi_crequest        type usmd_ts_wi_crequest,

like line of it_wi_crequest,

type usmd_ts_wi,

like line of it_wi,

type ref to if_usmd_crequest_api,

type usmd_t_crequest_entity,

type ref to data,

type usmd_ts_field,

like line of it_field,

type string value 'wi_id = wa_wi_crequest-wi_id',

type usmd_ts_sel,

like line of it_sel,

like line of it_entity.

field-symbols: <fs_results>      type any,

type any,

type any table,

type any,

type any,

type any,

type any.




= i_username

= i_applid

= i_type

= i_selcrit_values

*     I_LANGU                 = SY-LANGU

*     I_VISIBLE_FIELDS        =


= e_results

= e_messages

= e_workflow_result_count.

e_results assigning <fs_results>.

assign component 'WI_ID' of structure <fs_results> to <fs_id>.

= <fs_id>.

append wa_wi to it_wi.


= cl_usmd_wf_crequest_mapper=>get_crequest_by_wi( it_wi = it_wi ).

loop at it_wi_crequest into wa_wi_crequest.

call method cl_usmd_crequest_api=>get_instance(


= wa_wi_crequest-usmd_crequest

= <model name>


= lo_usmd_crequest_api ).

call method lo_usmd_crequest_api->read_objectlist(


= 'MARA'


= it_entity ).

read table it_entity into wa_entity index 1.

if sy-subrc = 0.

refresh it_field.

-fieldname = 'WEKGR'.

insert wa_field into table it_field.

call method lo_usmd_crequest_api->create_data_reference(


= 'MAW1'


= it_field


= lr_data ).

assign lr_data->* to <fs_data>.

-fieldname = 'MARA'.

-low       = wa_entity-usmd_value.

-option    = 'EQ'.

-sign      = 'I'.

insert wa_sel into table it_sel.

call method lo_usmd_crequest_api->read_value(


= 'MAW1'

= 'X'

= it_sel


= <fs_data> ).

refresh it_sel.

if <fs_data> is assigned.

loop at <fs_data> assigning <fs_wa>.

assign component 'WEKGR' of structure <fs_wa> to <fs_wekgr>.

if <fs_wekgr> is assigned.

loop at e_results assigning <fs_results> where (lv_cond).

assign component 'WEKGR' of structure <fs_results> to <fs_wekgr1>.

assign component 'ARTNR' of structure <fs_results> to <fs_matnr>.

move <fs_wekgr> to <fs_wekgr1>.

move wa_entity-usmd_value to <fs_matnr>.

modify e_results from <fs_results> index sy-tabix.





refresh it_field.




this will give you the result including the Purchasing group. Now the inbox has to be changed based on this.

So, go to transaction code powl_type and change the entry usmd_changerequest_wi and change the class name11.jpg

Now your inbox will be reflected with the new value.

Note: Since inbox is a common component where all workitems from all domains are received, this column will be visible also when you login to govern your vendor master data (for example). In order to avoid this, you have to create a separate role and have your own Powl Id in that which means it will be reflected only in your current Article Inbox.




We started implementing Cost center and Profit center  with MDG 7.0 SP02. Our scenario is to have  a central MDG hub system where the cost centers and profit centers would be maintained and then in turn replicated to other SAP/Non SAP systems.


We decided to use the communication channel 'Replication via Idoc' to SAP systems.During the initial tests in development system, we found out that the standard outbound implementation classes provided by SAP perform remote validations in the target systems via BAPIs before creating and sending a IDOC for e.g.the outbound implementation class was checking if the values are being passed for mandatory fields , whether the values being transferred are available in respective check tables in target systems etc.,If these checks fail , then the replication is stopped at the MDG hub itself and the error messages are logged. These messages could be seen in DRFLOG.



This feature is in fact pretty straight forward and helps in avoiding transferring junk data from MDG hub to other SAP systems.

However , we faced couple of issues while performing tests in development system


1) Existence check:For some fields , the existence check is done. For e.g. there is a field called User responsible. It displays users available in MDG hub system. But users available in MDG hub system were not available in target systems and this caused issues in our tests.


2) Performance: We found out that the performance of the replication was not that great.  During our analysis we found out that the remote checks are taking significant amount of time.


I also wondered if this feature is needed in the scenarios where the MDG  hub and the target system are in the same system.


But this looked like a standard solution and we didn't think of contacting SAP or checking for OSS notes. So , to overcome the above mentioned issues ,  we contemplated the option of copying the standard outbound implementation class to a custom class and then skipping the validations to improve the performance. However , before starting with the implementation , I somehow had this feeling that this is not a problem unique to our organization and it could have been faced by other organizations as well. So out of curiosity I started exploring SDN and OSS notes.


To my surprise , I found out that SAP had already provided a solution for this via OSS notes  2052107 - MDG-F: New Parameter for DRF Outbound Implementations  and   2054082 - MDG-F: Issues in the ALE IDoc Replication for Cost Centers .


With the above two notes SAP has provided a new outbound parameter MDGF_NO_REMOTE_CHECK and also corresponding adaptions in the standard outbound implementation classes. If  the outbound parameter MDGF_NO_REMOTE_CHECK is set to value Y in replication model , the standard SAP  outbound implementation class skips the remote validations. This indeed greatly improved the performance.


I hope this blog would be helpful for all those looking to have the remote validations skipped.

Only recently, I gave a lecture about data quality and master data management/governance for a larger audience. It was a not the first time that I presented the topic, and I started my speech as usual with common business needs for adopting a master data strategy and then moved to the SAP software portfolio that is set to tackle the challenge.

I began with SAP Data Services and Information Steward being the appropriate weaponry for data quality improvement and control, and then came to SAP Master Data Governance bringing in the process component ensuring sustained master data quality by involving predefined validations and putting the relevant data stewards in the driver's seat.

The session went well, there was a lot of interest in the audience, and after the official Q&A part I was approached by a listener who stated that he liked the session overall, but was a bit confused by the product variety outlined in my presentation.


Well, I took the feedback... and forgot about it on my way home. It was only yesterday that this came to my mind again, and I started thinking about what the listener wanted to tell me. From an outside SAP perspective, the world obviously looks a bit different:


As a business or IT specialist in a company, if you are faced with data quality related business issues you want to:


  1. Be in a position where you can easily analyze and visualize existing data issues
  2. Be able to dig into the root cause, and be able to cleanse defective data
  3. Avoid in the long-term that such issues occur again


Actually the outlined SAP solution portfolio perfectly matches these needs, but the way data managers think starts with their needs and ends with a solution, not vice versa. So If I had told the story straight from a solution-oriented perspective and had come up with the associated software only afterwards, I guess the message would have been clearer.

It was really revealing how important it is to take the customers' perspective to get the message across and not just by telling how great our products are.





Dear MDG-Community!


Looking for information on how to build a UI for your custom object?

Then check-out the updated documentation on the help portal:

Creating User Interfaces for Single Object Processing


If you have the change to attend SAP TechEd && d-code, there is also a hands-on session on creating a custom object scenario, including the creation of a UI configuration. Join us at session DMM265 Build Processes for Your Own Master Data with SAP Master Data Governance in Las Vegas, Berlin, or Bangalore.


Can’t get there? Check-out SAP TechEd && d-code online!


Best regards,


Dear MDG-community!


With the availability of SAP MDG 7.0 SP03 we also enhanced the documentation around the change request process. Now, there is a new topic on the help portal: Configuration of the Change Request Process


This topic and its related sub-topics

- explain the change request process

- tell you about step, step type and status

- suggest a notation for change request process flow

- show how to configure the rule-based workflow in detail


We look forward to hear your feedback!


Additionally I want to make you aware of the new edition of the SAP workflow book. It also includes an extensive chapter on MDG - A must-know for all MDG Gurus! (All authors donate their proceeds to Doctors without Borders).


See: Hot off the presses, Practical Workflow for SAP http://scn.sap.com/community/bpm/blog/2014/08/03/hot-off-the-presses-practical-workflow-for-sap


And https://www.facebook.com/Workflowbook


All the best,


Hi SCN folks,

TechEd && d-code is coming closer and I prepare myself for some interesting days soon to come.  I will be in Berlin (November 11–13, 2014) at the EIM table and I am looking forward to having meetings with our customers, partners and of course with many of you.  Please stop by to chat about all EIM related topics.  I can also show you a lot of new live demos showcasing many of the latest new  EIM features. Specifically I have prepared in the last weeks the following scenarios to share with you:

  1. MDG-HANA Roundtrip Demo:
    This will guide you through brand new content which has been available since MDG7 SP02 in Q2 2014: Starting with triggering a MDG CR from a mobile app and approval in NWBC, we will then check the MDG Analytical Reporting dashboard. Lastly, we will drill down in the HANA search to the newly created supplier
  2. New MDG Fiori Apps:
    We have all the new MDG Fiori Apps up and running – we materials, customers or supplier request forms in addition to the new  financial Fiori Apps.
  3. New MDG Hana Drill Down Search for MDG-Suppliers
    This is a dedicated demo for the enhanced capabilities in the HANA Drill Down search. The demo concentrates on a supplier example.
  4. New MDG Analytics based on HANA and SAP Smart Business
    This is very exciting content: We will explore the new dashboard Tiles and Drill Downs available and additionally show how we can configure our own reports.
  5. MDG-IS including single sign-on (SSO)
    An improvement on our existing scenario but still worth looking into the details. I have managed to setup the Single Sign On between the two solutions, as well as the ability to pick multiple records for remediation.
  6. MDG-C: New Workflow Template-content based workflow routing
    Content-based routing is a well-known requirement for a master data related processes. This demo will show you the brand new MDG standard template which supports also parallel processing of content based routing. Triggering the process is done from NWBC or from Fiori app.
  7. MDG-M: BRFplus workflow – Content based routing on Material Group
    Content based workflow routing for material master data.
  8. New MDG-DMS Integration
    This will show you the new capabilities around integration of Document Management Services and MDG including a side panel graphical display to view attached images.
  9. MDG-M: Multiple Record Processing
    Was introduced with MDG7 and has interesting features available.
  10. Like & Lean UIs for Customers and Suppliers
    See how simple you can trigger new Change Requests for customers and suppliers. The complexity of the business partner is hidden to the end user.


Again, I look forward to hopefully seeing you soon and I hope we can also talk about other topics and  answer all your questions.
Let’s see us at TechEd && d-code
Best Regards

To get a complete picture of the lectures and hands-on sessions offered in the context of SAP Master Data Governance at SAP d-code 2014 in Berlin, you can simply go to the agenda builder for the event and filter by search term "SAP Master Data Governance”.
This way, you get an overview of all related sessions. From there, you can dig into the individual sessions that you are interested in to get the details.


Here is the agenda builder SAP d-code Berlin (November 11-13, 2014) already filtered for SAP Master Data Governance


Check it out and filter according to your specific needs.



Today, SAP Master Data Governance (MDG) provides applications to centrally create, change and distribute master data. Being highly integrated with SAP Business Suite, MDG re-uses data models, business rules and process logic. It provides pre-build domain-specific content and a flexible framework to define data models, processes, and user interfaces also for custom-built master data.


If you'd like to be informed on the way ahead, you may check the product roadmap for SAP MDG which has just been updated, providing the current picture of the solution today (SAP MDG 7.0 SP02), planned innovations and future trends.


SAP customers and partners can check out the document on SAP Service Marketplace at http://service.sap.com/roadmaps => Product and solution roadmaps => Database & Technology (SAP Master Data Governance: Edition 2014Q3) (SMP log-in required).




You are trying to enhance standard data model by creating new entity types and creating relationships.



Error while trying to create a leading relationship for new entity type (SU type-4) on entity type-1 .


Error Screenshot




Create new relationship by prefixing ZZ i.e., ZZMATMARC1
MDG menu not visible on NWBC. Instead, It shows an error “The user menu tree for user is empty."
Error Screenshot
Role is assigned but folder is defined as a "link collection" instead of a "service map" - see:http://goo.gl/OEq9qa
Steps to solution
Step-1: Goto transaction PFCG


Step-2: Open your Role in edit mode.


Step-3: Goto ‘Menu’ Tab.


Step-4: Double click on the folder in which your views are defined. If no folder defined, then create one and move the views to this folder.


Step-5: Click on ‘Other Node Details’ button


Step-6: Select ‘Folder Option’ as ‘As Service Map'


Step-7: Save & Execute NWBC
Solution Screenshot




1378659 - NWBC known issues & what to check when opening a ticket


In service master i have  changed the number ranges in ACNR transaction .Now  we are facing the short dump

Asset condition was violated.This is due to the deletion of NR ,how to revert back

.i am able to create in AC03 with new number range But in Nwbc screen the mentioned short dump appears

Issue :


Whenever we are trying to Finalize the change Request (CR) which belongs to country Jersey C I, we have received the process error because of  below error message.




Solution :


To resolve this issue we have followed the below steps.


1.SAP OSS # 1901429 the country Jersey, C.I. ( Code: JE) is related to GB (this country is a crown dependency of the United Kingdom). But when we verified the country’s global parameter setup it is pointing to US (Screen shot: 1). Hence I believe for this reason we are getting the above  error message.







We have mapped  the country code JE to GB parameters.


2. Then we tried to finalize the change request again we have received the process error. This time the error message as "No geocoder for country JE maintained in system (table GEOCODERS)".


To resolve this we maintained the  below entry in the path SPRO--> SAP NetWeaver -->General settings --> Set Geocoding --> Assign Geocoding Program to Countries.



3. After this entry we tried to finalize the CR and received the error message as “Geocoder SAP0: Country specification is incomplete (Customizing)”. To resolve this I maintained the below value in table V_GEOT005 & V_GEOT005S (for Region details).



I found these  values from the URL : http://www.theodora.com/country_digraphs.html (Country : JE --> Geography) . The Geography code is similar to country code GB.


4. After this, when we tried to finalize the CR,we received the error message as “Telephone/fax code for country code JE is not maintained”. Based on this we maintained the entry in the below path


SPRO --> SAP NetWeaver  --> General settings --> Set Countries --> Define Country




I have found the Jersey Calling code from the URL: http://countrycode.org/jersey. This code is similar to GB.




After completing the above configuration, again I tried to finalize the CR  and this time it has been successfully finalized and created the Vendor Master in ECC without any issues.




I believe it might an useful.





just an small update on the work I'm doing with SAP MDG and SAP Information Steward integration: Last week I invested some time in getting the SSO working on an internal system. The good news is:

1. Its working as expected

2. Its pretty simple to configure the SSO.



SAP MDG comes with a DQR (Data Quality Remediation) scenario (see here: http://scn.sap.com/community/mdm/master-data-governance/blog/2013/10/22/sap-mdg-sap-information-steward-a-perfect-combination-for-data-quality-remediation-dqr-scenarios). In general you can integrate any Data Quality tool into this framework. Most of the time I have used SAP Information Steward but i have never tested the SSO between both stacks. The disadvantage of not having SSO configured is that the end users have manually login each time the DQ-dashboard comes up in the SAP MDG User Interface for DQR. With a configured SSO between both stack the users get automatically logged in into the dashboard! - Big advantage, big simplification!


What to do?

On high level you need to do the following steps:

  1. Define a authentication system in CMC - A wizard exists
  2. Generate and import certificates -  with SAP tools provides in your SAP Information Steward installation
  3. Define SSO in your configuration of SAP Information Steward
  4. Restart Tomcat/ Web Server of SAP Information Steward
  5. Define SAP ERP/MDG roles to be SSO'ed in SAP Information Steward
  6. Give the SAP users the correct right in SAP Information Steward


Instead of writing again a guide I would like to mention these detailed guides:






Want to see a demo?

if you want to see a demo, please contact your local SAP contact person The scenario is configured in our sapdemocloud (https://sapdemocloud.com/cloudportal/index.html)


Best Regards


Dear SAP Master Data Governance community,


On behalf of SAP MDG development and knowledge management, I am happy to announce the availablity of an additional SCN site about SAP Master Data Governance. The new site is aimed at featuring learning videos about specific data processing tasks across the master data domains that are supported with out-of-the-box content, while also covering specific processing tasks related to custom objects.
The intention is to give onboarding MDG users a quick start on user interaction in MDG processing.

As such, the new site perfectly complements our SCN learning offering which already features technical best-practice information covering MDG configuration and extensibility, which is specifically tailored for consultants.


As a starting point, the new site already presents three video recordings related to MDG processing topics in MDG for Financials, including change request processing for single and multiple objects, creating a profit center and creating an edition.


... and of course, this initital scope is planned to be extended.


Credit goes to the SAP MDG documentation team who made this possible. I really think this is a perfect means to convey easy-to-digest information about SAP MDG to the user community. Thanks a lot for this great piece of work!


We hope you'll find these videos beneficial for your daily work. Please let us know your thoughts. Your comments help us to continue this path of providing you with additional learning videos.

Thanks, and awaiting your feedback.



Every organization is now muddled with multi system ERP landscape. No matter how many IT consolidation projects are undertaken, after a few years it is back to square one. The dynamic business environment always allows evolution of niche IT solutions while the big brothers SAP & Oracle can keep gobbling them and enhance their portfolio but still within their portfolio of applications, the niche solution tend to maintain their uniqueness and all SAP & Oracle will do is to create a bolt on to their core product that will make the integration simplified.


The biggest pain area due to the multiplicity of IT or ERP systems is master data numbers being different in different systems. To make transactions pass through such multiple systems, interfaces will have all sorts of logic built-in to ensure the different master data numbers are somehow logically matched so that in all the systems same material/vendor/customer or any common master data is being transaction upon. But this turns out to be the weak link that breaks regularly.


Best practice on numbers for master data is never to build logic or intelligence in the numbering systems. Put it differently make it non-speaking so it will not identify itself to you. But this is the rule that is always broken in the environment I have painted above as the end users want the master data numbers to be intelligent and identify itself. Also in an environment where-in you have multiple applications or ERP systems, achieving common numbering systems means it has to be external numbering system. Sometimes this is called "Global Number".


Let us take for discussion the concept of "Global Material Number". By default this number will be externally defined which means some sort of logical process have to be defined. I would say it need not be very intelligent numbering system, but a simple program that can generate sequential numbers with say one character prefix or a suffix. There is no need to even list down the advantages of having a common number like "Global Material Number" across the IT or ERP systems as the benefits far outweigh the shortcomings of such a system.


Hence I strongly feel that having Global numbers that are externally defined in a multi IT or ERP system landscape should be considered a best practice too.


Any thoughts or counter views to my conclusion?


Filter Blog

By author:
By date:
By tag: