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

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…

Join details

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

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle, JD Edwards, and EnterpriseOne are registered trademarks of Oracle and/or its affiliates.