Skip to content
JDE Reference

R31410

Batch UBE

Order Processing — the batch job that attaches the parts list and routing to work orders, commits inventory, and prints shop floor paperwork in one pass.

Lineage hook

Rows written by R31410 carry …PID = 'R31410' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide

Notes

Copies the standard BOM (F3002) and routing (F3003) into work-order-specific F3111/F3112 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

3 parameters not filled: <catalog>, <schema_data>, <DOCO>

-- ============================================================
-- Program: R31410 Order Processing — the batch job that attaches the parts list and routing to work orders, commits inventory, and prints shop floor paperwork in one pass.
-- Purpose: Order Processing — the batch job that attaches the parts list and routing to work orders, commits inventory, and prints shop floor paperwork in one pass. — auto-generated boilerplate from program-table-map
-- Grain  : F4801 × F3111, F3112 — 1:N joins yield one row per detail line
-- Tables : F4801, F3111, F3112
-- 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: F3002, F3003, F41021 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",
  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"
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
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…

Join details

  • F4801F3111header detail · 1:N
    ON f4801.WADOCO = f3111.WMDOCO
  • F4801F3112header detail · 1:N
    ON f4801.WADOCO = f3112.WLDOCO

R read · W write · R/W read + write

Primary tables

Secondary tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle, JD Edwards, and EnterpriseOne are registered trademarks of Oracle and/or its affiliates.