1. Online Help
  2. Post Packing Support for Existing Picking Tasks

Post Packing Support for Existing Picking Tasks

You can make updates on a packed OBLPN using the RF Post Packing transaction, and you can also access RF Post Packing as part of your tasks without having to exit the task or manually initiate the transaction separately.

Non-Cubed Picking Tasked Flows to Support Post Packing Updates

To configure this flow, please follow the instructions below:

  1. Configure the module rf.outbound.cwrfpostpackinglpnhandling as the second program (Sequence Number 2) or/and the fourth program in the following task types/allocation types:
    • LPNUNITS: Tasks that allocate and pick individual units from a License Plate Number (LPN).
    • LPNPACKS: Picking and allocating tasks at the pack level within an LPN.
    • LPNCASES: Handles tasks for picking and allocating full cases within an LPN.
    • NC-ACTIVE-PICK: Active picking tasks that are not container-specific (Non-Container Active Pick), useful for dynamic picking operations.
    • FULL-CONTAINER: Tasks involving the picking of a full container or LPN as a single unit.
    • FULL-LPN-PALLET: Designed for handling tasks that pick and allocate a full pallet, treated as a single LPN.

  2. Configure Task Zone movements and OBLPN Putaway as needed.

    The handling of screen parameters and other considerations for Pack NC tasked flow are as follows:

    • It is recommended that users utilize the Ctrl-E command for closing all the OBLPNs for which packing is completed.
    • Load assignment and manifesting should be explicitly done after completing post-packing updates.
    • Post-packing updates are not supported for the magic flow of Pack NC (i.e., configuration set for auto-pack-one-uom and split-allocs-on-closeby).
    • Post-packing flow is not supported when retain-lpn-on-task is set to NO. This feature is mainly used for pushing LPNs onto a conveyor for the next zone picking or for the LPNs on the conveyor when MHE Route Instruction Rules come into effect.
  • Screen parameters related to printing, loading, LPN type, prompting drop and others will not be suppressed when Post packing is involved. It is up to the user’s discretion to configure parameters that will not be changed or updated again in the post-packing program.
Note: Each of the newly added programs are not mandatory in the Pack NC Task types, but at least one program must be configured in the task type for a meaningful task.

Full LPN Tasked Flows to Support Post Packing Updates

For Full LPN task types:

  1. Configure the module rf.outbound.cwrfpostpackinglpnhandling as the second program (Sequence Number 2) or/and the fourth program in the following task types/allocation types:
    • FULL-CONTAINER / Full LPN
    • FULL-LPN-PALLET / Full LPN
  2. Configure Task Zone Movements and OBLPN putaway transactions as needed.

The handling of screen parameters and other considerations for Full LPN tasked flow are as follows:

  • The parameter ‘oblpn-status-post-picking’ can have values of Packed or Picked. The OBLPNs with either status will work for post-packing updates (similar to Repack functionality).
  • When the palletize-flag is set to “palletize after packing,” the resulting output will be a pallet. However, it’s important to note that pallet handling is not supported in the post-packing process if configured after. In such cases, an error message will be displayed during post packing, indicating that “Pallet handling is not supported.”
  • It is recommended that users utilize the CTRL-E command to close all OBLPNs packed for each individual OBLPN.
  • Load assignment and manifesting should be explicitly done after completing post-packing updates.
  • Screen parameters such as printing, update LPN type, and others (parameters that also exist in the post-packing transaction) will not be suppressed when post-packing is involved. Users have the discretion to configure parameters that will not be changed or updated again in the post-packing program. However, please be aware that parameters like the palletize-flag, when set to “palletize after packing,” will result in a pallet, which is not supported in the post-packing process.
  • Pallet handling is not supported in the post-packing process. If the container type is set to Pallet in the post-packing transaction, an error will occur.
Note: Each of the newly added programs is not mandatory in the Full LPN Task types, but at least one program must be configured in the task type for a meaningful task.

For more detailed information on Post Packing Transactions for Full LPN Picking, see the following video: