PlanningScheduleDetailType

Complex type information

Content

• Sequence [1..1]
  from type LineIdentificationBaseType
  LineNumberID [0..1]    Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system.
  LineIDSet [0..*]    
  from type LineBaseType
  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 PlanningScheduleDetailBaseType
  PriorityCode [0..1]    Indicates the priority or urgency of the associated entity.
  BucketTypeCode [0..1]    Identifies a bucket defined above for the type of buckets the plan has requested. Examples of values for this field include Days, Weeks (Starting Monday for 5 Days), Calendar Months, Lunar Months (Starting Jan 1st 28 Days per period, Balance on Last Period), Quarters (Starting Jan 1st. 3 Calendar Months Each.) or some other user defined and named value.
  AuthorizationID [0..1]    Identifyies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized be the receiving system indicates what can be done on the receiving system(s).
  EffectiveTimePeriod [0..1]    A time period in which an associated object is effective.
  ItemQuantity [0..1]    Is used to describe the quantity of item's, products or resources being budgeted, produced, purchased, received, sold, or used.
  MaximumQuantity [0..1]    The customer's actual requested amount of the item to be shipped.
  MinimumQuantity [0..1]    The customer's actual requested amount of the item to be shipped.
  LabourDuration [0..*]    Number of hours.
  LastShipmentDateTime [0..1]    Indicates the date and time an item was shipped. It is used to specify the last shipment date for the particular sequenced part.
  LastShipmentReceivedQuantity [0..1]    Indicates the actual amount shipped. It is used to specify the last quanity recieved for a particular sequenced part.
  RespondingScheduleReference [0..*]    Identifies the previously received plan schedule that this new schedule is responding to as a reference. The typical scenario is a supplier uses a Sync PlanningSchedule or Sync ShipmentSchedule to respond to a customer demand schedule, and this will identify the customer demand schedule that this supplier previously received. The date and time is also used in identifying the previously received plan schedule that the new plan schedule is responding to. Note that the combination of document id, document date, and revision number can uniquely identify a plan schedule.DateType indicates whether the dates specified on the schedule are delivery based or shipment based. Dates specified on the schedule include FromDateTime and ToDateTime at Header and Line levels. ScheduleType indicates whether the PlanningSchedule is a demand schedule from a customer or a supply schedule from a supplier. For the supplier schedule to respond to the original demand schedule, the RespondingScheduleReference is used to identify the customer's original demand schedule that it is responding to.
  ScheduleException [0..*]    Specifies exception detail for Detail or Line information.
  Status [0..*]    Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective.
  ItemQuantityBucket [0..*]    
  ProductTypeInventory [0..*]    Inventory by type of product in a planning schedule or forecast.
  FixedPlanningScheduleDetailIndicator [0..1]    An indicator specifying a fixed shipping schedule detail.
  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 PlanningScheduleDetail

Type inheritance chain

• LineIdentificationBaseType
  • LineBaseType
    • PlanningScheduleDetailBaseType
      • PlanningScheduleDetailType