Reserve Summary Report

Fixed Assets◆ Seeded · Reserve

Beginning balance, transactions, and ending balance for each depreciation reserve account, totaled by balancing segment and reserve account — the summary used to reconcile accumulated depreciation to the general ledger.

Sample build of the Reserve Summary Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Period

FEB-26

Ledger

US Primary

Currency

USD

Reserve accounts

$1.20M

Period depreciation

$0 diff

Ties to GL

Balancing Segment	Reserve Account	Beginning	Depreciation	Ending
Sample	1000-2100-000	Sample	Sample	Sample
—	1000-5400-000	—	—	—
Sample	1000-1410-000	Sample	Sample	Sample
—	2000-2100-000	—	—	—
Sample	1000-6300-000	Sample	Sample	Sample
Sample	1000-2100-000	Sample	Sample	Sample

AI Analyst · active

reading

The report totals reserve movement by balancing segment and reserve account for the GL tie-out.

flag

Period depreciation is flat versus prior month except one segment that jumped — a mass addition or a method change drove it.

root cause & next step

Confirm the driver of the segment's depreciation jump; an unexplained reserve swing is a close-review item.

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

FA_DEPRN_SUMMARY
FA_BOOKS

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.

●— fact → dimension join

Element	Type	Definition
FA_BOOKS	dimension	dimension
Amount	measure	measure

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.

Fixed Assets 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.

Table	Reporting columns	Subject areas
FA_DEPRN_SUMMARY	Setup / configuration table — joined for reference, not exposed for analytics
FA_BOOKS	20	2

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 Usually merged with the detail version into one drill-down reserve reconciliation rather than two separate reports. Irvine rebuilds these on your data.