Asset Additions by Source Report

Fixed Assets◆ Seeded · Additions

Assets added in a period grouped by the source they came from — Payables, Projects, or manual — so finance can trace each addition to its origin.

Sample build of the Asset Additions by Source 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

320

Additions

$5.10M

From Payables

$640K

Manual additions

Source	Asset	Cost	Originating Document	In-service
Sample	Sample	$1,240,500.00	Sample	Sample
—	—	$842,150.75	—	—
Sample	Sample	$96,400.00	Sample	Sample
—	—	$1,005,233.10	—	—
Sample	Sample	$58,720.40	Sample	Sample
Sample	Sample	$1,240,500.00	Sample	Sample

AI Analyst · active

reading

The report groups additions by the source they came from — Payables, Projects, or manual.

flag

$640K of additions were entered manually rather than flowing from Payables or Projects, bypassing the source audit trail.

root cause & next step

Route capital through mass additions where possible; a manual addition has no invoice or project to trace back to.

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_ADDITIONS_B
FA_MASS_ADDITIONS
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_MASS_ADDITIONS	dimension	dimension
FA_BOOKS	dimension	dimension
Cost	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_ADDITIONS_B	15	9
FA_MASS_ADDITIONS	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 Rebuilt as a source-lineage view linking each asset back to the originating invoice or project. Irvine rebuilds these on your data.