## Office-oriented formatting specification for UBL Order Change example instance

Copyright © 2004 OASIS

$Date: 2004/10/22 15:12:38 $(UTC)

## 1. Purchase order change formatting specification

This formatting specification describes a rendering of an instance of the UBL Order Change document model according to a conceptual office-oriented layout.

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:

- PDF printable format (A4 page size)

  - `OfficeOrderChange.Example-a4.pdf`

- PDF printable format (US-letter page size)

  - `OfficeOrderChange.Example-us.pdf`

### 1.3. Layout order and information

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.

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.

### 1.4. Namespaces

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

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

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

  `co` = "`urn:oasis:names:specification:ubl:schema:xsd:OrderChange-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
`/​co:OrderChange/​co:BuyersID`
`/​co:OrderChange/​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. Header information

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

### 3.1. Order No.

Table 2. XPath information

XPath address
`/​co:OrderChange/​cac:OrderReference/​cac:BuyersID`

### 3.2. Issue Date

Table 3. XPath information

XPath address
`/​co:OrderChange/​cac:OrderReference/​cbc:IssueDate`

### 3.3. Change Number

Table 4. XPath information

XPath address
`/​co:OrderChange/​co:BuyersID`

### 3.4. Change Date

Table 5. XPath information

XPath address
`/​co:OrderChange/​cbc:IssueDate`

### 3.5. Buyer

Table 6. XPath information

XPath addresses
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:PartyName/​cbc:Name`
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:BuildingNumber`
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:StreetName`
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CityName`
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:PostalZone`
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity`
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode`

The field for the name and address to which documents are sent (buyer).

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

### 3.6. Contact

Table 7. XPath information

XPath address
`/​co:OrderChange/​cac:BuyerParty/​cac:Party/​cac:Contact/​cbc:Name`

The buyer's contact for the order

### 3.7. Seller

Table 8. XPath information

XPath addresses
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:PartyName/​cbc:Name`
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:BuildingNumber`
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:StreetName`
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:CityName`
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:PostalZone`
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity`
`/​co:OrderChange/​cac:SellerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode`

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.8. Order Contact

This field is not filled in at this time

### 3.9. Delivery address

Table 9. XPath information

XPath addresses
`/​co:OrderChange/​cac:Delivery/​cac:DeliveryAddress/​cbc:BuildingNumber`
`/​co:OrderChange/​cac:Delivery/​cac:DeliveryAddress/​cbc:StreetName`
`/​co:OrderChange/​cac:Delivery/​cac:DeliveryAddress/​cbc:CityName`
`/​co:OrderChange/​cac:Delivery/​cac:DeliveryAddress/​cbc:PostalZone`
`/​co:OrderChange/​cac:Delivery/​cac:DeliveryAddress/​cbc:CountrySubentity`
`/​co:OrderChange/​cac:Delivery/​cac:DeliveryAddress/​cac:CountrySubentityCode`

The address where the order is being delivered.

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

### 3.10. Requested Delivery Date

Table 10. XPath information

XPath address
`/​co:OrderChange/​cac:Delivery/​cbc:RequestedDeliveryDateTime`

### 3.11. Delivery Terms

Table 11. XPath information

XPath address
`/​co:OrderChange/​cac:DeliveryTerms/​cbc:SpecialTerms`

## 4. Line item information

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

### 4.1. Line no.

Table 12. XPath information

XPath address
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cac:BuyersID`

This is the reference to the Order line.

### 4.2. Part number

Table 13. XPath information

XPath address
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cac:Item/​cac:SellersItemIdentification/​cac:ID`

### 4.3. Description

Table 14. XPath information

XPath address
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cac:Item/​cbc:Description`

One of these exists for each Line item.

### 4.4. Quantity U/M

Table 15. XPath information

XPath addresses
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cbc:Quantity`
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cbc:Quantity/​@quantityUnitCode`

One of these exists for each line item.

### 4.5. Unit price

Table 16. XPath information

XPath addresses
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cac:Item/​cac:BasePrice/​cbc:PriceAmount/​@amountCurrencyID`
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cac:Item/​cac:BasePrice/​cbc:PriceAmount`

One of these exists for each line item.

### 4.6. Extended Amount

Table 17. XPath information

XPath addresses
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cbc:LineExtensionAmount/​@amountCurrencyID`
`/​co:OrderChange/​cac:OrderLine/​cac:LineItem/​cbc:LineExtensionAmount`

This is not calculated - it is transmitted

## 5. Summary information

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

### 5.1. Total amount

Table 18. XPath information

XPath addresses
`/​co:OrderChange/​cbc:LineExtensionTotalAmount/​@amountCurrencyID`
`/​co:OrderChange/​cbc:LineExtensionTotalAmount`

Two data fields populate this one form field: the currency and the total amount.