Skip to content
JDE Reference

F4209

transactionAlso in JDE World

Held orders file - one row per order or line currently or previously on hold, including who released it and when

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
KPI definitions
Dashboard patterns

Fields

27 fields · 11 key

27 fields.

Table fields: key flag, field name, DD alias, description, data type, length, and quirk flags (Julian date, implied decimals, padded string, UDC decode). 27 fields.
KeyFieldAliasDescriptionTypeLengthFlags
Primary keyHOHCODHCODHold code placed on the orderString2
Primary keyHODCTODCTOOrder document type (e.g. OP purchase order, SO sales order)String2
Primary keyHODOCODOCOOrder numberNumeric8
Primary keyHOKCOOKCOOCompany that owns the order-number sequence; part of the composite order keyString5
Primary keyHOSFXOSFXOOrder suffix distinguishing multiple documents under one order numberString3
Primary keyHOLNIDLNIDOrder line number (3 implied decimals, e.g. 1.000)Numeric6
Primary keyHODLNIDDLNIDDistribution line number the hold applies toNumeric6
Primary keyHORDJRDJDate the hold was releasedNumeric (DD type: Date)6
Primary keyHORDTRDTTime the hold was releasedNumeric6
Primary keyHOASTSASTSApproval status of the held orderString2
Primary keyHORPERRPERAddress number of the person responsible for reviewing the holdNumeric8
HOAN8AN8Address book number of the customer or supplier on the held orderNumeric8
HOMCUMCUBranch/plant business unit; right-justified, space-padded to 12String12
HOITMITMShort internal item number - joins to F4101/F4102Numeric8
HOLITMLITMSecond item number, the long code users normally keyString25
HOAITMAITMThird item number (catalog or alternate identifier)String25
HOTRDJTRDJOrder date of the held documentNumeric (DD type: Date)6
HODRQJDRQJRequested date on the held orderNumeric (DD type: Date)6
HOPDDJPDDJScheduled pick/delivery date on the held orderNumeric (DD type: Date)6
HOCTYPCTYPCode type qualifying what kind of hold this isString2
HORDCRDCRelease code recorded when the hold is liftedString2
HORDBRDBUser who released the holdString10
HOARTGARTGApproval routing code for approval-hold processingString12
HOATYATYType of approver requiredCharacter1
HOEDEIEDEIEDI discrepancy error identifierString4
HOPA8PA8Parent address book numberNumeric8
HOSHANSHANShip-to address book numberNumeric8

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading F4209 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

7 parameters not filled: <catalog>, <schema_data>, <DCTO>, <DOCO>, <KCOO>, <TRDJ_FROM>, <TRDJ_TO>

-- ============================================================
-- Table  : F4209 Held orders file - one row per order or line currently or previously on hold, including who released it and when
-- Purpose: Column-selected read of F4209 — auto-generated from field metadata
-- Grain  : One row per HOHCOD + HODCTO + HODOCO + HOKCOO + HOSFXO + HOLNID + HODLNID + HORDJ + HORDT + HOASTS + HORPER
-- 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.HOHCOD AS "Hold code placed on the order",
  f.HODCTO AS "Order document type (e.g. OP purchase order, SO sales order)",
  f.HODOCO AS "Order number",
  f.HOKCOO AS "Company that owns the order-number sequence; part of the composite order key",
  f.HOSFXO AS "Order suffix distinguishing multiple documents under one order number",
  f.HOLNID / POWER(10, 3) AS "Order line number (3 implied decimals, e.g. 1.000)",  -- implied decimals: 3 (verify in F9210)
  f.HODLNID / POWER(10, 3) AS "Distribution line number the hold applies to",  -- implied decimals: 3 (verify in F9210)
  CASE WHEN f.HORDJ IS NULL OR f.HORDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.HORDJ AS INT) DIV 1000, 1, 1), CAST(f.HORDJ AS INT) % 1000 - 1) END AS "Date the hold was released",  -- CYYDDD Julian → DATE
  f.HORDT AS "Time the hold was released",
  f.HOASTS AS "Approval status of the held order",
  f.HORPER AS "Address number of the person responsible for reviewing the hold",
  f.HOAN8 AS "Address book number of the customer or supplier on the held order",
  TRIM(f.HOMCU) AS "Branch/plant business unit; right-justified, space-padded to 12",
  f.HOITM AS "Short internal item number - joins to F4101/F4102",
  f.HOLITM AS "Second item number, the long code users normally key",
  f.HOAITM AS "Third item number (catalog or alternate identifier)",
  CASE WHEN f.HOTRDJ IS NULL OR f.HOTRDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.HOTRDJ AS INT) DIV 1000, 1, 1), CAST(f.HOTRDJ AS INT) % 1000 - 1) END AS "Order date of the held document",  -- CYYDDD Julian → DATE
  CASE WHEN f.HODRQJ IS NULL OR f.HODRQJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.HODRQJ AS INT) DIV 1000, 1, 1), CAST(f.HODRQJ AS INT) % 1000 - 1) END AS "Requested date on the held order",  -- CYYDDD Julian → DATE
  CASE WHEN f.HOPDDJ IS NULL OR f.HOPDDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.HOPDDJ AS INT) DIV 1000, 1, 1), CAST(f.HOPDDJ AS INT) % 1000 - 1) END AS "Scheduled pick/delivery date on the held order",  -- CYYDDD Julian → DATE
  f.HOCTYP AS "Code type qualifying what kind of hold this is",
  f.HORDC AS "Release code recorded when the hold is lifted",
  f.HORDB AS "User who released the hold",
  f.HOARTG AS "Approval routing code for approval-hold processing",
  f.HOATY AS "Type of approver required",
  f.HOEDEI AS "EDI discrepancy error identifier",
  f.HOPA8 AS "Parent address book number",
  f.HOSHAN AS "Ship-to address book number"
FROM <catalog>.<schema_data>.f4209 f
WHERE
  f.HODCTO = '<DCTO>'
  -- AND f.HODOCO = <DOCO>
  -- AND f.HOKCOO = '<KCOO>'
  -- AND f.HOTRDJ >= <TRDJ_FROM>  -- Julian CYYDDD, e.g. 126001
  -- AND f.HOTRDJ <= <TRDJ_TO>  -- Julian CYYDDD, e.g. 126365
ORDER BY f.HOHCOD;

Verified September 2026

Relationships

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

Join details

  • F4209F4201foreign key · N:1
    ON f4209.HODOCO = f4201.SHDOCO

Programs That Use This Table

No program mappings populated for this table yet.

Browse more 42 tables

More Sales Order Management 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.