Documentation for Open Applications Group (OAGIS)
Definition Type: Element
Name: GetCatalog
Namespace: http://www.openapplications.org/oagis/9
Type: nsA:GetCatalogType
Containing Schema: GetCatalog.xsd
Abstract
Documentation:
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.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema getcatalog_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 GetCatalogType in schema getcatalog_xsdXSD Diagram of GetCatalog in schema getcatalog_xsd (Open Applications Group (OAGIS))
Collapse XSD Schema Code: 
<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>
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