R46171
Batch UBELocation Selection Driver — the batch engine that processes open putaway, picking, and replenishment requests and creates location suggestions using movement instructions, item profiles, and location capacity
Rows written by R46171 carry …PID = 'R46171' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
One UBE run in different versions for putaway, pick, and replenishment request processing — the core Warehouse Management algorithm.
Boilerplate SQL
Databricks SQLStarting point for querying the tables behind this program. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
2 parameters not filled: <catalog>, <schema_data>
-- ============================================================
-- Program: R46171 Location Selection Driver — the batch engine that processes open putaway, picking, and replenishment requests and creates location suggestions using movement instructions, item profiles, and location capacity
-- Purpose: Location Selection Driver — the batch engine that processes open putaway, picking, and replenishment requests and creates location suggestions using movement instructions, item profiles, and location capacity — auto-generated boilerplate from program-table-map
-- Grain : F4600 × F4611 — 1:N joins yield one row per detail line
-- Tables : F4600, F4611
-- Notes : Auto-generated skeleton. Julian dates are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210). Audit columns (…USER/…PID/…UPMJ) are omitted — see the quirks guide. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- Omitted: F46010, F46011, F4602, F41021 are cataloged for this program, but no verified join condition connects them to F4600, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
h.R1RQBT AS "Batch number grouping requests created in the same run; first half of the request key.",
h.R1RQSQ / POWER(10, 3) AS "Line sequence of the request within its batch; second half of the request key.", -- implied decimals: 3 (verify in F9210)
f.R2SGBT AS "Batch number grouping suggestions from one location-driver run; first half of the suggestion key.",
f.R2SGSQ / POWER(10, 3) AS "Line sequence of the suggestion within its batch; second half of the suggestion key." -- implied decimals: 3 (verify in F9210)
FROM <catalog>.<schema_data>.f4600 h
LEFT JOIN <catalog>.<schema_data>.f4611 f
ON f.R2RQBT = h.R1RQBT
ORDER BY h.R1RQBT;Tables Used by This Program
How these tables connect — join details in the list below.
Loading relationship diagram…
R read · W write · R/W read + write
Primary tables
- F4600One row per requested warehouse movement — the demand side of WMS: a putaway, pick, or replenishment waiting for the system to decide where stock should move.Read/write accesstransaction
- F4611One row per system-generated movement suggestion answering an F4600 request: the proposed from/to location, quantity, cube and weight charged, and wave/task assignment.Write accesstransaction
Secondary tables
- F41021Item location — on-hand, committed, and inbound quantities by item, branch, location, and lotRead accessmaster
- F46010Item warehouse profile: one row per branch/item holding WMS handling rules — mixing, one- vs two-phase movement, and the item's fixed special-purpose locations.Read accessmaster
- F46011Item unit-of-measure definition for WMS: one row per branch, item or dimension group, and UOM carrying physical dimensions, weight, cube, container, and stacking rules the capacity engine uses.Read accessmaster
- F4602Warehouse-managed contents of each location: one row per item/lot/UOM-structure detail with on-hand, committed, inbound/outbound quantities, and the cube and weight consumed.Read/write accessmaster