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
-- ============================================================
-- 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 Infor Data Lake-landed M3 data. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); status ladders decoded inline where verified; 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"
FROM <catalog>.<schema>.FSLEDG h
WHERE
h.ESCONO = <company>
ORDER BY h.ESYEA4;3 parameters not filled: <catalog>, <schema>, <company>