Name
|
Type
|
Description
|
ActualDeliveryDateTime
|
DateTimeAny
|
The actual delivery date reported by?
|
Attachments
|
reference
|
|
Authorization
|
AuthorizationId
|
Represents a list of codes that specify status values for the acknowledgment.
Valid codes are:
- Purchase Release
- Manufacturing Release
- Shipment Release
|
Commodity
|
Commodity
|
Are codes that identify user-defined groupings of items.
|
DeliveredQuantity
|
Quantity
|
Indicates the quantity delivered.
A decimal value.
|
Description
|
Description
|
Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description..
|
DocumentReferences
|
reference
|
|
EffectivePeriod
|
TimePeriodAny
|
The effective dates for the schedule represents the schedule horizon dates and times . This is derived based on demand contained within the schedule if not specified. This can be a date or a time depending on the granularity of the manufacturing process.
|
EngineeringChangeDateTime
|
DateTimeAny
|
identifies the date on which engineering changes to the item or product is effective.
|
HazardousMaterial
|
reference
|
Provides the Hazardous Material Code and description.
|
Item
|
reference
|
|
ItemQuantity
|
Quantity
|
The customer’s actual requested amount of the item to be shipped.
A decimal value.
|
Kanban
|
Kanban
|
Indicates the reference number associated with in-plant routing information. Typically routing information specified on customer’s Kanban ship label includes and could be specified in the user area:
facility/dock
location build area
part description
first delivery location
empty container location
beginning kanban serial
ending kanban serial
pickup date/time
· delivery date/time
Is the reference number associated with in-plant routing information.
|
LineType
|
Type
|
Indicates the type of demand requested. Examples of values for this field include:
- Forecast
- Firm
- Authorization
- Past Due
- Shipment/Receipt
- Other
|
LoadingDock
|
LoadingDockCode
|
Itentifies the loading dock.
|
Note
|
reference
|
A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified.
|
Packing
|
Packaging
|
Represents the secondary packing code used to further identify the package of the product. Hmmm, where is the primary packing code?
Identifies the Packaging information for a given item.
Note: The UPC here is the UPC of the packaging for a given item.
|
PackingDescription
|
Description
|
Contains information about the packing material, such as dimensions and description. Examples include Bubble pack and Styrofoam peanuts
Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description..
|
Parties
|
reference
|
|
Priority
|
xs:string
|
Priority of a document, task, or activity. Could be used for production orders, sales orders, purchase orders, etc.
When used within the context of Schedules, priorities specify the urgency of the demand schedule, the higher the number the lower the priority.
Examples of values for this field include:
1, 2, 3
or
Highest Priority, Lower, Least.
|
PriorQuantity
|
Quantity
|
Indicates the quantity recieved.
A decimal value.
|
Project
|
Project
|
Identifies a set of tasks with the following attributes: a singular purpose, a start and end date, those that accumulate costs, and those that may have materials and overhead.
A set of tasks with the following attributes: a singular purpose, a start and end date, those that accumulate costs, and those that may have materials and overhead. SYNONYMS: Job, Process Model, Program, Work Breakdown Structure (WBS) element
|
ReceivedDateTime
|
DateTimeAny
|
The recieved date reported by?
|
ReceivedQuantity
|
Quantity
|
Indicates the quantity recieved.
A decimal value.
|
RespondingScheduleReference
|
DocumentReference
|
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.
Identifies another document within the scope of the OAGIS specification, such as a PurchaseOrder or Invoice that maybe associated with a particular Business Object Document.
|
ShipmentDateTime
|
DateTimeAny
|
Indicates the date and time an item was shipped.
|
ShippedQuantity
|
Quantity
|
Indicates the quantity recieved.
A decimal value.
|
ShipperNumber
|
Id
|
Generic identifier type with open qualifyingAgency.
|
Task
|
Task
|
|