BOD: Get Catalog
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.
Child Components
Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
Get 1..1
Catalog 1..∞
Scenarios in which Get Catalog is used
Feedback
OAGi and its members welcome your feedback.
UUID: f5d4a05a5ffa46e38bcfd64d34faaf56
OAGIS Version 10.12