Using a Domain (Hierarchy)

A Hierarchy in PCC enables you to have multiple Catalog structures (with all entities of Taxonomy, Attribute, Schema and their related characteristics like LoVs, UoMs, and so on) within the same catalog. When you first create a new catalog, it is created by default in a primary Hierarchy. The Hierarchy within which the catalog exists is visible as shown in the following figure.

Any subsequent import will be updated in the primary Hierarchy itself until you explicitly create a non-primary Hierarchy and work in this Hierarchy. SKUs in the input files must conform to the Node they belong to in the primary Hierarchy.

A company dealing with product content will have multiple uses of the same content. The primary Hierarchy will ideally have all the content relevant for the company. The non-primary or other Hierarchy could be used by various departments within the same company such as marketing department, e-commerce team and so on for the content that is relevant for their teams. So, Hierarchy will enable a company to have multiple views of the same catalog that is relevant to each team as multiple Hierarchy can be created.

The SKU can reside in multiple nodes across multiple Hierarchy, but the actual SKUs will reside in the primary hierarchy itself as there can be only one version of the SKU data in the entire catalog. You cannot make any changes to the SKU, nor add any new SKUs in the non-primary hierarchy. You can only add SKUs to nodes in a non-primary hierarchy from any other hierarchy, that is, it is a mirror view of all SKUs which can only be viewed.  Also, you can delete SKUs from a node in a non-primary hierarchy.

A detailed description of how to add, edit and delete a hierarchy as well as manage SKUs is mentioned in the following sub-sections.

• Adding a New Hierarchy

• Viewing a Hierarchy

• Editing a Hierarchy

• Working in a Hierarchy

• Managing SKUs in Non-Primary Hierarchy

• Deleting a Hierarchy

Adding a New Hierarchy

You can add multiple non-primary Hierarchy for a catalog.

To add a new hierarchy:

1. On the Catalog action bar, select the hierarchy drop-down list and then click Add New Hierarchy as shown in the following figure.

Figure 195: Add new hierarchy

The following dialog box appears.

Figure 196: Enter hierarchy details

2. Enter the Hierarchy Name (the name should be unique to the catalog) and the Hierarchy Description (a brief summary about the hierarchy).

Astro: This should be turned on only if you need to use recommendations for adding nodes and schema attributes.

3. Turn on the Astro toggle to use recommendations from the CKB for adding nodes as explained in section 6.3.1.1 Creating a Taxonomy Structure using Astro or to add schema attributes as explained in section 0 Adding Schema Attributes using Astro.

Review Mode: This should be turned on only if any user action being performed in a catalog needs to be reviewed.

4. Turn on the Review Mode toggle to configure the user actions that need to be reviewed and the following options are displayed.

You can scroll further to view the various user actions that can be reviewed for different catalog entities. Refer section 19.1Overview of User Actions Eligible for Review for a detailed description about the user actions covered for each entity. Alternatively, you can also hover on the icon next to each action to know the various actions covered.

For example, let us turn on the toggle for an action under SKU Authoring as shown below.

5. Select the Reviewer from the drop-down list who will be assigned the task of reviewing the changes, that is, in this case we have turned on the review mode for Review user actions of updates to SKU attribute value. Thus, any changes made to the SKU attribute value (add edit or delete) will not happen directly as it will be sent to the reviewer for approval.

Similarly, multiple user actions can be set for review and assigned to a reviewer.

6. Click Add and the hierarchy is added successfully to the catalog. For example, a hierarchy Test is created. It is now visible in the Hierarchy drop-down list as shown below.

Figure 197: Hierarchy created successfully

Viewing a Hierarchy

Once the hierarchy is created, click the Configure Hierarchy icon next to the hierarchy name as shown in the following figure.

Figure 198: View a hierarchy

The non-primary hierarchy created will be empty, that is, there are no nodes in it. You need to create the required structure with all the catalog entities.

To switch between Hierarchy, click the Hierarchy drop-down list and then click the Configure Hierarchy icon next to the hierarchy name.

Editing a Hierarchy

You can edit the hierarchy name and description in case of any changes to be made. Click the Edit Hierarchy icon as shown in the following figure.

Figure 199: Edit a hierarchy

The following screen appears.

Make the necessary changes and click Submit. The hierarchy is edited successfully.

Working in a Hierarchy

You can manage the structure of a non-primary hierarchy as needed. Nodes can be copied from another hierarchy (primary/non-primary) to this hierarchy. Details on how to copy nodes is mentioned in section 6.3.1.6 Copying Nodes. Once the nodes are copied or newly created, you can perform structural changes like adding/editing/deleting nodes, creating/maintaining schemas with LOVs, UoMs and Schema Constraints. While copying nodes, you can copy the schemas, LoVs and UoMs or create new schemas as needed.

The attributes created in the primary hierarchy will be displayed in the non-primary hierarchy too. The attribute master list is common across Hierarchy and the actions to be performed are similar.

A non-primary hierarchy can contain a node that does not exist in the primary hierarchy or in any other hierarchy.

Also, the PF view is disabled in non-primary Hierarchy as PF can belong to a primary hierarchy only. Similarly, it is possible that an attribute is part of a schema in a non-primary hierarchy, but not part of any schema in any other hierarchy. Similarly, LOVs, UoMs and schema constraints can also be totally different and unique in a non-primary hierarchy.

Managing SKUs in Non-Primary Hierarchy

A single version of the SKU data exists in the entire catalog. Hence, actual SKUs will reside in primary hierarchy only and a mirror copy of these SKUs will reside in non-primary Hierarchy. The SKU Attribute Values will be the same irrespective of the hierarchy/node.

In a non-primary hierarchy, all SKU information is viewable, but not editable. Hence, you cannot change any attribute values for the SKUs when not in the primary hierarchy. Also, you cannot add a new SKU in a non-primary hierarchy. However, you can mirror eligible SKUs from any hierarchy, that is, a SKU can be mirrored only once in a hierarchy. If 4 SKUs exist in a node in primary hierarchy and 1 has already been mirrored to a different or same node in the secondary hierarchy, that SKU will not appear in the selection and that is why the term ‘mirror eligible SKUs’.

Thus, the SKU count on the taxonomy tree and the SKU count in the mirror SKU section in the middle panel will not match if it has been cross listed to this hierarchy already.

Let us understand how to mirror eligible SKUs from any node from any hierarchy in a non-primary hierarchy.

To mirror eligible SKUs from Hierarchy:

1. Go to the non-primary hierarchy and click the SKU view.

Figure 200: SKU view in non-primary hierarchy

2. Select the node and then click the Mirror eligible SKUs from Hierarchy icon as shown below.

The following screen appears.

Figure 201: Mirror eligible SKUs

3. Select the Source Hierarchy from where the SKUs need to be mirrored. The taxonomy tree is displayed based on the hierarchy selected as shown below.

Figure 202: Select source hierarchy

4. Select the nodes and then select the SKU/multiple SKUs from the source node and the details of the SKUs selected is displayed as shown below.

Figure 203: Select SKUs from source node.

5. Select the SKUs to be added in the non-primary hierarchy and click the icon next to the SKU. This will move the SKUs to the next panel indicating the SKUs to be added in the non-primary hierarchy as shown in the following figure.

Figure 204: Add selected SKUs to non-primary hierarchy

6. Similarly, you can click the icon next to the SKU to remove it from the panel.

7. Click Mirror SKUs and the SKUs are mirrored successfully from the selected source hierarchy. However, if there are any validation failures based on the schema constraints, it will be displayed.

   You can also remove SKUs from a node in a non-primary hierarchy. To remove a SKU/multiple SKUs, select the SKU and then click the Remove Mirrored SKUsicon and the SKUs are removed successfully.

You can also move the SKUs from one node to another in a non-primary hierarchy, relate SKUs to each other, download the assets linked to the SKUs and attach/detach SKUs to the PF .

However, if the review mode is turned on for user action Review user actions of classifying a SKU within or to a hierarchy while adding / editing a non-primary hierarchy, you cannot mirror the SKUs directly as it will be assigned to a reviewer. In this case, when you mirror the SKUs, a message is displayed as shown in Figure 122: Action under review message.

Depending on the source hierarchy from where the SKU is being mirrored, the SKU will be updated with an orange icon as explained here.

Depending on the action taken by the reviewer, the value will be approved/rejected /aborted as explained in section 19.4 Reviewing the User Actions Assigned.

Deleting a Hierarchy

You can delete a non-primary hierarchy. However, a primary hierarchy cannot be deleted as it contains all actual SKUs and hence the delete icon is not provided for the same. To delete a non-primary hierarchy, click the Delete Hierarchyicon next to the hierarchy name as shown below.

Figure 205: Delete a hierarchy

A warning message is displayed indicating that the entire data that will be deleted cannot be retrieved once the hierarchy is deleted.

To proceed with the process, click Proceed to Generate OTP and an OTP is sent to the email ID added in PCC as shown below.

You need to enter this OTP in the screen displayed after generating the OTP as shown below.

A timer is set within which you need to enter the OTP received. In case you have not received the OTP, click Resend OTP to generate it again. If the session expires, you will have to generate the OTP again.

Once the OTP is entered, the Delete option is enabled as shown below.

Click Delete and the non-primary hierarchy is deleted successfully.