JDE Reference
P31114
InteractiveWork Order Completions — the screen that records finished goods coming off a work order, moving completed quantity into on-hand inventory and updating order status.
Lineage hook
Rows written by P31114 carry …PID = 'P31114' 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
3 parameters not filled: <catalog>, <schema_data>, <DOCO>
-- ============================================================
-- Program: P31114 Work Order Completions — the screen that records finished goods coming off a work order, moving completed quantity into on-hand inventory and updating order status.
-- Purpose: Work Order Completions — the screen that records finished goods coming off a work order, moving completed quantity into on-hand inventory and updating order status. — auto-generated boilerplate from program-table-map
-- Grain : F4801 × F3111 — 1:N joins yield one row per detail line
-- Tables : F4801, F3111
-- 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: F41021, F4111 are cataloged for this program, but no verified join condition connects them to F4801, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
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"
FROM <catalog>.<schema_data>.f4801 h
LEFT JOIN <catalog>.<schema_data>.f3111 f
ON f.WMDOCO = h.WADOCO
WHERE
h.WADOCO = <DOCO>
ORDER BY h.WADOCO;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
- 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
- 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