Online OIOUBL Dokumentation


Reading guidelines

CommonLibrary

ApplicationResponse

Catalogue

CatalogueDeletion

CatalogueItemSpecificationUpdate

CataloguePricingUpdate

CatalogueRequest

Creditnote

Invoice

Order

Ordercancellation

OrderChange

OrdreResponse

OrdreResponseSimple

Reminder

Statement

Download all documents (PDF)

Download all documents (ODT)

Catalogue
Catalogue

Catalogue specification

Name Catalogue (Show as PDF) Alternative Term  
Definition OIOUBL-2.0 Catalogue is a document for the creation and maintenance of electronic catalogues. The document is used for the creation of new catalogues as well as for additions, updates or deletions of items in existing catalogues.

Five documents are used to implement and maintain catalogues. Catalogue can be used to create a new catalogue or update entire lines. A catalogue can be exchanged between a supplier and a customer, between a supplier and a third party, for example a purchase portal, between a third party and a customer or between two third parties. As a result it is possible to specify the identity of the customer and the supplier in both document and line level.

The Catalogue Request document is used to specify which types of catalogues the supplier requests, for example a new catalogue or an update, and also which products are requested. As described, the Catalogue document can be used for creating and adding, updating or deleting items in existing catalogues. the Catalogue Item Specification Update document can be used when only the item specification needs to be updated in an existing catalogue. The Catalogue Deletion document deletes an entire catalogue. Catalogue documents differs from other document types in that sender and receiver can be third parties. For example, the receiver can be an electronic marketplace in stead of the customer himself.

But the catalogue documents must also be viewed in relation to the entire purchasing process running from sourcing, ordering and invoicing to payment and the other OIOUBL 2.0 documents used for these purposes. Implementation of a catalogue can be the first step in the purchasing process followed by an order and an invoice.

The apparent advantages of the OIOUBL 2.0 documents is the standardization of business documents for different purposes. The UBL 2.0 standard is a flexible standard that supports most of the business needs. Because it also is an international standard the document can be used across national boundaries. The Danish version is named OIOUBL 2.0 and is designed to meet Danish needs and demands.

The advantage of OIOUBL-2.0 is the possibility of designing fully automated purchasing flows in which the electronic documents can be validated and matched automatically, thereby saving resources compared to manual processing.

Fields

UBL-Name Name Datatype Usage Cardinality
UBLVersionID UBLVersionID Identifier Yes 1
CustomizationID CustomizationID Identifier Yes 1
ProfileID ProfileID Identifier Yes 1
ID ID Identifier Yes 1
UUID UUID Identifier Yes 0..1
Name Name Name Yes 0..1
IssueDate IssueDate Date Yes 1
IssueTime IssueTime Time Bilateral 0..1
RevisionDate RevisionDate Date Yes 0..1
RevisionTime RevisionTime Time Bilateral 0..1
Note Note Text Yes 0..n
Description Description Text Yes 0..n
VersionID VersionID Identifier Yes 1
PreviousVersionID PreviousVersionID Identifier Yes 0..1

Subclasses in class Catalogue

UBL-Name Name Usage Cardinality Reference to the printed documentation See also
UBLExtensions UBLExtensions Bilateral 0..1   OIOUBL_GUIDE_EXTENSION
ValidityPeriod ValidityPeriod Yes 1 3.2 OIOUBL_GUIDE_CATALOGUE_ID
ReferencedContract ReferencedContract Yes 0..1 3.3  
Signature Signature Yes 0..n Common Library, 3.96  
ProviderParty ProviderParty Yes 1 3.4 OIOUBL_GUIDE_CATALOGUE_PARTIES
ReceiverParty ReceiverParty Yes 1 3.5 OIOUBL_GUIDE_CATALOGUE_PARTIES
SellerSupplierParty SellerSupplierParty Yes 1 Common Library, 3.100 OIOUBL_GUIDE_CATALOGUE_PARTIES
ContractorCustomerParty ContractorCustomerParty Yes 0..1 Common Library, 3.27 OIOUBL_GUIDE_CATALOGUE_PARTIES
TradingTerms TradingTerms Yes 0..n Common Library, 3.106  
CatalogueLine CatalogueLine Yes 1..n 3.6  

Excluded classes and fields in Catalogue

Name Name Type
LineCountNumeric LineCountNumeric Field

Example

<Catalogue >
<cbc:UBLVersionID>2.0</cbc:UBLVersionID>
<cbc:CustomizationID>OIOUBL-2.01</cbc:CustomizationID>
<cbc:ProfileID schemeDataURI="urn:oioubl:id:profileid-1.0">Catalogue-CatAdv-1.0</cbc:ProfileID>
<cbc:ID>CAT-EX-1</cbc:ID>
<cbc:UUID>9756b516-8815-1029-857a-e388fe63f399</cbc:UUID>
<cbc:Name>Mobile phone</cbc:Name>
<cbc:IssueDate>2006-04-30</cbc:IssueDate>
<cbc:IssueTime>12:00:00</cbc:IssueTime>
<cbc:RevisionDate>2006-03-10</cbc:RevisionDate>
<cbc:RevisionTime>09:30:47</cbc:RevisionTime>
<cbc:Note>Teleeksperten A/S will from mach 2006 introduce a new improved and even more comprehensive catalogue.</cbc:Note>
<cbc:Description>Teleekspertens sells alle the best-known models in mobile phone and accessories.</cbc:Description>
<cbc:VersionID>1.0</cbc:VersionID>
<cbc:PreviousVersionID />
+ <cac:ValidityPeriod />
+ <cac:ReferencedContract />
+ <cac:ProviderParty />
+ <cac:ReceiverParty />
+ <cac:ContractorCustomerParty />
+ <cac:TradingTerms />
+ <cac:CatalogueLine />
+ <cac:CatalogueLine />
+ <cac:CatalogueLine />
</Catalogue>