Skip to content
JDE Reference

P4310

Interactive

Purchase Order Entry — create and revise purchase orders, requisitions, and quotes (header and detail lines)

Lineage hook

Rows written by P4310 carry …PID = 'P4310' 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: P4310 Purchase Order Entry — create and revise purchase orders, requisitions, and quotes (header and detail lines)
-- Purpose: Purchase Order Entry — create and revise purchase orders, requisitions, and quotes (header and detail lines) — auto-generated boilerplate from program-table-map
-- Grain  : F4301 × F4311 — 1:N joins yield one row per detail line
-- Tables : F4301, F4311
-- 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: F0101, F0401, F4101, F4102, F4105, F41061, F0014 are cataloged for this program, but no verified join condition connects them to F4301, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
  h.PHKCOO AS "Company that owns the order-number sequence; part of the composite order key",
  h.PHDOCO AS "Order number",
  h.PHDCTO AS "Order document type (e.g. OP purchase order, SO sales order)",
  h.PHSFXO AS "Order suffix distinguishing multiple documents under one order number",
  d.PDLNID / POWER(10, 3) AS "Order line number (3 implied decimals, e.g. 1.000)"  -- implied decimals: 3 (verify in F9210)
FROM <catalog>.<schema_data>.f4301 h
LEFT JOIN <catalog>.<schema_data>.f4311 d
  ON d.PDDOCO = h.PHDOCO
 AND d.PDKCOO = h.PHKCOO
 AND d.PDDCTO = h.PHDCTO
 AND d.PDSFXO = h.PHSFXO
WHERE
  h.PHKCOO = '<KCOO>'
  AND h.PHDOCO = <DOCO>
  AND h.PHDCTO = '<DCTO>'
ORDER BY h.PHKCOO;

Tables Used by This Program

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

Loading relationship diagram…

Join details

  • F4102F4101foreign key · N:1
    ON f4102.IBITM = f4101.IMITM
  • F4301F4311header detail · 1:N
    ON f4301.PHDOCO = f4311.PDDOCO
  • F4311F0401foreign key · N:1
    ON f4311.PDAN8 = f0401.A6AN8
  • F4311F4101foreign key · N:1
    ON f4311.PDITM = f4101.IMITM
  • F4311F0101foreign key · N:1
    ON f4311.PDAN8 = f0101.ABAN8
  • F41061F4101foreign key · N:1
    ON f41061.CBITM = f4101.IMITM
  • F41061F0401foreign key · N:1
    ON f41061.CBAN8 = f0401.A6AN8
  • F0401F0101foreign key · 1:1
    ON f0401.A6AN8 = f0101.ABAN8
  • F4105F4102foreign key · N:1
    ON f4105.COITM = f4102.IBITM

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

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.