<!--

** 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\GetListSalesOrder.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/SalesOrder.xsd"/>
        <xsd:element name="GetListSalesOrder" type="GetListSalesOrderType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">In an effort to simpilify the usage of the verbs the GetListSalesOrder BOD is being depricated as of OAGIS 9.0, the GetListSalesOrder 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 GetSalesOrder BOD which may serve the same function of the GetListSalesOrder BOD.

The purpose of the GetList SalesOrder is to enable a business application module to request information containing summary information for one or more SalesOrder from another business application.

The response to this request is the List SalesOrder.

The GetList SalesOrder also enables the retrieval of information across several documents by using selection fields.  An example of this could be requesting all SalesOrder Lines for a specific ITEM.  This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. 

This BOD does not usually cause updates to occur.  It may be used as part of a large integration scenario or as a single tool for requesting information on existing demands for goods or services.

For example, a Sales Automation application may use this BOD to ask for information from a Customer Order application.
</xsd:documentation>
                </xsd:annotation>
        </xsd:element>
        <xsd:complexType name="GetListSalesOrderType">
                <xsd:complexContent>
                        <xsd:extension base="BusinessObjectDocumentType">
                                <xsd:sequence>
                                        <xsd:element name="DataArea" type="GetListSalesOrderDataAreaType">
                                                <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 GetListSalesOrder. The information consists of a Verb and one or more Nouns. The verb (GetList) indicates the action to be performed on the Noun (SalesOrder).</xsd:documentation>
                                                </xsd:annotation>
                                        </xsd:element>
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
        <xsd:complexType name="GetListSalesOrderDataAreaType">
                <xsd:sequence>
                        <xsd:element ref="GetList"/>
                        <xsd:element ref="SalesOrder" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

• GetListSalesOrderDataAreaType
• GetListSalesOrderType

• GetListSalesOrder