<?xml version="1.0" encoding="utf-8"?>
<!--
        
        ** OAGIS® Revision: 9.1  **
        ** Date: 11 May 2007 **
        ** Copyright 1997-2007, All Rights Reserved **
        
        This is an OAGIS® BOD XML Schema (XSD) Definition.
        
       License information for this file is provided in the file **OAGi License Agreement.txt** that is provided with this download package.
        
        For support, more information, or to report implementation bugs, please contact the Open Applications Group at xml@openapplications.org.
        
        XML Schema 
        
-->
 
<!--
© Copyright 2007 Infor Global Solutions Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. The 
word and design marks set forth herein are trademarks and/or registered trademarks of Infor Global Solutions 
Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein 
are the property of their respective owners.
 
-->
 
<!--    *****     Update Log     *****
 
        Date          By      Note
        14 Jun 2011   NO      Initial version (JIRA BOD-1571).
 
        *****     Update End     *****
 
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schema.infor.com/InforOAGIS/2" targetNamespace="http://schema.infor.com/InforOAGIS/2" elementFormDefault="qualified" attributeFormDefault="unqualified">
        
        <xsd:include schemaLocation="../../Resources/Nouns/SupplierPlanningSchedule.xsd"/>
        
        <xsd:element name="SyncSupplierPlanningSchedule" type="SyncSupplierPlanningScheduleType">
                
                <xsd:annotation>
                        
                        <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">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 
                                SupplierPlanningScheduleException.  
                                
                                The purpose of the SyncSupplierPlanningSchedule 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 
                                SupplierPlanningSchedule.  
                                
                                SyncSupplierPlanningSchedule allows the adding of new requirements and the modification of previously 
                                established requirements.  Customers can use this SupplierPlanningSchedule 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>
        
        <xsd:complexType name="SyncSupplierPlanningScheduleType">
                
                <xsd:annotation>
                        
                        <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">Allows the adding of new requirements and the 
                                modification of previously established requirements through various Sync Indicator values. 
                                Customers can use SupplierPlanningSchedule 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 Data Type FeatureValueData.</xsd:documentation>
                
                </xsd:annotation>
                
                <xsd:complexContent>
                        
                        <xsd:extension base="BusinessObjectDocumentType">
                                
                                <xsd:sequence>
                                        
                                        <xsd:element name="DataArea" type="SyncSupplierPlanningScheduleDataAreaType">
                                                
                                                <xsd:annotation>
                                                        
                                                        <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">Is where the information 
                                                                that the BOD message carries is provided, in this case 
                                                                SyncSupplierPlanningSchedule. The information consists of a Verb and one or more 
                                                                Nouns. The verb (Sync) indicates the action to be performed on the Noun 
                                                                (SupplierPlanningSchedule).</xsd:documentation>
                                                
                                                </xsd:annotation>
                                        
                                        </xsd:element>
                                
                                </xsd:sequence>
                        
                        </xsd:extension>
                
                </xsd:complexContent>
        
        </xsd:complexType>
        
        <xsd:complexType name="SyncSupplierPlanningScheduleDataAreaType">
                
                <xsd:sequence>
                        
                        <xsd:element ref="Sync"/>
                        
                        <xsd:element ref="SupplierPlanningSchedule" maxOccurs="unbounded"/>
                
                </xsd:sequence>
        
        </xsd:complexType>

</xsd:schema>