Copyright © 2003 OASIS
$Date: 2003/10/24 01:33:52 $(UTC)
Table of Contents
This formatting specification describes a rendering of the UBL Despatch Advice document model according to the United Nations Layout Key for Trade Documents guidelines for application for the 351 despatch advice form:
351 Despatch Advice: Document by means of which the seller or consignor informs the consignee about the despatch of goods.
For a list of all formatting specifications and an overview of the documentation conventions, please visit the formatting specification home page.
This specification has no formal status at this time. It should not be considered a reference interpretation of UBL documents. Feedback is sought from users of stylesheets that implement this formatting specification regarding suggestions for change for consideration by the OASIS UBL committees for incorporation into these formatting specifications.
Presentational semantics may never be formalized or normative in the UBL project due to differing international requirements and conventions for the presentation of information found in business documents. This document contains only examples from a few of what will probably be many available UBL stylesheet libraries.
Example renderings:
PDF printable format (A4 page size)
Items in this formatting specification are ordered roughly from the laid out fields on the form in the order left-to-right, top to bottom.
Certain descriptions are verbatim quotes from the United Nations guidelines document.
Important: the rendering of a number of fields is very simplified, reflecting a Western European interpretation of a subset of fields (as in names and addresses). User requirements need to be better understood for the level of granularity in these stylesheets.
The following information is unrelated to the visible fields of the form.
Header information is associated with the form as a whole, not to the individual items of goods.
Table 2. XPath information
| XPath addresses |
| /da:DespatchAdvice/cat:SellerParty/cat:PartyName/cat:Name |
| /da:DespatchAdvice/cat:SellerParty/cat:Address/cat:Street |
| /da:DespatchAdvice/cat:SellerParty/cat:Address/cat:CityName |
| /da:DespatchAdvice/cat:SellerParty/cat:Address/cat:CountrySub‑EntityCode |
| /da:DespatchAdvice/cat:SellerParty/cat:Address/cat:Country/cat:Code |
This field is intended to show the name and address of the sender of goods or the originator of the documents, as the case may be.
reference for the goods
reference for the goods
The field for the name and address of the consignee has been located in conformity with international postal specifications so as to allow the use of window envelopes.
The contents of this field is the same as the Section 3.5, “Buyer” field.
Table 5. XPath information
| XPath addresses |
| /da:DespatchAdvice/cat:BuyerParty/cat:PartyName/cat:Name |
| /da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:Street |
| /da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:CityName |
| /da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:CountrySub‑EntityCode |
| /da:DespatchAdvice/cat:BuyerParty/cat:Address/cat:Country/cat:Code |
The field for the name and address to which documents are sent (buyer).
Transportation fields that are header-like and applicable to the entire order.
Table 6. XPath information
| XPath address |
| /da:DespatchAdvice/cat:ActualShipment/cat:ShipmentStage/cat:TransportModeCode |
NB may be more than one
Table 7. XPath information
| XPath address |
| /da:DespatchAdvice/cat:ActualShipment/cat:ShipmentStage/cat:TransitPeriod/cat:StartDateTimeDate |
Use the earliest date (if more than one)
Table 8. XPath information
| XPath address |
| /da:DespatchAdvice/cat:ActualShipment/cat:ShipmentStage/cat:TransportMeansTypeCode |
NB may be more than one
Table 9. XPath information
| XPath addresses |
| /da:DespatchAdvice/cat:DeliveryRequirement/cat:SendFromAddress/cat:CityName |
| /da:DespatchAdvice/cat:DeliveryRequirement/cat:SendFromAddress/cat:Country/cat:Code |
Despatch is the required place
Table 10. XPath information
| XPath addresses |
| /da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:SendFromAddress/cat:CityName |
| /da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:SendFromToAddress/cat:Country/cat:Code |
Loading is the actual place
Goods information is associated with the individual items of the goods in the shipment
Table 13. XPath information
| XPath address |
| /da:DespatchAdvice/cat:DespatchedTransportHandlingUnit/cat:ID |
This field is not clearly defined in the message
Table 14. XPath information
| XPath address |
| /da:DespatchAdvice/cat:ActualShipment/cat:TransportEquipment/cat:ID |
NB may be many of these
Table 15. XPath information
| XPath addresses |
| /da:DespatchAdvice/cat:DespatchedTransportHandlingUnit/cat:TypeCode |
| /da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:OrderLine/cat:Quantity |
| /da:DespatchAdvice/cat:ActualShipment/cat:DeliveryRequirement/cat:OrderLine/cat:Item/cat:Description |
Summary information is associated with the form as a whole, not to the individual items of goods.
Table 18. XPath information
| XPath addresses |
| /da:DespatchAdvice/cat:FreightForwarderParty/cat:PartyName/cat:Name |
| /da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:Street |
| /da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:CityName |
| /da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:CountrySub‑EntityCode |
| /da:DespatchAdvice/cat:FreightForwarderParty/cat:Address/cat:Country/cat:Code |
Section 2.1, “ Document header information” - Note
The information in the document header isn't revealed anywhere in the body of the form; is this acceptable? Should it be changed?
Section 4.1, “Mode of transport” - Note
How should multiple mode of transport fields be formatted?
Section 4.2, “Date of despatch” - Note
The "earliest" test hasn't yet been implemented.
Section 4.3, “Means of transport” - Note
How should multiple means of transport fields be formatted?
Section 5.2, “Container Nr.” - Note
How should multiple container number fields be formatted?
Section 6.1, “Documentary instructions” - Note
How should multiple notes be formatted? Need they be enumerated? Any impact on "footnote"-like pointers?