Layaway Transactions Are Resulting In Late Sales Records Being Published To RMS
Last updated on OCTOBER 31, 2017
Applies to:Oracle Retail Store Inventory Management - Version 14.1.2 and later
Information in this document applies to any platform.
When a layaway transaction is created in Store Inventory Management (SIM) for an item-location, then if the item has open stock count for that store, then if the layaway transaction is created from POS (postransaction webservice)
then it inserts that (180 record) in stock_count_sale table with reason code 180 in SIM. The issue here is that when user Authorize the stock count (without pressing update snapshot button), then this 180 layaway transaction will also send as LATE sales to Retail Merchandising System(RMS), keeping RMS and SIM inventory out of sync.
The same issue occurs even if we cancel reservation(181 reason code records are inserted)
Steps To Reproduce:
1. Create stock count for an item in SIM.
2. Now create a simple layaway transaction from POS using pos transaction webservice for reserving some quantity
3. Notice that the customer reservation bucket (quantity_customer_reserve) has been increased with the amount of quantity reserved from layaway transaction.
4. Note that an entry is inserted in STOCK_COUNT_SALE table for this transaction with 180 Reason code.
5. Authorize the stock count without pressing update snapshot button.
6. Now a late sale is generated for RMS which is wrong.
7. RMS-SIM will not be in sync.
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