UN aligned layout formatting specification for UBL Order Response Simple instances

Copyright © 2004 OASIS

$Date: 2004/09/09 01:30:40 $(UTC)

Table of Contents

1. Order response simple formatting specification
1.1. Status
1.2. Example rendering
1.3. Layout order and information
1.4. Namespaces
2. Miscellaneous information
2.1. Document header information
3. Party information
3.1. Seller
3.2. Seller's reference
3.3. Date
3.4. Buyer's reference
3.5. Purchase order date
3.6. Consignee
3.7. Buyer
3.8. Rejection reason / Rejection note
3.9. Order response status
3.10. Country of origin
3.11. Country of destination
4. Delivery and transport
4.1. Mode of transport
4.2. Date of despatch
4.3. Means of transport
4.4. Place of despatch
4.5. Vessel/flight no.
4.6. Port of loading
4.7. Port of discharge
4.8. Place of delivery
4.9. Terms of delivery
4.10. Location
4.11. Special terms
4.12. Terms of payment
4.13. Currency of payment
5. Consignment information
5.1. Shipping marks; container number
5.2. No. and kind of packages; description of goods
5.3. Total gross weight (kg)
5.4. Total cube (m3)
5.5. Total net weight (kg)
6. Line item information
6.1. Item / References
6.2. Description
6.3. Country of origin
6.4. Commodity code
6.5. Quantity
6.6. Unit price
7. Summary information
7.1. Notes
7.2. Seller's company and telephone no.
7.3. Name of contact
7.4. Date
7.5. Signature

1.  Order response simple formatting specification

This formatting specification describes a rendering of the UBL Order Response Simple document model according to a subset of the United Nations Layout Key for Trade Documents guidelines for application for the 320 Acknowledgement of Order form:

  • 320 Acknowledgement of Order: Document acknowledging an undertaking to fulfill an order and confirming conditions or acceptance of conditions.

For a list of all formatting specifications and an overview of the documentation conventions, please visit the formatting specification home page.

1.1.  Status

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.

1.2.  Example rendering

The following is an example rendering that illustrates the position and decoration of the information items found in an instance of the document type:

1.3.  Layout order and information

At this stage, the layout has been created as no official layout is available.

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 formatting specifications.

1.4.  Namespaces

The following namespaces are mapped to the prefixes in the expressions below:

  • xmlns:rs="urn:oasis:names:specification:ubl:schema:xsd:OrderResponseSimple-1.0"

  • xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0"

  • xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"

2.  Miscellaneous information

The following information is unrelated to the visible fields of the form.

2.1.  Document header information

Table 1. XPath information

XPath addresses
/​rs:OrderResponseSimple/​cac:OrderReference/​cac:SellersID
/​rs:OrderResponseSimple/​cbc:IssueDate

This information shows up in the window-title bar of the HTML browser, and in the document title supported by some XSL-FO processors.

3. Party information

Header information is associated with the form as a whole, not to the individual items of goods.

3.1. Seller

Table 2. XPath information

XPath addresses
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:PartyName/​cbc:Name
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:BuildingNumber
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:StreetName
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:CityName
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:PostalZone
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Address/​cac:Country/​cbc:Name

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.

Note that only one of cbc:CountrySubentity and cac:CountrySubentityCode need be used, with preference to cbc:CountrySubentity if it exists.

3.2. Seller's reference

Table 3. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:OrderReference/​cac:SellersID

This number is a unique number assigned to the order response simple by the seller.

3.3. Date

Table 4. XPath information

XPath address
/​rs:OrderResponseSimple/​cbc:IssueDate

This field states the date of the order response simple.

3.4. Buyer's reference

Table 5. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:OrderReference/​cac:BuyersID

This field provides a reference to the original order.

3.5. Purchase order date

Table 6. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:OrderReference/​cbc:IssueDate

This field provides the issue date of the original order.

3.6. Consignee

At this time this field is not being used in the order response simple.

3.7. Buyer

Table 7. XPath information

XPath addresses
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:PartyName/​cbc:Name
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:BuildingNumber
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:StreetName
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CityName
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:PostalZone
/​rs:OrderResponseSimple/​cac:BuyerParty/​cac:Party/​cac:Address/​cac:Country/​cbc:Name

These fields are used to provide the name and address of the buyer of the goods involved in the transaction.

Note that only one of cbc:CountrySubentity and cac:CountrySubentityCode need be used, with preference to cbc:CountrySubentity if it exists.

3.8. Rejection reason / Rejection note

Table 8. XPath information

XPath address
/​rs:OrderResponseSimple/​rs:RejectionNote

This field provides free text information relating to the order response simple.

3.9. Order response status

Table 9. XPath information

XPath address
/​rs:OrderResponseSimple/​rs:DocumentStatusCode

This field provides the status of the order response simple, the response status code should be translated into text form for clarity.

3.10. Country of origin

At this time this field is not being used in the order response simple.

3.11. Country of destination

At this time this field is not being used in the order response simple.

4. Delivery and transport

Transportation fields are header-like and applicable to the entire order response simple.

4.1. Mode of transport

At this time this field is not being used in the order response simple.

4.2. Date of despatch

At this time this field is not being used in the order response simple.

4.3. Means of transport

At this time this field is not being used in the order response simple.

4.4. Place of despatch

At this time this field is not being used in the order response simple.

4.5. Vessel/flight no.

At this time this field is not being used in the order response simple.

4.6. Port of loading

At this time this field is not being used in the order response simple.

4.7. Port of discharge

At this time this field is not being used in the order response simple.

4.8. Place of delivery

At this time this field is not being used in the order response simple.

4.9. Terms of delivery

At this time this field is not being used in the order response simple.

4.10. Location

At this time this field is not being used in the order response simple.

4.11. Special terms

At this time this field is not being used in the order response simple.

4.12. Terms of payment

At this time this field is not being used in the order response simple.

4.13. Currency of payment

At this time this field is not being used in the order response simple.

5. Consignment information

The consignment information holds generic details and totals relating to all the goods items in the order response simple.

5.1. Shipping marks; container number

At this time this field is not being used in the order response simple.

5.2. No. and kind of packages; description of goods

At this time this field is not being used in the order response simple.

5.3. Total gross weight (kg)

At this time this field is not being used in the order response simple.

5.4. Total cube (m3)

At this time this field is not being used in the order response simple.

5.5. Total net weight (kg)

At this time this field is not being used in the order response simple.

6. Line item information

Line item information is associated with the individual item of goods in the order response simple.

6.1. Item / References

At this time this field is not being used in the order response simple.

6.2. Description

At this time this field is not being used in the order response simple.

6.3. Country of origin

At this time this field is not being used in the order response simple.

6.4. Commodity code

At this time this field is not being used in the order response simple.

6.5. Quantity

At this time this field is not being used in the order response simple.

6.6. Unit price

At this time this field is not being used in the order response simple.

7. Summary information

Summary information is associated to the entire order response simple.

7.1. Notes

Table 10. XPath information

XPath address
/​rs:OrderResponseSimple/​cbc:Note

This notes field is used for any free text information that relates to the entire order response simple.

7.2. Seller's company and telephone no.

Table 11. XPath information

XPath addresses
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:PartyName/​cbc:Name
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Contact/​cbc:Telephone

These fields identified the name of the seller's company and a contact telephone number.

7.3. Name of contact

Table 12. XPath information

XPath address
/​rs:OrderResponseSimple/​cac:SellerParty/​cac:Party/​cac:Contact/​cbc:Name

This field identified the name of the seller's contact.

7.4. Date

Table 13. XPath information

XPath address
/​rs:OrderResponseSimple/​cbc:IssueDate

This field provide the date of issue of the order response simple.

7.5. Signature

This field is not currently being filled automatically as it is a manual entry.