<!--

** OAGIS® Revision: 9.0 **
** Date: 08 April 2005 **
** Copyright 1998-2005, All Rights Reserved **

This is an OAGIS® BOD XML Schema (XSD) Definition.

License information for this file is provided in the file **2005 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 
     
    Name: \OAGIS\9.0\BODs\Developer\ListPurchaseOrder.xsd
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.openapplications.org/oagis/9" targetNamespace="http://www.openapplications.org/oagis/9" elementFormDefault="qualified" attributeFormDefault="unqualified">
        <xsd:include schemaLocation="../../Resources/Nouns/PurchaseOrder.xsd"/>
        <xsd:element name="ListPurchaseOrder" type="ListPurchaseOrderType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">In an effort to simpilify the usage of the verbs the ListPurchaseOrder BOD is being depricated as of OAGIS 9.0, the ListPurchaseOrder will still be provided for the next three releases at which time it is scheduled to be removed from OAGIS.  As such for all new development we recommend that you use the ShowPurchaseOrder BOD which may serve the same function of the ListPurchaseOrder BOD.

The purpose of the List PurchaseOrder is to send information relative to demand for goods or services to another business application.  This may be in response to a GetList PurchaseOrder request, or it may be a notification vehicle, initiated upon an event in a business application.

The List verb describes the behavior of supplying one or several documents in a summary format to the requesting business application.  These listings of information may be supplied for Purchase Orders, PO Lines, or PO Sub-Lines.

This BOD usually does not cause updates to occur and may be used as part of a larger integration scenario or as a single tool for communicating demand. There are many possible business applications in several environments that may use this capability.

For example:

1. A PO application could use this BOD to send information to a Plant Data Collection application.

3. A MRP, Inventory or Manufacturing business application could use this to obtain order information.

</xsd:documentation>
                </xsd:annotation>
        </xsd:element>
        <xsd:complexType name="ListPurchaseOrderType">
                <xsd:complexContent>
                        <xsd:extension base="BusinessObjectDocumentType">
                                <xsd:sequence>
                                        <xsd:element name="DataArea" type="ListPurchaseOrderDataAreaType">
                                                <xsd:annotation>
                                                        <xsd:documentation source="http://www.openapplications.org/oagis/9">Is where the information that the BOD message carries is provided, in this case ListPurchaseOrder. The information consists of a Verb and one or more Nouns. The verb (List) 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="ListPurchaseOrderDataAreaType">
                <xsd:sequence>
                        <xsd:element ref="List"/>
                        <xsd:element ref="PurchaseOrder" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

• ListPurchaseOrderDataAreaType
• ListPurchaseOrderType

• ListPurchaseOrder