Skip to content
JDE Reference

P03B102

Interactive

Standard Receipts Entry — the screen where cash receipts are entered and applied against open invoices, handling short pays, chargebacks, and unearned discounts.

Lineage hook

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

Notes

The most common manual cash application method; 9.2 update added record reservation.

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

2 parameters not filled: <catalog>, <schema_data>

-- ============================================================
-- Program: P03B102 Standard Receipts Entry — the screen where cash receipts are entered and applied against open invoices, handling short pays, chargebacks, and unearned discounts.
-- Purpose: Standard Receipts Entry — the screen where cash receipts are entered and applied against open invoices, handling short pays, chargebacks, and unearned discounts. — auto-generated boilerplate from program-table-map
-- Grain  : F03B13 × F03B14 — 1:N joins yield one row per detail line
-- Tables : F03B13, F03B14
-- 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: F03B11, F03012, F0911 are cataloged for this program, but no verified join condition connects them to F03B13, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
  h.RYPYID AS "System-assigned payment ID — the key that receipt detail rows hang off",
  h.RYALPH AS "Customer name captured at entry, handy for quick lookups without joining F0101",
  f.RZRC5 AS "Line number within the receipt — makes each application row unique"
FROM <catalog>.<schema_data>.f03b13 h
LEFT JOIN <catalog>.<schema_data>.f03b14 f
  ON f.RZPYID = h.RYPYID
ORDER BY h.RYPYID;

Tables Used by This Program

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

Loading relationship diagram…

Join details

  • F03B13F03B14header detail · 1:N
    ON f03b13.RYPYID = f03b14.RZPYID
  • F03B11F03012foreign key · N:1
    ON f03b11.RPAN8 = f03012.AIAN8
  • F03B14F03B11foreign key · N:1
    ON f03b14.RZDOC = f03b11.RPDOC

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.