Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Nested LPN vs. OBLPN — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Nested LPN vs. OBLPN

Accepted answer
29
Views
4
Comments
edited Nov 11, 2022 1:30AM in Warehouse Management 4 comments

Summary:

Nested LPN vs. OBLPN

Content (required):

I understand WMS does not support Nested LPN but also know user can create Outbound LPN based on current LPN in the storage locations. My current use case is that, user breaks "Master LPN" into "Child LPNs" during shipping and assign different Child LPNs into different Outbound Shipments. At times, user may need to refer back to the master LPN number from child LPN.

It seems to me that WMS can support this use case. Is that correct? If yes, is there any pitfall that I need to be aware of?

Version (include the version you are using, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!