P04571
InteractiveWork With Payment Groups — the screen that steps payment groups through write and update: printing checks or EFT files, then posting payments against vouchers.
Rows written by P04571 carry …PID = 'P04571' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
The update step writes the payment header/detail records and closes the paid vouchers.
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: P04571 Work With Payment Groups — the screen that steps payment groups through write and update: printing checks or EFT files, then posting payments against vouchers.
-- Purpose: Work With Payment Groups — the screen that steps payment groups through write and update: printing checks or EFT files, then posting payments against vouchers. — auto-generated boilerplate from program-table-map
-- Grain : F0413 × F0414 — 1:N joins yield one row per detail line
-- Tables : F0413, F0414
-- 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: F0411, F0911 are cataloged for this program, but no verified join condition connects them to F0413, so they are left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
h.RMPYID AS "System-assigned payment ID — the key detail application rows hang off",
f.RNRC5 AS "Line number within the payment — makes each application row unique"
FROM <catalog>.<schema_data>.f0413 h
LEFT JOIN <catalog>.<schema_data>.f0414 f
ON f.RNPYID = h.RMPYID
ORDER BY h.RMPYID;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
- F0413A/P matching document: one row per supplier payment (check, EFT, draft) with the payment amount, bank account, dates, and void/reconciliation state.Write accesstransaction
- F0414A/P matching document detail: one row per application of a payment against a voucher pay item, carrying the paid amount and discount taken in both currencies.Write accesstransaction
Secondary tables
- F0411Accounts payable ledger: one row per voucher pay item with gross, open, discount, and tax amounts, due dates, pay status, and the PO keys behind three-way match.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