Wrong Unit Retail and Cost Posted for TRAN_DATA 3 When a Non-Inventory Item Sale Is Uploaded by POSUPLD

(Doc ID 1969745.1)

Last updated on AUGUST 17, 2016

Applies to:

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


The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.

In Oracle Retail Merchandising System (RMS) 13.2.4, when a non-inventory item sale is posted in TRAN_DATA by POSUPLD, the wrong retail and cost value is being posted for tran_code = 3.
The problem is occurring for locations for which the item has an entry in ITEM_LOC but NOT in ITEM_LOC_SOH.

Also, the below error is encountered:

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

1. Have an non-inv item/loc combination for which ITEM_LOC entry is there but ITEM_LOC_SOH entry is missing.
2. Unit_retail is set as $0 for that item in ITEM_LOC.
3. Post a sale for that item with a sale value >0.
4. Check TRAN_DATA retail and cost value for tran_code=3.


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