Skip to content
JDE Reference

P4210

Interactive

Sales Order Entry — the interactive application that creates and maintains F4201/F4211 orders

Lineage hook

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

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

5 parameters not filled: <catalog>, <schema_data>, <KCOO>, <DOCO>, <DCTO>

-- ============================================================
-- Program: P4210 Sales Order Entry — the interactive application that creates and maintains F4201/F4211 orders
-- Purpose: Sales Order Entry — the interactive application that creates and maintains F4201/F4211 orders — auto-generated boilerplate from program-table-map
-- Grain  : F4201 × F4211, F41021, F0101 — 1:N joins yield one row per detail line
-- Tables : F4201, F4211, F41021, F0101
-- 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.SHKCOO AS "Order key company - disambiguates order numbers across companies",
  h.SHDOCO AS "Order number",
  h.SHDCTO AS "Order type code (SO, ST, CO, ...)",
  d.SDLNID / POWER(10, 3) AS "Order line number, stored x1000 (3 implied decimals)",  -- implied decimals: 3 (verify in F9210)
  loc.LIITM AS "Short item number - the internal numeric item key",
  TRIM(loc.LIMCU) AS "Business unit / branch plant (right-justified, space-padded to 12)",
  loc.LILOCN AS "Storage location within the branch plant",
  loc.LILOTN AS "Lot or serial number",
  ab.ABAN8 AS "Address book number - the master key for any entity"
FROM <catalog>.<schema_data>.f4201 h
LEFT JOIN <catalog>.<schema_data>.f4211 d
  ON d.SDDOCO = h.SHDOCO
 AND d.SDKCOO = h.SHKCOO
 AND d.SDDCTO = h.SHDCTO
LEFT JOIN <catalog>.<schema_data>.f41021 loc
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f0101 ab
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
WHERE
  h.SHKCOO = '<KCOO>'
  AND h.SHDOCO = <DOCO>
  AND h.SHDCTO = '<DCTO>'
ORDER BY h.SHKCOO;

Tables Used by This Program

How these tables connect — join details in the list below.

Join details

  • F4201F4211header detail · 1:N
    ON f4201.SHDOCO = f4211.SDDOCO
  • F4211F0101foreign key · N:1
    ON f4211.SDAN8 = f0101.ABAN8

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.