Greece Daily Journal Book - Line Descriptions Report

General Ledger

The Greek statutory daily journal book — every journal posted, in date order, with line-level descriptions, in the legally prescribed format for the daily book of original entry.

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 Greece Daily Journal Book - Line Descriptions Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Entity

Globex Holdings

Entity Name

Globex Holdings

From Effective Date

2026-02-28

From Gl Date

2026-02-28

Subledger

US Primary

To Effective Date

2026-02-28

8,400

Journals

41,000

Lines

120

Missing description

Journal Date	Voucher	Account	Line Description	Debit	Credit
2026-04-30	Sample	1000-2100-000	Sample	$1,240,500.00	$1,240,500.00
2026-03-31	—	1000-5400-000	—	$842,150.75	$842,150.75
2026-02-28	Sample	1000-1410-000	Sample	$96,400.00	$96,400.00
2026-01-31	—	2000-2100-000	—	$1,005,233.10	$1,005,233.10
2025-12-31	Sample	1000-6300-000	Sample	$58,720.40	$58,720.40
2026-04-30	Sample	1000-2100-000	Sample	$1,240,500.00	$1,240,500.00

AI Analyst · active

reading

The report reads GL_JE_LINES in date order with their descriptions, in the Greek daily-book layout.

flag

120 lines have no description — the Greek statutory daily book requires one on every line, so these would fail the legal format.

root cause & next step

Enforce line descriptions at entry or backfill before filing; a blank description is the most common Greek daily-book rejection.

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.

●— fact → dimension join

Element	Type	Definition
GL_JE_LINES	dimension	dimension
GL_JE_BATCHES	dimension	dimension
GL_CODE_COMBINATIONS	dimension	dimension
RA_CUSTOMER_TRX_ALL	dimension	dimension
Debit	measure	measure
Credit	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.

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.

Table	Reporting columns	Subject areas
GL_JE_HEADERS	34	2
GL_JE_LINES	26	2
GL_JE_BATCHES	14	2
GL_CODE_COMBINATIONS	7	61
RA_CUSTOMER_TRX_ALL	58	16

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.