CatalogHeaderType
This identifies header information about the Catalog. This information applies to all the lines in the Catalog. PartyReferences in the Header are defaults that apply to all the Catalog lines, if there is no value specified at line level The SupplierParty in the Header identifies the provider of the item. Depending on the exchange scenario, the provider may be either a Supplier, Manufacturer or a Catalog Party. If no SupplierParty is specified at line level, the header value of the SupplierParty is assumed to hold true for the line
See http://www.openapplications.org/oagis/9.
Complex type information
Namespace: http://www.openapplications.org/oagis/9
Schema document: org_openapplications_oagis/9_4_1/Developer/Nouns/Catalog.xsd
Content
- Sequence
[1..1]
- Sequence
[0..1]
- DocumentID [0..1] Is the primary document id for the document associated.
- AlternateDocumentID [0..*] Is the alternate document id for the associated document.
- LastModificationDateTime [0..1] The datetime on which the object was last modified
- DocumentDateTime [0..1] The date that document was created within the system of record.
- Sequence
[0..1]
- Description [0..*]
- Note [0..*]
- Sequence
[0..1]
- DocumentReference [0..*]
- Attachment [0..*] The Attachment represents binary data files that may be included within a BOD. These files replace the paper specifications and drawings attached to a BOD definition to clearly communicate design requirements. This Data Type is optional. Attachment usage is further defined by its position.
- Name [0..*] Is the name of the Catalog.
- CurrencyCode [0..1] Is the default currency of the Catalog. If a Currencey is specified for the Catalog, all the prices in the Catalog are assumed to be in the corresponding currency.Is the default currency of the Catalog. If a Currencey is specified for the Catalog, all the prices in the Catalog are assumed to be in the corresponding currency.
- EffectiveTimePeriod [0..1] Is the effective period of the Catalog or Catalog revision. The EffectiveTimePeriod indicates the effectivity date and the expiration date for the validity of the Catalog. Often times the effectivity of a Catalog Revision is indicated by the release of a new revision of the Catalog. As such the Finish Effectivity date is never specified but assumed to be the Starting Effectivity date on the next revision
- UsageRestrictionCode [0..1] UsageRestriction is used to indicate additional restrictions on the Catalog usage. The implementation of this is to be agreed upon between trading partners. An example of usage of this is when a supplier has different Catalogs - one for general usage and others for usage by specific customers/ group of customers. In this scenario, the UsageRestriction can be specified as PUBLIC/ PRIVATE
- ClassificationScheme [0..1] Describes the classification scheme as a whole. A Catalog can have one ClassificationScheme associated with it. For example, a classification scheme for inventory management may classify items according to handling characteristics.
- PublisherParty [0..1] Identifies the publisher organization/entity of the Catalog or transaction in which it is associated for the associated.
- SupplierParty [0..*] Identifies the supplier organization/entity of the items or inventory for the associated transaction. In most cases there is one SupplierParty per transaction. i.e. one SupplierParty for a given PurchaseOrder. However in the cases where an transaction Broker is involved there are cases where a single transaction may have different SupplierParties at the line level or in the case of a Catalog for the Catalog.
- Party [0..*] A generic Party for non-validated or application-validated parties. A work-around for situations where Schema-validation of Parties is not feasible or not desired.
- UserArea [0..1] Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.
from type HeaderTypefrom group DocumentIDsGroupfrom group FreeFormTextGroupfrom group ReferencesGroup - Sequence
[0..1]
Attributes
None
Used by
- Element CatalogHeader
Type inheritance chain
- HeaderType
- CatalogHeaderType