Skip to Content

Introduction

 

Warning_20.jpgPrecautionary statement: If you are new to SAP MDG, you might want to read my blog SAP Master Data Governance in SAP Business Suite 7 Innovations 2011 first. That other blog will provide you more of an overall introduction to SAP MDG. This blog here is focusing completely on additional value that the release 6.1 provides.
SAP Master Data Governance (SAP MDG) offers governance applications for master data domains like financials, supplier, customer, and material, all tailored for centralized data maintenance. The applications allow for managing of master data that is ready to use within SAP environments, but also beyond.
Update: We have now released the newest version SAP MDG 6.1 into General Availability by December 14, 2012 after an extremely successfull ramp-up phase of three months. We have seen even higher than anticipated participation of customers and SAP partners in that ramp-up, and we got very good feedback with regards to product quality as well as on the new features. SAP MDG 6.1 is now openly available for all customers.

 

Like the last release of SAP MDG before, this release is also based on Enhancement Package 6 for SAP ERP 6.0. For existing installations, you do not need to upgrade to any higher Enhancement Package, but can just upgrade to SAP MDG 6.1 in that system.
SAP MDG 6.1 ships enhancements for SAP MDG for the mentioned master data domains. It also provides improvements for the MDG Application Foundation that allows for extending the standard content or building governance processes for your self-defined objects.
What is new in SAP MDG 6.1?

The new version of SAP MDG provides an even broader out-of-the-box data model, in particular for the master data domains of Material, Customer and Supplier. Based on the customer feedback we are already receiving via early customer validation and Ramp-Up projects, we are spot on with the new coverage. And it’s huge! See more below. It provides SAP MDG customers a jump start of their implementation projects, since most of the master data attributes they will want to put under central governance is already delivered in standard.

 

Create_Material_640.jpg

 

Figure 1: Create a new material using the wide-ranging master data model of SAP MDG 6.1
SAP MDG’s Application Foundation saw quite some enhancements with regards to integration improvements towards other SAP solutions or also 3rd party solutions via open web services. In addition, there are new capabilities to further ease the configuration of SAP MDG. This is particularly in order to support SAP MDG implementation projects with an even bigger scope, supported by the very broad data models now available in SAP MDG 6.1.
The combination of SAP Information Steward and SAP MDG now allows for data-quality monitoring, as well as integration with processes in SAP Master Data Governance to remediate the issues in the erroneous data.
Let me explain these focus areas of SAP MDG 6.1 in a little more detail.
Increased data model coverage for material, customer and supplier

In the Enhancement Package 6 version, SAP MDG covered identifying and descriptive attributes of material master including basic data and classification. We have extended this scope dramatically by extending the coverage of basic data, as well as by introducing many attributes that are dependent on organizational units like on plants, sales organizations, or distribution channels. Extensions also include data for valuation or tax classification as well as long texts.
As you might know, both data models for the supplier as well as for the customer domain are based on the so-called generic business partner. Until the last release, the focus for supplier and customer data was on generic business partner attributes, corporate, company and purchasing attributes of suppliers, as well as general customer data, and address information. SAP MDG 6.1 provides much broader data models, that now also include partner functions, dunning areas, and withholding tax types, as well as sales area data, tax indicators, and company code data for customers and additional purchasing organization data for suppliers. In addition, SAP MDG can now also handle business partner relationships, contact partners, as well as persons and groups – in addition to organizations that could already be handled before.

 

MDG61_Data_Model_640.jpg

Figure 2: The broad out-of-the-box data model coverage in SAP Master Data Governance 6.1

 

Enhanced Application Foundation facilitating integration and configuration

As mentioned before, you will find improvements in the application foundation of SAP MDG 6.1 that will support easier integration of SAP MDG with other applications in the system landscape. For example, inbound processing of material master data is now supported via Enterprise Services that also support the enhanced data model. Through this you may want to connect SAP or non-SAP applications in order to trigger creation of or changes to material master data managed in SAP MDG.
Another example could be that you want to manage the early lifecycle of supplier in SAP Supplier Lifecycle Collaboration (SLC) and hand over the master data creation or enrichment process to SAP MDG whenever you decide to do business with that particular supplier. While SAP SLC handles the supplier portfolio management of interested suppliers, bidders, and potential suppliers, SAP MDG handles the enrichment of the approved suppliers’ master data with all the attributes that are needed to run purchasing processes with them. SAP MDG 6.1 provides you with the interfaces to enable that integration between SAP SLC and SAP MDG.
As you have seen above, the data model coverage has increased a lot in SAP MDG 6.1. It has increased so much that it goes beyond the scope that some customers might want to cover in their first SAP MDG implementation project. So you might ask yourselves: How can I decrease the scope of the standard data model to what I need now? And can I extend that scope later? In SAP MDG 6.1, we provide a solution for that. The configuration environment has been enhanced by a feature called Governance Scope. Through this you can easy define which part of the data model shall be put under central governance. You can virtually remove or add complete entity types or also single attributes of the data model. The according master data attributes will then be ignored in your governance processes and cannot be maintained through SAP MDG. But they stay part of the data model and can easily be added to your governance scope in the next phase of your implementation or roll-out.

 

GovernanceScope2_640.jpg

Figure 3: Simply switching the Governance Scope on or off in the SAP MDG data model

 

Improved data quality through seamless analytics and remediation

Whenever you access master data in a change request, SAP MDG will enforce data quality based on the configured validation rules. But what about the data that is currently not in a change request? Sometimes master data validation rules may change over time or some validations make only sense when combining master data with related transactional data, which you can obviously not do at time of master data creation. SAP Information Steward allows you to access all master data in your system regardless if it is currently in an change request or not. Based on validation rules and aggregation into data quality KPIs, it can visualize the data quality and allows drill-down to erroneous data. From the list of that bad data, you may want to start a remediation request to have the data corrected. SAP MDG 6.1 allows triggering correction processes to fix master data inconsistencies.
In order to help companies in setting up a seamless experience for their end-users, we are also offering a Rapid Deployment Solution (RDS) that focuses on providing pre-defined content in SAP Information Steward software for profiling and assessing the quality of master data in SAP ECC (table views, validation rules, and so on). It hence provides a data-quality monitoring cockpit for SAP Master Data Governance with direct and transparent insight into the current level of data quality, as well as integration with processes in SAP Master Data Governance to remediate the data issues.

 

InfoSteward_MDG_Remediation_640.jpg

Figure 4: Example UI integration between SAP Information Steward and SAP MDG for data quality remediation

 

For the next years to come, we plan to further extend the standard scope for SAP MDG’s master data domains and selected industry-specific master data models with the next releases of SAP MDG. We plan for additional investments in SAP MDG’s Application Foundation regarding extensibility, flexibility, usability, and ease of consumption. And we plan for further enabling of mobile access to SAP MDG, as well as native integration with SAP’s in-memory technology.
SAP MDG is an important part of SAP’s EIM portfolio

SAP MDG is a tool for central creation or change of master data. Based on your broader Information Governance initiatives, you will want to combine SAP MDG with other solutions of SAP’s Enterprise Information Management (EIM) portfolio.
SAP_EIM_book_200.jpgSAP has recently published a book “Enterprise Information Management with SAP” that is available at SAP Press. The book provides the big picture of SAP’s EIM offerings: what the different products are, how they work together, and how to get started using them. After the overview, you can dive into the details. The book provides very good explanations how to perform the most important tasks in SAP Master Data Governance, SAP Information Steward, SAP NetWeaver Information Lifecycle Management, and SAP Extended Content Management as well as step-by-step instructions for working with SAP Data Services. (Remark that I am actually one of the authors. But since all royalties are donated to Doctors without Borders, I do not feel bad at all promoting the book here.)

 

I already mentioned SAP Information Steward for continuous monitoring of master data quality in all relevant systems and correction in SAP MDG. You will find additional information on the Information Steward site on SCN.
SAP Data Services supports SAP MDG with data quality services, duplicate prevention, validations and data enrichment. This helps to prevent creation of duplicates early and embedded in the process for increased effectiveness and efficiency. You can find more information on the Data Services site on SCN.
As briefly laid out in this blog and in more detail in my other blog mention above, SAP MDG focuses on comprehensive master data ready for use in SAP applications, through ready-to-run governance applications for specific master data domains. In addition, the MDG Application Foundation allows for custom-defined master data objects, processes, and user interfaces. SAP MDG provides pre-built validation against SAP business logic and customer’s configuration settings, and can distribute master data to SAP and non-SAP systems. You can find more information on the SAP Master Data Governance site on SCN.

To report this post you need to login first.

34 Comments

You must be Logged on to comment or reply to a post.

  1. Anurag Garg

    Hi Markus,

    Its an excellent blog highlighting  valuable info on mDG 6.1 new features.

    We are looking for more information and documents on utilising inbound enterprise services for material with MDG6.1. Can you please share me some link on that or pdf’s?

    We are integrating third party as Sender  and MDG as target for Material Create\change\Delete. And need to achieve this through webservices.

    Please share some poiints and docs.

    Many thanks for your help in advance.

    Regards,

    Anurag

    (0) 
    1. Markus Kuppe Post author

      Hi Anurag,

      thanks a lot.

      The service you are referring to is a new inbound SOA service for material replication from any service-enabled external client system to the MDG hub. The service supports the main scope of MDG 6.1 material views, like Basic Data, Classification, Purchasing, Sales, MRP and Accounting.

      The service is asynchronous and mass enabled in order to replicate materials in bulk. During inbound processing it can handle key mapping for identifying fields, value mapping for code relevant fields, and forward error handling.

      You can decide whether the data is written only to the MDG “staging area”. That is, MDG change requests are being created for the incoming changes. Or the data can directly be written into “active area”. That means that the data is directly written into the SAP ERP material master data tables without creating MDG change requests. Or the data can be written into the ERP tables directly and for all erroneous data that cannot be posted, MDG change requests are being created.

      You may find more information on enterprise services for SPA MDG under the following link in SAP Documentation:
      http://help.sap.com/erp_mdg_addon61/helpdata/en/56/071a748f67482f83eca92b965f89f3/frameset.htm.

      You may also want to use transaction “SOAMANAGER” in your system to access the service definition or to create a sample WSDL file.

      In case that you would have access to the SAP MDG 6.1 Ramp-Up Knowledge Transfer Material (http://service.sap.com/rkt), there is more information available on the service in the “SAP Master Data Governance 6.1: Learning Map for Application Consultants” within the presentation “What’s New with Master Data Governance  for Material in MDG 6.1”.

      Best regards,
      Markus

      (0) 
      1. Anurag Garg

        Thanks for your quick answers- Markus.

        I am not getting any documents for MDG6.1 ramup in the link you specified. Can you please give me more deep link specific to MDG6.1?

        I found following services as per the given sap link:

        Material ERP Bulk Replicate Confirmation Out

        Material ERP Bulk Replicate Request In

        Q. Am I referring the correct services for change request to create\change material trigger through webservice?

        Q. I got these services in my Sandbox MDG6.0 system  not MDG6.1. Are there any new services in MDG6.1?

        Many Thanks for your help Markus.

        Regards,

        Anurag

        (0) 
        1. Markus Kuppe Post author

          Hi Anurag,

          as said before, you would need to get yourself access to the Ramp-Up Knowledge Transfer Material. This material is free of charge for companies participating in the (just recently completed) SAP MDG 6.1 Ramp-Up. Else, there is information available under the provided link, how to access the material at additional costs.

          The name of the new service is “Material ERP Bulk Replicate Request In” (technical name “MaterialERPBulkReplicationRequest_In”). You may be able to see the service definition already in any SAP ERP 6.0 EhP6 system. But all you will find is just the technical definition. The service can only be called in SAP MDG 6.1 systems. (Remark that there is nothing like an “MDG 6.0” system.)

          Best regards,

          Markus

          (0) 
  2. Matthew Dawe

    Hi Markus,

    How does SAP MDG handle mass data loads for materials, with hundreds of lines of data.  We use Excel and LSMW at present to do this, but, of course, there is no up-front user validation.

    Thanks!

    Matt Dawe

    (0) 
    1. Ingo Bruss

      Hi Matt

      What exactly is meant with ‘up-front user validation’? LSMW and other standard data migration tools support the standard material master business logic (as executed also in MM01). If you only load into active area (not into a change request), you can use these.

      If you want to load the data into a change request, you can use (depending on your scenario)

      • Data Import Framework (DIF) to load IDocs into a change request (or directly into the active area): Create IDoc XMLs and load them from the application server
      • SOA service MaterialERPBulkReplicateRequest (new with MDG 6.1) for mass material creation/update in active area or via change request: Have a system like BPM or PI create and send a message to MDG-M; the service is of course mass enabled
      • Entity based ‘File Upload’ (application USMD_FILE_UPLOAD): Create one CSV file per entity (and load them one after another into the same change request); this file can contain some hundred records (but not recommended for thousands)

      Best regards, Ingo Bruß

      (0) 
      1. Matthew Dawe

        Hi Ingo,

        Thanks for the response.  I’ve looked at quite a lot of information about SAP MDG, and have seen demonstrations where a business user uses the MDG portal to request the creation of one new material master, or an extend to one material master.  My original question is how does MDG for materials work with a request where, for example, 200 material masters require the same two fields changed for each MM (a mass request)?  Would the MaterialERPBulkReplicateRequest handle this?  If so how?  I’ve found the You Tube demos for MDG to be very useful.  Is there a You Tube demo for MaterialERPBulkReplicateRequest?

        Thanks for looking into this,

        Matt

        (0) 
        1. Ingo Bruss

          Hi Matt, I believe you are looking for a mass maintenance process, changing the same small set of material master attributes for about 200 materials (mas o menos).

          I assume you are looking for a kind of mass maintenance UI, that is to say somebody manually maintains these changes.

          For this, you can

          • Use application USMD_MASS_CHANGE to change entity MATERIAL, MARASALES and MARAPURCH
          • Download data from any entity via USMD_FILE_DOWNLOAD to a csv file, change the fields, upload again via USMD_FILE_UPLOAD

          For more info, please check the documentation for these two applications.

          I know of no video of MaterialERPBulkReplicateRequest, as this has no own dedicated UI.

          Best regards, Ingo Bruß

          (0) 
  3. Abu Zahir Al-Mamun

    Thanks for your blog.

    Currently we are using MDG 606 and MDG_FND 731 with ERP6/EHP6 , when we try to upgrade to MDG 6.1 ( MDG 607 and MDG_FND 732 ) , we don’t see the components in the service market place , later came to know MDG 6.1 is not with our license ,  just wondering if I need additional license to upgrade to  MDG 6.1 when it is available in general.

    Thanks

    Al Mamun

    (0) 
    1. Markus Kuppe Post author

      Thanks for your comment.

      SAP MDG 6.1 does not require any other license than earlier releases of SAP MDG. Usage of SAP MDG is not included in the standard SAP ERP licenses, though. The license for SAP MDG is based on the number of master data objects you are putting under governance and comes on top of your SAP ERP or SAP Business Suite license.

      If your company already purchased one of the following products, you should be able to access all versions of SAP MDG on SAP Service Marketplace:

      • SAP Master Data Governance, Financial data
      • SAP Master Data Governance, Suppliers
      • SAP Master Data Governance, Customers
      • SAP Master Data Governance, Consumers
      • SAP Master Data Governance, Product
      • SAP Master Data Governance, Custom Objects
      • SAP Enterprise Master Data Management

      You can find the software on SAP Service Marketplace under => Support Portal => Software Downloads => (A–Z Index for) Installations and Upgrades => M => SAP Master Data Governance => SAP Master Data Governance 6.1 => Installation. If you cannot find it, please get in contact with your SAP contact person to check whether your purchased licenses are maintained correctly to allow you to access that download.

      Best regards,
      Markus

      P.S.: Let me add some remarks here, regarding what changed in software download in SAP MDG 6.1 compared to earlier versions.

      All earlier versions of SAP MDG have been part of an SAP ERP 6.0 Enhancement Package shipment (4, 5, or 6). SAP MDG 6.1 is the first version that is shipped independently from an Enhancement Package shipment. This means you find earlier versions of SAP MDG also on SAP Service Marketplace under the Enhancement Packages sections, while 6.1 has its own download section.

      This also means that, technically, you would be able to install earlier versions of SAP MDG via Enhancement Packages based on any SAP license that allows you to use certain parts of SAP ERP – even if you do not have an SAP MDG license. (In this case, you are of course not allowed to switch on SAP MDG’s business functions and use SAP MDG, though. See note 1524246 on SAP Service Marketplace.)

      SAP MDG 6.1, on the other hand, you would not even see on SAP Service Marketplace, because here the system checks against the dedicated SAP MDG licenses, which are the only ones that allow for the SAP MDG 6.1 download.

      (0) 
      1. Abu Zahir Al-Mamun

        Hi Markus ,

        Thanks for your prompt reply with all the information, it
        really helped us ( my company ) to understand the licensing option for MDG 6.1.

        I have forwarded MDG 6.1 Licensing options with the higher
        management for further decision.

        Thanks again for the clarification on the matter which is right in
        time, it is really appreciated !

        Al Mamun

        (0) 
  4. Arvind Shenoy

    Hello Markus

    Does the future release of MDG after 6.1 be tied to SAP ECC EHP’s? Will this not necessitate the need for whole ERP upgrade everytime an MDG upgrade is required? We have a situation where we need to implement MDG on a productive instance of ECC which is on EHP4. If we upgrade to EHP 6 for MDG 6.1, and decide we need MDG_APPL or MDG_FND that comes with EHP7, should we plan another ECC upgrade soon in near future?

    Thanks

    Arvind

    (0) 
    1. Markus Kuppe Post author

      Hi Arvind,

      Sorry for the late reply, seems that I accidently turned off subscriptions to my own blog…

        

      We have just released Enhancement Package 7 for SAP ERP 6.0. This Enhancement Package also contains the same version of SAP MDG as SAP MDG 6.1. This means, you can consume our newest version by either installing SAP MDG 6.1 on top of Enhancement Package 6 for SAP ERP 6.0 or by installing Enhancement Package 7 for SAP ERP 6.0.

      For our next SAP MDG release, we currently plan to also allow installation on top of either Enhancement Package 6 for SAP ERP 6.0 or Enhancement Package 7 for SAP ERP 6.0. This would mean: no need to upgrade the Enhancement Package level from SAP MDG 6.1 to next release. Of course this is currently just the plan, stay tuned for an official announcement when we ship the next release.

      Best regards,

      Markus

      (0) 
      1. Matthew Dawe

        Hi Markus,

        Do you have any more information on whether or not it will be possible to install new versions of SAP MDG on top of older EHPs? And if this will be the official policy in the future?

        We are concerned that by choosing to co-deploy MDG on top of our existing ECC, we will run the risk of being behind on new versions of MDG if we are not running the latest EHP. We need to make a decision on co-deployment of MDG or installing MDG as a hub (we only have one instance of ECC). Would it be the case that new versions of MDG as a hub would be independent of ECC EHPs? We are currently running ECC 6 EHP 6.

        Thank you,

        Matt

        (0) 
        1. Markus Kuppe Post author

          Hi Matthew,

          as said, we plan to make the next release (SAP MDG 7.0) available for installation on Enhancement Package 7 for SAP ERP 6.0 as well as for Enhancement Package 6 for SAP ERP 6.0. But we will not offer this for lower Enhancement Packages.

          For future releases of SAP MDG, I cannot tell you as of today. But I would not expect that we will always provide them for “all” Enhancement Packages that SAP might deliver in the meanwhile. It will most probably always be the most recent and maybe sometimes also one lower, or so. In particular, there will always also be a minimum Support Package Stack level for the underlying Enhancement Package as well as for the underlying SAP NetWeaver (AS ABAB) layer, in order to install the newest version of SAP MDG.

          There are benefits for either approach, hub versus co-deployment. If you go for co-deployment, there will be dependencies between the SAP MDG and SAP ERP part of the system. Generally speaking, it means common (Enhancement Package) upgrade schedules. Maybe once in a while, we will give you some extra freedom by providing one extra Enhancement Package for SAP MDG installation.

          Best regards,

          Markus

          (0) 
  5. Pravin Bhute

    Hi Markus,

    This is pretty interesting information on MDG 6.1. Thanks for putting it together.

    We have a concern coming up in MDG that we would rather like to handle proactively than reactively.

    The concern is as the Change Request database would grow bigger as time goes by and eventually it could affect the system performance specially in terms of Response time to End Users.

    We need to work proactively to handle this otherwise this may turn out to be a big bottleneck. I have experienced this in past MDM 5.5 days where this came out an issue because initially a mechanism to delete completed CRs in Portal was not there and this caused entire Portal UI system to go slow. Later on a utility was provided by SAP thru SAP note.

    We would rather prefer Archive/Unarchive instead of CR deletion because it attracts audit requirements.

    Your comments in terms of SAP’s strategy to handle CRs growing database would be highly appreciated.

    Thanks

    Pravin Bhute

    (0) 
    1. Markus Kuppe Post author

      Hi Pravin,

      Thanks for your post.

      You are right; we currently do not offer an archiving function for SAP MDG Change Requests. This is on our roadmap, but I could not give you a date when this will become available.

      On the other hand, typically the amount of master data is smaller by orders of magnitudes than transactional data. Hence, archiving is most of the times a little less critical.

      SAP MDG also does have a quite different database concept than SAP NetWeaver MDM. (SAP MDG has the same as SAP ERP.) So it is a little bit apples and oranges if we try to compare effects on either side.

      Best regards,

      Markus

      (0) 
      1. Pravin Bhute

        Hi Markus,

        Thanks for your prompt response. I do agree since MDG is constantly evolving availability date for such MDG archiving function may not be readily available. We would appreciate this be taken in roadmap and approx. date of availability announced.

        I agree amount of master data would be smaller e.g. Material master data compared to transaction data. However within MDG, Change Request data is equivalent to Transactional data of PO Data or Sales Order data in ECC. Just to give an idea within 2 weeks of go live we already have 2200+ change requests and they are individual, not created thru some bulk load. This is just for one master data object- material. So definitely we feel a need to address the Archiving of CRs rather sooner than later, the way we archive PO and SO transactional data.

        Thanks

        Pravin Bhute

        (0) 
      2. Hans-Joachim Welsing

        Hello Markus,
        are there some news to the archiving of CRs? I am desperately looking for documentation but was not able to find some.

        I am also looking for archiving of MDG-F data.
        Can you provide some new information?

        Kind regards

        Hajo

        (0) 
  6. David Ruiz Badia

    Hi Marcus

    Very interesting blog.

    We are looking for more information and documents MDG 6.1 for Financials.

    We have found two pdf called:

    -SAP Master Data Governance 6.1 MDG for Supplier and Customer – Overview.pdf

    -SAP Master Data Governance for Material Data_Overview.pdf

    Could be so kind to provide some links with the same info but for Financials?

    We are looking architectural specific information.

    Thanks a lot in advance.

    BR

    David

    (0) 
    1. Markus Kuppe Post author

      Hi David,

      Thanks for the feedback.

      The two documents you mention were actually part of the Ramp-Up Knowledge Transfer (RKT) Learning Map for SAP MDG 6.1. Since you have them, I assume that you do have access to this material via http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000752705 (special RKT material license needed).  You will find an overview presentation for SAP MDG for Financial Data on that same RKT Learning Map.

         

      Best regards,

      Markus

      (0) 
      1. David Ruiz Badia

        Hi Markus

        I am afraid we don’t have access to RKT. When trying to access your link, empty page

        appears.

        We found those two doc’s on the web linking directly to SDN:

        http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00f37adb-9e6c-2d10-adad-9ec4b98290e9?overridelayout=true

        So we could not access to MDG for Financials. Could you send us via mail or another way?

        Also we don’t find how to size an ERP in order to install the MDG-F add-on.

        Could you also help us?

        Thanks a lot in advance

        David

        david.ruizb@endesa.es

        (0) 
        1. Markus Kuppe Post author

          Hi David,

          Good to see that these overview documents have also been posted to SCN. The one for Financial Data is actually also at the same place that you referred to:

          The MDG Sizing Guides are available on SAP Service Marketplace (http://service.sap.com/sizing) and via notes.

          You may use the sizing guide for SAP MDG in SAP EhP6 for SAP ERP 6.0 also for sizing of SAP MDG 6.1 since 6.1 is deployed on top of EhP6.

          Best regards,

          Markus

          (0) 
  7. Asidhara Lahiri

    Hi Markus,

    A lot of useful information in your blog and also in reply to various queries – thanks for that.

    I too have a query about an SAP MDG 5 upgrade to MDG 6.1 for a system where MDG-F has been implemented. The architecture is in a Hub model. If we go for a technical upgrade, what is the impact on the existing implementation?

    If you can share any pointers, it would be great.

    Thanks and regards

    Asidhara Lahiri

    (0) 
  8. Simon Cowley

    Hi Markus

    We have been using SOA and in particular FEH in our implementation as a standard for any inbound interfaces. I noticed that is the ESR content there is an Service Interface MaterialERPBulkReplicateConfirmation_In. This appears to be a response message inbound to MDG for updating the Key Mapping but is not yet released. FEH has allowed the business have one framework for error handling and integrates with SWF_BAM and ALM easily so do you know if this is planned to be released?

    We are running MDG 607 SP03.

    Many Thanks

    Simon.

    (0) 
    1. Frank Damaschke

      Hi Simon,

      with MDG 6.1 we deliver the Service Interface MaterialERPBulkReplicateRequest_In which allows to send material master data to an MDG hub. As a response the MDG hub will return a message via Service Interface MaterialERPBulkReplicateConfirmation_Out.

      The other two interfaces MaterialERPBulkReplicateRequest_Out and MaterialERPBulkReplicateConfirmation_In which are meant to replicate material master data from an MDG hub to a client system and receive a confirmation have not been released so far and currently there are no plans to do so.

      Note: It would not make sense to use the interface MaterialERPBulkReplicateConfirmation_In for any other purpose then to receive a confirmation that refers to a request message which has been sent out before.

      Kind regards,

      Frank

      (0) 
    1. Markus Kuppe Post author

      Hi Matt,

      SAP MDG technically is an SAP ERP system (just with dedicated Business Functions switched on and – in case of MDG 6.1 – new Software Component Versions of two Software Components). As you can see on the page you linked above, SAP has already certified the AWS platform for SAP ERP and thus also for SAP MDG.

      Best regards,

      Markus

      (0) 
  9. Adrivit Bhattacharya

    Hi Markus, 

    thanks for sharing this info.

    We have one of our customers going in to MDG-F , and would appreciate SAP’s inputs / thoughts on the following :

    1. Is there any Rapid Deployment Solution focused for MDG-F ?

    2. what are the integration channels with BODS or BPC ? are there any adapters provided or all needs to be custom developed ?

    3. What level of rules & template customization can be done ?

    4. If deployment is standalone (HUB) then how it will be in sync/use the underlying ECC work flow ? In that case is there any workable way to reuse the stuff from ECC ?

    and finally,

    5. any recommendations from SAP on the deployment scenario with the background that if there is road map to move to HANA in the future – what will be pros and cons then to migrate to HANA platform ( if we don’t adopt HANA now)

    Thanks in advance,

    -Adrivit

    (0) 
    1. Markus Kuppe Post author

      Hi Adrivit,

      Rapid Deployment Solutions for MDG can be found at http://service.sap.com/rds => Solution availability by technology => Enterprise Information Management => SAP Master Data Governance rapid-deployment solution (http://service.sap.com/rds-mdgca). Under Solution Discovery you will find a description of the offering, with a focus on Customer, Supplier, and Material/Product. We plan to extend the focus to Financials in future versions.

      SAP MDG can distribute master data, for example, using web services. These web services can be consumed by any retrieving application that wants to consume the master data from SAP MDG. To my knowledge, the consumption in BODS as well as in BPC will still involve some project work.

      SAP MDG is extremely flexible with respect to data model, user interface configuration, rules definition and flexible rules execution, workflow – including run-time routing based on master data attributes or change request status, etc. And in the unlikely event that these configuration options would not be sufficient, you can even branch out into ABAP coding for everything else.

      An SAP MDG system is always an SAP ERP system. This means, SAP MDG always has full access to (the underlying) SAP ERP system and its capabilities. “Co-Deployment” versus “Hub” rather refers to the fact whether you pick one existing ERP system and switch on MDG on that system (co-deployment) or whether you set up a completely new system as an MDG hub. Reasons to pick a hub might for example be system landscape considerations, or that the potential SAP ERP system for co-deployment follows a different upgrade strategy than you would like to have for your SAP MDG deployment.

      Each company’s SAP HANA adoption strategy seems to be a little different. But obviously SAP MDG is a very natural first choice for using HANA, and to benefit from HANA capabilities like fuzzy search and matching or attribute-based drill-down scenarios. The migration itself will technically be the same in both cases, be it co-deployment or hub. So the consideration is rather whether you want to do the HANA migration for the MDG scope and the ERP scope together or separately. Obviously if you co-deploy, you can only move MDG and ERP to HANA at the same time. In a hub deployment, you have the flexibility to move the MDG system and the other ERP system(s) at different times.

      Best regards,
      Markus

      (0) 

Leave a Reply