GL_LEDGERS
Product: GLmasterOne row per ledger — currency, calendar, chart of accounts, and accounting convention; the ledger context business units and subledgers resolve to
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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 →
Fields
14 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | LEDGER_ID | Surrogate key of the ledger — what business units and subledgers point at | NUMBER | Key |
| 2 | NAME | Ledger name (unique) | VARCHAR2 | |
| 3 | SHORT_NAME | Ledger short name (unique) | VARCHAR2 | |
| 4 | DESCRIPTION | Ledger description | VARCHAR2 | |
| 5 | OBJECT_TYPE_CODE | Ledger vs ledger-set discriminator — filter it or ledger counts inflate | VARCHAR2 | |
| 6 | LEDGER_CATEGORY_CODE | Primary, secondary, or reporting-currency ledger — filter to primary for most analytics | VARCHAR2 | |
| 7 | LE_LEDGER_TYPE_CODE | Legal vs management ledger | VARCHAR2 | |
| 8 | CURRENCY_CODE | The ledger currency | VARCHAR2 | |
| 9 | CHART_OF_ACCOUNTS_ID | The chart of accounts (accounting flexfield structure) the ledger posts against | NUMBER | |
| 10 | PERIOD_SET_NAME | The accounting calendar the ledger runs on | VARCHAR2 | |
| 11 | ACCOUNTED_PERIOD_TYPE | Which period type within the calendar the ledger accounts in | VARCHAR2 | |
| 12 | SLA_ACCOUNTING_METHOD_CODE | Subledger accounting method the ledger uses | VARCHAR2 | |
| 13 | COMPLETION_STATUS_CODE | Setup completion status of the ledger | VARCHAR2 | |
| 14 | RET_EARN_CODE_COMBINATION_ID | Retained earnings account — joins the code combinations table | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of GL_LEDGERSon 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.
-- ============================================================
-- 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 partition column 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;4 parameters not filled: <catalog>, <schema>, <LEDGER_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. 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_LEDGERS.RET_EARN_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID