P4617
InteractiveWarehouse Movement Confirmations — the interactive application that confirms (or overrides and cancels) putaway, pick, and replenishment suggestions, committing the physical inventory moves
Rows written by P4617 carry …PID = 'P4617' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
Confirmation updates location detail and item location balances and writes item ledger records.
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: P4617 Warehouse Movement Confirmations — the interactive application that confirms (or overrides and cancels) putaway, pick, and replenishment suggestions, committing the physical inventory moves
-- Purpose: Warehouse Movement Confirmations — the interactive application that confirms (or overrides and cancels) putaway, pick, and replenishment suggestions, committing the physical inventory moves — auto-generated boilerplate from program-table-map
-- Grain : F4611 × F4600 — 1:N joins yield one row per detail line
-- Tables : F4611, F4600
-- 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: F4602, F41021, F4111 are cataloged for this program, but no verified join condition connects them to F4611, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
h.R2SGBT AS "Batch number grouping suggestions from one location-driver run; first half of the suggestion key.",
h.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)
f4.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)
FROM <catalog>.<schema_data>.f4611 h
LEFT JOIN <catalog>.<schema_data>.f4600 f4
ON f4.R1RQBT = h.R2RQBT
ORDER BY h.R2SGBT;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
Secondary tables
- F41021Item location — on-hand, committed, and inbound quantities by item, branch, location, and lotRead/write accessmaster
- F4111Item ledger (Cardex) — every inventory movement with quantity, cost, and links back to source documentsWrite accesstransaction
- 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
- 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