GDS?
- Global Data Synchronization (GDS) is a term used to describe an industry initiative focused on keeping item information in sync between retailers and their suppliers.
- GDS is a standardized process for the exchange of product data in the Global Data Synchronization Network (GDSN),built around the GS1 Global Registry and certified data pools.
- GS1 Standard Board developed the Global Data Synchronization (GDS) process.
- The solution integrates with downstream systems to help suppliers aggregate and validate GDS specific data and send this data through the appropriate format and process to their data pool.
- For retailers, the solution enables a company to publish/subscribe to information, integrates downstream current, new product introduction or maintenance processes.
- The following industries are actively participating in GDS:
- Grocery
- Food and Beverage
- Health and Beauty
- Electronics
- Over the Counter (OTC)
- Music, Movie, Games
- Apparel (minimal)
- Hardlines
Overview
- The SAP solution for Global Data Synchronization is a turn-key application which leverages the NetWeaver platform and MDM to provide a comprehensive end-to-end solution.
- Source data is sent from SAP MDM or SAP ECC to SAP GDS using PI interface.
- There are five simple steps that allow trading partners to synchronize item,
- Load Data: The seller registers product and company information in its data pool.
- Register Data: A small subset of this data is sent to the GS1 Global Registry.
- Request Subscription: The buyer, through its own data pool, subscribes to receive a seller's information.
- Publish Data: The seller’s data pool publishes the requested information to the buyer’s data pool.
- Confirm & Inform: The buyer sends a confirmation to the seller via each company's data pool, which informs the supplier of the action taken by the retailer using the information.
GDS Architecture
Registering Inbound Interfaces for GDS
- To receive inbound messages from SAP PI, the Java Proxy Runtime (JPR) to be registered on the SAP GDS.
- This task is performed on the PI Adapter Engine on the Web AS Java for the SAP GDS Console.
- Open the JPR proxy server configuration pages of the Web AS Java on which the GDS Console is installed: http://<GDS server name>:<port number>/ProxyServer/.
- Use the /register command to register the following interfaces one after the other, using the nomenclature shown on the JPR proxy server page:
| Part of Register Command | Entry |
|---|---|
| myNamespace | http://sap.com/xi/GDS/21 |
| Interface | MI_TradeItems_In |
| Bean | TradeItemsInProxy |
| Method | mITradeItemsIn |
- The URL for registering the inbound proxy will be as follows :
http://<GDS Server>/ProxyServer/register?ns=http://sap.com/xi/GDS/21&interface=MI_TradeItems_In&bean=TradeItemsInProxy&method=mITradeItemsIn
http://<GDS server>/ProxyServer/register?ns=http://sap.com/xi/GDS/21&interface=MI_DataPoolResponse_In&bean=DataPoolResponseInProxy&method=mIDataPoolResponseIn
Process Integration - SAP PI
- SAP NetWeaver Process Integration is the central component for exchanging messages between SAP GDS and 1-Sync.
- Based on GDS Version 2.0 / 2.1 the respective standard content to be imported to SAP PI.
- SAP GDS Inbound mapping to be developed using the standard GDS data types. E.g.: TradeItems
- Data can be sourced from any system with PI certified connectivity.
- Default values and additional mappings can be set.
- Customize the GDS outbound mapping (GDS to 1SYNC) based on business needs available under the SWC 1SYNC/68 -1SYNC current version.
- XI Adapter - Java Proxy is used to communicate with SAP GDS application.
- Technical and Business system should be properly configured in PI SLD.
- PIAFUSER is used to connect to SAP GDS Application from PI. PIAFUSER – User should be created in PI and GDS systems.
- AS2 adapter is used to communicate between SAP GDS and 1SYNC.
Please feel free to share your thoughts and suggestions in the comments!
Follow me on Google+