Analytics Catalog/Oracle Fusion ERP/Fixed Assets/Cost Summary Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Seeded report · Cost

Cost Summary Report

Fixed Assets◆ Seeded · Cost

Beginning balance, additions, retirements, adjustments, and ending balance for each asset cost account — the summary used to reconcile asset cost to the general ledger.

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

Cost Summary Report
Sample build · illustrative
Filters
Period
FEB-26
Ledger
US Primary
Currency
USD
18
Cost accounts
$100.00M
Ending cost
$0 diff
Ties to GL
Cost AccountBeginningAdditionsRetirementsAdjustmentsEnding
$1,240,500.00SampleSampleSampleSampleSample
$842,150.75—————
$96,400.00SampleSampleSampleSampleSample
$1,005,233.10—————
$58,720.40SampleSampleSampleSampleSample
$1,240,500.00SampleSampleSampleSampleSample
AI Analyst · active
reading

The report rolls each cost account from beginning plus additions minus retirements plus or minus adjustments to ending.

flag

The roll-forward ties except one account where ending doesn't equal the computed movement — a direct GL post to the asset cost account.

root cause & next step

Keep manual journals off asset cost accounts; a direct post breaks the cost roll-forward's tie to the ledger.

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.

FA_ADDITIONS_BdimensionFA_RETIREMENTSdimensionFA_BOOKSfact · one row per source transactionCost Account
●— fact → dimension join
ElementTypeDefinition
FA_ADDITIONS_Bdimensiondimension
FA_RETIREMENTSdimensiondimension
Cost Accountmeasuremeasure
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.

TableReporting columnsSubject areas
FA_BOOKS202
FA_ADDITIONS_B159
FA_RETIREMENTSSetup / configuration table — joined for reference, not exposed for analytics
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  The build ties this to the GL Account Analysis so asset cost proves to the ledger. Irvine rebuilds these on your data.