“RF IB Sorting” Transaction Cannot Proceed Due To An LPN In “consumed” Status
Last updated on JULY 02, 2018
Applies to:Oracle Warehouse Management Enterprise Edition Cloud Service - Version 8.0.0 and later
Information in this document applies to any platform.
“RF IB Sorting” transaction cannot proceed due to an LPN in “consumed” status
You want to sort an inbound LPN (xxxxxx) from the ASN (yyyyyy).
For that purpose, you use the transaction “RF_Clasificar LPN”.
The RF shows the code of an LPN with a "consumed" status as the destination for sorting, which should have been removed from the inbound sorting criteria once it changed status to “consumed”.
Also, once you input the the LPN code the system won’t let the SKU be sorted to the appointed LPN - the system points out that it already exists.
Which means that neither the appointed LPN nor a blind LPN can be scanned, therefore stopping the rest of the transaction and even blocking the sorting location for further use.
The RF should allow to continue sorting by using blind LPN
The RF should not show an LPN with a “consumed” status as part of the sorting location, it should make way for a new LPN code with a different status.
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