Skip to Content
Author's profile photo Markus Ganser

What is new with SAP MDM Global Data Synchronization 2.1

SAP MDM Global Data Synchronization lets you manage data and communication in an integrated central console for better supply chain operations. In particular, GDS can drive unnecessary costs out of the supply chain by decreasing retail out-of-stock situations, reducing price settlement claims, and achieving more efficient promotion planning as well as a more-efficient replenishment process between supplier and customer. Find more information in the GDS Solution Brief.

With the new version of SAP NetWeaver Master Data Management Global Data Synchronization (release 2.1, currently in ramp up) SAP provides, for example, enhanced process automation and the ability to exchange prices in compliance with the GS1 format. GS1 is a non-profit organization establishing standards for World Trade.

In particular, SAP NetWeaver MDM GDS 2.1 has the following new and enhanced features:

  • Price synch capabilities

    ERP Import based on VPRICAT transaction. UI for price component maintenance. Outgoing catalog type message based on GS1 interface without out of box response handling.

  • SA2 Worldsync connectivity

    Certificated Trade Item Synch Message Choreography

  • P2P data exchange

    Sending out selected set of trade item in a catalog xml format to a trade partner via PI

  • Functional improvements

    > Publication Automation
    > Workflow Identification by Item
    > Process Log (GTIN, Validation, Mass Delete, Co-Relation Manager in Log) 
    > Display Images
    > Propagate data through a hierarchy based upon material number 
    > Workflow Mass Delete
    > Limit User Visibility by Target Market
    > Trade Partner Selection by TM, GPC in Publication
    > Plan EJB or Web Service Interface for Partners
    > Create Trade Item to Multiple Target Market
    > Search for Publication Results
    > Lock/Unlock User

If your company is interested in participating in the GDS 2.1 product ramp-up, you may contact your SAP Account Executive.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Hi Markus,

      thank you for the information.
      We are about to implement GDS. According to my understanding however, we would need one GDS repository per Data Pool we connect to. That means basically for each country we have one repository, which would add up to about 20. That is hardly manageable. Is my understanding correct? According to SAP this is as well solved now in GDS 2.1.
      Could you enligthen me here a little? I did not find clear information on this in the documentation.

      Thank you in advance.

      Best regards

      Author's profile photo Markus Ganser
      Markus Ganser
      Blog Post Author
      Hi Christian,

      Thanks for your comment. I'd say that you'd in fact need to have different installations for different data pools (e.g., 1Sync and SA2 (SINFOS)), but there is no need to have one repository per target market. One repository can cover several target markets.

      Regards, Markus