Attribute Data-Model and important tables with queries.

Attribute Data-Model

--Information related to ATTR_ID & IDENTIFIER based on this we will get the ATTR_ID with which we will be proceeding further for the next table.

select * from attr;

-- Information related to ATTRVAL_ID & ATTR_ID & IDENTIFIER based on the previous step we will be getting the ATTRVAL_ID with which we further proceed to get the catentries related to the particular value.

select * from attrval where attr_id=7000000000000009685;

-- Information related to ATTRVAL_ID  & ATTR_ID & CATENTRY_ID based on the previous step we will get the catEntries which are associated to a particular ATTR_ID

(Stores the catalog entry (CATENTRY) and attribute dictionary attribute (ATTR) relationship)

select * from catentryattr where attrval_id=7000000000000021190 and attr_id =7000000000000009685;

Attribute data model

Attribute Data Model-tables

Important Commands & DataBeans present in Catalog Subsystem

Commands--
StoreCatalogDisplayCmdImpl-
This command sets the view task that will display the Catalogs available to browse in the current Store.

TopCategoriesDisplayImpl-
This command sets the view task that will display the root Categories in a specified Catalog.

CategoryDisplayCmdImpl-
retrieves the configured display page for the specified category in the specified catalog.

ErrorMissingAttributeCmd-
This error task command is set when a Product to Item resolution fails due to missing product attributes.

ErrorProductAttributeCmd-
This error task command is set when a Product to Item resolution fails due to incorrect product attributes

ProductDisplayCmdImpl-
This command retrieves the configured Display Page for the specified CatalogEntry which will in turn be launched in order to
display information about the CatalogEntry.This command first ensures that the CatalogEntry specified by the
ProductId can be displayed in the current store, if published, and is not marked for delete.

ResolveSkuCmd-Certain catalog entries may need further processing before being added to an order.
An example is resolving a product into an item through SKU resolution, performed by the ResolveSkuCmd task command.


DataBeans--
StoreDataBean--extends StoreAccessBean ->salesCatalogs()
CatalogDataBean-extends CachedCatalogAccessBean ->getTopCategories()
CategoryDataBean-extends CachedCatalogAccessBean ->getSubCategories()
CatalogEntryDataBean-extends CachedCatalogEntryAccessBean
ProductDataBean-extends CachedProductAccessBean

Important Tables & URLS present in Catalog Subsystem

Tables
STORECAT -store to catalog
CATTOGRP -catalog to group
CATGRPREL -group to group
CATGPENREL -group to parent
CATENTREL -group to praent
CATENTREL -parent to item

URLS---
StoreCatalogDisplay
TopCategoriesDisplay
CategoryDisplay
ProductDisplay

Detailed Description of Catalog Subsystem

CatalogSubsystem

The catalog subsystem is a component of theWebSphere Commerce Server that provides online catalog navigation,partitioning, categorization, and associations. The catalog subsystem containsall logic and data relevant to an online catalog, including catalog groups (orcategories), catalog entries, and any associations or relationships among them.

Catalogentries classification:

· Products.

· Items.

· Packages.

· Bundles.

· Dynamic or static kit.

PRODUCT and ITEM:
An item is a tangible unit of merchandise that has a specific name, partnumber, and price. For example, a 15 inch hammer with a wooden handle (partnumber 15) is an item.
A product, however, is a group of items that exhibit the same attributes.For example, a hammer is a product, while the 15 inch hammer with a woodenhandle is an item. The attributes of this product are "handle type"and "size," which are defined by the corresponding attribute values, wooden and 15 inch.
To distinguish products and items, keep in mind that a product cannot bepurchased, while an item can potentially be purchased.

PACKAGEand BUNDLE:

Packages and bundlesare groupings of catalog entries used for promotional purposes.

A bundle is acollection of catalog entries that allow customers to buy multiple items withone click. A bundle can be agrouping of items, or a combination of products, items, and fully resolvedpackages. The bundle is decomposed into separate orderableSKUs that are added individually to the shopping cart.

Unlike bundles, apackage is an atomic collection of catalog entries. Viewed in similar ways as aproduct, you cannot decompose ormodify a package during navigation or after the package has been placed in theshopping cart. For example, a computer package might contain a specific centralprocessing unit, monitor, and hard drive that cannot be sold separately.

Dynamic kit and Static kit

A dynamic kit is a typeof catalog entry which can be dynamically configured by the customer.
This configuration (or grouping) of products is based on the customer'srequirements and is sold as a single unit.

A static kit is a groupof products that are ordered as a unit. The information about the productscontained in a static kit is predefined and controlled within WebSphereCommerce.