Namespace
ubl urn:oasis:names:specification:ubl:schema:xsd:Catalogue-2
Child elements
Card Name Description
1..1 cbc:CustomizationID

Specification identification
Identifies the specification of content and rules that apply to the transaction.

Example value: urn:fdc:peppol.eu:poacc:trns:catalogue:3

1..1 cbc:ProfileID

Business process type identifier
Identifies the BII profile or business process context in which the transaction appears. Values to be used are either urn:fdc:peppol.eu:poacc:bis:catalogue_only:3 or urn:fdc:peppol.eu:poacc:bis:catalogue_wo_response:3

Example value: urn:fdc:peppol.eu:poacc:bis:catalogue_only:3

1..1 cbc:ID

Catalogue identifier
An catalogue instance must contain an identifier. The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.

Example value: Cat-02

0..1 cbc:ActionCode

Catalogue action code
Identifies how a received catalogue should be used against existing catalogue lines sent in previous catalogues, so that no discrepancies occur between the suppliers and customers information. Describes how to treat existing items, not part of the received catalogue and those that are included (unchanged, changed or deleted). Default action is to fully replace the source catalogue.

Example value: Add

0..1 cbc:Name

Catalogue name
A name of the catalogue for general reference. E.g. "Christmas catalogue"

Example value: Spring Catalogue

1..1 cbc:IssueDate

Catalogue issue date
The date on which the catalogue instance was issued. Format = "YYYY-MM-DD"

Example value: 2018-05-31

0..1 cbc:VersionID

Catalogue version
The version of the catalogue revision. The version ID is used to controll how a Catalogue transaction acts on existing lines that are not stated in the transactions. Should they be left alone or deleted. If Catalogue transaction is 'Replace' then action codes on the line have no relevance. All existing lines are deleted and the ones stated in the Catalogue transaction added. If Catalogue transaction is 'Update' then action codes on lines controll each line.

Example value: v2

1..1 cac:ValidityPeriod

Catalogue validity period
The period during which the content of the catalogue is valid and can be used for trade.

0..1 cac:ReferencedContract

Contract reference
The identification of a contract.

0..1 cac:SourceCatalogueReference

Source Catalogue reference
The identification of a source catalogue

1..1 cac:ProviderParty

Catalogue provider
The party that sends the catalogue. The seller or a catalogue repository.

1..1 cac:ReceiverParty

Catalogue receiver
The party to which the catalogue is sent. Buyer or a catalogue repository on his behalf.

0..1 cac:SellerSupplierParty

Catalogue supplier
The party that provides the items specified in the catalogue.

0..1 cac:ContractorCustomerParty

Catalogue customer
The party who may order from the catalogue.

0..n cac:TradingTerms

Trading terms

1..n cac:CatalogueLine

Catalogue line
Catalogue line content

Rules
Identifier/Error message Flag
PEPPOL-T19-B00101
Element 'cbc:CustomizationID' MUST be provided.
fatal
PEPPOL-T19-B00102
Element 'cbc:ProfileID' MUST be provided.
fatal
PEPPOL-T19-B00103
Element 'cbc:ID' MUST be provided.
fatal
PEPPOL-T19-B00104
Element 'cbc:IssueDate' MUST be provided.
fatal
PEPPOL-T19-B00105
Element 'cac:ValidityPeriod' MUST be provided.
fatal
PEPPOL-T19-B00106
Element 'cac:ProviderParty' MUST be provided.
fatal
PEPPOL-T19-B00107
Element 'cac:ReceiverParty' MUST be provided.
fatal
PEPPOL-T19-B00108
Element 'cac:CatalogueLine' MUST be provided.
fatal
PEPPOL-T19-B00109
Document MUST not contain schema location.
fatal
PEPPOL-T19-B00110
Document MUST NOT contain elements not part of the data model.
fatal