Skip to content
JDE Reference

P43214

Interactive

Purchase Receipts Inquiry — review open and historical receipt records and reverse receipts when needed

Lineage hook

Rows written by P43214 carry …PID = 'P43214' 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

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

-- ============================================================
-- Program: P43214 Purchase Receipts Inquiry — review open and historical receipt records and reverse receipts when needed
-- Purpose: Purchase Receipts Inquiry — review open and historical receipt records and reverse receipts when needed — auto-generated boilerplate from program-table-map
-- Grain  : F43121 × F4311, F4111, F41021 — 1:N joins yield one row per detail line
-- Tables : F43121, F4311, F4111, F41021
-- 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.PRMATC AS "Match record type - separates receipt rows from voucher-match rows",
  h.PRDOCO AS "Order number",
  h.PRDCTO AS "Order document type (e.g. OP purchase order, SO sales order)",
  h.PRKCOO AS "Company that owns the order-number sequence; part of the composite order key",
  h.PRSFXO AS "Order suffix distinguishing multiple documents under one order number",
  h.PRLNID / POWER(10, 3) AS "Order line number (3 implied decimals, e.g. 1.000)",  -- implied decimals: 3 (verify in F9210)
  h.PRNLIN AS "Sequence number of this receipt/match event against the PO line",
  h.PRDOC AS "Voucher document number created by the match",
  il.ILUKID AS "Unique key ID - the system-assigned surrogate key",
  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"
FROM <catalog>.<schema_data>.f43121 h
LEFT JOIN <catalog>.<schema_data>.f4311 d
  ON d.PDDOCO = h.PRDOCO
 AND d.PDKCOO = h.PRKCOO
 AND d.PDDCTO = h.PRDCTO
 AND d.PDSFXO = h.PRSFXO
 AND d.PDLNID = h.PRLNID
LEFT JOIN <catalog>.<schema_data>.f4111 il
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f41021 loc
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
WHERE
  h.PRDOCO = <DOCO>
  AND h.PRDCTO = '<DCTO>'
  AND h.PRKCOO = '<KCOO>'
  AND h.PRDOC = <DOC>
ORDER BY h.PRDOCO;

Tables Used by This Program

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

Join details

  • F43121F4311foreign key · N:1
    ON f43121.PRDOCO = f4311.PDDOCO

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.