|
Business Processes |
|
|
ALIGN |
|
|
GDSN |
|
|
ORDER |
|
|
DELIVER |
|
|
PAY |
|
|
|
|
|
OTHER |
|
|
|
|
|
ALIGN BUSINESS
PROCESS |
|
|
|
|
|
PARTY |
|
|
PEER-TO-PEER
TRADE ITEM |
|
|
PRICE |
|
|
PRICE BRACKET |
|
|
FMCG EXTENSION FOR TRADE ITEM |
|
|
HARDLINES EXTENSION FOR TRADE ITEM |
|
|
SOFTLINES EXTENSION
FOR TRADE ITEM |
|
|
SWEDEN EXTENSION FOR TRADE ITEM |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PARTY
|
|
|
Message
definition |
|
|
Party
is the first message in the trade process. Party
message communicates the initial Party data describing
the seller, buyer and any third party in a trading relationship. It
includes communicating Party (supplier, buyer and third party) details
such as primary party identification,
organizational related details, relationship roles and the Party
attributes. |
|
|
Go to full message description |
|
|
|
|
|
PEER-TO-PEER TRADE
ITEM |
|
|
Message
definition |
|
|
Item
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 Peer-to-Peer Trade Item
contains the base/core item information requirements needed for a
simple
(Peer-to-Peer) electronic commerce data exchange. |
|
|
Go to full message description |
|
|
|
|
|
FMCG
EXTENSION FOR TRADE ITEM |
|
|
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 |
|
|
|
|
|
HARDLINES
EXTENSION FOR TRADE ITEM |
|
|
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 |
|
|
|
|
|
SOTFLINES
EXTENSION FOR TRADE ITEM |
|
|
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 |
|
|
|
|
|
SWEDEN
EXTENSION FOR TRADE ITEM |
|
|
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 |
|
|
|
|
|
PRICE |
|
|
Message
definition |
|
|
Price
is the message communicating the Price data elements between the
seller, buyer and
any third party. Price communicates either a
generic global price or the agreed upon negotiated price between
trading
partners.
Price data message may be
processed, once the Core Party and Core Item data attributes are
aligned. Specifically, the Price can be communicated as
part of the Item alignment data or in a subsequent separate message. |
|
|
Go to full message description |
|
|
|
|
|
PRICE
BRACKET |
|
|
|
|
|
Price
bracket is the message communicating the basic price bracket criteria
between
the seller, buyer and any third party.
The Price Bracket provides the
ability to communicate the business rules associated with the criteria
required
to qualify for varying levels of pricing for a trade item.
This Price Bracket definition
intentionally does not support additional “business rules
based” price
communication, e.g. temporary price reductions/promotions, variable
measure
pricing, efficiency criteria associated with the trading partnership,
allowances and charges, etc.
The
Price Bracket may accompany, precede or follow the communication of a
price. It
follows communication of the core data elements of item and party, as
well as
any subsequent maintenance messages. |
|
|
Go to full message description
|
|
|
|
|
|
CONDITION DOCUMENT |
|
|
Message
definition |
|
|
Price synchronisation of
relationship dependent data
requires three (3) business messages to be used together.
They are Trading Partner Profile (TPP), Condition
Documents and Monetary Documents.
Condition Documents are
components that
when properly sequenced can enable the calculation of an end price from
a given
starting price. Condition Documents contain information about a debit
or credit,
which can affect the final price. Condition Documents can also be used
to represent
a final price, for example transaction price |
|
|
Go to full message description |
|
|
|
|
|
MONETARY DOCUMENT |
|
|
Message
definition |
|
|
Price synchronisation of
relationship dependent data
requires three (3) business messages to be used together.
They are Trading Partner Profile (TPP), Condition
Documents and Monetary Documents.
Monetary Documents contain
a value, rate or
percent relating to a specific price condition.
Monetary Documents can be GTIN specific or not
GTIN specific (for
example backhauls). |
|
|
Go to full message description |
|
|
|
|
|
EXTENSION
SPECIFIC TECHNICAL CHARACTERISTICS |
|
|
Message
definition |
|
|
The purpose of this message
is to exchange
specific technical characteristics which are not listed in the GDD.
Those
specific technical characteristics are coded by an agency, e.g. code 65
identifies GS1 FRANCE
(but any other MO can codify technical characteristics to respond to
their
members’ needs).
This allows exchanging specific information
on products, information which does not exist in the GDD, and which are
not
intended to be added into the GDD. The intention is not to add
information
already existing in GDD. |
|
|
Go to full message description |
|
|
|
|
|
TRADING
PARTNER PROFILE DOCUMENT |
|
|
Message
definition |
|
|
Price synchronisation of
relationship dependent data
requires three (3) business messages to be used together.
They are Trading Partner Profile (TPP), Condition
Documents and Monetary Documents.
Trading Partner Profiles
enable the
electronic representation of the trading partners’ agreement
for the inclusion,
depiction, and application sequence for price components on an invoice. |
|
|
Go to full message description |
|
|
|
|
|
TOP
|
|
|
|
|
|
|
|
|
|
|
|
CATALOGUE ITEM SYNCHRONISATION
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PARTY SYNCHRONISATION
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GDSN SEARCH
|
|
|
|
|
|
|
|
|
|
|
|
TRADE ITEM FOR DATA
SYNCHRONISATION |
|
|
Message
definition |
|
|
Item 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 Trade Item
for Data Synchronisation contains the base/core item information
requirements needed for data exchange witin Global Data
Synchronisation 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 |
|
|
|
|
|
DATA
SYNCHRONISATION DATA POOL PROFILE |
|
|
Message
definition |
|
|
A message used to
identify a data pool within the Global Data Synchronisation Network. |
|
|
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 |
|
|
|
|
|
PARTY CONFIRMATION |
|
|
Message
definition |
|
|
A message
sent from the Data Recipient to the Recipient Data Pool indicating what
action has been taken on the party data. The confirmation process
occurs in the recipient’s data pool.
It can be also sent from the Data Recipient informing the Source Data
pool of the status of an individual Party Data synchronisation that was
the result of a Publication / Subscription match. Confirmations are
passed to the Source Data Pool from the Recipient Data Pool. |
|
|
Go to full message description |
|
|
|
|
|
PARTY NOTIFICATION |
|
|
Message
definition |
|
|
A business
message used to transmit party information from a data source or a data
pool to a data recipient with the Global Data Synchronisation Network
In the data synchronisation process, 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
-
request for
notification |
|
|
Go to full message description |
|
|
|
|
|
PARTY PUBLICATION |
|
|
Message
definition |
|
|
A
message distributing party 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 |
|
|
|
|
|
PARTY REGISTRATION |
|
|
Message
definition |
|
|
A business
message used to register party information from a data pool to the
Global Registry within the Global Data Synchronisation Network. |
|
|
Go to full message description |
|
|
|
|
|
PARTY 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 party. |
|
|
Go to full message description |
|
|
|
|
|
PARTY SUBSCRIPTION |
|
|
Message
definition |
|
|
A message
used to establish a request for the update of party information from an
end recipient on a continuous basis. |
|
|
Go to full message description |
|
|
|
|
|
REQUEST FOR
PARTY NOTIFICATION |
|
|
Message
definition |
|
|
A message
used to establish a subscription to party 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 parties 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 |
|
|
|
|
|
SEARCH REQUEST |
|
|
Message
definition |
|
|
A message
used in the Global Data Synchronisation Network (GDSN) to allow Data
Recipients, via their Data Pools, to search the Global Registry for
data related to Registry Catalogue Item, Party and/or Trade Item. |
|
|
Go to full message description |
|
|
|
|
|
SEARCH RESULT |
|
|
Message
definition |
|
|
A message
used in the Global Data Synchronisation Network (GDSN) to allow Data
Recipients, via their Data Pools, to receive Registry Catalogue Item,
Party and/or Trade Item data via the Global Data Synchronisation
Network. |
|
|
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 |
|
|
|
|
|
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 |
|
|
|
|
|
CONFIGURE TO ORDER |
|
|
Message
definition |
|
|
The
Configure to Order provides support for configurable items on
a purchase
order. A configurable item is one that
starts with a single structure, but to which a large variety of options
may be
added in a variety of combinations. A
unique product identification code is assigned to the main structure of
a
configurable item, but due to the variety of combinations of options,
it is NOT
practical to assign unique product identification to each completed
configured
item.
This scenario applies to many manufacturers and
retailers. For manufacturers and retailers who specialize in
upholstered
furniture, it can apply to the vast majority of their business. For
these
companies, any model that does not support configured product is not an
accurate
business model, and any implementation from a model that does not
support configured
product is not usable. As such, the
business benefits of this request are the ability to do business at all.
|
|
|
Go to full message description |
|
|
|
|
|
MULTI
SHIP TO ORDER |
|
|
Message
definition |
|
|
The Multi Ship to
Order provides the ability for a
buyer to order variable quantities of trade items/services
shipped to multiple locations using one transmission. |
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
DESPATCH
ADVICE |
|
|
RECEIVING
ADVICE |
|
|
CARRIER ROUTING INSTRUCTION |
|
|
INVENTORY ACTIVITY OR INVENTORY STATUS |
|
|
SPC SHIPMENT STATUS |
|
|
SPC SHIPMENT STATUS INQUIRY |
|
|
WAREHOUSE
SHIPPING ORDER |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DESPATCH ADVICE |
|
|
Message
definition |
|
|
The
Despatch Advice enables
one Shipper to provide information about the content of a shipment to
one
Receiver. Specifically,
the Despatch
Advice serves as a link to a prior agreement between Shipper and
Receiver and
is applicable to one or many Receiver destination points from one
Shipper
launch point. Furthermore,
the Despatch
Advice may be used to indicate the despatch of goods being returned by
the
Receiver. The
Despatch Advice may be
utilized downstream between retailers, suppliers, 3PLs, carriers and
manufacturers as well as upstream between manufacturers, 3PLs and
material
suppliers. |
|
|
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 |
|
|
|
|
|
CARRIER
ROUTING INSTRUCTION |
|
|
Message
definition |
|
|
A
message passing transportation routing instructions, it
consists of a buyer’s carrier
routing instructions and buyer’s party cross reference
(Store, Distribution
Centre, Department) to the seller.
|
|
|
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. |
|
|
Go to full message description |
|
|
|
|
|
SPC
SHIPMENT STATUS |
|
|
Message
definition |
|
|
A message
addressing address the requirements of having a core
transport
status response for the Small Package Carriers (SPC) within the motor
carrier
industry. |
|
|
Go to full message description |
|
|
|
|
|
SPC
SHIPMENT STATUS INQUIRY |
|
|
Message
definition |
|
|
A message
addressing address the requirements of having a core
transport
status inquiry for the Small Package Carriers (SPC) within the
motor carrier
industry. |
|
|
Go to full message description |
|
|
|
|
|
WAREHOUSE
SHIPPING ORDER |
|
|
Message
definition |
|
|
A message passing
order information from a supplier to ship goods from the warehouse. |
|
|
Go to full message description |
|
|
|
|
|
FTL LTL SHIPMENT
STATUS |
|
|
Message
definition |
|
|
A message sent by
a Shipment Handler (Carrier, 3PL) providing the status of
goods in
transit. The Shipment Status message can be sent in response to
a Shipment Status Inquiry Message (solicited). It can also be
sent
without the
receipt of an inquiry (unsolicited). |
|
|
Go to full message description |
|
|
|
|
|
FTL LTL
SHIPMENT STATUS INQUIRY |
|
|
Message
definition |
|
|
A message sent by a Supplier,
Buyer or 3PL, requesting a shipping status from a Shipment
Handler. The Shipment Handler is any party involved in
the
shipment of goods including a carrier or a 3PL. |
|
|
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 |
|
|
|
|
|
FTL LTL
CARRIER BILL OF LADING |
|
|
Message
definition |
|
|
A message
used by a shipper to pass load information from a consignor to a
less-than-truckload (LTL) or (FTL) motor carrier to a consignee. The
use of an LTL carrier or (FTL) motor carrier Bill of Lading represents
a shipment from a single origin to a single destination. |
|
|
Go to full message description |
|
|
|
|
|
MOTOR
FUEL CARRIER BILL OF LADING |
|
|
Message
definition |
|
|
A message
used by a shipper to pass load information from a consignor to a motor
fuel carrier to a consignee. The use of a Motor Carrier Bill of Lading
can represent a shipment from a single origin to multiple destinations. |
|
|
Go to full message description |
|
|
|
|
|
PICKUP NOTIFICATION
LTL |
|
|
Message
definition |
|
|
A message used by the Shipper, Consignee or 3rd
Party to notify the Carrier that a shipment is available for
pick up. |
|
|
Go to full message description |
|
|
|
|
|
SMALL PACKAGE
PICKUP MANIFEST |
|
|
Message
definition |
|
|
A message
providing manifest information of all packages tendered to the carrier
from the Shipper, Consignee or Third Party. It is used by the Shipper
to communicate package level detail about a shipment ready for pickup
by small package carrier. |
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
REQUEST FOR PAYMENT |
|
|
Message
definition |
|
|
The Core Request for Payment Message is
defined as requesting payment for goods or services under conditions
agreed
upon between the seller and the buyer. It contains only the necessary
information needed for payment consisting of parties, items, and
quantities.
Extensions are available to add functionality and are categorized by
business
process. For example, the Core Request for Payment could be used with
the
Simple Invoice Extension for data relative to pricing and reference
numbers.
|
|
|
Go to full message description |
|
|
|
|
|
SIMPLE INVOICE |
|
|
Message
definition |
|
|
The Simple Invoice Extension to Core
Request for Payment contains data relative to pricing and reference
numbers. It
can be used in conjunction with the Core Request for Payment message in
a
business-to-business exchange of Simple Invoice information between
trading
partners. As an extension, it cannot be used independently.
|
|
|
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 |
|
|
|
|
|
DEBIT OR CREDIT
ADVICE |
|
|
Message
definition |
|
|
The
goal of this 'Debit Or Credit Advice' use case is to provide an
electronic
advice to a trading partner that a monetary adjustment - debit or
credit amount
value - is being applied to the purchase of goods or services.
Situations that result
in the need for one party to notify the other trading party that an
adjustment
is being applied, resulting in a change to the monetary amount owed/due
between
the parties include (but are not limited to): goods being received
damaged, incorrect
quantity of goods are received, retroactive volume discounts.
|
|
|
Go to full message description |
|
|
|
|
|
BUYER RECONCILIATION OF REQUEST
FOR PAYMENT |
|
|
Message
definition |
|
|
A message enabling
a buyer to respond to Requests For Payment received from a seller. The
document reports to the seller whether or not the buyer was able to
schedule the requested payment through the accounts payable system. |
|
|
Go to full message description |
|
|
|
|
|
CNOFIRMATION
OF SETTLEMENT INSTRUCTIONS |
|
|
Message
definition |
|
|
A message handling
the acknowledgment of payment orders, by transaction, from the
financial institution to the payer. The payer submits payment requests
to the financial institution. The payer has requested that the
financial institution confirm receipt for processing of the payment
requests. |
|
|
Go to full message description |
|
|
|
|
|
CONTROL
TOTALS BUYER TO BUYER FINANCIAL INSTITUTION |
|
|
Message
definition |
|
|
A message verifying
payment requests submitted to the paying financial institution, as a
part of the financial checks and balances employed within a company. It
ensures that sufficient funds are available for payment by the
financial institution, and removes the possibility of the submission of
fraudulent payment transactions.
Typically, payment transactions are generated by the accounts payable
department of a company and forwarded to a financial institution for
payment. As part of a company’s control mechanism,
this message provides a verification to the financial
institution, confirming the monetary value and count of payments to be
made by the financial institution. |
|
|
Go to full message description |
|
|
|
|
|
FINANCIAL INSTITUTION CONTROL TOTALS |
|
|
Message
definition |
|
|
A message allowing
a financial institution to advise the payer (the submitter of one or
more Settlement of Requests for Payment) of the total monetary value of
Settlement messages processed for a particular day. |
|
|
Go to full message description |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
|
CPFR
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
REPLENISHMENT
|
|
|
|
|
|
|
|
|
|
|
|
EVENT |
|
|
Message
definition |
|
|
A message describing discrete
events that affect
supply or demand. For example, a sale on
an item increases demand. Events are not
restricted to promotions; they may include weather-related activity, or
inventory policy changes. |
|
|
Go to full message description |
|
|
|
|
|
EXCEPTION CRITERIA |
|
|
Message
definition |
|
|
The exception criteria is
created during the
development of the collaborative agreement and used as an input to
revise
forecasts. Exception criteria are rules that describe the
thresholds for forecast variance, product activity, and performance
history
beyond which exceptions should be triggered.
CPFR implementations exchange
exception criteria so that their respective exception engines can use
the same
rules to evaluate data, and trigger identical exceptions in parallel.
Forecast item exception criteria may be restricted
to a single component of a forecast (for example, a variance in the
promotional
component of two sales forecasts), or they can compare totals. The
effective dates for an exception describe
a horizon in which a criterion is valid. |
|
|
Go to full message description |
|
|
|
|
|
EXCEPTION
NOTIFICATION |
|
|
Message
definition |
|
|
message
notifying a trading partner when a
buyer or seller exception has been triggered. There are several types
of exceptions, but all types
describe a variance of a data item from an expected value during a
particular
time interval. |
|
|
Go to full message description |
|
|
|
|
|
FORECAST |
|
|
Message
definition |
|
|
Forecast can be either asales
forecasts – reflecting consumer demand or
manufacturing
consumption – or an order forecast, indicating the
supply
needed to meet future consumption requirements. Each forecast data item
within a forecast
represents a quantity of demand or supply for a specific product that
is
expected between buyer and seller locations for a given time interval.
An item may be for the total volume during
the period, or a component (base/turn, promotional, or seasonal) of the
total
demand. Promotional forecast data items
may also identify an associated promotion and the number of buyer
locations
that are participating.
Forecast data items may be frozen, in which case
they may not be adjusted. Otherwise, the
receiving organization has the option of revising the item and
notifying an
appropriate trading partner via a forecast revision (See forecast revision). |
|
|
Go to full message description |
|
|
|
|
|
FORECAST BULK DATA |
|
|
Message
definition |
|
|
Each bulk data message is a
uniform series of
records of a single message type. Records criteria include width, order
of
fields and default values.
A
bulk data description may be provided with every batch file, or a
single
description may be used to describe all files of that type exchanged
between a
buyer and a seller.
Bulk data for forecast restricts the
transfer of bulk data to forecast data. |
|
|
Go to full message description |
|
|
|
|
|
FORECAST REVISION |
|
|
Message
definition |
|
|
Forecast items may be frozen,
in which case they may
not be adjusted. Otherwise, the
receiving organization has the option of revising the item and
notifying an
appropriate trading partner via a forecast revision.
Forecast revision message has the same structure
as a forecast. However, forecast
revision trade item has a comment and an adjustment reason code, which
explain why the revision is being proposed. orecast revision
trade items also includes the timestamp of the forecast
being revised, so that comparisons with the original forecast can be
made.
Forecast revision may be submitted (new),
acknowledged, accepted, rejected or superseded. |
|
|
Go to full message description |
|
|
|
|
|
PERFORMANCE HISTORY |
|
|
Message
definition |
|
|
Performance history captures
key supply chain
metrics. These metrics can include
forecast accuracy, in-stock percentage, fill rate, days of supply, or
on-time
delivery percentage. |
|
|
Go to full message description |
|
|
|
|
|
PRODUCT ACTIVITY |
|
|
Message
definition |
|
|
Product activity reports are
collections of product activity items that
indicate the quantities of product movement during the specified time
intervals. Types of product activity include sales (which may
also
be interpreted
as manufacturing consumption or warehouse withdrawals, depending upon
the type
of buyer/seller relationship), orders, canceled orders, emergency
orders,
receipts, shipments and on-hand inventory. |
|
|
Go to full message description |
|
|
|
|