My Oracle Support Banner

Pricing Cost in Future Cost Table is Not Getting Recalculated After Execution Of Price Change in RMS (Doc ID 2651450.1)

Last updated on MARCH 31, 2020

Applies to:

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


Pricing cost is not getting recalculated in future_cost table after running fc_pricechg batch.

 Steps to Recreate:

1.Make sure to setup, event_type = 'RTC', event_run_type = 'SYNC' or 'ASYNC in the Cost_event_run_type_config table.
2.Let the vdate be date1.
3.Define % Off retail template .
4.Create the relationship for the dept and template.
5.Create item for that dept.
6.Validate the future cost records.
7.Create price change from RPM for date2.
8.Run batch priceeventexecution and priceeventexecutionrms in RPM.
9.Run batch fc_pricechg in RMS.
10.Observe logger_logs table hold the error data: unique constraint (RMS01.PK_COST_EVENT_THREAD) violated@2FUTURE_COST_THREAD_SQL.THREAD_ITEM_LOC.


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.