Analytics Catalog/Oracle Fusion ERP/General Ledger/Account Ledger by Account Greece Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · General Ledger

Account Ledger by Account Greece Report

General Ledger

The Greek statutory account ledger — every posting to each general ledger account over a period, in date order with a running balance, in the format the Greek authorities require for the books of account.

Run note · BIP run  High-volume GL extracts can exceed BI Publisher's online output limit and time out. Run it as a scheduled process (ESS) with output bursted to file or email rather than online preview, and bound it by ledger and period.

Sample build of the Account Ledger by Account Greece Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Account Ledger by Account Greece Report
Sample build · illustrative
Filters
Mi
Sample
Accounts
1000-1410-000
Batch St
Sample
Entity
Globex Holdings
From Period
FEB-26
To Period
FEB-26
1,420
Accounts
48,200
Postings
$0 diff
In balance
AccountJournal DateSourceDebitCreditRunning Balance
1000-2100-0002026-04-30Sample$1,240,500.00$1,240,500.00$1,240,500.00
1000-5400-0002026-03-31—$842,150.75$842,150.75$842,150.75
1000-1410-0002026-02-28Sample$96,400.00$96,400.00$96,400.00
2000-2100-0002026-01-31—$1,005,233.10$1,005,233.10$1,005,233.10
1000-6300-0002025-12-31Sample$58,720.40$58,720.40$58,720.40
1000-2100-0002026-04-30Sample$1,240,500.00$1,240,500.00$1,240,500.00
AI Analyst · active
reading

The report reads GL_JE_LINES per account in date order, carrying a running balance in the Greek statutory layout.

flag

A few accounts carry backdated postings whose journal date precedes their entry date — the statutory book must present movements in strict date order, so these can break the legal sequence.

root cause & next step

Confirm the backdated entries are authorized adjustments and document them; Greek statutory ledgers require chronological integrity, so unexplained backdating is a filing risk.

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_JE_HEADERSdimensionGL_CODE_COMBINATIONSdimensionGL_BALANCESdimensionGL_LEDGERSdimensionGL_JE_LINESfact · one row per source transactionDebit · Credit · Running Balance
●— fact → dimension join
ElementTypeDefinition
GL_JE_HEADERSdimensiondimension
GL_CODE_COMBINATIONSdimensiondimension
GL_BALANCESdimensiondimension
GL_LEDGERSdimensiondimension
Debitmeasuremeasure
Creditmeasuremeasure
Running Balancemeasuremeasure
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_JE_LINES262
GL_JE_HEADERS342
GL_CODE_COMBINATIONS761
GL_BALANCESNo page in this catalog’s data dictionary yet
GL_LEDGERS10104
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.