Oracle Commerce Does Not Send Price Changes for SKUs via PriceLists to Endeca During Incremental Indexing

(Doc ID 1674059.1)

Last updated on DECEMBER 22, 2016

Applies to:

Oracle Commerce Platform - Version 10.2 and later
Information in this document applies to any platform.


Statement of Issue:
After doing the change in price of a SKU no records are inserted into the srch_update_queue. Due to this, after triggering the incremental indexing, zero records are sent to Endeca.
If we change any other attribute like display name, the expected records are inserted into srch_update_queue table and ProductCatalogOutputConfig, which sends the record to Endeca for indexing. We are able to see the updated indexed value in Endeca.

Oracle Commerce 10.2

1. Using the BCC change the price of a SKU
2. Deploy the project containing the SKU change.
3. Trigger incremental indexing through dyn/admin.
4. 0 records are sent to the mdex.

No Errors are logged.

Expected Behavior:
A row is inserted in the incremental item queue resulting in a record being sent to Endeca when incremental indexing is triggered.
This updates the SKU.price in the mdex.

Actual Behavior:
No row is inserted in the incremental item queue.

Business Impact:
Stale price data will persist in the MDEX.


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