My Oracle Support Banner

VPLU Type 2 E Quantity Calculation (Doc ID 2591402.1)

Last updated on SEPTEMBER 24, 2019

Applies to:

Oracle Retail Store Inventory Management - Version 16.0.2 and later
Information in this document applies to any platform.

Symptoms


VPLU Type 2 E quantity calculation is wrong.

As per the SIM documentation, following is the type 2 E format (2-4-5-1): 2 digit prefix say "20"+4 digit item id "XXXX" + check digit say "0" + 5 digit price (with assumed 2 decimal places) say 00240.

If  user scans 20 XXXX 0 00240 and the unit price of the item is 1.20, it should return 2 as quantity but it looks like its taking one more decimal. Its returning 0.2 as quantity.

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


1. Create a VPLU type 2 E item in RMS, say XXXX (Level 1 transaction item) and range it to a store (Standard UOM :KG).
2 .Set the price to say 1.20 per KG.
3. Make sure that SIM has Type 2E enabled in barcode_processor table (If you change it in DB, it may need a server bounce to reflect).
4. Try creating a new inventory adjustment in handheld.
5. Scan "20 XXXX 0 00240" - Notice that the quantity detected is 0.2 KG. Shouldn't it be 2 KG ("00240" with 2 decimal places = 2.40: 2.40/1.20 = 2 KG).


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.