Analytics Catalog/Oracle Fusion ERP/General Ledger/Journal Approval Audit History Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · General Ledger

Journal Approval Audit History Report

General Ledger

The approval trail for journals — who submitted, who approved or rejected, and when — so finance can prove journals went through the required approvals and spot entries that posted without them.

Sample build of the Journal Approval Audit History Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Journal Approval Audit History Report
Sample build · illustrative
Filters
Batch Status
Validated
From Period
FEB-26
Ledger
US Primary
To Period
FEB-26
Xdo User Name
Globex Holdings
640
Journals routed
612
Approved
4
Posted w/o approval
Journal BatchSubmitted ByApproverActionAction DateAmount
SampleSampleSampleSample2026-04-30$1,240,500.00
————2026-03-31$842,150.75
SampleSampleSampleSample2026-02-28$96,400.00
————2026-01-31$1,005,233.10
SampleSampleSampleSample2025-12-31$58,720.40
SampleSampleSampleSample2026-04-30$1,240,500.00
AI Analyst · active
reading

The report reads GL_JE_ACTION_LOG joined to the approver's HR record, reconstructing each journal's approval path.

flag

Four journals posted without a recorded approval — auto-approved under a rule, or entered by a role that bypasses approval, which is exactly the control auditors test.

root cause & next step

Confirm whether the bypass is intended; if not, tighten the approval rule so journals above the threshold cannot self-approve.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

The SQL behind this report is not published. Its logic is one organisation's own setup, so it would not run anywhere else. The tables it reads are listed below, and the warehouse model shows how the same data lands in your warehouse.

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 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.

GL_ACCESS_SETSdimensionFUN_USER_ROLE_DATA_ASGNM…dimensionPER_ROLES_DNdimensionPER_USER_ROLESdimensionGL_LEDGERSfact · one row per source transactionAmount
●— fact → dimension join
ElementTypeDefinition
GL_ACCESS_SETSdimensiondimension
FUN_USER_ROLE_DATA_ASGNMNTSdimensiondimension
PER_ROLES_DNdimensiondimension
PER_USER_ROLESdimensiondimension
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.
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.

TableReporting columnsSubject areas
GL_LEDGERS10104
GL_ACCESS_SETSNo page in this catalog’s data dictionary yet
FUN_USER_ROLE_DATA_ASGNMNTSNo page in this catalog’s data dictionary yet
PER_ROLES_DNNo page in this catalog’s data dictionary yet
PER_USER_ROLES160
PER_USERS2227
GL_JE_ACTION_LOGNo page in this catalog’s data dictionary yet
PER_ALL_ASSIGNMENTS_M12921
PER_JOBS_F_TL128
PER_JOBS_F984
GL_DAILY_RATES110
GL_JE_BATCHES142
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.