Skip to content
JDE Reference

P04571

Interactive

Work With Payment Groups — the screen that steps payment groups through write and update: printing checks or EFT files, then posting payments against vouchers.

Lineage hook

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 →

Notes

The update step writes the payment header/detail records and closes the paid vouchers.

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: 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, F0411, F0911 — 1:N joins yield one row per detail line
-- Tables : F0413, F0414, F0411, F0911
-- 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.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",
  f0.RPKCO AS "Document company that owns the voucher number sequence",
  f0.RPDOC AS "Voucher document number",
  f0.RPDCT AS "Voucher document type (PV standard voucher, PD debit memo, PL logged, etc.)",
  f0.RPSFX AS "Pay item — vouchers split into pay items with independent terms and status",
  f0.RPSFXE AS "Pay item extension used by prepayments and multi-tax-rate splits",
  f09.GLDCT AS "Document type of the journal entry (JE, PV, RI, etc.).",
  f09.GLDOC AS "Document number of the journal entry.",
  f09.GLKCO AS "Company that assigned the document number (key company).",
  CASE WHEN f09.GLDGJ IS NULL OR f09.GLDGJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f09.GLDGJ AS INT) DIV 1000, 1, 1), CAST(f09.GLDGJ AS INT) % 1000 - 1) END AS "G/L date driving the fiscal period the line posts to.",  -- CYYDDD Julian → DATE
  f09.GLJELN AS "Line number within the journal entry.",
  f09.GLEXTL AS "Line extension code completing the unique key.",
  f09.GLLT AS "Ledger type the line belongs to (AA actual, CA foreign currency, etc.)."
FROM <catalog>.<schema_data>.f0413 h
LEFT JOIN <catalog>.<schema_data>.f0414 f
  ON f.RNPYID = h.RMPYID
LEFT JOIN <catalog>.<schema_data>.f0411 f0
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f0911 f09
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
ORDER BY h.RMPYID;

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

Tables Used by This Program

How these tables connect. Nodes are clickable.

Join details

  • F0413F0414header detail · 1:N
    ON f0413.RMPYID = f0414.RNPYID
  • F0414F0411foreign key · N:1
    ON f0414.RNDOC = f0411.RPDOC