RFQHeaderType

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 StatusHeaderBaseType
  Status [0..*]    Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective.
  from type RequestHeaderBaseType
  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.
  CustomerParty [0..1]    Is the organization that is the end customer of the goods or services being provided in the associated transaction.
  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.
  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
  PlannerContact [0..1]    Identifies the contact information of the person, organization, department, or group that planned for the timing of the exchange of goods/services that this document is associated at the document or line level.
  CatalogReference [0..1]    Is a reference to a catalog.
  ContractReference [0..1]    Is a reference to a contract
  ExtendedAmount [0..1]    Is an amount not including taxes or charges. In the case of orders, this is typically the Unit Price times the Order Quantity.
  TotalAmount [0..1]    Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes.
  AmountDiscount [0..1]    Specifies details for how an amount is calculated
  EnterpriseUnit [0..1]    Identifies the given portion of an organization. Some commonly defined Units are identified here. These units are typically used to track financial data in reporting systems within an organization. Similar to Business Units, Organizational Units are only relevant within an enterprise
  from type ProcurementHeaderBaseType
  BillToParty [0..1]    Identifies the party that the bill or invoice is to be sent. In most cases this is the same as the CustomerParty however there are many cases where the CustomerParty and the BillToParty will be different.
  CarrierParty [0..1]    Identifies the party that serves as the carrier of the goods or services for the transaction.
  PayFromParty [0..1]    Identifies the party that the payment for the goods or services will come.
  PartialShipmentAllowedIndicator [0..1]    Identifies if a partial shipment to a customer is allowed.
  DropShipmentAllowedIndicator [0..1]    Indicates whether the order can be drop shipped or not.
  EarlyShipmentAllowedIndicator [0..1]    Communicates if it is permitted to ship a good or service prior to the date it is due
  LicenseIndicator [0..*]    Indicates what type of licenses are required and indicates which are required.
  TaxExemptIndicator [0..1]    Specifies whether the associated element is exempt from withholding taxes.
  FulfillmentTerm [0..*]    
  TransportationTerm [0..*]    The terms of the transportation agreement.
  TransportStep [0..*]    
  PaymentTerm [0..*]    Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment.
  DistributeCharge [0..*]    Specifies the details for allocating a portion of a charge properly
  DistributeTax [0..*]    Specifies the details for allocating a portion of a tax properly
  Tax [0..*]    Specifies all the details needed for specific kinds of Taxes and Tax charges
  Distribution [0..*]    A distribution of the financial credit or debit of the transaction across an organization.
  Charge [0..*]    Specifies the details for Charges that may be applied to the associated transaction
  Allowance [0..*]    Specifies the discount or allowance that the Customer is to receive off of the TotalAmount owed as a result of the associated document or sub-portion of a document.
  from type RFQHeaderBaseType
  BuyerParty [0..1]    The entity that is responsible for Buying the document or element in which it is associated. Additionally, the contact may be a person or a group or department.
  RequesterParty [0..1]    The party that requested the associated entity.
  PriorityCode [0..1]    Indicates the priority or urgency of the associated entity.
  EffectiveTimePeriod [0..1]    A time period in which an associated object is effective.
  SupplierSelectionTimePeriod [0..1]    Is the TimePeriod that Supplier(s) will be selected
  BiddingTimePeriod [0..1]    Is the period in which bidding can occur.
  QualificationTerm [0..*]    This is used to describe preferences that will be used to evaluate responses to an RFQ. For example, to identify a preference for sharing CAD data in VRML format the ID = VRML, Type = CAD and Value = 1 or Yes
  Message [0..*]    
  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

None

Used by

• Element RFQHeader

Type inheritance chain

• DocumentIdentificationBaseType
  • HeaderBaseType
    • StatusHeaderBaseType
      • RequestHeaderBaseType
        • ProcurementHeaderBaseType
          • RFQHeaderBaseType
            • RFQHeaderType