Skip to content
JDE Reference

R03B551

Batch UBE

Update Receipts Header — the batch job in the automatic receipts process that turns uploaded bank payment records into unapplied receipt headers ready for matching.

Lineage hook

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

Notes

First step of auto cash application; R03B50 then applies the receipts to invoices.

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
-- ============================================================
-- Program: R03B551 Update Receipts Header — the batch job in the automatic receipts process that turns uploaded bank payment records into unapplied receipt headers ready for matching.
-- Purpose: Update Receipts Header — the batch job in the automatic receipts process that turns uploaded bank payment records into unapplied receipt headers ready for matching. — auto-generated boilerplate from program-table-map
-- Grain  : F03B13 × F03B11, F03012 — 1:N joins yield one row per detail line
-- Tables : F03B13, F03B11, F03012
-- 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.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.RPDOC AS "Invoice document number",
  f.RPDCT AS "Invoice document type (RI standard invoice, RM credit memo, RU unapplied cash, etc.)",
  f.RPKCO AS "Document company that owns the invoice number sequence",
  f.RPSFX AS "Pay item — one invoice can split into multiple pay items with their own terms",
  f0.AIAN8 AS "Customer address book number; join to F0101 for name and to F03B11 for invoices",
  f0.AICO AS "Company this customer record applies to; company 00000 holds the default line-of-business record"
FROM <catalog>.<schema_data>.f03b13 h
LEFT JOIN <catalog>.<schema_data>.f03b11 f
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f03012 f0
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
ORDER BY h.RYPYID;

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

Tables Used by This Program

How these tables connect. Nodes are clickable.

Join details

  • F03B11F03012foreign key · N:1
    ON f03b11.RPAN8 = f03012.AIAN8