ReSA Mass SKU_NOT_FOUND Update Does Not Mark The Impacted Stores As Re-Audit Required (Doc ID 2917509.1)

Last updated on DECEMBER 23, 2022

Applies to:

Symptoms

On : 19.3 version, ReSA - Others

ACTUAL BEHAVIOR
---------------
ReSA mass SKU_NOT_FOUND update does not mark the impacted stores as Re-Audit required

While fixing thousands of SKU_NOT_FOUND transactions, we noticed the transactions are getting resolved, but now we would have to manually re-audit > 6000 pending Store-Day's.

After the mass update across all open Store-Days, the transactions are resolved, but ReSA is not updating the AUDIT_STATUS from H (Errors Pending) to R (Re-Totaling/Auditing Required) which will prevent these Store Days from being automatically audited once the next daily cycle is executed.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Upload big RTLog for processing and make sure you have SKU_NOT_FOUND errors reported.
2. Fix the error in Mass update screen.
3. Notice that sa_store_day.audit_status stays in 'H' status. This needs to change to 'R' for re-audit/re-totaling.

Cause

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