Print Adjustments Report

Receivables◆ Seeded · Billing

Prints adjustments tied to specified transactions and customers, organized by business unit, adjustment number, and transaction number.

Sample build of the Print Adjustments 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

420

Adjustments

$540K

Adjusted value

Pending approval

Adjustment	Transaction	Customer	Type	Amount	Status
Sample	Sample	Acme Industrial	Standard	$1,240,500.00	Open
—	—	Northwind Trading	Corporate	$842,150.75	Posted
Sample	Sample	Globex Holdings	Standard	$96,400.00	Validated
—	—	Initech LLC	Default	$1,005,233.10	Open
Sample	Sample	Umbrella Corp	Standard	$58,720.40	Paid
Sample	Sample	Acme Industrial	Standard	$1,240,500.00	Open

AI Analyst · active

reading

The report prints adjustments tied to transactions, organized by business unit and number.

flag

26 adjustments are pending approval — write-offs and credits not yet authorized but already reducing apparent AR.

root cause & next step

Clear the approval queue; an unapproved adjustment is a control gap and a possible revenue leak.

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
RA_CUSTOMER_TRX_ALL	dimension	dimension
HZ_CUST_ACCOUNTS	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.

Receivables 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
AR_ADJUSTMENTS_ALL	19	2
RA_CUSTOMER_TRX_ALL	58	16
HZ_CUST_ACCOUNTS	14	43

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 re-cut as an adjustment-analysis view with the reason-code and approver dimensions the print report omits. Irvine rebuilds these on your data.