Analytics Catalog/Oracle Fusion ERP/Payables/Payables Open Items Revaluation Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Seeded report · Period close

Payables Open Items Revaluation Report

Payables◆ Seeded · Period close

Lists changes in the value of open items such as unpaid invoices and credit memos due to conversion-rate fluctuations.

Sample build of the Payables Open Items Revaluation Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Payables Open Items Revaluation Report
Sample build · illustrative
Filters
Period
FEB-26
Ledger
US Primary
Currency
USD
420
Open FX items
-$160K
Revaluation adj
6
Currencies
SupplierCurrencyOpen OriginalReval RateRevaluedAdjustment
Acme IndustrialUSDSampleSampleSampleSample
Northwind TradingUSD————
Globex HoldingsUSDSampleSampleSampleSample
Initech LLCUSD————
Umbrella CorpUSDSampleSampleSampleSample
Acme IndustrialUSDSampleSampleSampleSample
AI Analyst · active
reading

The report lists value changes on open invoices and credit memos from conversion-rate movement.

flag

A -$160K revaluation is needed on open foreign-currency AP at period end — unrealized FX the close must book.

root cause & next step

Post the revaluation as part of close; open AP left unrevalued misstates the liability and the FX result.

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.
The SQL data set is authored to this report's exact spec during the build and ships as the BI Publisher data model plus a matching dbt model — one definition, both layers.

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 source transaction.

AP_INVOICES_ALLdimensionGL_DAILY_RATESdimensionAP_PAYMENT_SCHEDULES_ALLfact · one row per source transactionAmount
●— fact → dimension join
ElementTypeDefinition
AP_INVOICES_ALLdimensiondimension
GL_DAILY_RATESdimensiondimension
Amountmeasuremeasure
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_PAYMENT_SCHEDULES_ALL212
AP_INVOICES_ALL6315
GL_DAILY_RATES110
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.

Customization note  Revaluation gain/loss is sensitive to rate type; teams rebuild it with rate-source transparency and a GL tie-out. Irvine rebuilds these on your data.