Name	Order (Show as PDF)	Alternative Term
Definition	OIOUBL Order is used for the exchange of electronic orders. The order can be used in a coherent order-to-invoice flow. Order is sent from BuyerCustomerParty to SellerSupplierParty. Order is structured to fulfill the formal requirements for a valid order change for use in Denmark, including taxnumber, time of delivery, specifications etc. Apart from the formal demands on sender and receiver and the order content, the electronic version must contain EndPointID, a Personreference and usually an order number or request number. It also has to fulfill the requirements in this document guideline. EndPointID is used to identify the "electronic mailbox" where the electronic document is to be delivered and also provides the basis for routing the message. PersonReference is used to identify the person responsible for placing the order. Order number or requisition number is used to identify the order. These three types of information are used subsequently when the electronic invoice is issued with reference to a previous order or requisition. Depending on the profile used, the order can form part of an advanced order flow allowing the exchange of order changes, order deletions and order responses.

Fields

UBL-Name

Name

Datatype

Usage

Cardinality

UBLVersionID

Identifier

Yes

CustomizationID

Identifier

Yes

ProfileID

Identifier

Yes

Identifier

Yes

CopyIndicator

Indicator

Yes

0..1

UUID

Identifier

Yes

0..1

IssueDate

Date

Yes

IssueTime

Time

Bilateral

0..1

Note

Text

Yes

0..n

RequestedInvoiceCurrencyCode

Code

Yes

0..1

DocumentCurrencyCode

Code

Yes

0..1

PricingCurrencyCode

Code

Yes

0..1

TaxCurrencyCode

Code

Yes

0..1

CustomerReference

Text

Bilateral

0..1

AccountingCostCode

Code

Bilateral

0..1

AccountingCost

Text

Yes

0..1

Subclasses in class Order

UBL-Name

Name

Usage

Cardinality

Reference to the printed documentation

Excluded classes and fields in Order

Name	Name	Type
SalesOrderID	SalesOrderID	Field
LineCountNumeric	LineCountNumeric	Field
OrderDocumentReference	OrderDocumentReference	Class

Example

<Order >
<cbc:UBLVersionID>2.0</cbc:UBLVersionID>
<cbc:CustomizationID>OIOUBL-2.01</cbc:CustomizationID>
<cbc:ProfileID schemeDataURI="urn:oioubl:id:profileid-1.0">Procurement-OrdSimR-BilSim-1.0</cbc:ProfileID>
<cbc:ID>5002701</cbc:ID>
<cbc:CopyIndicator>false</cbc:CopyIndicator>
<cbc:UUID>9756b468-8815-1029-857a-e388fe63f399</cbc:UUID>
<cbc:IssueDate>2005-11-01</cbc:IssueDate>
<cbc:Note>Note pÃ¥ ordreheader</cbc:Note>
<cbc:RequestedInvoiceCurrencyCode>DKK</cbc:RequestedInvoiceCurrencyCode>
<cbc:DocumentCurrencyCode>DKK</cbc:DocumentCurrencyCode>
<cbc:AccountingCost>5250124502</cbc:AccountingCost>
+ <cac:ValidityPeriod />
+ <cac:QuotationDocumentReference />
+ <cac:AdditionalDocumentReference />
+ <cac:Contract />
+ <cac:Signature />
+ <cac:BuyerCustomerParty />
+ <cac:SellerSupplierParty />
+ <cac:OriginatorCustomerParty />
+ <cac:AccountingCustomerParty />
+ <cac:Delivery />
+ <cac:DeliveryTerms />
+ <cac:AllowanceCharge />
+ <cac:TaxTotal />
+ <cac:AnticipatedMonetaryTotal />
+ <cac:OrderLine />
</Order>