Fusion Reference

GL_CODE_COMBINATIONS

Product: GLmaster

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

Identity

Module: FoundationNot org-partitioned

Notes

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

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.
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.
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.

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 (opens in new tab)

Fields

17 fields · 1 key

17 fields.

Table fields: position, field name, description, data type, and flags. 17 fields.
#	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	Flex segment
13	SEGMENT2	Accounting flexfield segment 2	VARCHAR2	Flex segment
14	SEGMENT3	Accounting flexfield segment 3	VARCHAR2	Flex segment
15	SEGMENT4	Accounting flexfield segment 4	VARCHAR2	Flex segment
16	SEGMENT5	Accounting flexfield segment 5	VARCHAR2	Flex segment
17	SEGMENT6	Accounting flexfield segment 6 (SEGMENT7–30 exist physically; catalog shows the first six)	VARCHAR2	Flex segment

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of GL_CODE_COMBINATIONS 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

CatalogSchemaAccount combination (CCID)watermark

Include optional filters (2)

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

-- ============================================================
-- 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 automatic partition anchor 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;

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
PO_DISTRIBUTIONS_ALLGL_CODE_COMBINATIONSforeign key · N:1
ON PO_DISTRIBUTIONS_ALL.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
CST_COST_DISTRIBUTION_LINESGL_CODE_COMBINATIONSforeign key · N:1
ON CST_COST_DISTRIBUTION_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
CST_COST_DISTRIBUTION_LINESGL_CODE_COMBINATIONSforeign key · N:1
ON CST_COST_DISTRIBUTION_LINES.SLA_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
AP_INVOICES_ALLGL_CODE_COMBINATIONSforeign key · N:1
ON AP_INVOICES_ALL.ACCTS_PAY_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
AP_INVOICE_DISTRIBUTIONS_ALLGL_CODE_COMBINATIONSforeign key · N:1
ON AP_INVOICE_DISTRIBUTIONS_ALL.DIST_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
GL_JE_LINESGL_CODE_COMBINATIONSforeign key · N:1
ON GL_JE_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID

Browse more Foundation tables