<!--

** 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\GetCatalog.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/Catalog.xsd"/>
        <xsd:element name="GetCatalog" type="GetCatalogType">
                <xsd:annotation>
                        <xsd:documentation source="http://www.openapplications.org/oagis/9">The purpose of the GetCatalog is to enable a business application module or system to request catalog information.

The Catalog information that is requested by the GetCatalog may include
·  Item Identifiers
·  Specifications
·  Pricing Information agreed on either
  ·  Purchase Agreements
  ·  Price Lists
·  Availability and Delivery Information
·  Related Items and accessories

There are many possible business applications in several environments that may use this capability. Some examples of usage scenarios are:
·  Manufacturer exchanging catalogs with distributors/ suppliers/e-marketplaces
·  Distributors/ Suppliers/ e-marketplaces exchanging catalogs with Buyers or other trading partners

It may also be necessary to support Component Supplier Management (CSM) scenarios.  In this scenario a company will provide a service of sourcing and codifying the products of many companies and publishing a consolidated catalog. 

The Catalog exchange scenario can be implemented either as a simple scenario using a single BOD, or in the case or large catalogs involving complex pricing scenarios or partner specific details, as multiple BODs.</xsd:documentation>
                </xsd:annotation>
        </xsd:element>
        <xsd:complexType name="GetCatalogType">
                <xsd:complexContent>
                        <xsd:extension base="BusinessObjectDocumentType">
                                <xsd:sequence>
                                        <xsd:element name="DataArea" type="GetCatalogDataAreaType">
                                                <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 GetCatalog. The information consists of a Verb and one or more Nouns. The verb (Get) indicates the action to be performed on the Noun (Catalog).</xsd:documentation>
                                                </xsd:annotation>
                                        </xsd:element>
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
        <xsd:complexType name="GetCatalogDataAreaType">
                <xsd:sequence>
                        <xsd:element ref="Get"/>
                        <xsd:element ref="Catalog" maxOccurs="unbounded"/>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

• GetCatalogDataAreaType
• GetCatalogType

• GetCatalog