GL_LEDGERS
Schema: GLmasterOne row per ledger, tying together the four Cs — currency, calendar, chart of accounts, and accounting convention; the R12 replacement for the 11i sets-of-books table, and the ledger context every operating unit resolves to
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | LEDGER_ID | Surrogate key of the ledger — what operating units and subledgers point at | NUMBER | Primary-key field |
| 2 | NAME | Ledger name (unique) | VARCHAR2 | |
| 3 | SHORT_NAME | Ledger short name (unique) | VARCHAR2 | |
| 4 | DESCRIPTION | Ledger description | VARCHAR2 | |
| 5 | LEDGER_CATEGORY_CODE | Primary, secondary, or reporting-currency ledger — filter to primary for most analytics | VARCHAR2 | |
| 6 | CURRENCY_CODE | The ledger currency | VARCHAR2 | |
| 7 | CHART_OF_ACCOUNTS_ID | The chart of accounts (accounting flexfield structure) the ledger posts against | NUMBER | |
| 8 | PERIOD_SET_NAME | The accounting calendar the ledger runs on | VARCHAR2 | |
| 9 | ACCOUNTED_PERIOD_TYPE | Which period type within the calendar the ledger accounts in | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading GL_LEDGERS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <LEDGER_ID>, <watermark>
-- ============================================================
-- Table : GL_LEDGERS — One row per ledger, tying together the four Cs — currency, calendar, chart of accounts, and accounting convention; the R12 replacement for the 11i sets-of-books table, and the ledger context every operating unit resolves 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 EBS R12 data landed in your lakehouse. 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 operating 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.LEDGER_CATEGORY_CODE AS "Primary, secondary, or reporting-currency ledger — filter to primary for most analytics",
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"
FROM <catalog>.<schema>.GL_LEDGERS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.LEDGER_ID = <LEDGER_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.LEDGER_ID;Verified September 2026
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
ON GL_CODE_COMBINATIONS.CHART_OF_ACCOUNTS_ID = GL_LEDGERS.CHART_OF_ACCOUNTS_IDON GL_JE_HEADERS.LEDGER_ID = GL_LEDGERS.LEDGER_ID
More Foundation tables
- HR_ALL_ORGANIZATION_UNITSThe master list of every organization unit of every classification — business groups, legal entities, operating units, inventory organizations, HR organizations — across all business groups; classification detail lives in HR_ORGANIZATION_INFORMATION
- HR_OPERATING_UNITSThe delivered view that enumerates operating units — the ORG_ID domain — with their business group, ledger, and legal context; the standard way to turn the ORG_ID on an _ALL table into a name
- HR_ORGANIZATION_INFORMATIONClassification rows for each organization unit — which orgs are operating units, inventory orgs, or legal entities, and the per-classification attributes, keyed by a context code with generic attribute columns
- ORG_ORGANIZATION_DEFINITIONSThe delivered view that presents inventory organizations with their operating unit, legal entity, ledger, and chart of accounts in one row — the org-mapping backbone of most inventory reporting
- FND_FLEX_VALUE_SETSValue set definitions for key and descriptive flexfields — one row per value set with its validation type, format rules, and size limits; the configuration that gives SEGMENTn columns their meaning
- FND_FLEX_VALUESThe valid values belonging to each flexfield value set — one row per segment value, with enabled/date-effectivity flags and the parent-value linkage dependent and rollup hierarchies use