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

UBL VersionID
Identifies the UBL version on which the transaction instance is based.

Fixed value: 2.1

1..1 cbc:CustomizationID

Customization identifier
Identifies the specification of content and rules that apply to the transaction.

Example value: urn:www.cenbii.eu:transaction:biitrns19:ver2.0:#urn:www.difi.no:ehf:katalog:ver0.99

1..1 cbc:ProfileID

Profile identifier
Identifies the BII profile or business process context in which the transaction appears.

Example value: urn:www.cenbii.eu:profile:bii01:ver2.0

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. Legal values: Add, Update, Delete, Replace Add = New catalogue with all catalogue lines shall be established. If the catalogue allready exists, it must be rejected by the recipients system. Update=Update lines of an existing catalogue. Replace = Replacing the entire catalogue. Delete = Delete the entire 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: 2013-04-01

0..1 cbc:VersionID

Catalogue version
The version of the catalogue revision. The version ID is used to control 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 control each line.

Example value: v2

1..1 cac:ValidityPeriod

Validity period

0..1 cac:ReferencedContract

Contract

0..1 cac:SourceCatalogueReference

Source catalogue reference

1..1 cac:ProviderParty

Provider party

1..1 cac:ReceiverParty

Receiver party

0..1 cac:SellerSupplierParty

Supplier

0..1 cac:ContractorCustomerParty

Supplier

0..n cbc:TradingTermsType

Trading terms

1..n cac:CatalogueLine

Catalogue line

Rules
Identifier/Error message Flag
EHF-T19-B00101
Element 'cbc:UBLVersionID' MUST be provided.
warning
EHF-T19-B00102
Element 'cbc:CustomizationID' MUST be provided.
warning
EHF-T19-B00103
Element 'cbc:ProfileID' MUST be provided.
warning
EHF-T19-B00104
Element 'cbc:ID' MUST be provided.
warning
EHF-T19-B00105
Element 'cbc:IssueDate' MUST be provided.
warning
EHF-T19-B00106
Element 'cac:ValidityPeriod' MUST be provided.
warning
EHF-T19-B00107
Element 'cac:ProviderParty' MUST be provided.
warning
EHF-T19-B00108
Element 'cac:ReceiverParty' MUST be provided.
warning
EHF-T19-B00109
Element 'cac:CatalogueLine' MUST be provided.
warning