Journal Sources Report

Control Reports

The journal sources configured in the general ledger — where each journal originates (Payables, Receivables, Assets, Manual, Spreadsheet) and whether import, freezing, and reference tracking are on — used to confirm subledger feeds flow and audit correctly.

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

Sample build · illustrative

Filters

Sample

Journal sources

Subledger-fed

Import disabled

Journal Source	Import Enabled	Freeze Journals	Reference Tracking	Effective 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 reads GL_JE_SOURCES with its lookups, listing every source and its import, freeze, and reference-tracking flags.

flag

Two subledger sources have journal import disabled — entries from those subledgers will not reach GL automatically, so balances drift until someone imports them by hand.

root cause & next step

Enable import on the two sources, or confirm they are intentionally manual; a disabled subledger source is a frequent cause of AP-to-GL or AR-to-GL out-of-balance at close.

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

GL_JE_SOURCES_B
GL_JE_SOURCES_TL
GL_JE_SOURCES
GL_LOOKUPS

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.

SQL data set · genericized · parameterized · no hardcoded segments

Show / hide SQL

SELECT
    --gjsb.JE_SOURCE_NAME AS name,
	gjs.USER_JE_SOURCE_NAME AS name,
    gjsb.JE_SOURCE_KEY AS source_key,
    gjst.DESCRIPTION,
    DECODE(gjsb.OVERRIDE_EDITS_FLAG, 'Y', 'Yes', 'N', 'No')  AS freeze_journal,
	lkp.MEANING as Accounting_date_rule,
    DECODE(gjsb.Journal_reference_flag, 'Y', 'True', 'N', 'False')  AS import_journal_references,
    DECODE(gjsb.JOURNAL_APPROVAL_FLAG, 'Y', 'True', 'N', 'False') AS require_GL_journal_approval,
    DECODE(gjsb.IMPORT_USING_KEY_FLAG, 'Y', 'True', 'N', 'False') AS import_using_key,
     DECODE(gjsb.SINGLE_CURRENCY_JOURNAL_FLAG, 'Y', 'True', 'N', 'False') AS limit_journal_to_single_currency,
    gjsb.CREATED_BY,
    TO_CHAR(gjsb.CREATION_DATE, 'DD-Mon-YYYY HH:MM AM','NLS_DATE_LANGUAGE = ENGLISH') AS creation_date,
    gjsb.LAST_UPDATED_BY,
    TO_CHAR(gjsb.LAST_UPDATE_DATE, 'DD-Mon-YYYY HH:MM AM','NLS_DATE_LANGUAGE = ENGLISH') AS last_update_date
FROM
    GL_JE_SOURCES_B gjsb
JOIN
    GL_JE_SOURCES_TL gjst
    ON gjsb.JE_SOURCE_NAME = gjst.JE_SOURCE_NAME
JOIN GL_JE_SOURCES GJS ON gjsb.JE_SOURCE_NAME=gjs.JE_SOURCE_NAME
LEFT JOIN
    GL_LOOKUPS lkp
      ON lkp.LOOKUP_TYPE = 'GL_JE_SOURCE_ACC_DATE_RULE'      -- lookup type for the rule
     AND lkp.LOOKUP_CODE = gjsb.EFFECTIVE_DATE_RULE_CODE -- code -> meaning
WHERE
    gjst.LANGUAGE = 'US'
	and gjs.language='US'
ORDER BY
    --gjsb.JE_SOURCE_NAME
	gjs.USER_JE_SOURCE_NAME

:MM

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_JE_SOURCES_TL	dimension	dimension
GL_JE_SOURCES	dimension	dimension
GL_LOOKUPS	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.

Control Reports 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_JE_SOURCES_B	Setup / configuration table — joined for reference, not exposed for analytics
GL_JE_SOURCES_TL	3	4
GL_JE_SOURCES	Setup / configuration table — joined for reference, not exposed for analytics
GL_LOOKUPS	3	1

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.