|
RECEIVING ADVICE v. 2.0.2 |
|
|
|
|
|
Problem
Statement |
|
|
he business
process of shipping and
receiving requires the actors in this process to share information
regarding goods shipped and goods received. The Receiving
Advice
is developed to provide the receiver of the shipment the capability to
inform the shipper of actual goods received, compared to what was
adviced as being sent. Typical business uses of the receipt
information can include – updating of inventory, identifying
shipping
discrepancies, and adjusting orders and related invoicing.
This version of Receiving Advice, Version 2.1, was created in order to
improve upon the existing Receiving Advice (Version 1.0.2 of June 30,
2003), which is only an acknowledgement of goods received (proof of
delivery) from a Receiver to a Shipper. The Receiving Advice
should have the capability to link to the information that makes up a
Despatch Advice or Shipping Document, which provides detailed
information about the content of a shipment of goods from the Shipper
to the Receiver. With the capability of this link comes the
ability to compare exactly what was received to what was indicated as
sent on the Despatch Advice or Shipping Document. The
established
link between receipt and despatch information enables the comparison
and in turn allows the Receiving Advice to contain a range of
comparison information, from general to specific. |
|
|
Objective |
|
|
The
objective of the Receiving Advice
is to satisfy the business need as stated in section 1.1 above as well
as to provide a format that is flexible to serve the actors’
process
goals based on trading partner agreements.
For example, the Receiving Advice can be used in correlation with the
Despatch Advice or other shipment documentation to:
- Provide a
simple acknowledgment that
goods have been received
- Provide a
detailed verification of
actual goods received
- Provide
notification of exceptions
between shipment documentation (e.g. Despatch Advice and BOL) and
actual receipts
|
|
|
Audience |
|
|
Retailers,
manufacturers, warehouses, material suppliers, carriers and any other
third party such as a logistic service or 3PL provider involved in the
despatch and receipt of goods. |
|
|
Business
Context
|
|
|
Industry:
All
Geopolitical:
All
Product:
All
Process:
Deliver
System
Capabilities:
EAN.UCC
Official
Constraints: None |
|
|
Business
Transaction View
|
|
|
When the
Receiver receives a shipment
of goods from the Shipper, the Receiver compares the received goods to
what was adviced as despatched on the despatch advice or shipping
documents, and creates and sends a Receiving Advice. The
Receiver
has the following options to choose from regarding what the Receiving
Advice may contain:
- full
–details- Includes qualitative
and/or quantitative details regarding everything received (all line
items) whether or not there were exceptions between what was received
and what was adviced as being sent.
- exceptions
–
Includes only
qualitative and/or quantitative exceptions between what was re-ceived
and what was adviced as being sent.
- confirmation-
The acceptance of the
receipt of goods.
|
|
|
TOP |
|
|
Business
Transaction Use Case
Diagram |
|
|
 |
|
|
|
|
|
TOP |
|
|
Use
Case
Description
|
|
|
| Use
Case Name: |
Create and Send Receiving
Advice |
| Use
Case Description: |
Describes a
complete process
whereby a Receiver generates a Receiving Advice based on information
gained from received goods and physical or electronic documents from a
Shipper. |
| Actors
(Goal): |
Receiver
and Shipper |
| Preconditions:
|
Master
data alignment of locations (GLNs) and products (GTINs). |
| Postconditions: |
Indication
of exceptions,
full-detailed comparison or confirmation between goods received and
goods adviced as despatched. |
| Scenario:
|
Begins when
the Receiver receives a shipment of
goods accompanied or preceded by the Despatch Advice or Shipping
Documents
Ends
when the Receiver
compares the received goods (as well as qualitative properties) to what
was adviced as being sent on the despatch advice or shipping documents.
Receiving Advice will include full details OR exceptions OR a
confirmation of the received goods compared to what was adviced as
being despatched on the despatch advice or shipping documents.
Receiving Advice will include full details OR exceptions OR a
confirmation of the received goods compared to what was adviced as
being despatched on the despatch advice or shipping documents. |
|
|
|
Business
Transaction Activity Diagram |
|
|
|
|
|
TOP |
|
|
Business
Transaction Sequence Diagram |
|
|
|
|
|
It is noted that the primary intent of this
diagram is to show the creation and transfer of information and not
necessarily
the physical flow of goods although the assumption is that goods are
shipped
and received as a result of information sent and received as well as
prior
arrangements. In some cases, the information flow in the diagram will
be
predicated upon the physical flow, and that particular physical flow
instance
is shown. |
|
|
|
|
|
TOP |
|
|
Example
- Business
Document |
|
|
|
|
