1. Online Help
  2. Post Packing OBLPN Updates and Handling Module

Post Packing OBLPN Updates and Handling Module

You can update an OBLPN post packing using the Post Packing LPN Handling (rf.outbound.cwrfpostpackinglpnhandling) module. The Post Packing module is available with the following screen parameters:

Parameter Type Possible Values Behavior
print-column-order-descr Text Rule name configured from column ordering description created in the UI.
  • If the value is configured, the system prints the associated labels and documents tied with the column ordering rule in the sequence configured.
  • If the value is No / Blank, the system defaults to print the Shipping label (for OBLPN) and the Order packing Slip.
prompt-label-printer Selection None | Yes | No
  • If the value is Yes, the system prompts you to enter the label printer upon launching the screen.
  • If the value is No / Blank, the system does not prompt for printer launching the screen. And, the system defaults to label printer configured in the Users UI.
prompt-doc-printer Selection None | Yes | No
  • If the value is Yes, the system prompts you to enter the document printer upon launching the screen.
  • If the value is No / Blank the system does not prompt for printer when screen is launched. And, the system defaults to document printer configured in the Users UI.
validate-critical-dims Selection None | Yes | No
  • If the value is set to None, the updated LPN type critical dimensions will not be validated against item critical dimensions.
  • If the value is set to Yes, the updated LPN type critical dimensions will be validated against item critical dimensions.

NOTE: The Items dimension value are compared for Length, Width and Height with respective LPN type dimension value. And, if any value for the item is greater, the LPN type will not be updated and error message will be displayed.

  • If the value set to No, the updated LPN type critical dimensions will not be validated against item critical dimensions.

NOTE: Validate-critical-dims will not have any impact when container-type is 'Pallet'.
accept-container-dimensions Selection None | Yes | No
  • Default value is blank, the functionality works the same as No.
  • If the value is set to None / No, the dimensions fields (Length, Width and Height) for the LPN/pallet scanned (depending on container-type setting) will not be displayed in RF screen.
  • If the value is set to Yes, the dimensions (Length, Width and Height) of the LPN/pallet scanned (depending on container-type setting) will be displayed and can be updated in RF screen.
accept-container-weight Selection None | Yes | No
  • Default value is blank, the functionality works the same as No.
  • If the value is set to None / No, the weight field for the LPN / pallet scanned (depending on container-type setting) will not be displayed in RF screen.
  • If the value is set to Yes, the weight of the LPN / pallet scanned (depending on container-type setting) will be displayed and can be updated in RF screen.
container-type Selection None(blank) | LPN | Pallet
  • Default value is blank (None).
  • If the value is set to None / LPN, you can scan/enter LPN (inbound and outbound) in the RF screen and update LPN type for the scanned LPN. Weight/Dimensions for the LPN can be updated based on accept-container-weight and accept-container-dimensions settings.
  • If the value is set to Pallet, you can scan/enter pallet (inbound and outbound) in the RF screen and update LPN type for the scanned pallet. Weight/Dimensions for the pallet can be updated based on accept-container-weight and accept-container-dimensions settings.
output-file-to-generate Selection None | OBLPN Shipping Info | LPN Inventory | Pallet Shipping
  • Default value is None (blank), no file will be generated.
  • If the value is set to 'OBLPN Shipping Info', when the screen parameter container-type is LPN or Blank and the scanned LPN is Outbound LPN, the OBLPN shipping info file will be generated.
  • If set to 'LPN Inventory', when the screen parameter container-type is LPN or Blank and the scanned LPN is Outbound/Inbound LPN, LPN Inventory file will be generated.
  • If set to 'Pallet Shipping Info', when the screen parameter container-type is Pallet and contains outbound LPNs, the pallet shipping info file will be generated.

NOTE: You will not be able to generate any output:

  • If scanned entity is pallet and screen parameter is not configured to generate pallet shipping info.

  • If scanned entity is Inbound LPN and screen parameter is not configured to generate LPN Inventory.

  • If scanned entity is Outbound LPN and screen parameter is not configured to generate OBLPN Shipping Info or LPN Inventory.

Additionally,

  • The OBLPN Type prompt is not mandatory.
  • The printing parameters (that is, ‘print-column-order-descr’, ‘prompt-label-printer’, ‘prompt-doc-printer’) are not applicable for Pallet mode. And, the RF screen will display an error with an appropriate warning reflecting the same.
  • The RF transaction now validates users input for critical dimensions(L/W/H), Weight, and Volume.

The following table describes the RF behavior when the respective values are set for the following parameters:

print-column-order-descr prompt-label-printer prompt-doc-printer Behavior
Not Populated No No
  • No printing initiated.
Not Populated Yes Yes
  • Either one of the prompt printer parameters is Yes.
Populated No No
  • Defaults to print Shipping Label.
  • Defaults to print Order Packing Slip.
  • Label printing defaults to User's default label printer.
  • Document printing defaults to User's default document printer
Populated Yes No
  • Defaults to print Shipping Label.
  • Defaults to print Order Packing Slip.
  • RF prompts for the label printer. Displays an error if valid printer is not scanned.
  • Document printing defaults to User's default Document printer.
Populated Yes Yes
  • Defaults to print Shipping Label.
  • Defaults to print Order Packing Slip.
  • RF prompts for the label printer. Displays an error if valid printer is not scanned.
  • RF prompts for the document printer. Displays an error if valid printer is not scanned.
Populated Yes Yes
  • Triggers to print the Label types configured in the rule.
  • Defaults to print Order Packing Slip.
  • RF prompts for the label printer. Displays an error if valid printer is not scanned.
  • RF prompts for the document printer. Displays an error if valid printer is not scanned.
Populated Yes Yes
  • Defaults to print Shipping Label.
  • Triggers to print the document types configured in the rule.
  • RF prompts for the label printer. Displays an error if valid printer is not scanned.
  • RF prompts for the document printer. Displays an error if valid printer is not scanned.
Populated Yes Yes
  • Triggers to print the Label types configured in the rule.
  • Triggers to print the document types configured in the rule.
  • RF prompts for the label printer. Displays an error if valid printer is not scanned.
  • RF prompts for the document printer. Displays an error if valid printer is not scanned.

Perform Post Packing Transactions Through Tasking

You can perform perform task zone movements and OBLPN Putaway. using the task type “POST_PACK_HNDL.” This Task Type is available in the following non-tasked RF transactions:

  • RF Direct Allocation (rf.outbound.cwrfdirectallocation)
  • RF Combine OBLPN (rf.outbound.cwrfcombineoblpn)
  • RF Repack OBLPN (rf.outbound.cwrfrepackoblpn)

You can create and invoke a task of this task type through a control command (CTRL-T: Create Task) from inside of these RF transactions. When you use the control command, this indicates that you are done with packing and that you want to create a task for all the destination/to OBLPNs (one or more) scanned during the current session.

The system allows you to perform updates on the OBLPN (like capture weight/printing) based on the requirement, move the OBLPN between drop locations (through task zone movements) and finally putaway to loading/staging locations for shipping, all in one continuous tasked flow.

Configuration

The following two screen parameters have been added to RF Direct Allocation, RF Combine LPN, and RF Repack transactions. These parameters allow you to trigger the task for the new task type:

Parameter Name Type Values
post-pack-task-type-description Text Task type description for the task type “POST-PACK-HNDL”.
dest-task-zone Text Destination zone for the task zone move rules.
  • When you configure the above parameters with valid values and invoke the control command (CTRL+T) for the OBLPN(s) scanned in the transaction, a new task is created and executed which continues into the next program configured as part of the task type. This control command is visible in the RF only when the task type screen parameter is configured.
  • Invalid value will result in RF displaying an error 'No Task Created'. In case, when there are no OBLPNs to be tasked and the control command is invoked, the RF displays an error "No eligible OBLPNs to be tasked".
  • The RF transactions Direct Allocation/Combine/Repack also supports OBLPN updates, such as, Printing, Auto Loading, Movements or promoting Drop, LPN type, and so on, through their own screen parameters. When the mentioned transactions are configured for post packing, these screen parameters will be deliberately ignored.
Note: Once the post packing task type is configured, the screen parameters like printing/autoload/prompt drop will be ignored.

The screen parameters that may be ignored by the system are as follows:

  • prompt-drop
  • auto-load,
  • print-labels,
  • prompt-oblpn-type,
  • print-extras,
  • print-column-order-descr,
  • prompt-lpn-type-on-packed,
  • print-to-oblpn-label,etc.)
Note: Where 'column-ordering' is configured to print documents, the 'TASK_REPORT' report type does not apply for post packing updates and the associated allocations/task is completed and the OBLPN in question might be linked to allocations coming from multiple waves. In case you configure this, the application logs will be written to convey that the system will ignore it.

For RF Repack OBLPN:

  • Both picked and packed OBLPNs are eligible for post packing updates.
  • When you first scan the to-OBLPN in Repack and If Repack (or combine) is configured for post packing, the RF validates to check if it is linked to any incomplete task (of any task type) or if any open allocations are left for this OBLPN. If linked, the RF throws a hard error and does not allow you to proceed further.
Note:
  • Not all programs are mandatory, but at least one program must be configured in the new task type for the task to be created.
  • You may encounter noticeable delay if the OBLPN task count is more than a few.
  • It is recommended for you to use the Ctrl-E command for all updates to be successfully completed for each of the OBLPNs scanned in the session.
  • Load assignment/Manifesting is explicitly completed after post packing updates have been done.