Last updated on AUGUST 15, 2017
Applies to:Oracle Retail Merchandising System - Version 13.2.4 and later
Information in this document applies to any platform.
When an item is set for reclassification for a future date, FUTURE_COST table gets the record created with the reclass_no and active_date set as reclassification date and the department/class/subclass is the new hierarchy provided for the reclassification.
When a cost change is created for the same item for a future date, it creates a record in FUTURE_COST_WORKSPACE table with the new hierarchy, reclass_no and cost_change number. This gets created even before the item is reclassified to the new hierarchy.
Is this the expected behavior?
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