JDE Reference
P43214
InteractivePurchase 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 SQLStarting 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 — 1:N joins yield one row per detail line
-- Tables : F43121, 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: F4111, F41021 are cataloged for this program, but no verified join condition connects them to F43121, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
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"
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
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.
Loading relationship diagram…
R read · W write · R/W read + write
Secondary tables
- F41021Item location — on-hand, committed, and inbound quantities by item, branch, location, and lotRead/write accessmaster
- F4111Item ledger (Cardex) — every inventory movement with quantity, cost, and links back to source documentsWrite accesstransaction
- F4311Purchase order detail - one row per PO line with item, branch, quantities, unit/extended costs, and the status flowRead/write accesstransaction