EBS Reference
GL_CODE_COMBINATIONS
Schema: GLmasterEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; inventory accounting distributions and every journal line 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 (see quirks #flexfields). The catalog lists the first six.
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
In field listings, the Key chip marks a primary-key field.
Fields
14 fields · 1 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CODE_COMBINATION_ID | The CCID — the surrogate key every accounting distribution and journal line carries | NUMBER | Primary-key field |
| 2 | CHART_OF_ACCOUNTS_ID | The chart of accounts this combination belongs to | 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 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 8 | END_DATE_ACTIVE | Effectivity end date | DATE | |
| 9 | SEGMENT1 | Accounting flexfield segment 1 — meaning depends on the chart's configuration | VARCHAR2 | |
| 10 | SEGMENT2 | Accounting flexfield segment 2 | VARCHAR2 | |
| 11 | SEGMENT3 | Accounting flexfield segment 3 | VARCHAR2 | |
| 12 | SEGMENT4 | Accounting flexfield segment 4 | VARCHAR2 | |
| 13 | SEGMENT5 | Accounting flexfield segment 5 | VARCHAR2 | |
| 14 | 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 GL_CODE_COMBINATIONS 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.
Query parameters
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; inventory accounting distributions and every journal line 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 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.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",
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.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 — see quirks guide #flexfields
t.SEGMENT2 AS "Accounting flexfield segment 2", -- flexfield segment: concatenation is configuration-defined — see quirks guide #flexfields
t.SEGMENT3 AS "Accounting flexfield segment 3", -- flexfield segment: concatenation is configuration-defined — see quirks guide #flexfields
t.SEGMENT4 AS "Accounting flexfield segment 4", -- flexfield segment: concatenation is configuration-defined — see quirks guide #flexfields
t.SEGMENT5 AS "Accounting flexfield segment 5", -- flexfield segment: concatenation is configuration-defined — see quirks guide #flexfields
t.SEGMENT6 AS "Accounting flexfield segment 6 (SEGMENT7–30 exist physically; catalog shows the first six)" -- flexfield segment: concatenation is configuration-defined — see quirks guide #flexfields
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>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CODE_COMBINATION_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 MTL_TRANSACTION_ACCOUNTS.REFERENCE_ACCOUNT = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON PO_DISTRIBUTIONS_ALL.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON BOM_RESOURCES.ABSORPTION_ACCOUNT = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON AP_INVOICES_ALL.ACCTS_PAY_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON AP_INVOICE_DISTRIBUTIONS_ALL.DIST_CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON GL_JE_LINES.CODE_COMBINATION_ID = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
More Foundation tables
- GL_LEDGERSOne 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
- 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