[GDEC] Add New SKU issue in Get Counting Task Module

Creation date: 24/08/2023 16:15    Updated: 24/08/2023 16:15   add new sku counting task inventory count rf sku analyzer does not match data
Question:

Dear CSO Support,
I have noted an issue when actual inventory is in an empty location. (see count ID 0020112).
Per process, users will select "ADD SKU", scan the item found in the empty location, count the quantity for the said SKU, and customerid of the said SKU. However, when the SKU is scanned, a "SKU analyzer does not match data" error appears.


If I select the drop down of 'Customer id', I only get blank:


Answer:

Customer confirmed it's working.

Total issue:
1) “SKU analyzer does not match data appears”
This is due to the logic that when press Enter at SKU, it triggers Confirm button instead of filling other necessary information.

2) “Customer id selection is blank”
This is due to missing out calling query “query customer id” at the right place.

(Extra) 3) “Invalid product message”
This is due to the SKIP setting (INIT SQL) in module FLUX_INV_001_HIDE when SKU is not yet filled.


Change 1: “SKU analyzer does not match data appears”
-Change from trigger Confirm button to go to Qty





Change 2: “Customer id selection is blank”
-Add the query “query customer id” at Qty




Change 3:  “Invalid product message”
-Remove the INIT SQL in SKIP in module FLUX_INV_001_HIDE





Results:





Files