InspectDeliveryType

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.
  from type InspectDeliveryBaseType
  RejectedQuantity [0..1]    Indicates the quantity rejected for the specified Reason
  AcceptedQuantity [0..1]    Indicates the quantity accepted.
  InspectedQuantity [0..1]    Number of inventory items that have been inspected.
  TotalQuantity [0..1]    Total number of associated entities.
  ReasonCode [0..1]    Identifies the reason for an activity
  PurchasingParty [0..1]    Identifies the party that purchased the goods or services.
  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.
  InspectorContact [0..1]    Identifies the contact information of the person, organization, department, or group that is to or has inspected the contents communicated by the document or line.
  InspectDeliveryReference [0..*]    
  PurchaseOrderReference [0..*]    Is a reference to a PurchaseOrder
  DeliveryReference [0..*]    Is a reference to the Delivery document.
  RejectionDetails [0..*]    This describes the reasons for rejecting or accepting the corresponding quantity
  Effectivity [0..*]    Specifies effectivity of an associated object. Effectivity is expressed may be expressed as: multiple ranges, values, time period or as associated to a specific Item.
  1. Extension [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 Extension is always the last element in all components, except where the component has been extended inline.

Attributes

Used by

• Element InspectDelivery

Type inheritance chain

• DocumentIdentificationBaseType
  • HeaderBaseType
    • InspectDeliveryBaseType
      • InspectDeliveryType