Analytics Catalog/Oracle Fusion ERP/Fixed Assets/CIP Detail Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Seeded report · Construction in progress

CIP Detail Report

Fixed Assets◆ Seeded · Construction in progress

Construction-in-progress cost by asset and project — the detail of capital spend accumulating before assets are placed in service.

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

CIP Detail Report
Sample build · illustrative
Filters
Period
FEB-26
Ledger
US Primary
Currency
USD
64
CIP assets
$18.00M
CIP balance
9
Stale > 12 mo
ProjectAssetCip AccountCip CostLast Activity
SampleSample1000-2100-000$1,240,500.00Sample
1000-5400-000$842,150.75
SampleSample1000-1410-000$96,400.00Sample
2000-2100-000$1,005,233.10
SampleSample1000-6300-000$58,720.40Sample
SampleSample1000-2100-000$1,240,500.00Sample
AI Analyst · active
reading

The report lists construction-in-progress cost by asset and project before in-service.

flag

Nine CIP assets have had no activity in over 12 months — capital sitting in CIP, not depreciating, possibly ready to capitalize or write off.

root cause & next step

Review stale CIP for capitalization or impairment; long-dormant CIP overstates assets and defers depreciation.

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_CATEGORIES_BdimensionFA_BOOKSfact · one row per source transactionCip Cost
●— fact → dimension join
ElementTypeDefinition
FA_ADDITIONS_Bdimensiondimension
FA_CATEGORIES_Bdimensiondimension
Cip Costmeasuremeasure
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_CATEGORIES_B510
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 linked to Projects CIP so the Assets and project views of the same spend agree. Irvine rebuilds these on your data.