Chart of Accounts Mapping Rules Report

General Ledger◆ Seeded · Chart of accounts

Provides the segment and account rules defined for a chart of accounts mapping, printing subsidiary account ranges, parent accounts, and rollup ranges.

Sample build of the Chart of Accounts Mapping Rules 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

Mapping rules

COA mappings

Unmapped source values

Source Segment	Target Segment	Rule Type	Account Range	Status
Sample	Sample	Standard	1000-2100-000	Open
—	—	Corporate	1000-5400-000	Posted
Sample	Sample	Standard	1000-1410-000	Validated
—	—	Default	2000-2100-000	Open
Sample	Sample	Standard	1000-6300-000	Paid
Sample	Sample	Standard	1000-2100-000	Open

AI Analyst · active

reading

The report lists the segment and account rules behind each chart-of-accounts mapping.

flag

12 source account values fall outside every mapping rule — they won't carry into the target chart on consolidation.

root cause & next step

Extend the mapping to cover them; an unmapped source value drops out of the consolidated ledger silently.

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.

●— fact → dimension join

Element	Type	Definition
GL_LEDGERS	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.

General Ledger 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
GL_CODE_COMBINATIONS	7	61
GL_LEDGERS	10	104

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 Used during consolidation setup; usually extended to validate that every subsidiary account maps to a parent before close. Irvine rebuilds these on your data.