UBL-Name |
Name |
Usage |
Cardinality |
Reference to the printed documentation |
See also |
UBLExtensions |
UBLExtensions |
Bilateral |
0..1 |
|
OIOUBL_GUIDE_EXTENSION
|
Alternative term |
OIOUBL_GUIDE_EXTENSION |
Definition |
UBLExtensions are used to make extensions to the OIOUBL document. The extensions can be agreed by 2 or more parties and must be registered by IT- og Telestyrelsen. If the class is used it must contain a minimum of one UBLExtension. The content of UBLExtension will be ignored by validators supporting W3C XMLSchema. |
Datatype |
UBLExtensions
|
|
ValidityPeriod |
ValidityPeriod |
Yes |
0..1 |
|
OIOUBL_GUIDE_CATALOGUE_ID
|
Alternative term |
OIOUBL_GUIDE_CATALOGUE_ID |
Definition |
The period assigned by the Seller during which the information in the Catalogue Revision is effective. This may be given as start and end dates or a duration. |
Datatype |
Period
|
Businessrules |
Note that the ValidityPeriod specified on headerlevel of the CatalogueItemSpecificationUpdate will change the ValidityPeriod for the whole Catalogue. |
|
RelatedCatalogueReference |
RelatedCatalogueReference |
Yes |
1 |
3.2 |
|
Definition |
An association to the Catalogue containing the revised Items. |
Datatype |
CatalogueReference
|
|
ReferencedContract |
ReferencedContract |
Yes |
0..1 |
3.3 |
|
Definition |
An association to a framework agreement or contract. |
Datatype |
Contract
|
|
Signature |
Signature |
Yes |
0..n |
|
|
Definition |
One or more signatures applied to the document. |
Datatype |
Signature
|
|
ProviderParty |
ProviderParty |
Yes |
1 |
3.4 |
OIOUBL_GUIDE_CATALOGUE_PARTIES
|
Alternative term |
OIOUBL_GUIDE_CATALOGUE_PARTIES |
Definition |
An association to the Catalogue Provider Party. |
Datatype |
Party
|
Businessrules |
The Provider can be a supplier or a third party catalogue administrator |
|
ReceiverParty |
ReceiverParty |
Yes |
1 |
3.5 |
OIOUBL_GUIDE_CATALOGUE_PARTIES
|
Alternative term |
OIOUBL_GUIDE_CATALOGUE_PARTIES |
Definition |
An association to the Catalogue Receiver Party. |
Datatype |
Party
|
Businessrules |
The Receiver can be a buyer or a third party catalogue administrator e.g. a marketplace or a portal |
|
SellerSupplierParty |
SellerSupplierParty |
Yes |
1 |
Common Library, 3.100 |
OIOUBL_GUIDE_CATALOGUE_PARTIES
|
Alternative term |
OIOUBL_GUIDE_CATALOGUE_PARTIES |
Definition |
The Seller Party responsible for the contract to which the Catalogue relates. |
Datatype |
SupplierParty
|
Businessrules |
Is default value for CatalogueLine if the party is not specified on the line. Note that a SellerSupplierParty on the line overrules the SellerSupplierParty on the header |
|
ContractorCustomerParty |
ContractorCustomerParty |
Yes |
0..1 |
Common Library, 3.27 |
OIOUBL_GUIDE_CATALOGUE_PARTIES
|
Alternative term |
OIOUBL_GUIDE_CATALOGUE_PARTIES |
Definition |
The Customer Party responsible for the contract to which the Catalogue relates. |
Datatype |
CustomerParty
|
Businessrules |
Only used when different from ReceiverParty. Is default value for CatalogueLine if the party is not specified on the line. |
|
TradingTerms |
TradingTerms |
Yes |
0..1 |
|
|
Definition |
An association to trading terms. |
Datatype |
TradingTerms
|
Businessrules |
Note that the TradingTerms specified on headerlevel of the CatalogueItemSpecificationUpdate will change the TradingTerms for the whole Catalogue. Are the TradingTerms not specified here or in a contract, the TradingTerms on the Order are applicable. |
|
DefaultLanguage |
DefaultLanguage |
Yes |
0..1 |
|
|
Definition |
The default language for the item specifications. |
Datatype |
Language
|
|
CatalogueItemSpecificationUpdateLine |
CatalogueItemSpecificationUpdateLine |
Yes |
1..n |
3.6 |
|
|