Skip to content
JDE Reference

F4801

transactionAlso in JDE World

Work order header — one row per work order carrying the item being made, branch, quantities ordered/completed/scrapped, status, and the requested/start/completion dates that drive shop floor and maintenance analytics

Notes

erpref lists it under system 48 (Work Order Processing) as a 'Master File', but each row is an order document, so treat it as a transaction table. Manufacturing-specific extras live in the 1:1 tag table F4801T (same WADOCO key). All dates are Julian CYYDDD.

What the badges mean
Superseded
Superseded — a newer table has replaced it, but older scripts still read this one.
Also in JDE World
Also present in JDE World A9.x on the same table name.
master
Data class: what the table holds — master data, transaction documents, control/setup values, history, or a workfile.
Read/write access
Access mode: how the paired program reads or writes this table — R (read), W (write), or R/W (both).
No lifecycle badge means the table is current and not documented in JDE World. In field listings, K marks a primary-key field.
Used in the library

Fields

42 fields · 1 key

42 fields.

Table fields: key flag, field name, DD alias, description, data type, length, and quirk flags (Julian date, implied decimals, padded string, UDC decode). 42 fields.
KeyFieldAliasDescriptionTypeLengthFlags
WADCTODCTOOrder type — WO for manufacturing work orders; filter on this plus TYPS to separate manufacturing from maintenance and service ordersString2
Primary keyWADOCODOCOWork order number — the single primary key; join target for F3111 parts list, F3112 routing, and F4801T tag rowsNumeric8
WASFXOSFXOOrder suffix — part of the standard JDE document trio (DOCO/DCTO/SFXO); usually blank or 000 on work ordersString3
WARCTORCTORelated order type — order type of the sales order or parent document this work order was generated forString2
WARORNRORNRelated order number — links a make-to-order WO back to its sales order; stored as an 8-character string, not numericString8
WALNIDLNIDRelated order line number — pairs with RORN/RCTO to point at the exact sales order line; 3 implied decimals (line 1.000 stored as 1000)Numeric6
WAPARSPARSParent work order number — non-blank on child orders in multi-level or ETO work order structures; stored as a stringString8
WATYPSTYPSWork order type — one-character classifier separating manufacturing, equipment/maintenance, and service work ordersCharacter1
WAPRTSPRTSWork order priority codeCharacter1
WADL01DL01Work order description — free text, handy as a label in dashboardsString30
WACOCOCompany the work order belongs toString5
WAMCUMCUCharge-to business unit — right-justified 12-character; TRIM before joining or groupingString12
WAMMCUMMCUBranch/plant where the order is produced — the usual plant dimension for WO analytics; right-justified 12-characterString12
WASRSTSRSTCurrent work order status — the lifecycle field (created, released, on shop floor, complete, closed); status ranges are install-specificString2
WAAN8AN8Address book number tied to the order — customer on make-to-order work, blank on many make-to-stock ordersNumeric8
WAANPANPAssigned-to address number — typically the planner or lead responsible for the orderNumeric8
WADPLDPLPlanned completion date (Julian CYYDDD)Numeric (DD type: Date)6
WATRDJTRDJOrder date — when the work order was entered (Julian CYYDDD)Numeric (DD type: Date)6
WASTRTSTRTPlanned start date (Julian CYYDDD) — backscheduled from the requested date using routing leadtimesNumeric (DD type: Date)6
WADRQJDRQJRequested date — when the finished quantity is needed (Julian CYYDDD); the anchor for on-time completion metricsNumeric (DD type: Date)6
WASTRXSTRXActual completion date (Julian CYYDDD) — populated at full completion; compare to DRQJ for schedule attainmentNumeric (DD type: Date)6
WAWR01WR01Work order category code 01 — commonly used as the phase code; one of ten site-defined WO category codesString4
WAAMTOAMTOEstimated total cost of the order; 2 implied decimalsNumeric15
WAHRSOHRSOEstimated hours for the order; 2 implied decimalsNumeric15
WAAMTAAMTAActual total cost charged to the order; 2 implied decimals — compare to AMTO for cost varianceNumeric15
WAHRSAHRSAActual hours charged to the order; 2 implied decimalsNumeric15
WAITMITMShort item number of the parent item being produced — join to F4101/F4102Numeric8
WALITMLITMSecond (customer-facing) item number of the item being producedString25
WAUORGUORGQuantity ordered — how much the work order is supposed to produceNumeric15
WASOBKSOBKQuantity backordered or held against the orderNumeric15
WASOCNSOCNQuantity canceled or scrapped on the order — pairs with SOQS for yield analysisNumeric15
WASOQSSOQSQuantity completed to stock — updated by work order completions; UORG minus SOQS minus SOCN gives the open quantityNumeric15
WAQTYTQTYTCumulative quantity completed/shipped to date — used mainly in rate/repetitive schedulesNumeric15
WAUOMUOMUnit of measure the order quantities are expressed inString2
WATBMTBMBill of material type used when the parts list was attached (e.g. M for manufacturing)String3
WATRTTRTRouting type used when the routing was attachedString3
WALOTNLOTNLot/serial number produced by the order — key for lot genealogy in regulated industriesString30
WANTSTNTSTNext expected status in the order's workflowString2
WAAMLCAMLCEstimated labor cost; 2 implied decimalsNumeric15
WAAMMCAMMCEstimated material cost; 2 implied decimalsNumeric15
WALBAMLBAMActual labor cost charged; 2 implied decimals — with AMLC gives labor cost varianceNumeric15
WAMTAMMTAMActual material cost charged; 2 implied decimals — with AMMC gives material cost varianceNumeric15

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading F4801 on Databricks — Julian dates, implied decimals, and padded strings are already converted. Set your Unity Catalog location and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

5 parameters not filled: <catalog>, <schema_data>, <DOCO>, <TRDJ_FROM>, <TRDJ_TO>

-- ============================================================
-- Table  : F4801 Work order header — one row per work order carrying the item being made, branch, quantities ordered/completed/scrapped, status, and the requested/start/completion dates that drive shop floor and maintenance analytics
-- Purpose: Column-selected read of F4801 — auto-generated from field metadata
-- Grain  : One row per WADOCO
-- Notes  : Auto-generated skeleton. Julian dates (CYYDDD) are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210); padded business-unit/UDC keys are TRIMmed. 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
  f.WADOCO AS "Work order number — the single primary key; join target for F3111 parts list, F3112 routing, and F4801T tag rows",
  f.WADCTO AS "Order type — WO for manufacturing work orders; filter on this plus TYPS to separate manufacturing from maintenance and service orders",
  f.WASFXO AS "Order suffix — part of the standard JDE document trio (DOCO/DCTO/SFXO); usually blank or 000 on work orders",
  f.WARCTO AS "Related order type — order type of the sales order or parent document this work order was generated for",
  f.WARORN AS "Related order number — links a make-to-order WO back to its sales order; stored as an 8-character string, not numeric",
  f.WALNID / POWER(10, 3) AS "Related order line number — pairs with RORN/RCTO to point at the exact sales order line; 3 implied decimals (line 1.000 stored as 1000)",  -- implied decimals: 3 (verify in F9210)
  f.WAPARS AS "Parent work order number — non-blank on child orders in multi-level or ETO work order structures; stored as a string",
  f.WATYPS AS "Work order type — one-character classifier separating manufacturing, equipment/maintenance, and service work orders",
  f.WAPRTS AS "Work order priority code",
  f.WADL01 AS "Work order description — free text, handy as a label in dashboards",
  f.WACO AS "Company the work order belongs to",
  TRIM(f.WAMCU) AS "Charge-to business unit — right-justified 12-character; TRIM before joining or grouping",
  TRIM(f.WAMMCU) AS "Branch/plant where the order is produced — the usual plant dimension for WO analytics; right-justified 12-character",
  f.WASRST AS "Current work order status — the lifecycle field (created, released, on shop floor, complete, closed); status ranges are install-specific",
  f.WAAN8 AS "Address book number tied to the order — customer on make-to-order work, blank on many make-to-stock orders",
  f.WAANP AS "Assigned-to address number — typically the planner or lead responsible for the order",
  CASE WHEN f.WADPL IS NULL OR f.WADPL = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.WADPL AS INT) DIV 1000, 1, 1), CAST(f.WADPL AS INT) % 1000 - 1) END AS "Planned completion date (Julian CYYDDD)",  -- CYYDDD Julian → DATE
  CASE WHEN f.WATRDJ IS NULL OR f.WATRDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.WATRDJ AS INT) DIV 1000, 1, 1), CAST(f.WATRDJ AS INT) % 1000 - 1) END AS "Order date — when the work order was entered (Julian CYYDDD)",  -- CYYDDD Julian → DATE
  CASE WHEN f.WASTRT IS NULL OR f.WASTRT = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.WASTRT AS INT) DIV 1000, 1, 1), CAST(f.WASTRT AS INT) % 1000 - 1) END AS "Planned start date (Julian CYYDDD) — backscheduled from the requested date using routing leadtimes",  -- CYYDDD Julian → DATE
  CASE WHEN f.WADRQJ IS NULL OR f.WADRQJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.WADRQJ AS INT) DIV 1000, 1, 1), CAST(f.WADRQJ AS INT) % 1000 - 1) END AS "Requested date — when the finished quantity is needed (Julian CYYDDD); the anchor for on-time completion metrics",  -- CYYDDD Julian → DATE
  CASE WHEN f.WASTRX IS NULL OR f.WASTRX = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.WASTRX AS INT) DIV 1000, 1, 1), CAST(f.WASTRX AS INT) % 1000 - 1) END AS "Actual completion date (Julian CYYDDD) — populated at full completion; compare to DRQJ for schedule attainment",  -- CYYDDD Julian → DATE
  f.WAWR01 AS "Work order category code 01 — commonly used as the phase code; one of ten site-defined WO category codes",
  f.WAAMTO / POWER(10, 2) AS "Estimated total cost of the order; 2 implied decimals",  -- implied decimals: 2 (verify in F9210)
  f.WAHRSO / POWER(10, 2) AS "Estimated hours for the order; 2 implied decimals",  -- implied decimals: 2 (verify in F9210)
  f.WAAMTA / POWER(10, 2) AS "Actual total cost charged to the order; 2 implied decimals — compare to AMTO for cost variance",  -- implied decimals: 2 (verify in F9210)
  f.WAHRSA / POWER(10, 2) AS "Actual hours charged to the order; 2 implied decimals",  -- implied decimals: 2 (verify in F9210)
  f.WAITM AS "Short item number of the parent item being produced — join to F4101/F4102",
  f.WALITM AS "Second (customer-facing) item number of the item being produced",
  f.WAUORG AS "Quantity ordered — how much the work order is supposed to produce",
  f.WASOBK AS "Quantity backordered or held against the order",
  f.WASOCN AS "Quantity canceled or scrapped on the order — pairs with SOQS for yield analysis",
  f.WASOQS AS "Quantity completed to stock — updated by work order completions; UORG minus SOQS minus SOCN gives the open quantity",
  f.WAQTYT AS "Cumulative quantity completed/shipped to date — used mainly in rate/repetitive schedules",
  f.WAUOM AS "Unit of measure the order quantities are expressed in",
  f.WATBM AS "Bill of material type used when the parts list was attached (e.g. M for manufacturing)",
  f.WATRT AS "Routing type used when the routing was attached",
  f.WALOTN AS "Lot/serial number produced by the order — key for lot genealogy in regulated industries",
  f.WANTST AS "Next expected status in the order's workflow",
  f.WAAMLC / POWER(10, 2) AS "Estimated labor cost; 2 implied decimals",  -- implied decimals: 2 (verify in F9210)
  f.WAAMMC / POWER(10, 2) AS "Estimated material cost; 2 implied decimals"  -- implied decimals: 2 (verify in F9210)
  -- … plus 2 more columns — full list in the Fields section above
FROM <catalog>.<schema_data>.f4801 f
WHERE
  f.WADOCO = <DOCO>
  -- AND f.WATRDJ >= <TRDJ_FROM>  -- Julian CYYDDD, e.g. 126001
  -- AND f.WATRDJ <= <TRDJ_TO>  -- Julian CYYDDD, e.g. 126365
ORDER BY f.WADOCO;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. UDC decode edges point coded fields at their F0005 lookup.

Join details

  • F4801F3111header detail · 1:N
    ON f4801.WADOCO = f3111.WMDOCO
  • F4801F3112header detail · 1:N
    ON f4801.WADOCO = f3112.WLDOCO
  • F4801F3102header detail · 1:N
    ON f4801.WADOCO = f3102.IGDOCO
  • F4801TF4801foreign key · 1:1
    ON f4801t.WADOCO = f4801.WADOCO
  • F3411F4801foreign key · N:1
    ON f3411.MMDOCO = f4801.WADOCO
  • F3412F4801foreign key · N:1
    ON f3412.MWDOCO = f4801.WADOCO
  • F4801F0005UDC decode · N:1
    ON f0005.DRSY = '00' AND f0005.DRRT = 'SS' AND TRIM(f0005.DRKY) = TRIM(f4801.WASRST)

Programs That Use This Table

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

Primary programs

Secondary programs

More Work Order Processing 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.