RFQScheduleType

The Quantity on the Schedule Line Indicates the number of items that are to be deliveried on the Required Date or the number of items to be delivered on each occurance of the Schedule period frequency or the number of items to be delivered on each delivery where the number of deliveries is provided by the NumberOfDeliveries field below.

See http://www.openapplications.org/oagis/9.

Complex type information

Content

• Sequence [1..1]
  from type LineType
  LineNumber [0..1]    Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system.
  from group FreeFormTextGroup
  Sequence [0..1]
  1. Description [0..*]    
  2. Note [0..*]    
  from group ReferencesGroup
  Sequence [0..1]
  1. DocumentReference [0..*]    
  2. 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 ProcurementScheduleType
  Quantity [0..1]    Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated.
  Choice [1..1]
  • RequiredDeliveryDateTime [0..1]    Indicates the date in which the buyer/customer requests the order to be delivered.
  • ScheduleTimePeriod [0..1]    Indicates the time period in which the Quote Line is effective.
  NumberOfDeliveries [0..1]    Is the number of deliveries for the quantity on Schedule.
  ShipmentQuantityTolerence [0..1]    Depricated in favor of correct spelling.
  ShipmentQuantityTolerance [0..1]    
  ShipmemtTimeTolerance [0..1]    Depricate in favor of the correct spelling.
  ReasonCode [0..1]    Identifies the reason for an activity
  1. 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.

Attributes

None

Used by

• Element RFQSchedule

Type inheritance chain

• LineType
  • ProcurementScheduleType
    • RFQScheduleType