Putaway Page Allows Consolidation Between Two LPNs With Different Tasks (Doc ID 2245975.1)

Last updated on MARCH 20, 2017

Applies to:

Oracle Warehouse Management - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

You are performing a mobile putaway and find that the page allows consolidation between two LPNs with different tasks.
You are not able to complete the consolidation as the system throws the error message "LPN not valid".

ERROR
-----------------------
 "LPN not valid"

STEPS
-----------------------
Starting point:
A Sales Order with 3 lines:
1st line is a regular line, non-ATO, linked to project/Task P1.T1
2nd line is an ATO line, sourced by a PO, linked to project/task P1.T2
3rd line is an ATO line, sourced by a PO, linked to project/task P1.T1
---
1st step: Pick 1st SO Line
Submit pick release for 1st line.
Pick into LPN L1 and Drop into staging lane, let's say = Locator = SL1.P1.T1
  (project locator as it is project process)
---
2nd step: Receive PO for SO lines 2 and 3
PO routing is standard routing.
Receive step is done for the PO related to the lines 2 and 3 of our SO.
Each line is in a different LPN (there are 2 projects, so it cannot be in the
same LPN)
Let's say LPN L2 related to the line 2, and LPN L3 related to the line 3
SO lines 2 and 3 are at status In Receiving.
---
3rd step:
As: Opportunistic CrossDock is set up and active for these receipts.
As: Pre-generate put-away suggestion is active in organization parameters
The receipts are assigned to the delivery lines that are then at status
Released to Warehouse.
---
4th step: Move any LPN related to the SO Line #2
Scan LPN L2
The suggested destination locator is SL1 (project P1.T2 SL1.P1.T2)
BUT system suggests to put-away into LPN L1 (located in SL1.P1.T1)
OF COURSE, system rejects LPN L1 as a possible LPN to put-away into as it is
not located in the same project.
---
5th step: Move any LPN related to the SO Line #3
Scan LPN L3
The suggested destination locator is SL1 (project P1.T1 SL1.P1.T1)
BUT system suggests to put-away into LPN L2 (located in SL1.P1.T2)
OF COURSE, system rejects LPN L2 as a possible LPN to put-away into as it is
not located in the same project.


Cause

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