| Category:
|
Term |
Translation/Acronym |
Definition |
| Basic Party Sync |
Additional Party Identification Number Type |
|
Same as EAN.UCC XML Party Identification Additional Party Identifier Type. |
| Basic Party Sync |
Additional Party Identification Number. |
|
Same as EAN.UCC XML Party Identification Additional Identification. An identifier that allows a progression of existing id’s that may be used to identify organizations (for example in the U.S. companies frequently use Duns+4, Retailer Assigned Store #, etc. to identify locations) |
| Basic Party Sync |
City |
|
An attribute in the Address which provides a textual identification of the party’s City description of physical location. |
| Basic Party Sync |
Communication Channel Code |
|
The identifiers used for communicating with a Party, for example, their telephone number, email address, physical address etc. |
| Basic Party Sync |
Contact Email |
|
The e-mail address for a party’s contact. |
| Basic Party Sync |
Contact Number |
|
The primary telephone number for a party’s contact. |
| Basic Party Sync |
Country Code |
|
An attribute in the Address which provides a textual identification of the party’s Country Code description of physical location. It is presented as a 3-digit ISO Code 3166-1. |
| Basic Party Sync |
Information Provider GLN |
|
The Global Location Number of the originator of the data. This could either be a data source or a data recipient. |
| Basic Party Sync |
Language |
|
An attribute in the Address which provides a textual identification of the party’s Language description of physical location. It is presented as an ISO Code 639. |
| Basic Party Sync |
Party |
|
A business entity. |
| Basic Party Sync |
Party Name |
|
The textual identification of the Party. |
| Basic Party Sync |
Party Role |
|
An attribute which defines the relationships of the Party. |
| Basic Party Sync |
Postal Code |
|
An attribute in the Address which provides a textual identification of the party’s Postal Code description of physical location. |
| Basic Party Sync |
Primary Contact Name |
|
Attributes which identify and detail the textual identification of a person name or department name and their communication channels. There could be one or more for a Party. |
| Basic Party Sync |
Registration Date |
|
The date and time when the Party record is initiated / created in the GS1 GR. |
| Basic Party Sync |
Secondary Government Area |
|
Free form text for providing State/Province/Department of Party address. |
| Basic Party Sync |
Street Address |
|
An attribute in the Address which provides a textual identification of the party’s street description of physical location. |
| Catalog Item Sync Item Confirm |
Acceptance Acknowledgement |
|
A message sent by the receiving unit to the sending station or computer indicating that transmission has been processed successfully (syntax and content). |
| Catalog Item Sync Item Confirm |
Acknowledgement |
|
In the global data Synchronization process, this is a Response to a command returned to the originator of the command. Every command needs a Response. In the inter-operable network, Acknowledgement messages are standardized and may contain the following information: confirmation of message receipt (see receipt Acknowledgement), success/failure of processing for syntax and content (see acceptance Acknowledgement) or reason code for each type of failure (see Business error) |
| Catalog Item Sync Item Confirm |
Add Catalog Item |
|
The command to create a new Catalog Item record. |
| Catalog Item Sync Item Confirm |
Align Data |
|
The uniform definition of Electronic Commerce (EC) constructs to support defined business processes. This alignment is the exchange of basic business data such as the trading partners’ names, addresses and agreements, Item information, price lists, and locations. The process of alignment creates a common understanding between the trading parties and is fundamental to all trade activities. |
| Catalog Item Sync Item Confirm |
Business Error |
|
A message sent by the receiving unit to the sending station or computer indicating that transmission has errors (code type and text). |
| Catalog Item Sync Item Confirm |
Cancel Date |
|
Date assigned by Data Source and stored in the source Data Pool reflecting the date the Catalog Item was cancelled. This date will also be stored in the Registry. |
| Catalog Item Sync Item Confirm |
Cancel Item |
|
Global data Synchronization term describing a maintenance function used to communicate that a Catalog Item was never manufactured. This allows reuse of the GTIN 12 months after cancellation. |
| Catalog Item Sync Item Confirm |
Catalog Item |
|
The Item as it is stored in a catalog or Data Pool. This is uniquely identified by (GTIN + GLN + Target Market). |
| Catalog Item Sync Item Confirm |
Catalog Item Child Item Link |
|
A class of information to identify the quantity of items within a packaging hierarchy level within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Catalog Item Classification |
|
See classification |
| Catalog Item Sync Item Confirm |
Catalog Item Confirmation |
|
This refers to electronic communication from the Data Recipient to the Data Source indicating what action has been taken on the Item. The confirmation process occurs in the recipient’s Data Pool. Confirmation is not mandatory. When used, it provides for the following outcomes:
1. Synchronized: data is integrated, in synch and added to the Synchronization list.
2. Accepted: Data has been recieved by the Recipient, but no business decision has been made on the data.
3. Rejected: recipient requests that no further updates are desired. Data will no longer be synchronized or updates will no longer be provided.
4. Review: a request to the Data Source to “review” their data because the Data Recipient has received discrepant data which they cannot synchronize. |
| Catalog Item Sync Item Confirm |
Catalog Item State |
|
The four states are: Registered , Cancelled, In Progress and Discontinued. |
| Catalog Item Sync Item Confirm |
Catalogue Item Confirmation State |
|
The four states reflected by a Recipient Data Pool are: Accepted, Rejected, Review and Synchronised |
| Catalog Item Sync Item Confirm |
Catalogue Item Dates |
|
A class of information used to describe the dates of the action taken on the catalogue Item record within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Catalogue Item Link |
|
A business message used to identify the packaging hierarchy levels of trade items. |
| Catalog Item Sync Item Confirm |
Catalogue Item Notification |
|
A business message used to transmit trade Item information from a Data Source or a Data Pool to a Data Recipient with the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Catalogue Item Publication |
|
A business message standard used to distribute trade Item information within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Catalogue Item Reference |
|
A class of information from the Catalogue Item Common library used to identify the key to the trade Item information using the Data Source GLN, the GTIN, and the Target Market within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Catalogue Item Registration Information |
|
A class of information used to identify the the dates of the action taken on the Global Registry Item record within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Catalogue Item Registration Response |
|
A business message used to notify a Data Pool of the status of the Registration in the Global Registry for a trade Item. |
| Catalog Item Sync Item Confirm |
Catalogue Item Subscription |
|
A business message used to establish a request for the update of trade Item information from an end recipient on a continuous basis. |
| Catalog Item Sync Item Confirm |
Certification |
|
The accreditation of organizations to perform activities that conform to established business processes, business models and rules such as: Certification of other organizations, operation of the Global Registry, operation of data pools, Validation, authentication, consultancy, etc. |
| Catalog Item Sync Item Confirm |
Certification Body |
|
Organization that performs the Certification process. (This is stored in the Registry). |
| Catalog Item Sync Item Confirm |
Certification Expiration Date |
|
Date on which the Data Pool Certification is no longer valid. (This is stored in the Registry). |
| Catalog Item Sync Item Confirm |
Certification Identification |
|
Value that uniquely identifies a certified member of the Global Data Synchronization Network GDSN. (This is stored in the Registry). |
| Catalog Item Sync Item Confirm |
Certification Start Date |
|
Date on which the Data Pool obtains Certification. (This is stored in the Registry). |
| Catalog Item Sync Item Confirm |
Certification Status |
|
Indicator of the stage of the Certification process (This is stored in the Registry). |
| Catalog Item Sync Item Confirm |
Change Catalog Item |
|
The command to update an existing Catalog Item record. |
| Catalog Item Sync Item Confirm |
classification |
|
A classification schema is an Industry accepted, standardized method to group like products together so that global searches can be enabled. Within Data Synchronization, a classification for the Item is mandatory. |
| Catalog Item Sync Item Confirm |
Compliance Check |
|
The Validation of specific data or data constructs to defined industry standards. |
| Catalog Item Sync Item Confirm |
Construct |
|
Data or data structure. |
| Catalog Item Sync Item Confirm |
Content Provider |
|
See Data Source |
| Catalog Item Sync Item Confirm |
Context |
|
“Context is expressed as classifications drawn from various standards (business sub-process, industry, region and geography, product, legislative). The idea of Context is that the structure of a piece of business information is defined by the purpose which it serves within a business process, an industry, region, etc.”
Example: An Item can be defined in Context of Global for product type FMCG (Fast Moving Consumer Goods) or other verticals. |
| Catalog Item Sync Item Confirm |
Core Data |
|
Core is defined as “common, reusable elements across various business processes. They can be mandatory or optional. Core is a common denominator upon which extensions are built”. Example: GTIN, Ship To, Date |
| Catalog Item Sync Item Confirm |
Core Extensions = Cross Industry Extensions |
|
Data or data constructs specific to more than one process, industry or sector but not used across all. |
| Catalog Item Sync Item Confirm |
Correct Item |
|
Refers to a command that allows incorrect data to be altered in ways that would not normally be allowed by standard GTIN allocation rules. All other Validations still apply. This process is intended to correct errors, not to circumvent the Validation process. |
| Catalog Item Sync Item Confirm |
Correct Item Link |
|
Command that allows alteration of Item links that were incorrectly entered provided that the integrity of the Item Hierarchy is not impacted. If the Item Hierarchy is impacted, the “correct Item link” command must not be applied. Instead, the incorrect Item link must be deleted and a new Item Link added. |
| Catalog Item Sync Item Confirm |
Data Pool |
|
A repository of Data where Trading Partners can obtain, maintain and exchange information on items and parties in a standard format through electronic means. |
| Catalog Item Sync Item Confirm |
Data Pool Certification Information |
|
A class of information used to describe the status of a data pool’s Certification within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Data Pool Certification Status List |
|
A class of information used to identify the Certification status of a Data Pool within the Global Data Synchronisation Network. The values include: Certification initiated; Certification pending, Certified, and Reviewed for Certification. |
| Catalog Item Sync Item Confirm |
Data Pool Profile |
|
Information that allows data pools to interoperate with each other technically and from an operational business perspective. This information includes (but is not limited to): business, administration and technical contacts, capabilities, services, network addresses and transport protocols. |
| Catalog Item Sync Item Confirm |
Data Recipient |
|
Party, which is authorized to view, use, download a set of Master Data provided by a Data Source. |
| Catalog Item Sync Item Confirm |
Data Source |
|
Entity that provides the global data Synchronization network with Master Data. The Data Source is officially recognized as the owner of this data. For a given Item or Party, the source of data is responsible for permanent updates of the information under its responsibility. |
| Catalog Item Sync Item Confirm |
Data Synchronisation Data Pool Profile |
|
A business message used to identify a Data Pool within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Data Synchronisation Error |
|
A business message used to notify a member of the Global Data Synchronisation Network of an error that has occurred within the process. |
| Catalog Item Sync Item Confirm |
Data Synchronisation Error Information |
|
A class of information used to describe an error within the Global Data Synchronisation Network and it’s process. |
| Catalog Item Sync Item Confirm |
Data Synchronisation Error Reference |
|
A class of information used to describe the entity and the type of process identified as an error within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Delete Catalog Item |
|
The command to flag the existing Catalog Item record for deletion (The objective is to enable the eventual removal of the Catalog Item record from the Data Pool.) |
| Catalog Item Sync Item Confirm |
Delete Catalog Item Link |
|
The command to flag the existing Catalog Item link record for deletion. |
| Catalog Item Sync Item Confirm |
Deletion Date |
|
Date assigned by Data Source and stored in the source Data Pool reflecting the date the Catalog Item was flagged for deletion. This date will also be stored in the Registry. |
| Catalog Item Sync Item Confirm |
Discontinue Date |
|
Date assigned by Data Source and stored in the source Data Pool reflecting the date the Catalog Item was discontinued. This date will also be stored in the Registry. |
| Catalog Item Sync Item Confirm |
Discontinue Item – Permanent |
|
Refers to permanent removal of an Item in the supply chain. This involves maintaining a discontinuation date in the Registry. The discontinuation date is used to trigger and track the EAN.UCC retention period. |
| Catalog Item Sync Item Confirm |
Discontinue Item - Temporary |
|
Refers to removing an Item temporarily from the supply chain. This is communicated via End Availability Date. When available again, updated start and End Availability Dates are provided. Temporary removals are not reflected in the Registry. They are a responsibility of relevant data pools who maintain the availability period. |
| Catalog Item Sync Item Confirm |
Document |
|
“Business data being exchanged in support of business processes. It is a named collection of core and extensions”. Any self-contained piece of work created with an application program and, if saved on disk, given a unique filename by which it can be retrieved. Documents are generally thought of as word-processed materials only. To a computer, however, data is nothing more than a collection of characters, so a spreadsheet or a graphic is as much a Document as is a letter or report. |
| Catalog Item Sync Item Confirm |
Electronic Address |
|
The Internet Protocol identification for a certified Data Pool within the GDSN. |
| Catalog Item Sync Item Confirm |
End Availability Date |
|
The date at which a trade Item or a location will no longer exist. |
| Catalog Item Sync Item Confirm |
Error Name |
|
A brief, text description related to an Error Number. |
| Catalog Item Sync Item Confirm |
Error Number |
|
An identification code used to relate to an Error Name. |
| Catalog Item Sync Item Confirm |
Extension |
|
“Extensions to core represent defined business processes which go beyond core requirements. Optional Core Data may be used in an Extension but are not required.”
Example: US Grocery Extension for Item, VAT |
| Catalog Item Sync Item Confirm |
Full Hierarchy |
|
A Construct of data containing a set of GTINs and Links that make up a unique relationship from the highest level GTIN with no parent down to the lowest level GTIN with no children |
| Catalog Item Sync Item Confirm |
GCI |
|
Global Commerce Initiative |
| Catalog Item Sync Item Confirm |
Global Data Dictionary (GDD) |
|
The repository of definitions and attributes of all data elements used within the EAN·UCC Business Message Standards. |
| Catalog Item Sync Item Confirm |
Global Data Synchronization Network (GDSN) |
|
The Global Data Synchronization Network is a federation of interoperable certified Data Pools and a certified Global Registry that collectively provide for the Synchronization of Master Data between Trading Partners on a global basis. |
| Catalog Item Sync Item Confirm |
Global Location Number (GLN) |
|
Unique location number mandatory within the Global Data Synchronization process to identify data owners/info providers, etc such as Distributors, brokers, manufacturers. |
| Catalog Item Sync Item Confirm |
Global Registry |
|
A directory for the Registration of unique catalog items and parties. It contains a limited data set certified to be EAN.UCC compliant and acts as a pointer to source data pools where Master Data is housed. |
| Catalog Item Sync Item Confirm |
Global Trade Item Number (GTIN) |
|
A particular Global trade Item Number, a numerical value used to uniquely identify a trade Item. A trade Item is any trade Item (trade Item or service) upon which there is a need to retrieve pre-defined information and that may be planned, priced, ordered, delivered and or invoiced at any point in any supply chain. |
| Catalog Item Sync Item Confirm |
Governance |
|
It is the management of the ongoing process for Master Data Synchronization and consists of: controlling changes to scope, rules and standards, establishing and regulating the Global Registry, regulating the Certification of Organizations, and regulating the business model. |
| Catalog Item Sync Item Confirm |
Inter-Operability |
|
The ability to communicate Master Data in a standardized and transparent way throughout the global data Synchronization network. |
| Catalog Item Sync Item Confirm |
Item |
|
An Item is any product or service upon which there is a need to retrieve pre-defined information and that may be priced, ordered or invoiced at any point in any supply chain. An Item is uniquely identified by a EAN/UCC Item number (gtin)">Global Trade Item Number (GTIN). |
| Catalog Item Sync Item Confirm |
Item Link Notification |
|
A term used to advise data recipients of relationships among Items. This Notification always provides the entire Item hierarchy. In case of an Item Link correction, the entire hierarchy will be indicated as corrected in the Notification. The updated hierarchy always fully replaces the current hierarchy. |
| Catalog Item Sync Item Confirm |
Last Change Date |
|
Date assigned by system indicating last time the information was changed. This date is generic and will be stored where assigned and will accompany every message. |
| Catalog Item Sync Item Confirm |
Manufacturer |
|
The Party that produces the Item. |
| Catalog Item Sync Item Confirm |
Market Group |
|
A proprietary group of data recipients normally determined by the Information Provider, although it can also be created by buyers and third parties. The Market Group is a common term and should not be confused with the Target Market Codes. This group is developed and used by the Information Provider to control the Publication of data to a specific group of customers. |
| Catalog Item Sync Item Confirm |
Master Data |
|
Within the Context of Data Synchronization, any data or constructs that are applicable across multiple business transactions. Master Data describes each Item and Party involved in Supply Chain Processes. Each data set is uniquely identified by a Item number (gtin)">Global Trade Item Number (GTIN) and a Global Location Number (GLN). Master Data can be divided into neutral and relationship dependent data. Typically Master Data is static - not transactional. |
| Catalog Item Sync Item Confirm |
Master Data Global / Local Status |
|
GLOBAL = (G): Indicates that the data element is required by all markets and contains the same information (e.g. GTIN)
GLOBAL/LOCAL = (G/L): Indicates that the data element is required by all markets but that the actual value can be different for each one (i.e. language, tax indications etc.)
LOCAL = (L): Indicates that the data element is required for a limited number of markets (i.e. Green point – Germany) Local requirements occur in Response to national legislation, national standards or languages. |
| Catalog Item Sync Item Confirm |
Master Data Identification |
|
A Data Synchronization term used to describe the unique identification of an Item in a product catalogue (=key) in compliance with EAN.UCC standards. This is achieved by the combination of 3 attributes: GTIN, GLN of Information Provider, and Target Market. For product catalogue management purposes, a product cannot be uniquely identified by its GTIN alone as there are valid business cases for information provider and Target Market specific data. |
| Catalog Item Sync Item Confirm |
Master Data Synchronization |
|
The process of continuous harmonization of Master Data between all Trading Partners within the supply chain through use of EAN.UCC standards. |
| Catalog Item Sync Item Confirm |
Matching Process |
|
A critical step within the data Synchronization process that is owned and developed by each source Data Pool in order to trigger data distribution based on Publication and Subscription data. The Matching Process can be triggered either by Publication, Subscription or as a scheduled event. |
| Catalog Item Sync Item Confirm |
Neutral Data |
|
Within the Context of Data Synchronization, Master Data or constructs applicable across multiple business transactions and constant across all Trading Partners, such as Item, Party, standard terms, etc. |
| Catalog Item Sync Item Confirm |
New Item Hierarchy |
|
A new Construct of data containing a set of GTINs and Links that make up a unique relationship from the highest level GTIN with no parent to the lowest level with no children. To create a new Item Hierarchy, the Information Provider (or data owner) enters Item and Item Link data into the Source Data Pool. The Data Pool verifies that the information loaded is “correct” and then sends the relevant Item data to the registry for Registration. Item link data is not sent to the Registry as links are not registered. |
| Catalog Item Sync Item Confirm |
New Item Link |
|
The connection of two GTINs. The description of the relationship of the two connected GTINs. |
| Catalog Item Sync Item Confirm |
Notification |
|
In the data Synchronization process, the Data Source, through the source Data Pool, sends an electronic notice to a subscriber when a valid event occurs. This is based on the Subscription profile. Events that can trigger Notifications are: Publication of new data, change of Publication (visibility granted, deleted), change of published Item, Party, partner profile, change of owner, rights, Subscription, authorization, non-authorization rejection and request for Notification. |
| Catalog Item Sync Item Confirm |
Party |
|
A Party (or) Location is any legal, functional or physical entity involved at any point in any supply chain and upon which there is a need to retrieve pre-defined information. A Party is uniquely identified by a EAN/UCC Global Location Number (GLN). |
| Catalog Item Sync Item Confirm |
Party Identification |
|
The only valid Party identification is the Global Location Number (See GLN) |
| Catalog Item Sync Item Confirm |
Party Role |
|
These are elements defining the roles and relationships of the Party, such as buyer, seller, distribution center, store, etc. Examples of Party roles are: bill to, buyer, corporate identity, delivery Party, information provider, invoicee, issuer of invoice, payer, seller, ship from, ship to and supplier. |
| Catalog Item Sync Item Confirm |
Publication |
|
To prepare and issue data for distribution to one or a group of Trading Partners. A function within the Data Synchronization process whereby the Data Source grants visibility of Item, Party and partner profiles including Party capabilities data to a given list of parties (identified by their GLNs) or to all parties in a given Market. It also will trigger the Matching Process that is the precursor to the distribution of data |
| Catalog Item Sync Item Confirm |
Receipt Acknowledgement |
|
A message sent by the receiving unit to the sending station or computer indicating that transmission has been received. |
| Catalog Item Sync Item Confirm |
Recipient Data Pool |
|
A Data Pool that supports the functionality of the Data Recipient (Subscription, Confirmation, Search, Request for Notification, etc.) |
| Catalog Item Sync Item Confirm |
Registration |
|
Registration is the process, which references all Items and parties prior to Publication by all EAN.UCC certified data pools and on which there is a need to synchronize information. Registering a Trade Item involves Validation by the Registry for product uniqueness. The combination of attributes used to ensure unique records includes GTIN, GLN and Target Market. |
| Catalog Item Sync Item Confirm |
Registration Date |
|
Date assigned by the registry of successful Registration. |
| Catalog Item Sync Item Confirm |
Registry Catalogue Item |
|
A business message used to register trade Item information from a Data Pool to the Global Registry within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Registry Catalogue Item State |
|
The 4 states reflected by a Source Data Pool are: Canceled, Discontinued, In_Progress, Registered. |
| Catalog Item Sync Item Confirm |
Registry Validation |
|
Registry Validation is checking compliance against EAN.UCC standards in relation to GTIN,GLN and Target Market to ensure uniqueness of data being registered. |
| Catalog Item Sync Item Confirm |
Relationship Dependant Data |
|
Relationship Dependant Data is Master Data identifying all terms bilaterally agreed and communicated between Trading Partners such as a marketing conditions, prices, and discounts, logistics agreements, etc. |
| Catalog Item Sync Item Confirm |
Removing an Item from the Supply Chain |
|
Refers to canceling an Item that was never manufactured (see Cancel Item), temporarily discontinuing the Item, or communicating that the Item will be permanently discontinued. |
| Catalog Item Sync Item Confirm |
Request for Catalogue Item Notification |
|
A business message used to establish a Subscription to trade Item information for a Data Recipient within the Global Data Synchronisation Network. |
| Catalog Item Sync Item Confirm |
Response |
|
An abstract class of information in the Global Business Model used to define the status of a Document within the EAN.UCC system. |
| Catalog Item Sync Item Confirm |
Response Status |
|
The 3 states are: Accepted, Modified, Rejected |
| Catalog Item Sync Item Confirm |
Search |
|
This function provides data visibility according to user’s permissions and certain criteria such as Categories, GTIN, GLN, Target Market, etc. The Home Data Pool provides this visibility in the framework of the inter-operable network. |
| Catalog Item Sync Item Confirm |
Simple_eb |
|
“Simplified process in a B2B exchange of information that assumes data Synchronization.” |
| Catalog Item Sync Item Confirm |
Source Data Pool |
|
A Data Pool that supports the functionality required by a Data Source such as Data Loading, Publication, Notification, Registration, etc. |
| Catalog Item Sync Item Confirm |
Start Availability Date |
|
The date at which a trade Item or location begins it’s existence. |
| Catalog Item Sync Item Confirm |
Stop Publication Catalog Item |
|
The process by which the Data Source stops the Synchronization process by disallowing visibility of the Catalog Item. This will modify the Notification list if the Catalog Item was previously notified; and the Synchronization list if it has been synchronized, accepted or reviewed. |
| Catalog Item Sync Item Confirm |
Subscribe |
|
A data Synchronization function that refers to the creation of a Subscription that lists the criteria for receiving publications. |
| Catalog Item Sync Item Confirm |
Subscription |
|
GTIN, GLN of Information Provider, Target Market and Product classification or any combination of these can maintain Subscriptions. When a Subscription is established, a Data Recipient sets a profile to receive ongoing updates of the matching data. Subscriptions remain valid until they are deleted. Subscriptions are created by Data Recipients in their home Data Pool and sent to the registry. The Registry maintains a Subscription list that is used to route relevant Subscriptions to appropriate Source Data Pools. |
| Catalog Item Sync Item Confirm |
Synchronization |
|
The process of continuous harmonization of information between all Trading Partners within the supply chain through the use of Align Data standards as published by EAN.UCC. |
| Catalog Item Sync Item Confirm |
Synchronization List |
|
This is a subset of the Notification List maintained by the source Data Pool to keep track of where data has been notified - independent of the confirmations received. The list includes every Catalogue Item (GTIN+GLN+TM) that is synchronized. |
| Catalog Item Sync Item Confirm |
Target Market |
|
The Target Market is a geographical region based upon geographical boundaries sanctioned by the United Nations. There is one international system to describe geographical regions, the ISO-3166-code system. |
| Catalog Item Sync Item Confirm |
Target Market Country Code |
|
The country level or higher geographical definition in which the Information Provider will make the GTIN available to buyers. This does not in any way govern where the buyer may re-sell the GTIN to consumers. This code can be repeated as many times as needed. This code is represented by the 2-character ISO 3166-1 code. It is a mandatory attribute. Additionally, Target Market Subdivision Code indicates country subdivision where the trade Item is intended to be sold. This code is represented by the 3-character ISO 3166-2 code. |
| Catalog Item Sync Item Confirm |
Target Market Subdivision Code |
|
The Target Market Subdivision Code is the secondary code of the Target Market and must be a subdivision of a Target Market Country Code. The Target Market Subdivision Code describes the “geo-political subdivision of a country” where the trade Item is intended for sale, as determined by the Information Provider (e.g. “State” in the US). Target Market Subdivision Codes must be used in conjunction with Target Market Country Codes. The Target Market subdivision code is represented by the three-character ISO 3166-2 code. |
| Catalog Item Sync Item Confirm |
Trade Item Configuration |
|
The number of complete layers contained in a trade Item and number of trade Items contained in a complete layer. |
| Catalog Item Sync Item Confirm |
Trading Partners |
|
One or more parties engaged in trade. In the Context of EAN·UCC business models any combination of Buyer, Seller, or Third Party. |
| Catalog Item Sync Item Confirm |
Transactional Data |
|
Information necessary for the business process being executed. For example, Item codes and ordered quantities are transactional as these are mandatory fields within a purchase order: and, may vary by purchase order. |
| Catalog Item Sync Item Confirm |
UCC |
|
Uniform Code Council. |
| Catalog Item Sync Item Confirm |
Update Item |
|
A function used to make changes to an Item, which exists in a Data Pool whether the Item has been registered, or not. All changes must comply with EAN.UCC Validation rules. If the Item is registered, updates must be applied to the corresponding Global Registry data fields before the revised data can be propagated to data recipients. |
| Catalog Item Sync Item Confirm |
Validation |
|
The compliance checking of new or changed data against EAN.UCC Global Data Standards, principles, rules and models. |
| Catalogue Item Synchronisation |
Acceptance Acknowledgement |
|
A message sent by the receiving unit to the sending station or computer indicating that transmission has been processed successfully (syntax and content). |
| Catalogue Item Synchronisation |
Acknowledgement |
|
In the global data Synchronization process, this is a Response to a command returned to the originator of the command. Every command needs a Response. In the inter-operable network, Acknowledgement messages are standardized and may contain the following information: confirmation of message receipt (see receipt Acknowledgement), success/failure of processing for syntax and content (see acceptance Acknowledgement) or reason code for each type of failure (see Business error) |
| Catalogue Item Synchronisation |
Add Catalog Item |
|
The command to create a new Catalog Item record. |
| Catalogue Item Synchronisation |
Align Data |
|
The uniform definition of Electronic Commerce (EC) constructs to support defined business processes. This alignment is the exchange of basic business data such as the trading partners’ names, addresses and agreements, Item information, price lists, and locations. The process of alignment creates a common understanding between the trading parties and is fundamental to all trade activities. |
| Catalogue Item Synchronisation |
Business Error |
|
A message sent by the receiving unit to the sending station or computer indicating that transmission has errors (code type and text). |
| Catalogue Item Synchronisation |
Cancel Date |
|
Date assigned by Data Source and stored in the source Data Pool reflecting the date the Catalog Item was cancelled. This date will also be stored in the Registry. |
| Catalogue Item Synchronisation |
Cancel Item |
|
Global data Synchronization term describing a maintenance function used to communicate that a Catalog Item was never manufactured. This allows reuse of the GTIN 12 months after cancellation. |
| Catalogue Item Synchronisation |
Catalog Item |
|
The Item as it is stored in a catalog or Data Pool. This is uniquely identified by (GTIN + GLN + Target Market). |
| Catalogue Item Synchronisation |
Catalog Item Child Item Link |
|
A class of information to identify the quantity of items within a packaging hierarchy level within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Catalog Item Classification |
|
See classification |
| Catalogue Item Synchronisation |
Catalog Item Confirmation |
|
This refers to electronic communication from the Data Recipient to the Data Source indicating what action has been taken on the Item. The confirmation process occurs in the recipient’s Data Pool. Confirmation is not mandatory. When used, it provides for the following outcomes:
1. Synchronized: data is integrated, in synch and added to the Synchronization list.
2. Accepted: Data has been recieved by the Recipient, but no business decision has been made on the data.
3. Rejected: recipient requests that no further updates are desired. Data will no longer be synchronized or updates will no longer be provided.
4. Review: a request to the Data Source to “review” their data because the Data Recipient has received discrepant data which they cannot synchronize. |
| Catalogue Item Synchronisation |
Catalog Item State |
|
The four states are: Registered , Cancelled, In Progress and Discontinued. |
| Catalogue Item Synchronisation |
Catalogue Item Confirmation State |
|
The four states reflected by a Recipient Data Pool are: Accepted, Rejected, Review and Synchronised |
| Catalogue Item Synchronisation |
Catalogue Item Dates |
|
A class of information used to describe the dates of the action taken on the catalogue Item record within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Catalogue Item Link |
|
A business message used to identify the packaging hierarchy levels of trade items. |
| Catalogue Item Synchronisation |
Catalogue Item Notification |
|
A business message used to transmit trade Item information from a Data Source or a Data Pool to a Data Recipient with the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Catalogue Item Publication |
|
A business message standard used to distribute trade Item information within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Catalogue Item Reference |
|
A class of information from the Catalogue Item Common library used to identify the key to the trade Item information using the Data Source GLN, the GTIN, and the Target Market within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Catalogue Item Registration Information |
|
A class of information used to identify the the dates of the action taken on the Global Registry Item record within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Catalogue Item Registration Response |
|
A business message used to notify a Data Pool of the status of the Registration in the Global Registry for a trade Item. |
| Catalogue Item Synchronisation |
Catalogue Item Subscription |
|
A business message used to establish a request for the update of trade Item information from an end recipient on a continuous basis. |
| Catalogue Item Synchronisation |
Certification |
|
The accreditation of organizations to perform activities that conform to established business processes, business models and rules such as: Certification of other organizations, operation of the Global Registry, operation of data pools, Validation, authentication, consultancy, etc. |
| Catalogue Item Synchronisation |
Certification Body |
|
Organization that performs the Certification process. (This is stored in the Registry). |
| Catalogue Item Synchronisation |
Certification Expiration Date |
|
Date on which the Data Pool Certification is no longer valid. (This is stored in the Registry). |
| Catalogue Item Synchronisation |
Certification Identification |
|
Value that uniquely identifies a certified member of the Global Data Synchronization Network GDSN. (This is stored in the Registry). |
| Catalogue Item Synchronisation |
Certification Start Date |
|
Date on which the Data Pool obtains Certification. (This is stored in the Registry). |
| Catalogue Item Synchronisation |
Certification Status |
|
Indicator of the stage of the Certification process (This is stored in the Registry). |
| Catalogue Item Synchronisation |
Change Catalog Item |
|
The command to update an existing Catalog Item record. |
| Catalogue Item Synchronisation |
classification |
|
A classification schema is an Industry accepted, standardized method to group like products together so that global searches can be enabled. Within Data Synchronization, a classification for the Item is mandatory. |
| Catalogue Item Synchronisation |
Compliance Check |
|
The Validation of specific data or data constructs to defined industry standards. |
| Catalogue Item Synchronisation |
Construct |
|
Data or data structure. |
| Catalogue Item Synchronisation |
Content Provider |
|
See Data Source |
| Catalogue Item Synchronisation |
Context |
|
“Context is expressed as classifications drawn from various standards (business sub-process, industry, region and geography, product, legislative). The idea of Context is that the structure of a piece of business information is defined by the purpose which it serves within a business process, an industry, region, etc.”
Example: An Item can be defined in Context of Global for product type FMCG (Fast Moving Consumer Goods) or other verticals. |
| Catalogue Item Synchronisation |
Core Data |
|
Core is defined as “common, reusable elements across various business processes. They can be mandatory or optional. Core is a common denominator upon which extensions are built”.
Example: GTIN, Ship To, Date |
| Catalogue Item Synchronisation |
Core Extensions = Cross Industry Extensions |
|
Data or data constructs specific to more than one process, industry or sector but not used across all. |
| Catalogue Item Synchronisation |
Correct Item |
|
Refers to a command that allows incorrect data to be altered in ways that would not normally be allowed by standard GTIN allocation rules. All other Validations still apply. This process is intended to correct errors, not to circumvent the Validation process. |
| Catalogue Item Synchronisation |
Correct Item Link |
|
Command that allows alteration of Item links that were incorrectly entered provided that the integrity of the Item Hierarchy is not impacted. If the Item Hierarchy is impacted, the “correct Item link” command must not be applied. Instead, the incorrect Item link must be deleted and a new Item Link added. |
| Catalogue Item Synchronisation |
Data Pool |
|
A repository of Data where Trading Partners can obtain, maintain and exchange information on items and parties in a standard format through electronic means. |
| Catalogue Item Synchronisation |
Data Pool Certification Information |
|
A class of information used to describe the status of a data pool’s Certification within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Data Pool Certification Status List |
|
A class of information used to identify the Certification status of a Data Pool within the Global Data Synchronisation Network. The values include: Certification initiated; Certification pending, Certified, and Reviewed for Certification. |
| Catalogue Item Synchronisation |
Data Pool Profile |
|
Information that allows data pools to interoperate with each other technically and from an operational business perspective. This information includes (but is not limited to): business, administration and technical contacts, capabilities, services, network addresses and transport protocols. |
| Catalogue Item Synchronisation |
Data Recipient |
|
Party, which is authorized to view, use, download a set of Master Data provided by a Data Source. |
| Catalogue Item Synchronisation |
Data Source |
|
Entity that provides the global data Synchronization network with Master Data. The Data Source is officially recognized as the owner of this data. For a given Item or Party, the source of data is responsible for permanent updates of the information under its responsibility. |
| Catalogue Item Synchronisation |
Data Synchronisation Data Pool Profile |
|
A business message used to identify a Data Pool within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Data Synchronisation Error |
|
A business message used to notify a member of the Global Data Synchronisation Network of an error that has occurred within the process. |
| Catalogue Item Synchronisation |
Data Synchronisation Error Information |
|
A class of information used to describe an error within the Global Data Synchronisation Network and it’s process. |
| Catalogue Item Synchronisation |
Data Synchronisation Error Reference |
|
A class of information used to describe the entity and the type of process identified as an error within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Delete Catalog Item |
|
The command to flag the existing Catalog Item record for deletion (The objective is to enable the eventual removal of the Catalog Item record from the Data Pool.) |
| Catalogue Item Synchronisation |
Delete Catalog Item Link |
|
The command to flag the existing Catalog Item link record for deletion. |
| Catalogue Item Synchronisation |
Deletion Date |
|
Date assigned by Data Source and stored in the source Data Pool reflecting the date the Catalog Item was flagged for deletion. This date will also be stored in the Registry. |
| Catalogue Item Synchronisation |
Discontinue Date |
|
Date assigned by Data Source and stored in the source Data Pool reflecting the date the Catalog Item was discontinued. This date will also be stored in the Registry. |
| Catalogue Item Synchronisation |
Discontinue Item – Permanent |
|
Refers to permanent removal of an Item in the supply chain. This involves maintaining a discontinuation date in the Registry. The discontinuation date is used to trigger and track the EAN.UCC retention period. |
| Catalogue Item Synchronisation |
Discontinue Item - Temporary |
|
Refers to removing an Item temporarily from the supply chain. This is communicated via End Availability Date. When available again, updated start and End Availability Dates are provided. Temporary removals are not reflected in the Registry. They are a responsibility of relevant data pools who maintain the availability period. |
| Catalogue Item Synchronisation |
Document |
|
“Business data being exchanged in support of business processes. It is a named collection of core and extensions”. Any self-contained piece of work created with an application program and, if saved on disk, given a unique filename by which it can be retrieved. Documents are generally thought of as word-processed materials only. To a computer, however, data is nothing more than a collection of characters, so a spreadsheet or a graphic is as much a Document as is a letter or report. |
| Catalogue Item Synchronisation |
Electronic Address |
|
The Internet Protocol identification for a certified Data Pool within the GDSN. |
| Catalogue Item Synchronisation |
End Availability Date |
|
The date at which a trade Item or a location will no longer exist. |
| Catalogue Item Synchronisation |
Error Name |
|
A brief, text description related to an Error Number. |
| Catalogue Item Synchronisation |
Error Number |
|
An identification code used to relate to an Error Name. |
| Catalogue Item Synchronisation |
Extension |
|
“Extensions to core represent defined business processes which go beyond core requirements. Optional Core Data may be used in an Extension but are not required.”
Example: US Grocery Extension for Item, VAT |
| Catalogue Item Synchronisation |
Full Hierarchy |
|
A Construct of data containing a set of GTINs and Links that make up a unique relationship from the highest level GTIN with no parent down to the lowest level GTIN with no children |
| Catalogue Item Synchronisation |
GCI |
|
Global Commerce Initiative |
| Catalogue Item Synchronisation |
Global Data Dictionary (GDD) |
|
The repository of definitions and attributes of all data elements used within the EAN·UCC Business Message Standards. |
| Catalogue Item Synchronisation |
Global Data Synchronization Network (GDSN) |
|
The Global Data Synchronization Network is a federation of interoperable certified Data Pools and a certified Global Registry that collectively provide for the Synchronization of Master Data between Trading Partners on a global basis. |
| Catalogue Item Synchronisation |
Global Location Number(GLN) |
|
Unique location number mandatory within the Global Data Synchronization process to identify data owners/info providers, etc such as Distributors, brokers, manufacturers. |
| Catalogue Item Synchronisation |
Global Registry |
|
A directory for the Registration of unique catalog items and parties. It contains a limited data set certified to be EAN.UCC compliant and acts as a pointer to source data pools where Master Data is housed. |
| Catalogue Item Synchronisation |
Global Trade Item Number (GTIN) |
|
A particular Global trade Item Number, a numerical value used to uniquely identify a trade Item. A trade Item is any trade Item (trade Item or service) upon which there is a need to retrieve pre-defined information and that may be planned, priced, ordered, delivered and or invoiced at any point in any supply chain. |
| Catalogue Item Synchronisation |
Governance |
|
It is the management of the ongoing process for Master Data Synchronization and consists of: controlling changes to scope, rules and standards, establishing and regulating the Global Registry, regulating the Certification of Organizations, and regulating the business model. |
| Catalogue Item Synchronisation |
Initial Item Load |
|
First time the Item is being published within a trading relationship through GDSN for Items already in trade (prior to data synchronisation in GDSN). |
| Catalogue Item Synchronisation |
Inter-Operability |
|
The ability to communicate Master Data in a standardized and transparent way throughout the global data Synchronization network. |
| Catalogue Item Synchronisation |
Item |
|
An Item is any product or service upon which there is a need to retrieve pre-defined information and that may be priced, ordered or invoiced at any point in any supply chain. An Item is uniquely identified by a EAN/UCC Item number (gtin)">Global Trade Item Number (GTIN). |
| Catalogue Item Synchronisation |
Item Link Notification |
|
A term used to advise data recipients of relationships among Items. This Notification always provides the entire Item hierarchy. In case of an Item Link correction, the entire hierarchy will be indicated as corrected in the Notification. The updated hierarchy always fully replaces the current hierarchy. |
| Catalogue Item Synchronisation |
Last Change Date |
|
Date assigned by system indicating last time the information was changed. This date is generic and will be stored where assigned and will accompany every message. |
| Catalogue Item Synchronisation |
Manufacturer |
|
The Party that produces the Item. |
| Catalogue Item Synchronisation |
Market Group |
|
A proprietary group of data recipients normally determined by the Information Provider, although it can also be created by buyers and third parties. The Market Group is a common term and should not be confused with the Target Market Codes. This group is developed and used by the Information Provider to control the Publication of data to a specific group of customers. |
| Catalogue Item Synchronisation |
Master Data |
|
Within the Context of Data Synchronization, any data or constructs that are applicable across multiple business transactions. Master Data describes each Item and Party involved in Supply Chain Processes. Each data set is uniquely identified by a Item number (gtin)">Global Trade Item Number (GTIN) and a Global Location Number (GLN). Master Data can be divided into neutral and relationship dependent data. Typically Master Data is static - not transactional. |
| Catalogue Item Synchronisation |
Master Data Global / Local Status |
|
GLOBAL = (G): Indicates that the data element is required by all markets and contains the same information (e.g. GTIN)
GLOBAL/LOCAL = (G/L): Indicates that the data element is required by all markets but that the actual value can be different for each one (i.e. language, tax indications etc.)
LOCAL = (L): Indicates that the data element is required for a limited number of markets (i.e. Green point – Germany) Local requirements occur in Response to national legislation, national standards or languages. |
| Catalogue Item Synchronisation |
Master Data Identification |
|
A Data Synchronization term used to describe the unique identification of an Item in a product catalogue (=key) in compliance with EAN.UCC standards. This is achieved by the combination of 3 attributes: GTIN, GLN of Information Provider, and Target Market. For product catalogue management purposes, a product cannot be uniquely identified by its GTIN alone as there are valid business cases for information provider and Target Market specific data. |
| Catalogue Item Synchronisation |
Master Data Synchronization |
|
The process of continuous harmonization of Master Data between all Trading Partners within the supply chain through use of EAN.UCC standards. |
| Catalogue Item Synchronisation |
Matching Process |
|
A critical step within the data Synchronization process that is owned and developed by each source Data Pool in order to trigger data distribution based on Publication and Subscription data. The Matching Process can be triggered either by Publication, Subscription or as a scheduled event. |
| Catalogue Item Synchronisation |
Neutral Data |
|
Within the Context of Data Synchronization, Master Data or constructs applicable across multiple business transactions and constant across all Trading Partners, such as Item, Party, standard terms, etc. |
| Catalogue Item Synchronisation |
New Item Hierarchy |
|
A new Construct of data containing a set of GTINs and Links that make up a unique relationship from the highest level GTIN with no parent to the lowest level with no children. To create a new Item Hierarchy, the Information Provider (or data owner) enters Item and Item Link data into the Source Data Pool. The Data Pool verifies that the information loaded is “correct” and then sends the relevant Item data to the registry for Registration. Item link data is not sent to the Registry as links are not registered. |
| Catalogue Item Synchronisation |
New Item Link |
|
The connection of two GTINs. The description of the relationship of the two connected GTINs. |
| Catalogue Item Synchronisation |
Notification |
|
In the data Synchronization process, the Data Source, through the source Data Pool, sends an electronic notice to a subscriber when a valid event occurs. This is based on the Subscription profile. Events that can trigger Notifications are: Publication of new data, change of Publication (visibility granted, deleted), change of published Item, Party, partner profile, change of owner, rights, Subscription, authorization, non-authorization rejection and request for Notification. |
| Catalogue Item Synchronisation |
Party |
|
A Party (or) Location is any legal, functional or physical entity involved at any point in any supply chain and upon which there is a need to retrieve pre-defined information. A Party is uniquely identified by a EAN/UCC Global Location Number (GLN). |
| Catalogue Item Synchronisation |
Party Identification |
|
The only valid Party identification is the Global Location Number (See GLN) |
| Catalogue Item Synchronisation |
Party Role |
|
These are elements defining the roles and relationships of the Party, such as buyer, seller, distribution center, store, etc. Examples of Party roles are: bill to, buyer, corporate identity, delivery Party, information provider, invoicee, issuer of invoice, payer, seller, ship from, ship to and supplier. |
| Catalogue Item Synchronisation |
Publication |
|
To prepare and issue data for distribution to one or a group of Trading Partners. A function within the Data Synchronization process whereby the Data Source grants visibility of Item, Party and partner profiles including Party capabilities data to a given list of parties (identified by their GLNs) or to all parties in a given Market. It also will trigger the Matching Process that is the precursor to the distribution of data |
| Catalogue Item Synchronisation |
Receipt Acknowledgement |
|
A message sent by the receiving unit to the sending station or computer indicating that transmission has been received. |
| Catalogue Item Synchronisation |
Recipient Data Pool |
|
A Data Pool that supports the functionality of the Data Recipient (Subscription, Confirmation, Search, Request for Notification, etc.) |
| Catalogue Item Synchronisation |
Registration |
|
Registration is the process, which references all Items and parties prior to Publication by all EAN.UCC certified data pools and on which there is a need to synchronize information. Registering a Trade Item involves Validation by the Registry for product uniqueness. The combination of attributes used to ensure unique records includes GTIN, GLN and Target Market. |
| Catalogue Item Synchronisation |
Registration Date |
|
Date assigned by the registry of successful Registration. |
| Catalogue Item Synchronisation |
Registry Catalogue Item |
|
A business message used to register trade Item information from a Data Pool to the Global Registry within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Registry Catalogue Item State |
|
The 4 states reflected by a Source Data Pool are: Canceled, Discontinued, In_Progress, Registered. |
| Catalogue Item Synchronisation |
Registry Validation |
|
Registry Validation is checking compliance against EAN.UCC standards in relation to GTIN,GLN and Target Market to ensure uniqueness of data being registered. |
| Catalogue Item Synchronisation |
Relationship Dependant Data |
|
Relationship Dependant Data is Master Data identifying all terms bilaterally agreed and communicated between Trading Partners such as a marketing conditions, prices, and discounts, logistics agreements, etc. |
| Catalogue Item Synchronisation |
Removing an Item from the Supply Chain |
|
Refers to canceling an Item that was never manufactured (see Cancel Item), temporarily discontinuing the Item, or communicating that the Item will be permanently discontinued. |
| Catalogue Item Synchronisation |
Request for Catalogue Item Notification |
|
A business message used to establish a Subscription to trade Item information for a Data Recipient within the Global Data Synchronisation Network. |
| Catalogue Item Synchronisation |
Response |
|
An abstract class of information in the Global Business Model used to define the status of a Document within the EAN.UCC system. |
| Catalogue Item Synchronisation |
Response Status |
|
The 3 states are: Accepted, Modified, Rejected |
| Catalogue Item Synchronisation |
Search |
|
This function provides data visibility according to user’s permissions and certain criteria such as Categories, GTIN, GLN, Target Market, etc. The Home Data Pool provides this visibility in the framework of the inter-operable network. |
| Catalogue Item Synchronisation |
Simple_eb |
|
“Simplified process in a B2B exchange of information that assumes data Synchronization.” |
| Catalogue Item Synchronisation |
Source Data Pool |
|
A Data Pool that supports the functionality required by a Data Source such as Data Loading, Publication, Notification, Registration, etc. |
| Catalogue Item Synchronisation |
Start Availability Date |
|
The date at which a trade Item or location begins it’s existence. |
| Catalogue Item Synchronisation |
Stop Publication Catalog Item |
|
The process by which the Data Source stops the Synchronization process by disallowing visibility of the Catalog Item. This will modify the Notification list if the Catalog Item was previously notified; and the Synchronization list if it has been synchronized, accepted or reviewed. |
| Catalogue Item Synchronisation |
Subscribe |
|
A data Synchronization function that refers to the creation of a Subscription that lists the criteria for receiving publications. |
| Catalogue Item Synchronisation |
Subscription |
|
GTIN, GLN of Information Provider, Target Market and Product classification or any combination of these can maintain Subscriptions. When a Subscription is established, a Data Recipient sets a profile to receive ongoing updates of the matching data. Subscriptions remain valid until they are deleted. Subscriptions are created by Data Recipients in their home Data Pool and sent to the registry. The Registry maintains a Subscription list that is used to route relevant Subscriptions to appropriate Source Data Pools. |
| Catalogue Item Synchronisation |
Synchronization |
|
The process of continuous harmonization of information between all Trading Partners within the supply chain through the use of Align Data standards as published by EAN.UCC. |
| Catalogue Item Synchronisation |
Synchronization List |
|
This is a subset of the Notification List maintained by the source Data Pool to keep track of where data has been notified - independent of the confirmations received. The list includes every Catalogue Item (GTIN+GLN+TM) that is synchronized. |
| Catalogue Item Synchronisation |
Target Market |
|
The Target Market is a geographical region based upon geographical boundaries sanctioned by the United Nations. There is one international system to describe geographical regions, the ISO-3166-code system. |
| Catalogue Item Synchronisation |
Target Market Country Code |
|
The country level or higher geographical definition in which the Information Provider will make the GTIN available to buyers. This does not in any way govern where the buyer may re-sell the GTIN to consumers. This code can be repeated as many times as needed. This code is represented by the 2-character ISO 3166-1 code. It is a mandatory attribute. Additionally, Target Market Subdivision Code indicates country subdivision where the trade Item is intended to be sold. This code is represented by the 3-character ISO 3166-2 code. |
| Catalogue Item Synchronisation |
Target Market Subdivision Code |
|
The Target Market Subdivision Code is the secondary code of the Target Market and must be a subdivision of a Target Market Country Code. The Target Market Subdivision Code describes the “geo-political subdivision of a country” where the trade Item is intended for sale, as determined by the Information Provider (e.g. “State” in the US). Target Market Subdivision Codes must be used in conjunction with Target Market Country Codes. The Target Market subdivision code is represented by the three-character ISO 3166-2 code. |
| Catalogue Item Synchronisation |
Trade Item Configuration |
|
The number of complete layers contained in a trade Item and number of trade Items contained in a complete layer. |
| Catalogue Item Synchronisation |
Trading Partners |
|
One or more parties engaged in trade. In the Context of EAN·UCC business models any combination of Buyer, Seller, or Third Party. |
| Catalogue Item Synchronisation |
Transactional Data |
|
Information necessary for the business process being executed. For example, Item codes and ordered quantities are transactional as these are mandatory fields within a purchase order: and, may vary by purchase order. |
| Catalogue Item Synchronisation |
UCC |
|
Uniform Code Council. |
| Catalogue Item Synchronisation |
Update Item |
|
A function used to make changes to an Item, which exists in a Data Pool whether the Item has been registered, or not. All changes must comply with EAN.UCC Validation rules. If the Item is registered, updates must be applied to the corresponding Global Registry data fields before the revised data can be propagated to data recipients. |
| Catalogue Item Synchronisation |
Validation |
|
The compliance checking of new or changed data against EAN.UCC Global Data Standards, principles, rules and models. |
| Danish Glossary Translation |
applikation |
Application |
|
| D |
