InventoryConsumptionHeaderBaseType

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. TransactionDateTime [0..1]    The datetime of occurence of the transaction
  2. Facility [0..1]    A Facility identifies a location within an entity. The facility may have sub-locators identified using a sequenced identification notation e.g. Warehouse A100 Sub-Location 11, Row R10 would be represented as an array of three Facility elements with values as A100, 11, R10, name attribute as Warehouse, Sub-Location and Row and sequence attribute as 1,2 and 3 respectively.
  3. ShipToParty [0..1]    Identifies the ShipToParty for the document or the line. In a lot of cases, this is the same as the CustomerParty. In multi-organization purchasing, the CustomerParty may be different from the BuyerParty
  4. WarehouseParty [0..1]    
  5. SupplierParty [0..1]    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.
  6. CarrierParty [0..1]    Identifies the party that serves as the carrier of the goods or services for the transaction.
  7. 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.
  8. SupplierContractReference [0..1]    Is the reference to the supplier contract.
  9. BuyerContractReference [0..1]    Is the reference to the buyer contract.

Attributes

None

Used by

• Element InventoryConsumptionHeader via derived type InventoryConsumptionHeaderType

Type inheritance chain

• DocumentIdentificationBaseType
  • HeaderBaseType
    • InventoryConsumptionHeaderBaseType
      • extended by InventoryConsumptionHeaderType