Skip to Content

GDS Inbound Process:
In this blog we will see the process used to send data from SAP MDM to SAP GDS. SAP GDS will receive Product/Materials  information from SAP MDM or SAP ECC. All the GDS relevant data that is required to create items in GDS is entered in SAP MDM product and sent from MDM 7.1 to GDS 2.1 via PI.

The Product Global Master Data repository in MDM is a custom built repository.


  • MDM Adapter is used in PI to receive the data from SAP MDM.
  • GDS Standard content (XML structure) has to be used in PI to send the data to GDS.
  • Registering Inbound Interfaces of SAP GDS – Refer the blog GDS Overview and Technical Guide for PI.


Flow

Untitled.png


  1. Product Information details are sent from MDM Product Global.
  2. PI picks the files using MDM/File Adapter and transform the message to GDS understandable format – MT_Trade Items XML Message.
  3. MT_TradeItem message is sent to GDS Via Java proxy Run time call.(XI Proxy adapter is used )
  4. JPR Layer in SAP GDS Performs Pre validation and then passes on the data to GDS core component.
  5. The GDS core components apps drives the creation/Modification of the item by invoking MDM Java API to make calls to the MDM server and get the status for the transaction.
  6. Status and details for the transaction execution are then added to the process logs.


Points to remind


  1. GTIN, Information Provider GLN and Target Market are the mandatory attributes required in GDS to determine whether the item is New/Modified.
  2. GDS will insert/update the item based on the uniqueness of GTIN, IP (Information Provider) GLN and TM( Target Market).
  3. GDS custom attributes creation should follow the standard SAP naming conventions, it should start with Z<Attribute NAME>.
  4. Any new creation or modification of the GDS table requires GDS console and server restart for changes to be effective.
  5. Custom attribute mappings should be handled under custom elements in the PI mappings.
  6. CustomGenericElement,CustomLookupElement,CustomLanguageElement and CustomQualifierRecordElement are the types of GDS custom attributes.
  7. Table code, Field code and reference path to be mapped with reference to SAP GDS attributes.
  8. IP GLN key values mapping should be maintained in SAP GDS Parties table.
  9. Key and value attributes in the PI Mappings to be mapped accordingly.
  10. GDS Key value mappings are case sensitive, if hard coded in PI it should be case sensitive same as GDS.
  11. If key value mapping is not maintained in GDS the item will throw warnings and we can see it in GDS Process logs.

Next blog will discuss about the GDS export ProcessGDS Outbound Process – Item Register and Publish in 1Sync

Please feel free to share your thoughts and suggestions in the comments!!


Follow me on Google+

To report this post you need to login first.

6 Comments

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

Leave a Reply