CatalogHeaderBaseType

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 

Complex type information

Content

• Sequence [1..1]
  from type DocumentIdentificationBaseType
  ID [0..1]    Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier.
  RevisionID [0..1]    Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity.
  VariationID [0..1]    
  DocumentIDSet [0..*]    
  from type HeaderBaseType
  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.
  from group FreeFormTextGroup
  Description [0..*]    
  Note [0..*]    
  from group ReferencesGroup
  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.
  1. Name [0..*]    Identifies the Name of the object in which associated.
  2. CurrencyCode [0..1]    Specifies the currency code of the object in which it is associated.
  3. EffectiveTimePeriod [0..1]    A time period in which an associated object is effective.
  4. 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
  5. 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.
  6. PublisherParty [0..1]    Identifies the publisher organization/entity of the Catalog or transaction in which it is associated for the associated.
  7. 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.
  8. 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.

Attributes

None

Used by

• Element CatalogHeader via derived type CatalogHeaderType

Type inheritance chain

• DocumentIdentificationBaseType
  • HeaderBaseType
    • CatalogHeaderBaseType
      • extended by CatalogHeaderType