FPLEDG
Prefix: EPtransactionDivision-levelThe accounts payable ledger — one row per supplier invoice or payment transaction, mirroring the receivable ledger on the payable side; its voucher (division, fiscal year, series, number) can carry more than one such row, and joins it to the general ledger
Fields
11 fields · 5 key
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | EPCONO | CONO | Company | numeric | ||
| Key | EPDIVI | DIVI | Division | alphanumeric | ||
| Key | EPYEA4 | YEA4 | Fiscal year | numeric | ||
| Key | EPVSER | VSER | Voucher number series | alphanumeric | ||
| Key | EPVONO | VONO | Voucher number — the join back to the general ledger | numeric | ||
| EPJRNO | JRNO | Journal number | numeric | |||
| EPSUNO | SUNO | Supplier the transaction belongs to | alphanumeric | |||
| EPSINO | SINO | Supplier invoice number | alphanumeric | |||
| EPACDT | ACDT | Accounting date | numeric | |||
| EPDUDT | DUDT | Due date — the basis of payables aging | numeric | |||
| EPCUAM | CUAM | Amount in transaction currency, signed | numeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading FPLEDGon Databricks — numeric YYYYMMDD dates are wrapped to NULL, verified status ladders are decoded, and the CONO anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : FPLEDG — The accounts payable ledger — one row per supplier invoice or payment transaction, mirroring the receivable ledger on the payable side; its voucher (division, fiscal year, series, number) can carry more than one such row, and joins it to the general ledger
-- Purpose: Column-selected read of FPLEDG — auto-generated from field metadata
-- Grain : Transaction-grain — finer than company (CONO) + EPDIVI + EPYEA4 + EPVSER + EPVONO; the full row key is not yet cataloged (see the table description)
-- Notes : Auto-generated skeleton for Infor Data Lake-landed M3 data. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); status ladders decoded inline where verified. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
f.EPCONO AS "Company",
f.EPDIVI AS "Division",
f.EPYEA4 AS "Fiscal year",
f.EPVSER AS "Voucher number series",
f.EPVONO AS "Voucher number — the join back to the general ledger",
f.EPJRNO AS "Journal number",
f.EPSUNO AS "Supplier the transaction belongs to",
f.EPSINO AS "Supplier invoice number",
CASE WHEN f.EPACDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(f.EPACDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Accounting date", -- YYYYMMDD, 0 → NULL
CASE WHEN f.EPDUDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(f.EPDUDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Due date — the basis of payables aging", -- YYYYMMDD, 0 → NULL
f.EPCUAM AS "Amount in transaction currency, signed"
FROM <catalog>.<schema>.FPLEDG f
WHERE
f.EPCONO = <company>
-- AND f.EPDIVI = '<DIVI>'
-- AND f.EPACDT >= <DATE_FROM> -- yyyyMMdd numeric
-- AND f.EPACDT <= <DATE_TO> -- yyyyMMdd numeric
ORDER BY f.EPYEA4;6 parameters not filled: <catalog>, <schema>, <company>, <DIVI>, <DATE_FROM>, <DATE_TO>
Relationships
1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.