Analytics Catalog/SAP S/4HANA/Accounts Payable/AP Aging
Explore the catalogReportsModulesEnterprise modelCDS viewsExtraction
SAP S/4HANA · Accounts Payable (FI-AP)

AP Aging — Overdue Payables

Every open supplier invoice, sorted by how overdue it is — so you can see what's due, what's late, and which suppliers to pay first. Built on I_OperationalAcctgDocItem and tied to the supplier sub-ledger.

Sample build of the AP Aging report — bucketed by net due date as of a key date, tied to the Manage Supplier Line Items balance, and rendered tool-neutral so it runs in Power BI, SAC, or Tableau.

AP Aging — Overdue Payables sample
reconciled · key date 22 Jun 2026
Filters
Company code
1010
Key date
22 Jun 2026
Account type
K · Supplier
Currency
USD
12.40M
Open payables
9.22M
Not yet due
3.18M
Overdue
26%
Overdue share
SupplierCurrent1–3031–6060+Total
4800033 · Globex Logistics2,010,000120,0002,130,000
4800021 · Northwind Steel820,000410,000290,0001,100,0002,620,000
4800015 · Acme Components1,240,000180,00040,0001,460,000
4800048 · Initech Services980,00060,00035,0001,075,000
AI Analyst · active
reading

Open supplier items are bucketed by net due date — invoice baseline date plus payment terms — as of the key date, by supplier and company code, and tied to the Manage Supplier Line Items balance.

flag

Supplier 4800021 (Northwind Steel) has 1.10M past 60 days — 42% of its balance — yet its terms are NET 30. That points to disputed invoices or a posting issue, not normal lateness.

root cause & next step

Route the 60-plus items to AP for dispute / clearing review before the next payment run. Clearing or disputing them corrects the aging and frees the cash forecast.

Illustrative data · tied to the supplier sub-ledger · runs on your warehouse. See it live →
ACDOCA+BSEG · terms+Business Partner────▶AP Aging

The report's query logic — it reads the released CDS view I_OperationalAcctgDocItem (vendor lines), works out each item's due date, and sorts it into aging buckets. The same SQL becomes a dbt model in your warehouse.

How it interconnects: it reads the released CDS view — not the legacy BSIK / BSAK compatibility views. The amount comes from ACDOCA; the payment terms and due date come from BSEG, surfaced by the view as PaymentTerms and NetPaymentDays.
SQL data set · genericized · parameterized · released CDS view, never compat views
Show / hide SQL
WITH ap_open AS (
  SELECT it.CompanyCode,
         it.Supplier,
         it.GLAccount                                AS recon_account,
         je.AccountingDocument,
         je.FiscalYear,
         it.AmountInCompanyCodeCurrency              AS open_amount,
         it.PaymentTerms,
         it.NetPaymentDays,
         ADD_DAYS(it.DocumentItemDate,
                  TO_INTEGER(it.NetPaymentDays))      AS net_due_date,
         DAYS_BETWEEN(ADD_DAYS(it.DocumentItemDate,
                  TO_INTEGER(it.NetPaymentDays)),
                  :P_KEY_DATE)                        AS days_overdue
  FROM   I_JournalEntry            AS je
  JOIN   I_OperationalAcctgDocItem AS it
         ON  je.CompanyCode        = it.CompanyCode
         AND je.AccountingDocument = it.AccountingDocument
         AND je.FiscalYear         = it.FiscalYear
  WHERE  it.FinancialAccountType   = 'K'             -- K = vendor (Kreditor)
    AND  it.CompanyCode            = :P_COMPANY_CODE
    AND  it.ClearingDate           IS NULL           -- open as of the key date
)
SELECT Supplier,
       SUM(CASE WHEN days_overdue <= 0                  THEN open_amount ELSE 0 END) AS current_not_due,
       SUM(CASE WHEN days_overdue BETWEEN  1 AND 30      THEN open_amount ELSE 0 END) AS d_1_30,
       SUM(CASE WHEN days_overdue BETWEEN 31 AND 60      THEN open_amount ELSE 0 END) AS d_31_60,
       SUM(CASE WHEN days_overdue > 60                   THEN open_amount ELSE 0 END) AS d_60_plus,
       SUM(open_amount)                                                              AS total_open
FROM   ap_open
GROUP  BY Supplier
ORDER  BY d_60_plus DESC;
To tie out to the Manage Supplier Line Items ledger, match its open-item conditions: account type K, special-G/L indicator, posting date, and clearing date as of the key date. Open = not cleared on or before that date.

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per open AP item.

dim_supplierBusiness Partner · group dim_company_codecompany · ledger dim_gl_accountrecon account dim_datenet due date fct_ap_open_itemsfact · one row per open AP itemopen_amount · days_overdue · bucket
●— fact → dimension join
ElementTypeDefinition
dim_supplierdimensionSupplier — Business Partner (supplier role), name, group
dim_company_codedimensionCompany code & ledger context
dim_gl_accountdimensionReconciliation (payables) account — RACCT
dim_datedimensionConformed calendar on the net due date
open_amountmeasureOpen amount in company-code currency (HSL)
days_overduemeasureKey date minus net due date
aging_bucketmeasureCurrent / 1–30 / 31–60 / 60+ derived from days_overdue
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse. Reconciled to the supplier sub-ledger — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a SAP-compliant extract — released CDS view via SLT, or Table / Table-CDC — never ODP-RFC (prohibited under SAP Note 3255746, blocked June 2026). See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full ACDOCA-centered picture, via conformed keys.
Accounts Payable data model → Enterprise model →

Every source object behind this report. Each linked object has its own page — with its fields and its real S/4HANA status, so you build on the right thing.

ObjectRoleKey fieldsS/4HANA status
I_OperationalAcctgDocItemVendor line item with payment terms — the read objectreleasedReleased CDS view
ACDOCAUniversal Journal — the open amount & account assignment6 PK · 360+Transparent table
BSEGOpen-item management & payment terms (baseline date, net days)4 PKTransparent table
Business PartnerSupplier master (supplier role) — the dimensionBUT000Transparent table
BSIK / BSAKLegacy vendor open/cleared index — reference only, do not extractCompat view → ACDOCA
C_APFlexibleAgingSAP's standard AP aging grid (Aging Analysis app) — referencereleasedReleased CDS view
Key fields = the primary key plus the columns this report selects; S/4HANA status = whether the object is a live transparent table, a released CDS view, or a compatibility view over ACDOCA. The compat views are referenced by legacy joins but are never the extraction source — that's the point, not a gap.
Want this built & owned?
A reconciled, customer-owned AP aging layer on your cloud — your team owns the code. Ten-day proof of concept.
Download the AP pack → Talk to us →
Terms on this page
AP aging
Open supplier invoices grouped by how overdue they are.
Net due date
When an invoice is actually due: its baseline date plus the payment-term days.
ACDOCA
SAP's single table holding every finance posting (the "Universal Journal").
BSEG
The table that still manages open items and payment terms in S/4HANA.
CDS view
Core Data Services — an SAP-supplied, upgrade-safe view onto the data.
I_OperationalAcctgDocItem
The released view that gives the vendor line with its terms (account type K = vendor).
Business Partner
The single S/4HANA master for suppliers and customers (table BUT000).
BSIK / BSAK
The old vendor open / cleared tables — now compatibility views; don't extract them.
SLT
SAP Landscape Transformation — SAP's real-time table-copy tool.
ODP-RFC
An older extraction route SAP now bans for non-SAP tools (Note 3255746).
star schema
A simple, report-friendly layout: one "facts" table with "lookup" tables around it.