My Oracle Support Banner

ReSA Screen Updates Unit Retail After Entering Item in the Error Fix Screen (Doc ID 2886667.1)

Last updated on AUGUST 01, 2022

Applies to:

Oracle Retail Sales Audit - Version 19.0 and later
Information in this document applies to any platform.

Symptoms




Actual Behavior
-------------------------------

When an item not on file happens at the Xstore POS, the cashier enters a value of 9999999 for the item and then enters the real SKU manually into the description field. When the RTLOG comes into ReSA, it fails due to SKU_NOT_FOUND. The audit team then fixes the error by entering the correct item into the item field. When they do that, sometimes the retail changes. When the selling retail is changed in Xstore and sent across to ReSA, ReSA should persist the value upon correcting the SKU, which is not happening.


Expected Behavior
-------------------------------

ReSA should persist the value upon correcting the SKU, or ReSA should display a message dialog notifying users of the price being overridden with the ITEM_LOC.

Steps to Reproduce
-------------------------------
1. Create a sale in xstore with an item not on file. enter the actual item in the description field
2. RTLOG comes into ReSA
3. transaction fails with SKU_NOT_FOUND error code
4. get tran sequence number and search for transaction
5. more_actions - > edit
6. navigate to the errored item and edit
7. enter the real item in the item field and press the tab
8. sometimes the unit retail stays the same, sometimes it increases/decreases


Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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