GL_CODE_COMBINATIONS
Product: GLmasterEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; accounting distributions and journal lines reference accounts through CODE_COMBINATION_ID
SEGMENT1–SEGMENT30 exist physically; which segments a chart uses — and what each means — is configuration, defined per CHART_OF_ACCOUNTS_ID (see quirks #item-org-striping for the flexfield family). Unlike EBS, the base table carries DESCRIPTION and a delimited CONCATENATED_SEGMENTS string directly.
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.CodeCombinationExtractPVO
General Ledger Accounts data store — account combinations per accounting flexfield structure. In OTBI, combinations surface as the Account dimension inside the General Ledger subject areas.
Oracle data-store documentation →
Fields
17 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CODE_COMBINATION_ID | The CCID — the surrogate key every accounting distribution and journal line carries | NUMBER | Key |
| 2 | CHART_OF_ACCOUNTS_ID | The chart of accounts this combination belongs to — segment meaning is defined per chart | NUMBER | |
| 3 | ACCOUNT_TYPE | Asset, liability, equity, revenue, or expense — from the natural-account segment | VARCHAR2 | |
| 4 | ENABLED_FLAG | Whether the combination is active | VARCHAR2 | |
| 5 | SUMMARY_FLAG | Whether this is a summary (rollup) account rather than a detail account | VARCHAR2 | |
| 6 | DETAIL_POSTING_ALLOWED_FLAG | Whether journals may post to the combination directly | VARCHAR2 | |
| 7 | FINANCIAL_CATEGORY | Financial-statement category tag on the combination | VARCHAR2 | |
| 8 | DESCRIPTION | Description of the combination — on the base table in Fusion, unlike EBS | VARCHAR2 | |
| 9 | CONCATENATED_SEGMENTS | The full delimited account string — ready-made, no segment concatenation needed | VARCHAR2 | |
| 10 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 11 | END_DATE_ACTIVE | Effectivity end date | DATE | |
| 12 | SEGMENT1 | Accounting flexfield segment 1 — meaning depends on the chart's configuration | VARCHAR2 | |
| 13 | SEGMENT2 | Accounting flexfield segment 2 | VARCHAR2 | |
| 14 | SEGMENT3 | Accounting flexfield segment 3 | VARCHAR2 | |
| 15 | SEGMENT4 | Accounting flexfield segment 4 | VARCHAR2 | |
| 16 | SEGMENT5 | Accounting flexfield segment 5 | VARCHAR2 | |
| 17 | SEGMENT6 | Accounting flexfield segment 6 (SEGMENT7–30 exist physically; catalog shows the first six) | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of GL_CODE_COMBINATIONSon 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_CODE_COMBINATIONS — Every chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; accounting distributions and journal lines reference accounts through CODE_COMBINATION_ID
-- Purpose: Column-selected read of GL_CODE_COMBINATIONS — auto-generated from field metadata
-- Grain : One row per CODE_COMBINATION_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.CODE_COMBINATION_ID AS "The CCID — the surrogate key every accounting distribution and journal line carries",
t.CHART_OF_ACCOUNTS_ID AS "The chart of accounts this combination belongs to — segment meaning is defined per chart",
t.ACCOUNT_TYPE AS "Asset, liability, equity, revenue, or expense — from the natural-account segment",
t.ENABLED_FLAG AS "Whether the combination is active",
t.SUMMARY_FLAG AS "Whether this is a summary (rollup) account rather than a detail account",
t.DETAIL_POSTING_ALLOWED_FLAG AS "Whether journals may post to the combination directly",
t.FINANCIAL_CATEGORY AS "Financial-statement category tag on the combination",
t.DESCRIPTION AS "Description of the combination — on the base table in Fusion, unlike EBS",
t.CONCATENATED_SEGMENTS AS "The full delimited account string — ready-made, no segment concatenation needed",
t.START_DATE_ACTIVE AS "Effectivity start date",
t.END_DATE_ACTIVE AS "Effectivity end date",
t.SEGMENT1 AS "Accounting flexfield segment 1 — meaning depends on the chart's configuration", -- flexfield segment: concatenation is configuration-defined
t.SEGMENT2 AS "Accounting flexfield segment 2", -- flexfield segment: concatenation is configuration-defined
t.SEGMENT3 AS "Accounting flexfield segment 3", -- flexfield segment: concatenation is configuration-defined
t.SEGMENT4 AS "Accounting flexfield segment 4", -- flexfield segment: concatenation is configuration-defined
t.SEGMENT5 AS "Accounting flexfield segment 5", -- flexfield segment: concatenation is configuration-defined
t.SEGMENT6 AS "Accounting flexfield segment 6 (SEGMENT7–30 exist physically; catalog shows the first six)" -- flexfield segment: concatenation is configuration-defined
FROM <catalog>.<schema>.GL_CODE_COMBINATIONS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.CODE_COMBINATION_ID = <CODE_COMBINATION_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.CODE_COMBINATION_ID;4 parameters not filled: <catalog>, <schema>, <CODE_COMBINATION_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