In the GDSN, suppliers and retailers are not directly connected to each other- so there is no need to establish point-to-point connections, which is a huge advantage. A GDSN certified data pool, such as the atrify data pool, is always an entity in between both parties and receives messages from both: information providers such as suppliers, brand owners or medical device manufacturers and information recipients like retailers, app providers or hospitals. Information providers send their item data and publications. Whereas information recipients send subscriptions and item confirmations. In addition to that a data pool acts as a relay between other data pools and suppliers or retailers e.g. if both parties are working with different GDSN data pools.
That is why understanding the addressing topic is paramount to success!
The atrify data pool uses the Sender and Receiver identifier for authorization and routing of response messages (gdsnResponseMessage). All parties sending to atrify data pool need to be set-up for authorization purposes and to correctly address the response message (gdsnResponseMessages) that are generated by the GDSN data pool.
The entity sending a message is expected in the so called Sender identifier:
Sending messages to a GDSN data pool requires you to use the correct data pool GLN as Receiver identifier; 4049111100007 in production environment and 4049111170017 in pre-production environment when sending to atrify data pool.
atrify data pool also uses the Sender GLN to dispatch the gdsnResponseMessage and sends it back to the sender of the original message by using the Sender identifier GLN Value within Receiver identifier.
In the above example, the gdsnResponseMessage will have the following identifier:
Using a wrong Receiver or Sender GLN will cause issues with regards to successful XML processing and gdsnResponseMessage addressing.
In case any questions are left, our Professional Services Experts are very happy to help.