Skip to content
Fusion Reference

GL_LEDGERS

Product: GLmaster

One row per ledger — currency, calendar, chart of accounts, and accounting convention; the ledger context business units and subledgers resolve to

Identity
Module: FoundationNot org-partitioned
Notes

Ledger SETS share this table: OBJECT_TYPE_CODE discriminates ledger vs ledger-set rows — filter it or ledger counts inflate. LEDGER_CATEGORY_CODE separates primary from secondary and reporting-currency ledgers.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.FinExtractAM.GlBiccExtractAM.LedgerExtractPVO

    Ledgers data store (ledger currency, calendar, period type, chart of accounts). In OTBI, ledgers surface as the Ledger dimension inside the General Ledger subject areas.

    Oracle data-store documentation (opens in new tab)

Fields

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1LEDGER_IDSurrogate key of the ledger — what business units and subledgers point atNUMBER
Key
2NAMELedger name (unique)VARCHAR2
3SHORT_NAMELedger short name (unique)VARCHAR2
4DESCRIPTIONLedger descriptionVARCHAR2
5OBJECT_TYPE_CODELedger vs ledger-set discriminator — filter it or ledger counts inflateVARCHAR2
6LEDGER_CATEGORY_CODEPrimary, secondary, or reporting-currency ledger — filter to primary for most analyticsVARCHAR2
7LE_LEDGER_TYPE_CODELegal vs management ledgerVARCHAR2
8CURRENCY_CODEThe ledger currencyVARCHAR2
9CHART_OF_ACCOUNTS_IDThe chart of accounts (accounting flexfield structure) the ledger posts againstNUMBER
10PERIOD_SET_NAMEThe accounting calendar the ledger runs onVARCHAR2
11ACCOUNTED_PERIOD_TYPEWhich period type within the calendar the ledger accounts inVARCHAR2
12SLA_ACCOUNTING_METHOD_CODESubledger accounting method the ledger usesVARCHAR2
13COMPLETION_STATUS_CODESetup completion status of the ledgerVARCHAR2
14RET_EARN_CODE_COMBINATION_IDRetained earnings account — joins the code combinations tableNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of GL_LEDGERS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <LEDGER_ID>, <watermark>

-- ============================================================
-- Table  : GL_LEDGERS — One row per ledger — currency, calendar, chart of accounts, and accounting convention; the ledger context business units and subledgers resolve to
-- Purpose: Column-selected read of GL_LEDGERS — auto-generated from field metadata
-- Grain  : One row per LEDGER_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.LEDGER_ID AS "Surrogate key of the ledger — what business units and subledgers point at",
  t.NAME AS "Ledger name (unique)",
  t.SHORT_NAME AS "Ledger short name (unique)",
  t.DESCRIPTION AS "Ledger description",
  t.OBJECT_TYPE_CODE AS "Ledger vs ledger-set discriminator — filter it or ledger counts inflate",
  t.LEDGER_CATEGORY_CODE AS "Primary, secondary, or reporting-currency ledger — filter to primary for most analytics",
  t.LE_LEDGER_TYPE_CODE AS "Legal vs management ledger",
  t.CURRENCY_CODE AS "The ledger currency",
  t.CHART_OF_ACCOUNTS_ID AS "The chart of accounts (accounting flexfield structure) the ledger posts against",
  t.PERIOD_SET_NAME AS "The accounting calendar the ledger runs on",
  t.ACCOUNTED_PERIOD_TYPE AS "Which period type within the calendar the ledger accounts in",
  t.SLA_ACCOUNTING_METHOD_CODE AS "Subledger accounting method the ledger uses",
  t.COMPLETION_STATUS_CODE AS "Setup completion status of the ledger",
  t.RET_EARN_CODE_COMBINATION_ID AS "Retained earnings account — joins the code combinations table"
FROM <catalog>.<schema>.GL_LEDGERS t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.LEDGER_ID = <LEDGER_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.LEDGER_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • GL_CODE_COMBINATIONSGL_LEDGERSforeign key · N:M
    ON GL_CODE_COMBINATIONS.CHART_OF_ACCOUNTS_ID = GL_LEDGERS.CHART_OF_ACCOUNTS_ID
  • GL_LEDGERSGL_CODE_COMBINATIONSforeign key · N:1
    ON GL_LEDGERS.RET_EARN_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
  • CST_COST_ORG_BOOKSGL_LEDGERSforeign key · N:1
    ON CST_COST_ORG_BOOKS.LEDGER_ID = GL_LEDGERS.LEDGER_ID
  • CST_COST_DISTRIBUTIONSGL_LEDGERSforeign key · N:1
    ON CST_COST_DISTRIBUTIONS.LEDGER_ID = GL_LEDGERS.LEDGER_ID
  • AP_INVOICES_ALLGL_LEDGERSforeign key · N:1
    ON AP_INVOICES_ALL.SET_OF_BOOKS_ID = GL_LEDGERS.LEDGER_ID
  • GL_JE_HEADERSGL_LEDGERSforeign key · N:1
    ON GL_JE_HEADERS.LEDGER_ID = GL_LEDGERS.LEDGER_ID
  • GL_JE_LINESGL_LEDGERSforeign key · N:1
    ON GL_JE_LINES.LEDGER_ID = GL_LEDGERS.LEDGER_ID

Browse more Foundation tables

More Foundation tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.