M3 Reference
ARS200
InteractiveAccounts receivable display — the inquiry over the FSLEDG customer transactions
Tables vs APIs
This program works over the tables below. For analytics at scale, land the raw tables — the SQL further down reads them directly, joined on their keys and CONO. When to land tables vs call MI APIs
Boilerplate SQL
Databricks SQLStarting point for reading the tables behind ARS200 from landed data — the backing tables joined on their keys and CONO. Set your Unity Catalog location, company, and filter values below.
Query parameters
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Program: ARS200 — Accounts receivable display — the inquiry over the FSLEDG customer transactions
-- Purpose: Read the tables behind program ARS200 — auto-generated from program-table-map
-- Grain : One row per FSLEDG record
-- Tables : FSLEDG
-- Notes : Auto-generated skeleton for a prefixed physical M3 schema or a landing schema normalized to the prefixed names in this catalog. Raw Data Lake property names vary with the published object: map them through Data Catalog before running this SQL. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); all curated status values are decoded inline; company-partitioned tables are joined on CONO to prevent cross-company fan-out. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
h.ESCONO AS "Company",
h.ESDIVI AS "Division",
h.ESYEA4 AS "Fiscal year",
h.ESVSER AS "Voucher number series",
h.ESVONO AS "Voucher number — the join back to the general ledger",
h.ESCUNO AS "Customer the transaction belongs to",
h.ESCUAM AS "Amount in transaction currency, signed"
FROM <catalog>.<schema>.FSLEDG h
WHERE
h.ESCONO = <company>
ORDER BY h.ESYEA4;