Documentation for Open Applications Group (OAGIS)
Definition Type: Element
Name: SyncPlanningSchedule
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:SyncPlanningScheduleType
Containing Schema: SyncPlanningSchedule.xsd
Abstract
Documentation:
Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party. Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional component PlanningScheduleException . The purpose of the SyncPlanningSchedule is to communicate requirement information (part number, quantity, etc.) between a customer and their supplier on a regular basis, for example daily, weekly etc, or for a user-defined time bucket type definition (Component FexibileBucket) that is sent as part of this PlanningSchedule. SyncPlanningSchedule allows the adding of new requirements and the modification of previously established requirements. Customers can use this PlanningSchedule to communicate demand requirement in three different ways. It can be as specific as the Item level or at the Commodity code level, which is higher than item. Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValue.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema syncplanningschedule_xsd Drilldown into ApplicationArea in schema meta_xsd Drilldown into languageCode in schema meta_xsd Drilldown into systemEnvironmentCode in schema meta_xsd Drilldown into versionID in schema meta_xsd Drilldown into releaseID in schema meta_xsd Drilldown into BusinessObjectDocumentType in schema meta_xsd Drilldown into SyncPlanningScheduleType in schema syncplanningschedule_xsdXSD Diagram of SyncPlanningSchedule in schema syncplanningschedule_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code: 
<xsd:element name="SyncPlanningSchedule" type="SyncPlanningScheduleType">
    <xsd:annotation>
        <xsd:documentation source="http://www.openapplications.org/oagis/9">Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party.  Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional component PlanningScheduleException
.
The purpose of the SyncPlanningSchedule is to communicate requirement information (part number, quantity, etc.) between a customer and their supplier on a regular basis, for example daily, weekly etc, or for a user-defined time bucket type definition (Component FexibileBucket) that is sent as part of this PlanningSchedule.  

SyncPlanningSchedule allows the adding of new requirements and the modification of previously established requirements.  

Customers can use this PlanningSchedule to communicate demand requirement in three different ways.  It can be as specific as the Item level or at the Commodity code level, which is higher than item.  Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValue.</xsd:documentation>
    </xsd:annotation>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
ApplicationArea nsA:ApplicationArea (1) (1)
DataArea nsA:DataArea (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
releaseID nsA:releaseID Required
versionID nsA:versionID Optional
systemEnvironmentCode nsA:systemEnvironmentCode Production Optional
languageCode nsA:languageCode en-US Optional
Collapse Derivation Tree:
Documentation for Open Applications Group (OAGIS)

Generated using Liquid Studio - Developer Bundle 21.0.0.0