Upon completion of a GPC publication (twice per year) the GPC Service Provider (SP) sends the GDSN two files; XML Schema
- A complete snapshot of all active nodes in all published standards in the GPC Schema at the point of publication. The purpose of this document is to provide a complete and correct view of what is contained in the GPC Schema at the point of publication. XML Delta
– An XML document that contains all of the changes between the current and previous publications. The purpose of this document is to enable automatic changes/updates to GPC data contained in the GDSN. GDSN will integrate/process the XML Delta document. The XML Delta identifies changes to the GPC Schema by identifying the type of change using change codes and the level of change (Segment, Family, Class, etc.). A complete snapshot of all active nodes in all published standards in the GPC Schema at the point of publication. The purpose of this document is to provide a complete and correct view of what is contained in the GPC Schema at the point of publication. XML Delta
– An XML document that contains all of the changes between the current and previous publications. The purpose of this document is to enable automatic changes/updates to GPC data contained in the GDSN. GDSN will integrate/process the XML Delta document. The XML Delta identifies changes to the GPC Schema by identifying the type of change using change codes and the level of change (Segment, Family, Class, etc.).
The network will not/cannot validate if the code used is valid in context (i.e. this Brick code is valid for this product)
The type of code assigned depends on the relationship between the trading partners (TP) and solutions providers (SP). The TP will make every attempt to find the correct code. If the correct code cannot be found, they must use “8 nines” until an appropriate code is made available. In order to create a new code, the next step would be to submit a Work Request (WR), monitor the progress, and once an appropriate code is made available via the GSMP, update their system when it becomes available in the network. The GPC schema can only evolve when WRs are received. Every WR is processed individually and so categories can evolve separately at any time. This is the driving force behind GPC’s publication release strategy which prohibits version numbers. Each publication is date stamped.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article