|
Business Processes |
|
|
ALIGN |
|
|
GDSN |
|
|
ORDER |
|
|
DELIVER |
|
|
PAY |
|
|
|
|
|
|
|
|
ALIGN BUSINESS
PROCESS |
|
|
|
|
|
Item Data Notification
|
|
|
Message
definition |
|
|
Item Master Data is a set of data, which
describes the specifications and structures of each item involved in Supply
Chain Processes. Each set of data can uniquely be identified by a Global Trade
Item Number (GTIN).
The
transaction can be established by either the manufacturer or the supplier. Only
one party will initiate the transaction. Which of both parties initiates the
transaction needs to be agreed upon in the Integration Agreement; changes in
item master data need to be commonly agreed & realised by the party
initially initiating the transaction, i.e. the message flow will only be in one
direction in order to ensure data alignment.
Master
data will be aligned each time information changes or new information is added.
There is no need for a response message during the alignment
of master data between buyer and seller.
|
|
|
Go to full message description |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CATALOGUE ITEM AUTHORISATION
|
|
|
|
|
|
|
|
|
CATALOGUE ITEM SYNCHRONISATION
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BASIC PARTY SYNCHRONISATION
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TRADE ITEM |
|
|
Message
definition |
|
|
tem is the second message in the trade
process following the Party message. Item elements are the mandatory
attributes
needed to align the item information between trading partners. These
attributes
in combination ensure the uniqueness of the data set associated with a
GTIN.
The use, definition, and relevance of these attributes is the same for
ALL GS1 industries. Following the Item attributes is an extension of
cross
industry. These are data attributes that may be required in conducting
commerce
between partners for the trade of an item or service. These attributes
are relevant
to more than one industry. The
definition of these attributes must be the same for all industries.
Item and the extension of the cross
industry data processes include communicating the data elements necessary to
support the core business requirements in the global trading environment. The
Party and Item process are mandatory in the completion of the price, purchase
order, invoice, etc. messages that follow in the global trade process. |
|
|
Go to full message description |
|
|
|
|
|
ATTRIBUTE VALUE PAIR EXTENSION |
|
|
Message
definition |
|
|
Attribute / Value Pairs (A/VP) are a single schema “template”
of data structures. A/VPs provide a user with the ability to exchange new attributes
and their values in XML through the use of the template. Suppliers, retailers
and other sending partners now have the capability to include high-priority
attributes in transmitted XML documents immediately upon approval – without
waiting on the development and approval of attribute-specific schemas to be
finalized through the standards process. Recipient data pools and trading
partners may pull expected attribute names and their value pairs from the GDD
and use the template to parse their XML documents.
|
|
|
Go to full message description |
|
|
|
|
|
BAR CODE TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message
is to exchange barcode
related attributes identifying the bar code information on the product
packaging. Parties receiving
Trade Item Information need to know the actual product identifier that is
physically on the trade item and the related barcode symbology. Recipients also
need to know if the physical product identifier can be derived from the
14-digit GTIN data structure, particularly in instances where the same physical
trade item product identifier may be contained in multiple trade item
configurations. |
|
|
Go to full message description |
|
|
|
|
|
CASE LEVEL NON GTIN LOGISTICS UNIT EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message is to provide a means for data exchange in two business practices for obtaining
information when there is only one standard logistics unit configuration in a
target market:
A. At
the logistics unit level when a GTIN is assigned to the logistics unit
B. At
the “case” level when a GTIN is not assigned to the logistics unit
There are additional
attributes that need to be added to support this “case” level processing.
If any "GTIN + GLN +
TM" in the synchronized hierarchy has tradeitemunitdescriptor =
"PL" (pallet) or "MX" (mixed module) then the additional
attributes cannot be populated on any "GTIN + GLN + TM" in the
synchronized hierarchy.
It can only appear once in a
synchronized hierarchy.
If
a “case” level GTIN is never shipped as part of a standard logistic unit level
then the additional attributes are not applicable. |
|
|
Go to full message description |
|
|
|
|
|
EXTENSION
SPECIFIC TECHNICAL CHARACTERISTICS |
|
|
Message
definition |
|
|
The objective of this message is to allow
the standardization and the structuring of the specific technical
characteristics of items. These fact sheets allow the sending of the
technical characteristics on behalf of the manufacturer without being seized
again by the distributor.
It allows users to look for products with
regard to a range, or a feature, to use this information for an internal custom
(i.e. commercial, after sale services, etc.), or an external usage: (i.e. spread
the information with the partners and the end users).
The information is thus right, precise and
up to date; the risk of error is reduced and the adaptation of the data allows
an automation of the updates and the data processing. |
|
|
Go to full message description |
|
|
|
|
|
FOOD AND BEVERAGE TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message
is to exchange specific information that needs to be communicated for food & beverage
products. |
|
|
Go to full message description |
|
|
|
|
|
HARDLINES |
|
|
Message
definition |
|
|
An extension of the
Trade Item
message containing the additional
attributes necessary
to support Hardlines industry business requirements. |
|
|
Go to full message description |
|
|
|
|
|
OFFICE SUPPLIES TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
An extension of the
Trade Item
message containing the additional
attributes necessary
to support the Office Supplies industry business requirements. |
|
|
Go to full message description |
|
|
|
|
|
PROMOTIONAL TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message
is to provide information on promotional trade items (free quantities either included in the regular quantity or added to the regular
quantity) and to be able to link them to the standard trade items they replace or
complement.
|
|
|
Go to full message description |
|
|
|
|
|
REGULATORY COMPLIANCE EXTENSION |
|
|
Message
definition |
|
|
Due to legal regulations, in order to
commercialize some products, some regulations must be met and regulatory
information must be communicated to the Retailer. It is possible do achieve using this message. |
|
|
Go to full message description |
|
|
|
|
|
SOTFLINES |
|
|
Message
definition |
|
|
An extension of the
Trade Item message
containing the attributes applicable only within the context of Apparel
and Home Fashions. |
|
|
Go to full message description |
|
|
|
|
|
TRADE ITEM FMCG |
|
|
Message
definition |
|
|
An extension of the
Trade Item message
enabling the FMCG industry to communicate measurement, packaging
marking and additional identification information extending the
information available in the core item message. |
|
|
Go to full message description |
|
|
|
|
|
TRADE ITEM HAZARDOUS INFORMATION US EXTENSION |
|
|
Message
definition |
|
|
The objective of this message is to communicatethe attributes related to the trade of hazardous goods between
trading partners, in support of the need for compliance with US Department of
Transportation regulations for the transportation of hazardous goods |
|
|
Go to full message description |
|
|
|
|
|
ELECTRONIC GAMES TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message is to provide additional attributes
to completely and properly convey the data supporting current business processes
in the entertainment industry as well as facilitate participation on the Global Data
Synchronization Network. This message defines and describes the
additional attributes that have been identified as necessary to support electronic games. |
|
|
Go to full message description |
|
|
|
|
|
MOVIE PUBLICATION TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message is to provide additional attributes
to completely and properly convey the data supporting current business processes
in the entertainment industry as well as facilitate participation on the Global Data
Synchronization Network. This message defines and describes the
additional attributes that have been identified as necessary to support electronic games. |
|
|
Go to full message description |
|
|
|
|
|
MUSIC RECORDING TRADE ITEM EXTENSION |
|
|
Message
definition |
|
|
The purpose of this message is to provide additional attributes
to completely and properly convey the data supporting current business processes
in the entertainment industry as well as facilitate participation on the Global Data
Synchronization Network. This message defines and describes the
additional attributes that have been identified as necessary to support music recordings. |
|
|
Go to full message description |
|
|
|
|
|
TRADE ITEM SWEDEN |
|
|
Message
definition |
|
|
A local extension
of the Trade Item message,
containing additional information necessary to meet the needs and
business requirements for the Swedish retail market. |
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE ITEM AUTHORISATION |
|
|
Message
definition |
|
|
This message is meant to be used in the DSD business model. Its purpose is to grant permission to sell (or deliver) an item at a specific location or
groups of locations where the authorisation could be triggered by either
trading partner depending on the buying and selling relationship. This process
will facilitate the linkage of who can deliver a product to a store and who
will be paid for the product.
This Item Authorisation process can be used
either in the GDSN or in a Peer to Peer network.
|
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE ITEM AUTHORISATION RESPONSE |
|
|
Message
definition |
|
|
This message is meant to be used in the DSD business model. Its purpose is to grant permission to sell (or deliver) an item at a specific location or
groups of locations where the authorisation could be triggered by either
trading partner depending on the buying and selling relationship. This process
will facilitate the linkage of who can deliver a product to a store and who
will be paid for the product.
This Item Authorisation process can be used
either in the GDSN or in a Peer to Peer network. |
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE ITEM CONFIRMATION |
|
|
Message
definition |
|
|
A message sent by
the Data Recipient
to the Recipient Data Pool and then by the Recipient Data Pool to the
Source Data Pool, to indicate what action has been taken on the trade
item. The confirmation process takes place in the Recipient Data
Pool. If no confirmation is received, data updates will
continue
to be provided until the data recipient accepts, rejects or updates the
subscription, or until the data owner changes the publication. |
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE ITEM LINK |
|
|
Message
definition |
|
|
A message used to
identify the packaging hierarchy levels of trade items. |
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE
ITEM NOTIFICATION |
|
|
Message
definition |
|
|
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.
In
the data synchronisation CatalogueItemPublicationprocess, the data
source, through the source data pool, sends an electronic notice to a
subscriber when a valid event, based on the subscription profile,
occurs. Events that can trigger notifications are: new or
updated publication, subscription, change of published data, change of
owner/rights, synchronisation list update and request for notification.
|
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE
ITEM PUBLICATION |
|
|
Message
definition |
|
|
A message
distributing trade item information within the Global Data
Synchronisation Network.
A function of the publication process within the Data Synchronization
is for the Data Source to grant 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 triggers the matching process that is the
precursor to the distribution of data. |
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE
ITEM REGISTRATION
RESPONSE |
|
|
Message
definition |
|
|
A message sent from
the Global Registry to the Source Data Pool informing about the status
of the registration in the Global Registry for a trade item. |
|
|
Go to full message description |
|
|
|
|
|
CATALOGUE
ITEM SUBSRIPTION |
|
|
Message
definition |
|
|
A business message
used to establish a request for the update of trade item information
from an end recipient on a continuous basis. |
|
|
Go to full message description |
|
|
|
|
EANUCC RESPONSE |
|
|
Message
definition |
|
|
A message providing
information about the status of the previously sent message. The status
can be specified as:
-
Accepted
- Modified
- Rejected |
|
|
Go to full message description |
|
|
|
|
|
GDSN EXCEPTION |
|
|
Message
definition |
|
|
A message reporting
an error (exception) on specific level of levels of GDSN communication:
- Message
- Transaction
- Command
- Document
- Attribute |
|
|
Go to full message description |
|
|
|
|
|
REGISTRY
CATALOGUE ITEM |
|
|
Message
definition |
|
|
A business message
used to register trade item information from a data pool to the Global
Registry within the Global Data Synchronisation Network. |
|
|
Go to full message description |
|
|
|
|
|
REQUEST
FOR CATALOGUE ITEM
NOTIFICATION |
|
|
Message
definition |
|
|
A business message
used to establish a subscription to trade item information for a data
recipient within the Global Data Synchronisation Network. Request for
notification is only executed once and then discarded by the source
data pool. The request for notification is not distributed and stored
by the registry: the recipient data pool, where the request is created,
looks up the source data pool where it needs to be sent in the registry
and sends the request to the source data pool.
For Catalogue Items that were previously synchronised (= in
synchronisation list) or rejected, the request for notification resets
the confirmation status: undo reject or remove from synchronisation
list. |
|
|
Go to full message description |
|
|
|
|
|
BASIC PARTY REGISTRATION |
|
|
Message
definition |
|
|
Party
information is a part of Master Data. Trading Partner’s involved with the Global Data Synchronisation Network
(GDSN) require data regarding party (GLN) information to determine the unique
identification, the role definition, the business process capability and the
message capability required to function in the network defined to achieve
Master Data Synchronisation.Due to the complexities of full Party
Synchronisation, an initial Basic Party
Synchronisation process has been created. The process requirements for basic party
synchronisation within the Global Data Synchronisation Network includes:
- Load and Update Party Data within the Global
Registry
- Manage Party Data in the Global Registry
- Distribute Party Data
|
|
|
Go to full message description |
|
|
|
|
|
PARTY REGISTRATION RESPONSE |
|
|
Message
definition |
|
|
Party
information is a part of Master Data. Trading Partner’s involved with the Global Data Synchronisation Network
(GDSN) require data regarding party (GLN) information to determine the unique
identification, the role definition, the business process capability and the
message capability required to function in the network defined to achieve
Master Data Synchronisation.Due to the complexities of full Party
Synchronisation, an initial Basic Party
Synchronisation process has been created. The process requirements for basic party
synchronisation within the Global Data Synchronisation Network includes:
- Load and Update Party Data within the Global
Registry
- Manage Party Data in the Global Registry
- Distribute Party Data
|
|
|
Go to full message description |
|
|
|
|
|
REGISTRY PARTY DATA DUMP |
|
|
Message
definition |
|
|
Party
information is a part of Master Data. Trading Partner’s involved with the Global Data Synchronisation Network
(GDSN) require data regarding party (GLN) information to determine the unique
identification, the role definition, the business process capability and the
message capability required to function in the network defined to achieve
Master Data Synchronisation.Due to the complexities of full Party
Synchronisation, an initial Basic Party
Synchronisation process has been created. The process requirements for basic party
synchronisation within the Global Data Synchronisation Network includes:
- Load and Update Party Data within the Global
Registry
- Manage Party Data in the Global Registry
- Distribute Party Data
|
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ORDER |
|
|
Message
definition |
|
|
The
Order provides the
ability for a buyer to order specified quantities of goods and services
from a
seller for a single shipment to or from a single location. The process
is simplified by having
one order placed for one delivery for one location at one time.
The Order may be used only
when the buyer and seller have aligned data such as parties, item,
pricing,
payment terms, etc., prior to order creation. |
|
|
Go to full message description |
|
|
|
|
|
MULTI
SHIP TO ORDER |
|
|
Message
definition |
|
|
The Multi Shipment Order provides the ability
to order different quantities of trade items/services
originating from multiple locations of the seller shipped to multiple locations
of the buyer using one business message.
|
|
|
Go to full message description |
|
|
|
|
|
ORDER RESPONSE |
|
|
Message
definition |
|
|
The
Order Response provides the ability for a supplier to respond to an
order
previously sent by the buyer. The Order Response allows
the seller to inform about either the acceptance of the entire
order as transmitted, or the acceptance of the order
with modifications on items (substitutes), quantities, prices and/or
dates, or the rejection of the entire
order.
|
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INVENTORY ACTIVITY OR INVENTORY STATUS |
|
|
RECEIVING
ADVICE |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CONSUMPTION REPORT |
|
|
Message
definition |
|
|
This message is used in consignment business scenarios the buyer needs to
communicate the consumed materials or sold goods to the seller. |
|
|
Go to full message description |
|
|
|
|
|
FULL TRUCKLOAD LOAD TENDER |
|
|
Message
definition |
|
|
A message sent by a Shipper,
Consignee or 3rd Party to
the Carrier. It contains all
relevant data regarding the goods to be picked up and transported from
initial
origin to final destination and all intermediate stops if applicable. |
|
|
Go to full message description |
|
|
|
|
|
INVENTORY
ACTIVITY OR INVENTORY STATUS |
|
|
Message
definition |
|
|
A message
used to communicate inventory levels from the place where
goods are stored to the owner of goods and additional trading
partners involved in maintaining inventory levels such as the distributor,
manufacturer, material supplier, retailer, warehouse, and wholesaler. The Inventory Activity or
Inventory Status includes all the activities and techniques of maintaining the
stocks of items. |
|
|
Go to full message description |
|
|
|
|
|
RECEIVING ADVICE |
|
|
Message
definition |
|
|
The
Receiving Advice provides the receiver of the shipment the capability
to inform
the shipper of actual goods received, compared to what was adviced as
being
sent. It enables the link to the information that makes up a Despatch
Advice or
Shipping Document, providing detailed information about the content of
a
shipment of goods from the Shipper to the Receiver.
The
Receiving Advice can be used in correlation all
relevant data regarding the goods to be picked up and transported from
initial
origin to final destination and all intermediate stops if applicable.with the Despatch Advice or
other
shipment documentation to provide a simple acknowledgment that goods
have been
received, a detailed verification of actual goods received and
notification of
exceptions between shipment documentation (e.g. Despatch Advice and
BOL) and
actual receipts.
|
|
|
Go to full message description |
|
|
|
|
|
TRANSPORTATION RATE COMPLEX REQUEST |
|
|
Message
definition |
|
|
The purpose of this message is to support the communication of transportation services
provider rate requests and their corresponding responses. |
|
|
Go to full message description |
|
|
The purpose of this message is to support the communication of transportation services
provider rate requests and their corresponding responses. |
|
|
TRANSPORTATION RATE COMPLEX RESPONSE |
|
|
Message
definition |
|
|
The purpose of this message is to support the communication of transportation services
provider rate requests and their corresponding responses. |
|
|
Go to full message description |
|
|
|
|
|
TRANSPORTATION RATE SIMPLE REQUEST |
|
|
Message
definition |
|
|
The purpose of this message is to support the communication of transportation services
provider rate requests and their corresponding responses. |
|
|
Go to full message description |
|
|
|
|
|
TRANSPORTATION RATE SIMPLE RESPONSE |
|
|
Message
definition |
|
|
The purpose of this message is to support the communication of transportation services
provider rate requests and their corresponding responses. |
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ADVANCED REMITTANCE NOTIFICATION |
|
|
Message
definition |
|
|
The purpose of this
message is to support the Advanced Remittance Notification
business transaction needed to meet the requirements
of the Collaborative Receipt Settlement (CRS), which is the
process of rendering payment for goods received based upon quantity
received and synchronized pricing records without having to exchange an
invoice
from a seller to a buyer. |
|
|
Go to full message description |
|
|
|
|
|
CLAIMS NOTIFICATION |
|
|
Message
definition |
|
|
The purpose of this message is to support the Claims Notification
business transaction needed to meet the requirements
of the Collaborative Receipt Settlement (CRS), which is the
process of rendering payment for goods received based upon quantity
received and synchronized pricing records without having to exchange an
invoice
from a seller to a buyer. |
|
|
Go to full message description |
|
|
|
|
|
INVOICE |
|
|
Message
definition |
|
|
The Invoice Message is defined as
requesting payment for goods or services under conditions agreed upon between
the seller and the buyer. It contains the necessary information needed for
payment consisting of parties, items, prices, amounts and quantities. |
|
|
Go to full message description |
|
|
|
|
|
INVOICE RESPONSE |
|
|
Message
definition |
|
|
For some commercial transactions the
requesting party requires a formal response by the responding party in order to
ensure proper and timely processing. The Invoice Response message enables the
responding party to communicate the acceptance or rejection of the Invoice transaction. |
|
|
Go to full message description |
|
|
|
|
|
SETTLEMENT |
|
|
Message
definition |
|
|
The Settlement message provides the ability
is to send payment and remittance without adjustment, send remittance
with adjustments
and/or discounts, send payment and remittance with adjustment and/or
discounts,
send payment, send remittance without adjustments and/or discounts.
|
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
GOODS REQUIREMENTS
|
|
|
|
|
|
|
|
|
REPLENISHMENT
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GOODS REQUIREMENTS |
|
|
Message
definition |
|
|
In several business scenarios the buyer
needs to communicate his Goods Requirements to the seller. This can be needed
in traditional order driven scenarios and is definitely needed in supplier
managed scenarios. The Goods Requirements communicated by the buyer can be
gross or net (= gross requirements -/- inventory). |
|
|
Go to full message description |
|
|
|
|
|
GOODS REQUIREMENTS RESPONSE |
|
|
Message
definition |
|
|
In several business scenarios the buyer
needs to communicate his Goods Requirements to the seller. This can be needed
in traditional order driven scenarios and is definitely needed in supplier
managed scenarios. The Goods Requirements communicated by the buyer can be
gross or net (= gross requirements -/- inventory). |
|
|
Go to full message description |
|
|
|
|
|
REPLENISHMENT
PROPOSAL |
|
|
Message
definition |
|
|
A message
including the data for finished goods, semi-finished goods,
ingredients, packaging materials or raw materials. In more
collaborative scenarios also inventory data of the 'buying' party can
be included. The interchange is not defined for only inventory data. |
|
|
Go to full message description |
|
|
|
|
|
REPLENISHMENT REQUEST |
|
|
Message
definition |
|
|
A message
including the data for finished goods, semi-finished goods,
ingredients, packaging materials or raw materials. In more
collaborative scenarios also inventory data of the 'buying' party can
be included. The interchange is not defined for only inventory data. |
|
|
Go to full message description |
|
|
|
|
|
PURCHASE CONDITIONS |
|
|
Message
definition |
|
|
The Purchase Conditions sets the
contractual conditions for the ordering and delivering of the goods and so
details specific terms and conditions that apply for a given period. While
both parties need to agree on Purchase Conditions data, it is understood that
only one party, i.e. the buyer or seller, will send the Purchase Conditions
message and that the information flow will be in one direction only in order
to ensure alignment. |
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
