Asset Transfers Report

Fixed Assets◆ Seeded · Transfers

Assets transferred between cost centers, locations, or employees in a period, showing the from and to assignments and the reserve transferred.

Sample build of the Asset Transfers 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

140

Transfers

$3.20M

Cost transferred

Cross-segment

Asset	From	To	Reserve Transferred	Transfer Date
Sample	Sample	Sample	Sample	2026-04-30
—	—	—	—	2026-03-31
Sample	Sample	Sample	Sample	2026-02-28
—	—	—	—	2026-01-31
Sample	Sample	Sample	Sample	2025-12-31
Sample	Sample	Sample	Sample	2026-04-30

AI Analyst · active

reading

The report lists transfers with their from and to assignments and the reserve moved.

flag

Eight transfers cross balancing segments — they require an intercompany or reserve adjustment that may not have posted.

root cause & next step

Confirm the intercompany entry for cross-segment transfers; without it the two entities' books stay out of balance.

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_TRANSFER_DETAILS
FA_DISTRIBUTION_HISTORY
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_DISTRIBUTION_HISTORY	dimension	dimension
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_TRANSFER_DETAILS	Setup / configuration table — joined for reference, not exposed for analytics
FA_DISTRIBUTION_HISTORY	6	2
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 Often extended to flag transfers that cross balancing segments, which require an intercompany or reserve adjustment. Irvine rebuilds these on your data.