Support Pallet Handling in Full LPN Replenishment

Currently, warehouse users are required to process containers within a pallet, rather than handling the pallet as a whole, during the Full LPN Replenishment flow. 

To address this challenge, we’ve expanding the Pallet handling capabilities in Warehouse Management by enhancing the Move LPN and Distribute Replenishment transactions to prompt and handle Pallets. This will enable warehouse users to process pallets more efficiently and effectively, streamlining the Full LPN Replenishment flow.

INTRODUCING ADDITIONAL FIELD IN MOVEMENT REQUEST DETAIL

As we leverage pre-built pallets to simplify the process, we’ve added support for specifying a required pallet number in movement requests.

• A new field called "Required Pallet Number" is introduced to the "Movement Request" entity. In case of Multi-SKU LPNs or multiple inventory LPNs on Pallet allocated across movement request details, you can use this field to interface or populate multiple movement request details going to the same destination with the same pallet number.

NOTE: If the payload contains multiple movement requests and some of them have errors in the past data, the system will process only the valid requests. It will create or delete movement requests based on the action code, while skipping the requests with errors.

• The field can be interfaced through input interface, UI, and init_stage_interface API and is available for all supported formats.
• The field is also added to the search filter criteria and can be exported through the Export to CSV functionality.
• Additionally, the "Required Pallet Number" and "Required LPN Number" fields is added to the Patch API for Movement Request Detail.

NOTE: The system prevents both fields from being interfaced together as they are mutually exclusive.

REPLENISH AN ENTIRE REQUIRED PALLET TO ONE DESTINATION LOCATION

The movement of a pallet is optimized; for 25D, we are focusing to accomplish Full LPN replenishment by replenishing the pallet entirely to one location.

• This enhancement allows you to replenish an entire pallet to a single destination location via the RF Replenish Full LPN (rf.inbound.cwrfreplenlocn) flow, when the "Required Pallet Number" is specified on the movement request detail.
• The system will replenish the pallet as a whole in both Reserve to Active and Reserve to Reserve flows and displays the pallet number being distributed on the RF Replenish Full LPN screen.
  • Reserve to Active: System will replenish the entire contents of the Pallet to the destination active location.
  • Reserve to Reserve flows: system will replenish the entire Pallet as is to the destination reserve location.

INTRODUCING A NEW FLAG IN TASK CREATION TEMPLATE

To enable the movement of entire pallets instead of individual LPNs, you need to create a task movement by configuring the new flag on the task creation template detail UI.

• A new flag “Scan pallet number if whole pallet allocated” is introduced in the task creation template detail UI. This flag is applicable for only two Task Types (REPLEN-LPN and REPLEN-CS-PK-UNITS) and for all the replenishment trigger modes.
  • If the flag is enabled: The movement of the Pallet(s) is created for the task and the Pallet number is populated on the movements. During execution of the task, the system prompts for the Pallet number only (not for the LPN) for scanning the fully allocated pallet.
  • If the flag is disabled: The existing behaviour will retain, where a blind Pallet is scanned and all LPNs for movement are scanned to build the pallet.

MOVEMENT REQUEST TRIGGERED REPLENISHMENT TO CONSIDER REQUIRED PALLET NUMBER

Now, the replenishment allocation logic considers the "Required Pallet Number" field on the movement request detail ensuring that allocations are made correctly when this field is populated.

• The 'Required Pallet Number' field on the Movement Request Detail will be populated with an existing Pallet number.
• Replenishment rule is set for 'Movement Request' trigger and Full LPN Replenishment Mode in the Replenishment Template View.
• When you run replenishment, the addition of 'Required Pallet Number' allows allocating the entire Pallet against the movement request detail(s) for Full LPN Replenishment mode.
• The system considers following key validations before for allocation:
  • Movement Request details with 'Required Pallet Number' are considered first.
  • If 'Required Pallet Number' is populated, the system only allocates using that Pallet.

NOTE: The entire Pallet is allocated across multiple MR details only if the destination location matches the details.

• When allocating, the system main checks for following where the ordered Qty on the MR detail(s) with same destination and same required pallet number is greater than or equal to the total Qty of the SKU from all the LPNs on the Pallet, i.e.,
  • Movement Request Order Qty >= Total Qty of the SKU on the Pallet.
  • Movement Request Order Qty < Total Qty of the SKU on the Pallet.
  • If Required Pallet is populated and allocation fails, the detail is skipped.
  • If the allocation fails, the system skips executing the detail including regular replenishment allocation sequence execution. If Order Qty on the detail  > Pallet total Qty and Required Pallet is already allocated, the outstanding Qty remains unallocated.
  • Area/Alloc zone configured in the Allocation mode sequence is ignored when 'Required Pallet Number' is configured.
  • If MR detail has specific batch/attributes, the system honors them and fails allocation in case of a mismatch.
• If a Pallet is still unallocated after going through the required pallet logic, then the pallet is made available for allocation for other Movement Request details to allocate pallet or the full LPNs on the pallet.

Steps to Enable

1. Go to the Task Creation Template UI.
2. Select the record and go to details.
3. Click the Edit icon.
4. Enable the Scan pallet number if whole pallet allocated flag.

NOTE: This flag is applicable for only two Task Types (REPLEN-LPN and REPLEN-CS-PK-UNITS) and for all the replenishment trigger modes.

5. Click Save.