<?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/PurchaseOrder.xsd"/>
        
        <xsd:element name="UpdatePurchaseOrder" type="UpdatePurchaseOrderType">
                
                <xsd:annotation>
                        
                        <xsd:documentation source="http://schema.infor.com/InforOAGIS/2">The purpose of the Update Purchaseorder is to request another business application to make Updates to an existing Purchase Order.  This Update must refer to the original document and/or item ordered.  The Update processing assumes replacement of fields sent, with the exception the identifying fields of the Purchase Order.

If any of these key fields require changing, (i.e. the PurchaseOrder Document Id or a LineNumber) that constitutes a cancellation of the request and/or the addition of another Purchase Order.
</xsd:documentation>
                
                </xsd:annotation>
        
        </xsd:element>
        
        <xsd:complexType name="UpdatePurchaseOrderType">
                
                <xsd:complexContent>
                        
                        <xsd:extension base="BusinessObjectDocumentType">
                                
                                <xsd:sequence>
                                        
                                        <xsd:element name="DataArea" type="UpdatePurchaseOrderDataAreaType">
                                                
                                                <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 UpdatePurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (PurchaseOrder).</xsd:documentation>
                                                
                                                </xsd:annotation>
                                        
                                        </xsd:element>
                                
                                </xsd:sequence>
                        
                        </xsd:extension>
                
                </xsd:complexContent>
        
        </xsd:complexType>
        
        <xsd:complexType name="UpdatePurchaseOrderDataAreaType">
                
                <xsd:sequence>
                        
                        <xsd:element ref="Update"/>
                        
                        <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
                
                </xsd:sequence>
        
        </xsd:complexType>

</xsd:schema>
