<?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
10 Apr 2008    JB      Added correct Copyright and update comments to schema.
 
        *****     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/PlanningSchedule.xsd"/>
        
        <xsd:element name="GetPlanningSchedule" type="GetPlanningScheduleType">
                
                <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 Data Type PlanningScheduleException.

The purpose of the GetPlanningSchedule is to enable a business applications module to request this Planning Schedule information from another business application. The response to this BOD is ShowPlanningSchedule.
</xsd:documentation>
                
                </xsd:annotation>
        
        </xsd:element>
        
        <xsd:complexType name="GetPlanningScheduleType">
                
                <xsd:complexContent>
                        
                        <xsd:extension base="BusinessObjectDocumentType">
                                
                                <xsd:sequence>
                                        
                                        <xsd:element name="DataArea" type="GetPlanningScheduleDataAreaType">
                                                
                                                <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 GetPlanningSchedule. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (PlanningSchedule).</xsd:documentation>
                                                
                                                </xsd:annotation>
                                        
                                        </xsd:element>
                                
                                </xsd:sequence>
                        
                        </xsd:extension>
                
                </xsd:complexContent>
        
        </xsd:complexType>
        
        <xsd:complexType name="GetPlanningScheduleDataAreaType">
                
                <xsd:sequence>
                        
                        <xsd:element ref="Get"/>
                        
                        <xsd:element ref="PlanningSchedule" maxOccurs="unbounded"/>
                
                </xsd:sequence>
        
        </xsd:complexType>

</xsd:schema>
