Analytics Catalog/Oracle Fusion ERP/Payables/Oracle Fusion AP Aging Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Payables (AP)

Oracle Fusion AP Aging Report

Payables

How much the company owes suppliers, how overdue each balance is, and which suppliers and invoices drive the past-due total — every figure traceable to the source invoice and its GL distribution.

What the seeded report gives you

Payables Aging Report (BI Publisher) · OTBI subject area "Payables Invoices – Transactions Real Time". Columns: Business Unit, Supplier & Site, Invoice Number/Date/Due Date, Aging Bucket (fixed), Amount Remaining, Currency.

Where it falls short

What finance actually needs

Related  Closely related to the Payables Invoice Aging Report — same open-AP question; this is the classic 'AP Aging' name finance teams search for.

Sample build of the Oracle Fusion AP Aging Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Oracle Fusion AP Aging Report
Sample build · illustrative
Filters
Business Unit
US Operations
As of
31-JAN-2026
Currency
USD
$8.42M
Total open AP
$1.96M
Past due
$310K
90+ days
SupplierCurrent1–3031–6061–9090+Total Open
Acme Logistics120,00045,00012,00000177,000
Globex Materials88,5000022,0008,400118,900
Initech Services031,0000014,20045,200
Umbrella Supply210,40060,00018,5005,0000293,900
Total418,900136,00030,50027,00022,600635,000
AI Analyst · active
reading

The report buckets every open payment schedule by days past due against the due date in AP_PAYMENT_SCHEDULES_ALL, then rolls the open balance up by supplier. Current sits at $6.46M; the $1.96M past-due tail is concentrated in the 31-60 bucket.

flag

Twelve suppliers carry balances in the 90+ bucket totaling $310K, but three of them have invoices on payment hold — so the headline overdue figure overstates what is actually payable until those holds clear.

root cause & next step

The 90+ concentration traces to held invoices in AP_HOLDS_ALL. Release or write off the holds, then re-age so the past-due total reflects real payment obligations only.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.
SQL data set · genericized · parameterized · no hardcoded segments
Show / hide SQL
SELECT  s.vendor_name AS supplier, i.invoice_num AS invoice_number,
        i.invoice_date, ps.due_date, i.invoice_currency_code AS currency,
        ps.amount_remaining,
        CASE WHEN TRUNC(:as_of_date) <= ps.due_date THEN 'Current'
             WHEN TRUNC(:as_of_date)-ps.due_date <= 30 THEN '1-30'
             WHEN TRUNC(:as_of_date)-ps.due_date <= 60 THEN '31-60'
             WHEN TRUNC(:as_of_date)-ps.due_date <= 90 THEN '61-90'
             ELSE '90+' END AS aging_bucket
FROM    ap_invoices_all i
JOIN    ap_payment_schedules_all ps ON ps.invoice_id = i.invoice_id
JOIN    poz_suppliers s ON s.supplier_id = i.vendor_id
WHERE   ps.amount_remaining <> 0 AND i.org_id = :business_unit
ORDER BY supplier, ps.due_date;
:business_unit :as_of_date :reporting_currency :aging_basis

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 invoice payment schedule.

dim_suppliersupplier · sitedim_business_unitoperating unitdim_dateinvoice & duedim_gl_accountaccount combofct_ap_open_itemsfact · one row per invoice payment sched…amount_remaining · aging_bucket · d…
●— fact → dimension join
ElementTypeDefinition
dim_supplierdimensionsupplier · site
dim_business_unitdimensionoperating unit
dim_datedimensioninvoice & due
dim_gl_accountdimensionaccount combo
amount_remainingmeasureopen balance
aging_bucketmeasurederived, configurable
dpomeasuredays payable outstanding
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full picture, via conformed keys.
Payables data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

TableReporting columnsSubject areas
AP_INVOICES_ALL6315
AP_PAYMENT_SCHEDULES_ALL212
POZ_SUPPLIERS14575
AP_INVOICE_DISTRIBUTIONS_ALL5911
Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.

The same question across systems.

ConceptOracle FusionSAP S/4HANAWorkday
ReportPayables Aging ReportVendor line items (FBL1N) → agedFind Supplier Invoices / Aging
Open balanceAP_PAYMENT_SCHEDULES_ALLACDOCA + BSIKSupplier Invoice object
Supplier masterPOZ_SUPPLIERSLFA1 / BUT000Supplier (resource)
ExtractionBICCCDS / ODataRaaS / Prism