JDE Reference
P31123
InteractiveSuper Backflush — the screen that reports completions at pay points and backflushes material issues and labor for all prior operations in one transaction.
Lineage hook
Rows written by P31123 carry …PID = 'P31123' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide →
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: P31123 Super Backflush — the screen that reports completions at pay points and backflushes material issues and labor for all prior operations in one transaction.
-- Purpose: Super Backflush — the screen that reports completions at pay points and backflushes material issues and labor for all prior operations in one transaction. — auto-generated boilerplate from program-table-map
-- Grain : F4801 × F3111, F3112, F4111 — 1:N joins yield one row per detail line
-- Tables : F4801, F3111, F3112, F4111
-- 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.WADOCO AS "Work order number — the single primary key; join target for F3111 parts list, F3112 routing, and F4801T tag rows",
h.WADL01 AS "Work order description — free text, handy as a label in dashboards",
f.WMUKID AS "Internal unique key — the table's single-column primary key; carries no business meaning",
TRIM(f3.WLMCU) AS "Work center business unit performing the operation — part of the composite primary key; right-justified 12-character",
f3.WLOPSQ / POWER(10, 2) AS "Operation sequence number — orders the routing steps and is the join target for F3111 components; part of the primary key; 2 implied decimals (op 10 stored as 1000)", -- implied decimals: 2 (verify in F9210)
f3.WLOPSC AS "Operation type code — part of the primary key; distinguishes duplicate sequence numbers",
il.ILUKID AS "Unique key ID - the system-assigned surrogate key"
FROM <catalog>.<schema_data>.f4801 h
LEFT JOIN <catalog>.<schema_data>.f3111 f
ON f.WMDOCO = h.WADOCO
LEFT JOIN <catalog>.<schema_data>.f3112 f3
ON f3.WLDOCO = h.WADOCO
LEFT JOIN <catalog>.<schema_data>.f4111 il
ON 1 = 1 -- TODO: define join condition (no shared aliases detected)
WHERE
h.WADOCO = <DOCO>
ORDER BY h.WADOCO;3 parameters not filled: <catalog>, <schema_data>, <DOCO>
Tables Used by This Program
How these tables connect. Nodes are clickable.
Secondary tables
- F3111Work order parts list — one row per component required by a work order, with required vs. issued quantities, scrap, commitments, and the operation each part feedsRead/write accesstransaction
- F3112Work order routing — one row per operation on a work order, carrying the work center, standard vs. actual machine/labor/setup hours, and quantities completed or scrapped at each stepRead/write accesstransaction
- F4111Item ledger (Cardex) — every inventory movement with quantity, cost, and links back to source documentsWrite accesstransaction