Documentation for Open Applications Group (OAGIS)
Definition Type: Element
Name: RespondingScheduleReference
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:DocumentReferenceType
Containing Schema: ManufacturingComponents.xsd
Abstract
Documentation:
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.
Collapse XSD Schema Diagram:
Drilldown into UserArea in schema fields_xsd Drilldown into RequestedQuantity in schema fields_xsd Drilldown into ShippingTrackingID in schema fields_xsd Drilldown into FreightItemID in schema fields_xsd Drilldown into Type in schema fields_xsd Drilldown into SealID in schema fields_xsd Drilldown into ID in schema fields_xsd Drilldown into Item in schema components_xsd Drilldown into EffectiveTimePeriod in schema components_xsd Drilldown into ShipUnitReference in schema components_xsd Drilldown into SubLineNumber in schema fields_xsd Drilldown into ScheduleLineNumber in schema fields_xsd Drilldown into ReleaseNumber in schema fields_xsd Drilldown into OperationReference in schema components_xsd Drilldown into IssuingParty in schema components_xsd Drilldown into StepType in schema fields_xsd Drilldown into StepID in schema fields_xsd Drilldown into SequenceCode in schema fields_xsd Drilldown into GroupName in schema fields_xsd Drilldown into PurchaseOrderReference in schema components_xsd Drilldown into SalesOrderReference in schema components_xsd Drilldown into SerializedLot in schema components_xsd Drilldown into Facility in schema components_xsd Drilldown into ItemIDs in schema components_xsd Drilldown into LineNumber in schema fields_xsd Drilldown into Status in schema components_xsd Drilldown into StatusCode in schema fields_xsd Drilldown into Note in schema fields_xsd Drilldown into Description in schema fields_xsd Drilldown into FreeFormTextGroup in schema meta_xsd Drilldown into DocumentDateTime in schema fields_xsd Drilldown into AlternateDocumentID in schema components_xsd Drilldown into DocumentID in schema components_xsd Drilldown into DocumentIDsGroup in schema components_xsd Drilldown into DocumentReferenceBaseType in schema components_xsd Drilldown into type in schema components_xsd Drilldown into DocumentReferenceType in schema components_xsdXSD Diagram of RespondingScheduleReference in schema manufacturingcomponents_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code: 
<xsd:element name="RespondingScheduleReference" type="DocumentReferenceType">
    <xsd:annotation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">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.</xsd:documentation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">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.
</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
DocumentID nsA:DocumentID 0 (1)
AlternateDocumentID nsA:AlternateDocumentID 0 unbounded
DocumentDateTime nsA:DocumentDateTime 0 (1)
Description nsA:Description 0 unbounded
Note nsA:Note 0 unbounded
StatusCode nsA:StatusCode 0 (1)
Status nsA:Status 0 unbounded
LineNumber nsA:LineNumber 0 (1)
ItemIDs nsA:ItemIDs 0 (1)
Facility nsA:Facility 0 unbounded
SerializedLot nsA:SerializedLot 0 unbounded
SalesOrderReference nsA:SalesOrderReference 0 unbounded
PurchaseOrderReference nsA:PurchaseOrderReference 0 unbounded
GroupName nsA:GroupName 0 unbounded
SequenceCode nsA:SequenceCode 0 (1)
StepID nsA:StepID 0 (1)
StepType nsA:StepType 0 (1)
IssuingParty nsA:IssuingParty 0 (1)
OperationReference nsA:OperationReference 0 unbounded
ReleaseNumber nsA:ReleaseNumber 0 (1)
ScheduleLineNumber nsA:ScheduleLineNumber 0 (1)
SubLineNumber nsA:SubLineNumber 0 (1)
ShipUnitReference nsA:ShipUnitReference 0 (1)
EffectiveTimePeriod nsA:EffectiveTimePeriod 0 (1)
Item nsA:Item 0 (1)
ID nsA:ID 0 (1)
SealID nsA:SealID 0 (1)
Type nsA:Type 0 (1)
FreightItemID nsA:FreightItemID 0 (1)
ShippingTrackingID nsA:ShippingTrackingID 0 (1)
RequestedQuantity nsA:RequestedQuantity 0 (1)
UserArea nsA:UserArea 0 (1)
<xs:group> nsA:DocumentIDsGroup 0 (1)
<xs:group> nsA:FreeFormTextGroup 0 (1)
Collapse Child Attributes:
Name Type Default Value Use
type nsA:type (Optional)
Collapse Derivation Tree:
Documentation for Open Applications Group (OAGIS)

Generated using Liquid Studio - Developer Bundle 21.0.0.0