My Oracle Support Banner

An Update on UDA Default Value at Subclass Level Does Not Apply to Newly Created SKU of Existing Style (Doc ID 2605970.1)

Last updated on OCTOBER 31, 2019

Applies to:

Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.


Actual Behavior
After changing the User-defined Attributes (UDA) default value of any dept/class/subclass from existing to new, and when Level-2 Item (Children/SKUs) is created, the old UDA value gets reflected for newly created SKUs. It is being defaulted from Item Parent (Level-1/Style) to Level-2, not from UDA default.

Expected Behavior
UDA default value should get defaulted from what has been set on dept/class/subclass for any item creation (SKU).

Steps to Reproduce
The issue can be reproduced at will with the following steps:
1. Select an existing Default UDA value <UDA_VALUE1> for a particular dept/class/subclass.
2. Create an SKU and Style for the same dept/class/subclass.
3. Change the Default UDA value to <UDA_VALUE2> via Item Upload/Download process using UDA Template.
4. Now create a new SKU for the same style.
5. Check for the Default uda_value for the new SKU.
6. The Default uda_value for the new style is <UDA_VALUE1>. But it should be <UDA_VALUE2>.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.