Cluster with Same Look and Different Subclass Results in Cluster Label 'Not Used' Displaying in Build Wedge (Doc ID 2105319.1)

Last updated on JULY 30, 2017

Applies to:

Oracle Retail Assortment Planning - Version 14.1.1 and later
Information in this document applies to any platform.

Symptoms

Cluster with same Look but different Subclass shows unexpected result and Clustering in Build Wedge is showing 'Not Used' value.

For example:
Created plans for 2 different Subclasses and generated different Clusters using the same Look.
1. Create Look & Commit Plan (Look Maintenance)
2. Create & Approve Cluster (Clustering)
3. Build Wedge

Example of Results:
Plan 1 - Clustering in Build Wedge is correct e.g. 101010 Sandals
A | White | Hot Humid            
A | White | Hot Dry 

Plan 2 - Clustering in Build Wedge is correct e.g. 200934 3/4 Sleeved Tees
A | Mixed Humid | Large        
A | Cold | Medium 

Open Plan 1 again and now the clustering is displaying incorrect results:
Plan 1 reopened for 101010 Sandals
Not Used                              
A | Cold | Large

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms