Documentation for Open Applications Group (OAGIS)
Definition Type: Element
Name: GetListSalesOrder
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:GetListSalesOrderType
Containing Schema: GetListSalesOrder.xsd
Abstract
Documentation:
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.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema getlistsalesorder_xsd Drilldown into ApplicationArea in schema meta_xsd Drilldown into languageCode in schema meta_xsd Drilldown into systemEnvironmentCode in schema meta_xsd Drilldown into versionID in schema meta_xsd Drilldown into releaseID in schema meta_xsd Drilldown into BusinessObjectDocumentType in schema meta_xsd Drilldown into GetListSalesOrderType in schema getlistsalesorder_xsdXSD Diagram of GetListSalesOrder in schema getlistsalesorder_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code: 
<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>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
ApplicationArea nsA:ApplicationArea (1) (1)
DataArea nsA:DataArea (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
releaseID nsA:releaseID Required
versionID nsA:versionID Optional
systemEnvironmentCode nsA:systemEnvironmentCode Production Optional
languageCode nsA:languageCode en-US Optional
Collapse Derivation Tree:
Documentation for Open Applications Group (OAGIS)

Generated using Liquid Studio - Developer Bundle 21.0.0.0