Overview
Every LPN has a lifecycle status, can sit in a two-level Parent–Child hierarchy, and is checked against its container's capacity. Knowing these rules helps you understand why an LPN behaves the way it does in each operation.
Step-by-Step Instructions
Check an LPN's status
- Go to LPN Master → Click a Process Flow filter (Unallocated, Allocated, Archived or Blocked) → The grid shows the LPNs in that status.
Important Notes & Limitations
Lifecycle states:
- Unallocated: created, but not yet mapped with inventory.
- Allocated: mapped with stock and active in an operational flow.
- Blocked / Locked: restricted due to QC, audit, quarantine or operational hold.
- Archived: closed for operational use and retained for reference and audit.
Hierarchy:
- Only two levels are supported: Parent and Child.
- A Parent LPN can have multiple Child LPNs, but a Child LPN cannot act as a Parent.
- The hierarchy is supported in Inbound Receiving, Count & QC, Putaway, LPN Statement / Visibility, and Return flows.
Capacity validation:
- Weight and volume validation apply to both Child and Parent LPNs.
- For a Parent LPN, validation includes all mapped Child LPNs plus any stock allocated directly to the Parent.
Module rules:
- Inbound, Storage and Outbound are auto-enabled when Return is ON.
- Stock Management is auto-enabled when any of Inbound, Storage or Outbound is ON.
- Outbound is auto-enabled when Inbound is ON.
- Storage LPN (Bin Management) and Inbound cannot be enabled together.
Troubleshooting & Common Errors
| If the system shows this error | Follow these steps to fix it |
|---|---|
| "Block if capacity exceed", with Proceed unavailable | The weight or volume capacity is exceeded, and the system blocks the action. Correct the LPN, container or quantity so the capacity validation passes. |
| "This LPN contains unusable products. Scan another LPN or generate a new one." | Scan another LPN, or click Generate New LPN, then click Confirm. |
Comments
0 comments
Article is closed for comments.