HOME
The catalog subsystem provides the functionalities like on-line catalogue navigation, partitioning, categorization and association.
1)Master Catalog
It is the single catalog that contains all products, items, relationships, and standard prices for everything that is for sale in your store.Every store in the WebSphere Commerce system must have a master catalog. You can share the master catalog across stores and define as many stores as needed.
In addition to creating a master catalog for your catalog management, you might also choose to create one or more sales catalogs for display purposes. A sales catalog can contain the same entries as the master catalog, but the sales catalog has a flexible structure for customer display purposes. You can have as many sales catalogs as you want.
Use the Management Center Catalogs tool to view and manage your master catalog.
It is very important that the master catalog must be in a proper tree. For example, the parent category "Women" has a subcategory "WomenDress". It is important that WomenDress and any of WomenDress's subcategories like tops,jeans etc are not the parent category of "Women" category.
2)Sales Catalog
4)Products : Product is a group of items which exhibit same attributes. we can say Shirt is a products, but a shirt of red color of size 44 is a item. So it is clear in this example that there are two attributes size and color which belong to this item. And we can also say , that items belong to a particular product exhibit the same set of attributes.
5)Items : An item is a tangible unit of merchandise that has a specific name, part number,size and price. For example, a 44 size shirt with red color is an item for the above item.
6)SKU :Quantity is always attached to SKU ( Stock keeping unit ) .SKUs to represent each orderable item of merchandise for sale.
7)Catalog Groups
The main intent of catalog group is for partitioning and they determines navigational hierarchy of an online catalog.
8)Package and Bundle
A bundle is a collection of catalog entries that allow customers to buy multiple items with one click. A package is an atomic collection of catalog entries. A fully resolved package is comparable to an item, with its own price, and can be added to a shopping cart.
Packages can be unresolved or fully resolved. It is important to remember that only fully resolved packages can be added to an order. For example, a fully resolved computer package might contain a specific central processing unit, monitor, and hard drive that cannot be sold separately.
Components or products under bundle can be modified before adding to cart or after adding to cart. Components or products under package can't be modified
The association between the Package object and Bundle object is modeled in the CATENTREL table.
9)Dynamic kit and Static kit
A dynamic kit is a typeof catalog entry which can be dynamically configured by the customer.
A dynamic kit is a group of products that are ordered as a unit. The information about the products contained in a dynamic kit is controlled by an external configurator and supplied at order entry time. A dynamic kit's components are only tracked when your store uses the ATP inventory model. If your store uses the non-ATP inventory model, a dynamic kit will be treated as a single product.
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.A static kit is also a group of products that are ordered as a unit. The information about the products contained in a static kit is predefined and controlled within WebSphere Commerce. A static kit's components are only tracked when your store uses the ATP inventory model. If your store uses the non-ATP inventory model, a static kit will be treated as a single product. The individual components within the order cannot be modified and must be fulfilled together. A static kit will backorder if any of its components are unavailable.
Tables Used in Catalog Subsystem
1.STORECAT
2.CATCONFINF
This table holds additional information for catalog entries that represent configurable products. This information may be required by an external configurator to configure these catalog entries.
3.CATTOGRP
This table identifies the root catalog groups (or root categories) contained within a catalog.
4.OICOMPLIST
Each row contains information about the components of a configured Order Item.
5.OICOMPREL
Stores all kit level information for an Order item that is a kit. A kit may contain other kits and catalog entries outside of a kit. This table stores information about kit components and the OICOMPLIST table stores information about catalog entries outside of a kit.
6.CATALOG :This table holds the information related to a catalog.
The catalog subsystem provides the functionalities like on-line catalogue navigation, partitioning, categorization and association.
1)Master Catalog
It is the single catalog that contains all products, items, relationships, and standard prices for everything that is for sale in your store.Every store in the WebSphere Commerce system must have a master catalog. You can share the master catalog across stores and define as many stores as needed.
In addition to creating a master catalog for your catalog management, you might also choose to create one or more sales catalogs for display purposes. A sales catalog can contain the same entries as the master catalog, but the sales catalog has a flexible structure for customer display purposes. You can have as many sales catalogs as you want.
Use the Management Center Catalogs tool to view and manage your master catalog.
It is very important that the master catalog must be in a proper tree. For example, the parent category "Women" has a subcategory "WomenDress". It is important that WomenDress and any of WomenDress's subcategories like tops,jeans etc are not the parent category of "Women" category.
2)Sales Catalog
A sales catalog is a subset of the merchandise and services that are found in the master catalog.
You can create one or more sales catalogs for customer display purposes. A sales catalog has a flexible display structure that can associate products to more than one sales category, to suit the requirements of your store.
3)Default Catalog
A store has one master catalog and can have one or more sales catalogs. If your store has more than one catalog, you can specify a default catalog. Selecting a default catalog ensures that a shopper that visits your store without specifying a catalog in the URL, views the default catalog in the storefront.
To set the default catalog, use the Catalogs tool.
4)Products : Product is a group of items which exhibit same attributes. we can say Shirt is a products, but a shirt of red color of size 44 is a item. So it is clear in this example that there are two attributes size and color which belong to this item. And we can also say , that items belong to a particular product exhibit the same set of attributes.
5)Items : An item is a tangible unit of merchandise that has a specific name, part number,size and price. For example, a 44 size shirt with red color is an item for the above item.
6)SKU :Quantity is always attached to SKU ( Stock keeping unit ) .SKUs to represent each orderable item of merchandise for sale.
7)Catalog Groups
The main intent of catalog group is for partitioning and they determines navigational hierarchy of an online catalog.
8)Package and Bundle
A bundle is a collection of catalog entries that allow customers to buy multiple items with one click. A package is an atomic collection of catalog entries. A fully resolved package is comparable to an item, with its own price, and can be added to a shopping cart.
Packages can be unresolved or fully resolved. It is important to remember that only fully resolved packages can be added to an order. For example, a fully resolved computer package might contain a specific central processing unit, monitor, and hard drive that cannot be sold separately.
Components or products under bundle can be modified before adding to cart or after adding to cart. Components or products under package can't be modified
The association between the Package object and Bundle object is modeled in the CATENTREL table.
9)Dynamic kit and Static kit
A dynamic kit is a typeof catalog entry which can be dynamically configured by the customer.
A dynamic kit is a group of products that are ordered as a unit. The information about the products contained in a dynamic kit is controlled by an external configurator and supplied at order entry time. A dynamic kit's components are only tracked when your store uses the ATP inventory model. If your store uses the non-ATP inventory model, a dynamic kit will be treated as a single product.
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.A static kit is also a group of products that are ordered as a unit. The information about the products contained in a static kit is predefined and controlled within WebSphere Commerce. A static kit's components are only tracked when your store uses the ATP inventory model. If your store uses the non-ATP inventory model, a static kit will be treated as a single product. The individual components within the order cannot be modified and must be fulfilled together. A static kit will backorder if any of its components are unavailable.
Tables Used in Catalog Subsystem
1.STORECAT
This table holds the relationship between StoreEntities and the Catalogs that they offer.
Column Descriptions:
| Name | Type | Description |
|---|---|---|
| CATALOG_ID | BIGINT NOT NULL | The reference number of the Catalog. |
| STOREENT_ID | INTEGER NOT NULL | The reference number of the StoreEntity. |
| MASTERCATALOG | CHAR (1) | Specifies a master catalog for the Store. A value of 1 indicates that this Catalog is designated as a master catalog. |
| LASTUPDATE | TIMESTAMP | Indicates the last time that this relationship was updated. |
| OPTCOUNTER | SMALLINT | The optimistic concurrency control counter for the table. Every time there is an update to the table, the counter is incremented. |
Indexes:
| Name | Column Names | Type |
|---|---|---|
| <SYSTEM-GENERATED> | CATALOG_ID+STOREENT_ID | Primary Key |
| I0000782 | STOREENT_ID | Non-Unique Index |
2.CATCONFINF
This table holds additional information for catalog entries that represent configurable products. This information may be required by an external configurator to configure these catalog entries.
3.CATTOGRP
This table identifies the root catalog groups (or root categories) contained within a catalog.
4.OICOMPLIST
Each row contains information about the components of a configured Order Item.
5.OICOMPREL
Stores all kit level information for an Order item that is a kit. A kit may contain other kits and catalog entries outside of a kit. This table stores information about kit components and the OICOMPLIST table stores information about catalog entries outside of a kit.
6.CATALOG :This table holds the information related to a catalog.
| Name | Type | Description |
|---|---|---|
| CATALOG_ID | BIGINT NOT NULL | The internal reference number of the catalog. |
| MEMBER_ID | BIGINT NOT NULL | The internal reference number that identifies the owner of the catalog. Along with the IDENTIFIER, these columns are a unique index. |
| IDENTIFIER | VARCHAR (254) NOT NULL | The external identifier used to identify the catalog. Along with the MEMBER_ID, these columns are a unique index. |
| DESCRIPTION | VARCHAR (254) | An administrative description of the catalog. |
| TPCLEVEL | INTEGER | Reserved for IBM internal use. |
| OPTCOUNTER | SMALLINT | The optimistic concurrency control counter for the table. Every time there is an update to the table, the counter is incremented. |
Indexes:
| Name | Column Names | Type |
|---|---|---|
| <SYSTEM-GENERATED> | CATALOG_ID | Primary Key |
| I0000061 | MEMBER_ID+IDENTIFIER | Unique Index |
CATGROUP :This table hold the information related to a catalog group. A catalog group is similar to a generic category that can contain both other catalog groups and also catalog entries.
CATGRPDESC :This table holds the language-dependent information related to a catalog group.
URLS
1)StoreCatalogDisplay
2)TopCategoriesDisplay
3)CategoryDisplay
4)ProductDisplay
Commands
1)StoreCatalogDisplayCmdImpl
This command sets the view task that will display the Catalogs available to browse in the current Store.
2)TopCategoriesDisplayImpl
This command sets the view task that will display the root Categories in a specified Catalog.
3)CategoryDisplayCmdImpl
retrieves the configured display page for the specified category in the specified catalog.
4)ErrorMissingAttributeCmd
This error task command is set when a Product to Item resolution fails due to missing product attributes.
5)ErrorProductAttributeCmd
This error task command is set when a Product to Item resolution fails due to incorrect product attributes
6)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.
7)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--
1)StoreDataBean--extends StoreAccessBean ->salesCatalogs()
2)CatalogDataBean-extends CachedCatalogAccessBean ->getTopCategories()
3)CategoryDataBean-extends CachedCatalogAccessBean ->getSubCategories()
4)CatalogEntryDataBean-extends CachedCatalogEntryAccessBean
5)ProductDataBean-extends CachedProductAccessBean
CATGRPDESC :This table holds the language-dependent information related to a catalog group.
URLS
1)StoreCatalogDisplay
2)TopCategoriesDisplay
3)CategoryDisplay
4)ProductDisplay
Commands
1)StoreCatalogDisplayCmdImpl
This command sets the view task that will display the Catalogs available to browse in the current Store.
2)TopCategoriesDisplayImpl
This command sets the view task that will display the root Categories in a specified Catalog.
3)CategoryDisplayCmdImpl
retrieves the configured display page for the specified category in the specified catalog.
4)ErrorMissingAttributeCmd
This error task command is set when a Product to Item resolution fails due to missing product attributes.
5)ErrorProductAttributeCmd
This error task command is set when a Product to Item resolution fails due to incorrect product attributes
6)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.
7)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--
1)StoreDataBean--extends StoreAccessBean ->salesCatalogs()
2)CatalogDataBean-extends CachedCatalogAccessBean ->getTopCategories()
3)CategoryDataBean-extends CachedCatalogAccessBean ->getSubCategories()
4)CatalogEntryDataBean-extends CachedCatalogEntryAccessBean
5)ProductDataBean-extends CachedProductAccessBean
No comments:
Post a Comment