JDE Reference
P03B2002
InteractiveCustomer Ledger Inquiry — the screen for researching a customer's invoice history: open items, payment status, and drill-down into receipts and G/L detail.
Lineage hook
Rows written by P03B2002 carry …PID = 'P03B2002' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide →
Notes
Also the entry point for adding and revising invoices (calls Standard Invoice Entry P03B11).
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
-- ============================================================
-- Program: P03B2002 Customer Ledger Inquiry — the screen for researching a customer's invoice history: open items, payment status, and drill-down into receipts and G/L detail.
-- Purpose: Customer Ledger Inquiry — the screen for researching a customer's invoice history: open items, payment status, and drill-down into receipts and G/L detail. — auto-generated boilerplate from program-table-map
-- Grain : F03B11 × F03B14, F03012, F0101 — 1:N joins yield one row per detail line
-- Tables : F03B11, F03B14, F03012, F0101
-- 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.RPDOC AS "Invoice document number",
h.RPDCT AS "Invoice document type (RI standard invoice, RM credit memo, RU unapplied cash, etc.)",
h.RPKCO AS "Document company that owns the invoice number sequence",
h.RPSFX AS "Pay item — one invoice can split into multiple pay items with their own terms",
h.RPADSC / POWER(10, 2) AS "Discount offered to the customer if paid by the discount due date", -- implied decimals: 2 (verify in F9210)
f.RZPYID AS "Payment ID linking back to the F03B13 receipt header",
f.RZRC5 AS "Line number within the receipt — makes each application row unique",
f0.AICO AS "Company this customer record applies to; company 00000 holds the default line-of-business record"
FROM <catalog>.<schema_data>.f03b11 h
LEFT JOIN <catalog>.<schema_data>.f03b14 f
ON f.RZDOC = h.RPDOC
LEFT JOIN <catalog>.<schema_data>.f03012 f0
ON f0.AIAN8 = h.RPAN8
LEFT JOIN <catalog>.<schema_data>.f0101 ab
ON ab.ABAN8 = h.RPAN8
ORDER BY h.RPDOC;2 parameters not filled: <catalog>, <schema_data>
Tables Used by This Program
How these tables connect. Nodes are clickable.
Secondary tables
- F0101Address book master — the shared registry of customers, suppliers, employees, and other entitiesRead accessmaster
- 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
- 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 accesstransaction