Putwall Picks to Cart
Automatically batch putwall picks by zone, assign to cart slots based on capacity constraints, and create optimized pick work. Backend Smart Task Execution for high-volume putwall operations.
What is Putwall Picks to Cart?
Putwall Picks to Cart (STE_BE_PutwallPicksToCart) is a backend Smart Task Execution that automates the batching and assignment of putwall picks to cart slots. It finds all putwall picks for a specific zone, groups them into optimized batches based on cart capacity constraints, and creates BATCHPUTWALL work for efficient picking.
The execution processes carts with slots configured for putwall picks (ContainerUseCode = "PUTWALLS"). For each cart slot, it checks four capacity constraints: MaximumQty,MaximumWeight, StorageCubeNet, and Max_Lines(V1.6). When a slot reaches capacity, it automatically moves to the next available slot.
Smart Batching Logic
The execution selects the oldest Putwall with open picks (based on DateTimeAssigned) and locks it from other batch assignments. V1.8 adds logic to exclude putwalls withPutwall_Type='NOBATCH', allowing certain putwalls to be processed individually rather than batched.
V1.5 includes inventory verification: before batching, it checks if inventory quantity meets the work line requirements. If not, it automatically calls the allocation utility to find a new location with the same location type. V1.7 added LPN to the product key for more precise batch grouping.
Why Putwall Picks to Cart Matters
Automated batching optimizes putwall replenishment picking
Optimized Batching
Groups putwall picks by zone into efficient batches that respect cart slot capacity—qty, weight, cube, and line limits.
Putwall Locking
Locks the selected putwall during batch creation to prevent duplicate assignments from concurrent processes.
Inventory Verification
V1.5 checks inventory availability before batching. If short, automatically reallocates to a new location with same type.
Execution Flow
Backend process for automated putwall batch creation
Check Cart Configuration
Verify cart has slots with ContainerUseCode='PUTWALLS'. Load capacity limits for each slot (Qty, Weight, Cube, Lines).
Find Oldest Putwall
Select oldest putwall with open picks (DateTimeAssigned). V1.8: Exclude Putwall_Type='NOBATCH'. Lock for exclusive processing.
Get Zone Picks
Query WORK_TYPE_LINES and PUTWALL_CUBES for picks in the zone where Status='ASSIGNED' and not yet batched.
Verify Inventory
V1.5: Check inventory qty. If short, call allocationByWorkTypeLineLocationType to find new location with same type.
Batch to Cart Slots
Add picks to cart slot work. Check 4 capacity limits. When full, move to next slot. V1.7: Include LPN in product key.
Create BATCHPUTWALL Work
Write WORK_TYPE_HEADERS with WorkType='BATCHPUTWALL', Task='PICK', WorkFlowID='BATCHPUTWALL'. Assign PutwallID.
Four Capacity Constraints
Each cart slot is evaluated against four capacity limits from the CONTAINERS table. When any limit is reached, the execution moves to the next available slot.
MaximumQty
Total units that fit in the slot. Tracks QtyInSlot accumulator against container limit.
MaximumWeight
Weight limit in lbs. Calculates (Product Weight × Qty) for each pick added.
StorageCubeNet
Cubic volume limit. ProductCube = Height × Width × Length from PRODUCT_VARIABLES.
Max_Lines (V1.6)
Maximum pick lines per slot. Only checked if Max_Lines > 0 on the container.
Technical Specifications
Backend execution details and version history
Execution Configuration
STE_BE_PutwallPicksToCartBATCHPUTWALLBATCHPUTWALLSTE_BE_SinglesToCartTables Utilized
Version History
| Version | Date | Changes |
|---|---|---|
| V1.8 | 2025.05.28 | Add logic to batch works from Putwalls not having Putwall_Type='NOBATCH' |
| V1.7 | 2023.03.31 | Add LPN to the key when creating BATCHPUTWALL work |
| V1.6 | 2022.07.18 | Add logic to batch putwall pick lines to fit into container if it has set up Max_Lines > 0 |
| V1.5 | 2021.07.27 | Added logic to check inventory and re-allocation before batching order work type lines if Companies.Control03='Y' |
| V1.4 | 2016.04.26 | WorkType = PICKS |
| V1.2 | 2016.01.02 | Added PutwallID to work header |
| V1.0 | 2015.11.05 | Initial Draft |
Operational Impact
Automated batching drives efficiency and accuracy
Frequently Asked Questions
Common questions about Putwall Picks to Cart
QWhat is a Smart Task Execution (STE)?
Smart Task Executions are backend automation processes that run without user interaction. STE_BE_PutwallPicksToCart runs automatically to batch putwall picks and assign them to cart slots based on capacity constraints. The 'BE' indicates it's a Backend execution.
QHow does the execution select which putwall to process?
It selects the oldest putwall with open picks based on the DateTimeAssigned column in PUTWALL_CUBES. V1.8 adds exclusion logic: putwalls with Putwall_Type='NOBATCH' are skipped, allowing those to be processed individually rather than batched.
QWhat are the four capacity constraints?
Each cart slot is checked against: 1) MaximumQty - total units, 2) MaximumWeight - weight in lbs, 3) StorageCubeNet - cubic volume, and 4) Max_Lines - number of pick lines (V1.6). These are defined in the CONTAINERS table for each container assigned to cart slots.
QWhat happens when a cart slot reaches capacity?
When any of the four capacity limits is reached, the execution clears its accumulators (QtyInSlot, WeightInSlot, CubeInSlot, LinesInSlot) and moves to the next available cart slot. If no more slots are available, the execution ends.
QHow does inventory verification work (V1.5)?
If Companies.Control03='Y', the execution checks if INVENTORY_LEVELS.Quantity meets WORK_TYPE_LINES.Quantity_Required. If short, it calls allocationByWorkTypeLineLocationType to find a new location with the same location type and updates the work line with the new Area/Location.
QWhat is the NOBATCH putwall type (V1.8)?
Putwalls with Putwall_Type='NOBATCH' are excluded from batch processing. This allows certain putwalls to be processed individually through other workflows rather than being combined into batch picks. Useful for special handling or priority orders.
QWhy was LPN added to the product key (V1.7)?
Adding LPN to the product key ensures that picks from different LPNs are tracked separately even if they're for the same product/quality combination. This provides more precise batch grouping and better traceability in operations where LPN-level tracking is important.
QWhat work type does this execution create?
It creates work with WorkType='BATCHPUTWALL', Task='PICK', and WorkFlowID='BATCHPUTWALL'. The work headers include the PutwallID being processed. Work lines are created for each pick with Status='WORKING' and grouped by product key including LPN.
Ready to Automate Putwall Batching?
See how JASCI's Smart Task Executions optimize your putwall fulfillment operations.