Common issues seen while performing Count in WMS

Body

1. “WMS00013” error seen while accepting Positive variance on the Count UI.

   Consider a serial tracked item inside an LPN. When performing Cycle count on UI (Application console), the warehouse user realizes that there is new inventory in the location (a new LPN containing a serial tracked item).

   When completing the count task, since the user finds this extra LPN, he/she enters the LPN details. Since there is an unresolvable variance, Variance tasks are created. New LPN information is entered again and the tasks are completed.

   When recording the count details and accepting this positive variance, the user then receives the error:

   “WMS00013 Serial tracking mandatory for the Item”

   This issue can be overcome by using the Sterling Mobile application. Also, when providing the details of the new inventory that is found in the warehouse location, the serial number of the item should also be entered along with LPN.

2. “Unidentifiable barcode” error thrown when counting positive variance on Mobile Application

   When a user finds a new LPN containing a serial tracked item while performing count on Mobile application, he/she enters the new LPN and serial number information.

   However, when trying to complete the count operation, “Unidentifiable barcode” error is shown.

   This is due to the newly found LPN in a non-standard format.

   If a new LPN is not existing in the system, UCC128Code barcode is used.

   With OOB provided barcode source, the LPN scanned format expects - 20 digit length, Case ID beginning with "000" and Pallet ID beginning with "001".

   If the LPN is not in the above format, the Dummy translator barcode source should be used.

3. recordCountResult API throws an error: "Invalid Inventory Item / Organization Code" when Serial Range is passed in input.

   A user creates a count request and associated count tasks for a serial tracked item. RecordCountResult API is used to complete this count operation. This is due to the input XML having incorrect attributes.

   For example using the followng input would result in the error -

   <RecordCountResult CountRequestKey="20150220143053179498" LocationId="Loc1" Node="Node1" PersistRecords="" SummaryTaskId="21010013" TaskId="21010014">

   <CountResult CaseId="00000000000000001706" CountQuantity="1" InventoryStatus="" ItemID="CountItem" OrganizationCode="DEFAULT" ProductClass="FQ" ShipByDate="" UnitOfMeasure="EACH" VarianceType="No Variance">

   <SerialRangeList>

   <SerialRange FromSerialNo="serial5" ToSerialNo="serial5"/>

   </SerialRangeList>

   </CountResult>

   </RecordCountResult>

These are the incorrect attributes passed -

a. <SerialRangeList> element is not required.

b. FromSerialNo and ToSerialNo cannot be the same. If the range is same, the SerialNo attribute should be used.

c. Passing Alphanumeric Serial numbers. Default implementation is given only for numeric serial numbers. If you need to generateSerialNumbers which are non-numeric, implement UE (com.yantra.yfs.japi.ue.INVGetSerialSequenceUE), otherwise system will give INV80_038 error.

This is an XML that contains the correct attributes.

<RecordCountResult CountRequestKey="20150220143053179498" LocationId="Loc1" Node="Node1" PersistRecords="" SummaryTaskId="21010013" TaskId="21010014">

<CountResult CaseId="00000000000000001706" CountQuantity="1" InventoryStatus="" ItemID="CountItem" OrganizationCode="DEFAULT" ProductClass="FQ" ShipByDate="" UnitOfMeasure="EACH" VarianceType="No Variance">

<SerialRange FromSerialNo="1" ToSerialNo="2"/>

</CountResult>

</RecordCountResult>