P03B102
InteractiveStandard Receipts Entry — the screen where cash receipts are entered and applied against open invoices, handling short pays, chargebacks, and unearned discounts.
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
The most common manual cash application method; 9.2 update added record reservation.
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.
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…
R read · W write · R/W read + write
Primary tables
- F03B13Receipts header: one row per customer receipt or draft with the check amount, unapplied balance, bank account, and G/L batch identity.Read/write accesstransaction
- F03B14Receipts detail: one row per application of a receipt against an invoice pay item, splitting the cash into payment, discount, write-off, chargeback, and deduction amounts.Read/write accesstransaction
Secondary tables
- F03012Customer master by line of business: one row per customer address number and company holding A/R credit terms, collection settings, sales defaults, and rolled-up invoice history.Read accessmaster
- F03B11Customer ledger: one row per invoice pay item carrying gross, open, discount, and tax amounts plus the dates and status codes that drive A/R aging and collections.Read/write accesstransaction
- F0911General ledger transaction detail: every journal entry line with its account, G/L date, amount, batch, subledger, and source-document references.Write accesstransaction