This chapter provides a detailed description of how to manage the products by performing various product related actions.
A Stock Keeping Unit (SKU) is identified by a unique alphanumeric code. This is the most granular level of identifying a specific product. Any SKU in a catalog must reside in a taxonomy node (category) – the placement of the SKU in a node is called “classification”. The information about a SKU is described by defining multiple attributes (aka, properties) for the SKU, and then populating those attributes with appropriate values. This action is called “authoring”. This also involves linking digital assets (photos, videos, diagrams, manuals, etc.) to the SKU. The SKU can undergo modification in both classification and authoring – this process of editing the SKU is common to ensure that the SKU’s information is accurate and up to date.
The second step in PCC is to import/create, place, manage and populate the products, that is, SKUs in the catalog. Managing a product includes the following steps:
Creating SKUs to add SKUs to a node
Classifying SKUs to assign them to a node
Searching and Locating a SKU in a Catalog to search and locate a SKU
Managing SKUs to perform multiple actions on SKUs
Adding Attributes / Attribute Values in SKU using Astro to add attributes as well as attribute values to SKUs based on CKB recommendations
Locking Attribute Values for SKUs to lock the SKU attribute values which will stop that SKU attribute value from getting updated by any change process like import, synchronization or portal based SKU-Edit.
Managing SKU Relationship to relate SKUs to each other using the relationship verbiages
Cross Listing SKUs to make a SKU available at other nodes
Converting UoM Values to convert UoM values for selected or all SKUs in a node
Authoring SKUs to populate values of attributes for the SKU
Using PDP for SKUs to view the Product Detail Page (PDP) for a SKU and edit attribute values
Defining Product Families (PF) to logically categorize a group of SKUs belonging to a taxonomy node
Using a Domain (Hierarchy) to have multiple catalog structures within the same catalog
The following table lists the privileges required to perform various functions related to SKUs.
Table 15: SKU level privileges
Privilege | Required to | Description | Prerequisites |
|---|---|---|---|
sku_view | View all SKUs and product families in the catalog | You can view all SKUs and product families in the catalog. | taxonomy_view |
sku_add | Add a new SKU or product family to the catalog from the UI | You can add a new SKU or product family under any taxonomy node using the UI. This privilege does not allow you to use the batch import mechanism to add new SKUs. | sku_view |
sku_edit_location | Modify the taxonomy node location of a SKU or product family in the catalog from the UI | You can modify the taxonomy node location of any SKU or product family under any taxonomy node using the UI. It also allows for cross listing of SKUs. This privilege does not allow you to use the batch import mechanism to modify SKUs. | sku_view |
sku_edit_content | Modify any attribute or attribute value of a SKU or product family in the catalog from the UI | You can modify any attribute or attribute value of any SKU or product family under any taxonomy node using the UI. This privilege does not allow you to use the batch import mechanism to modify SKUs. | sku_edit_location |
sku_edit_invalidcontent | Modify any attribute value of a SKU in the catalog from the UI using data that violates existing schema constraint | You can modify any attribute value of any SKU under any taxonomy node using the UI using data that violates existing schema constraints. The invalid data will be allowed to be saved in the database, and the violation will be visible in the UI. If you do not have this privilege, the system will not let you save the invalid SKU attribute data. This privilege does not allow you to use the batch import mechanism to modify SKUs. | sku_edit_content |
sku_delete | Delete a SKU or product family in the catalog from the UI | You can delete the entire instance of a SKU or product family under any taxonomy node using the UI. | sku_edit_location |
sku_crosslist | Cross list a SKU to be visible in another taxonomy node | You can cross list to both:
| sku_edit_location |
sku_edit_lock | Lock or unlock the existing values in certain attributes for a set of SKUs | You can lock the existing values in certain attributes for a set of SKUs so that any import / synchronization process will not update these values. Similarly, you can unlock the locked attribute values as required. Note: The Manage Attribute Lock icon will be disabled on catalog list screen and in quick links, if this privilege is not assigned to the user. | sku_edit_location |
reviewer_sku_dalinkage | Review the linking or delinking of a digital asset to a SKU | You can review the action of linking or delinking a digital asset to/from SKU. | da_link |
reviewer_sku_classification | Review the classification of a SKU within or to a domain | You can review the action of where SKU classification changes are made, that is, SKU is moved or mirrored from one node to another. | sku_edit_location |
reviewer_sku_attributevalue | Review the updates to SKU attribute value | You can review the action where SKU attribute value is added, edited or deleted. | sku_edit_content |
reviewer_sku_adddelete | Review the addition or deletion of a SKU | You can review the action where SKU is newly added or existing SKU is deleted. | sku_delete |
*Prerequisites – This column lists the privileges that needs to be enabled first before granting the actual privilege.
The following sections provide a detailed description of the above-mentioned steps.