Validate Critical Dimensions for Putaway and Replenishment

Do you need to store items in a vertical space? Or perhaps, stacking width-wise in your warehouse might make things easier for the movement of logistics within your warehouse.

By setting parameter values for critical dimension validation, you can ensure items can be stored using accurate storage specifications. The following table describes the three types of dimension comparison available:

Method to Validate Critical Dimensions	Description
Random Match	(Default) - The length, width and height of LPNs are matched to the length, width and height of locations in the warehouse.
Height Match	Height of first entity is compared with height of second entity; length and width of first and second entity will be matched at random.
Exact Match	Height of first entity is compared with height of second entity; length of first entity is compared with length of second entity; width of first entity is compared with width of second entity.

Select Critical Dimension Validation

To select your preferred method, from the Items UI Create/Edit/Copy pane, click on the Dimension Validation Method drop-down. From this drop-down, you can choose between "RANDOM MATCH", "HEIGHT MATCH" and "EXACT MATCH" as the available methods of validating critical dimensions.

Note: Selecting the method of critical dimension validation is not mandatory. If the field is not set, critical dimension validation will default to Random Match logic.

In addition to this, in the Interface Protected Fields UI, you can also ensure your preferred method of critical dimension validation is persistent across transactions.

For example:

During cartonization, it is possible that if an item has been validated based on "HEIGHT MATCH" and before putaway if the new field is changed to "RANDOM MATCH", the box could be oriented and placed in any fashion in the Reserve Location.

From the Create/Edit/Copy pane of the Interface Protected Fields UI, select Dimension Validation from the Column Name drop-down to prevent any scrambling of critical dimension validation methods between or while running multiple transactions.

You can also set your preferred method of critical dimension validation in the Item Interface.

NOTE: It is not mandatory to enter a value for this field and if no value is sent, the default would be blank which will be interpreted as "RANDOM MATCH" on Item View.

Validate Dimensions for an Active or Reserve Locations

To further support critical dimensions, the "validate-critical-dims" parameter, (in the RF Putaway (rf.inbound.cwrfputaway) module) allows you to validate the dimensions of an Active or Reserve Location. If the parameter is set to YES, the dimensions of the Location (Active or Reserve) are validated against the dimensions of the Item or IBLPN that is being putaway to that Location.

NOTE: By default, the validation logic follows a RANDOM MATCH approach where any dimension of first entity is compared with any dimension of the second entity after sorting the dimensions of both the entities in descending order.

You can assign the (random/height/exact) values corresponding to your preferred critical dimension validation methods, as discussed previously, via the "Dimension Validation" drop-down in Item View or "Dimension Validation" item field in the Item Interface screens.

Define Dimension Validation for Wave-based, Standalone, and Reactive Replenishment

You can define dimension validation for Wave-based, Standalone, and Reactive Replenishment using a new flag "Perform Critical Dimension Check."

From Wave Template -> Replenishment Rule, check the flag "Perform Critical Dimension Check". Based on the values you have set on the "Dimension Validation" field in the Items UI, the dimensions of the Active Location (for Wave-based Replenishment) and Reserve/Active Locations (for Standalone and Reactive Replenishment) are validated against the dimensions of the item that is being replenished to that location.

With the flag "Perform Critical Dimension Check" checked on the replenishment rule, the values in the "Dimension Validation" field for Item/LPN will be interpreted as follows:

• For value 0 or Null, "RANDOM MATCH" logic is followed for the replenishment.
• For value 1, "HEIGHT MATCH" logic is followed for the replenishment.
• For value 2, "EXACT MATCH" logic is followed for the replenishment.

With this improved functionality in Warehouse Management, the system allows you to set alternate parameters for critical dimension validation.

Steps to Enable

• To enable Critical Dimension Checks during RF Putaway and RF IB Sorting: Set the validate-critical-dims screen parameter to Yes on these screens.

• To enable Critical Dimension Checks during Directed Putaway Location API: Set the validate_critical_dimensions_flg parameter to Yes.

• To enable Critical Dimension Checks during wave-based replenishment, standalone or reactive replenishment: Update the “Perform Critical Dimension Check” flag on the replenishment rule to checked.

Note: This feature also needs the value of item.dimension_validation_method to be populated with either 1 or 2. If the value is 0 or NULL, then critical dimension validation will happen via RANDOM MATCH logic.

Split LPN Flow for Cart-Based Putaway

The Putaway Cart process supports splitting an Inbound License Plate Number (IBLPN) across multiple active locations. This feature optimizes warehouse storage and dynamically allocates inventory based on real-time space availability.

Split IBLPN Across Multiple Locations

The system allows an IBLPN to be allocated across multiple destinations rather than a single location, improving task coordination by dynamically managing multiple tasks during putaway. This restricts overloading any single location through dynamic inventory distribution.

To Configure Split Functionality:

• Update System Settings:
  • Navigate to RF Build Putaway Cart settings.
  • Set split-lpn-mode to Split LPN Into Active Locations.
• Configure User Preferences (Optional):
  • Adjust the split-alloc-uom setting based on unit allocation needs.
  • Available options:
    • Units
    • Packs
    • Cases
    • Cases/Packs/Units

Critical Dimension Checks and Putaway Cart Compatibility

The system enforces critical dimension checks and ensures item compatibility with storage zones through advanced filtering and compatibility rules.

To Configure Critical Dimension Check:

1. In the Screen UI, configure the validate-critical-dimensions parameter for the following modules:
   • rf.inbound.cwrfputawaycart
   • rf.inbound.cwrfbuildputawaycart
2. Select the Module and click Detail.
3. Click Edit and choose the Module parm option.
4. The configuration will be updated and displayed on the Modules screen.

Note: In the Item UI, when creating an item, there is an option called "Dimension Validation Method." You can select one of the following from the drop-down list menu:

• Random Match
• Height Match
• Exact Match

The system enhances adaptability to diverse Putaway processes through task filtering and compatibility rules. By enabling concurrent task execution based on compatibility, warehouse operations improve efficiency and reduce incorrect item placements. The compatibility rule checks ensure proper alignment of inventory with specific zones and storage conditions. A broader set of columns is available for filtering tasks during creation, enabling precise inventory management.

Note:

• Upon scanning an IBLPN and placing it in the Putaway cart, the system automatically de-palletizes it to streamline task-based inventory movements. This applies to both split and non-split inventory. For split inventory, each unit is treated individually, whereas for non-split inventory, it is managed as a whole unit throughout the process.
• The automatic de-palletization process removes the pallet link to decouple inventory from the pallet, clears pallet positions for accurate storage tracking, and logs inventory movements automatically for audit and traceability. If an LPN fails the compatibility rule check, the system restricts de-palletization, ensuring accurate inventory adjustments.
• If a re-sequencing issue occurs during RF Putaway (Ctrl+K), the system displays the message: 'Resequencing for task failed.' This message appears only if LPN updates succeed but re-sequencing fails, allowing quicker troubleshooting and error resolution.