Analytics Catalog/Oracle Fusion ERP/Transaction Tax/Sales Tax Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Seeded report · Sales and use tax

Sales Tax Report

Transaction Tax◆ Seeded · Sales and use tax

US sales tax by jurisdiction and rate for Receivables transactions — the basis for state and local sales-tax returns.

Run note · Data latency  Several tax reports read the Tax Reporting Ledger extract rather than live transaction tables — run the extract first or the report returns stale or empty results.

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

Sales Tax Report
Sample build · illustrative
Filters
Period
FEB-26
Ledger
US Primary
Currency
USD
42
Jurisdictions
$880K
Sales tax
3
Nexus review
StateJurisdictionTax RateTaxableTax
SampleSampleSampleSampleSample
—————
SampleSampleSampleSampleSample
—————
SampleSampleSampleSampleSample
SampleSampleSampleSampleSample
AI Analyst · active
reading

The report summarizes sales tax by US jurisdiction and rate.

flag

Taxable sales in three states have no registered nexus setup — either collecting where you shouldn't or owing where you don't collect.

root cause & next step

Confirm nexus in those states; getting nexus wrong is the most expensive sales-tax mistake.

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.

RA_CUSTOMER_TRX_ALLdimensionZX_RATES_BdimensionZX_LINESfact · one row per source transactionAmount
●— fact → dimension join
ElementTypeDefinition
RA_CUSTOMER_TRX_ALLdimensiondimension
ZX_RATES_Bdimensiondimension
Amountmeasuremeasure
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.
Transaction Tax 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
ZX_LINESSetup / configuration table — joined for reference, not exposed for analytics
RA_CUSTOMER_TRX_ALL5816
ZX_RATES_BSetup / 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  Rebuilt by jurisdiction with nexus flags so multi-state returns can be prepared from one model. Irvine rebuilds these on your data.