JDE Reference
P4600
InteractiveRequest Inquiry — the interactive application for reviewing putaway, picking, and replenishment requests, checking their status, and creating or canceling suggestions manually
Lineage hook
Rows written by P4600 carry …PID = 'P4600' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide →
Notes
Also called the manual planner for warehouse movement requests.
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.
Query parameters
-- ============================================================
-- Program: P4600 Request Inquiry — the interactive application for reviewing putaway, picking, and replenishment requests, checking their status, and creating or canceling suggestions manually
-- Purpose: Request Inquiry — the interactive application for reviewing putaway, picking, and replenishment requests, checking their status, and creating or canceling suggestions manually — auto-generated boilerplate from program-table-map
-- Grain : F4600 × F4611, F4602, F41021 — 1:N joins yield one row per detail line
-- Tables : F4600, F4611, F4602, F41021
-- 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.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)
f4.IFITM AS "Short item number stored in the location.",
TRIM(f4.IFMCU) AS "Branch/plant (warehouse) the location belongs to.",
f4.IFLOCN AS "Warehouse location (bin) this row describes.",
f4.IFLOTN AS "Lot/serial number of the stock in the location.",
f4.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"
FROM <catalog>.<schema_data>.f4600 h
LEFT JOIN <catalog>.<schema_data>.f4611 f
ON f.R2RQBT = h.R1RQBT
LEFT JOIN <catalog>.<schema_data>.f4602 f4
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)
ORDER BY h.R1RQBT;2 parameters not filled: <catalog>, <schema_data>
Tables Used by This Program
How these tables connect. Nodes are clickable.
Secondary tables
- F41021Item location — on-hand, committed, and inbound quantities by item, branch, location, and lotRead 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 accessmaster
- 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.Read accesstransaction