Skip to content
JDE Reference

P4617

Interactive

Warehouse Movement Confirmations — the interactive application that confirms (or overrides and cancels) putaway, pick, and replenishment suggestions, committing the physical inventory moves

Lineage hook

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 →

Notes

Confirmation updates location detail and item location balances and writes item ledger records.

Boilerplate SQL

Databricks SQL

Starting 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.

Query parameters
-- ============================================================
-- 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 × F4602, F41021, F4111, F4600 — 1:N joins yield one row per detail line
-- Tables : F4611, F4602, F41021, F4111, 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.
-- ============================================================
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)
  f.IFITM AS "Short item number stored in the location.",
  TRIM(f.IFMCU) AS "Branch/plant (warehouse) the location belongs to.",
  f.IFLOCN AS "Warehouse location (bin) this row describes.",
  f.IFLOTN AS "Lot/serial number of the stock in the location.",
  f.IFLDSQ AS "Sequence distinguishing multiple detail rows for the same item/location/lot — the same key F4600/F4611 carry in their from/to sequence fields.",
  loc.LIITM AS "Short item number - the internal numeric item key",
  TRIM(loc.LIMCU) AS "Business unit / branch plant (right-justified, space-padded to 12)",
  loc.LILOCN AS "Storage location within the branch plant",
  loc.LILOTN AS "Lot or serial number",
  il.ILUKID AS "Unique key ID - the system-assigned surrogate key",
  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>.f4602 f
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f41021 loc
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f4111 il
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f4600 f4
  ON f4.R1RQBT = h.R2RQBT
ORDER BY h.R2SGBT;

2 parameters not filled: <catalog>, <schema_data>

Tables Used by This Program

How these tables connect. Nodes are clickable.

Join details

  • F4611F4600foreign key · N:1
    ON f4611.R2RQBT = f4600.R1RQBT