Search Results gl_code_combinations_pk

Overview

GL_CODE_COMBINATIONS is the master account-combination table in the Oracle E-Business Suite General Ledger (GL) schema. It stores every valid account combination that results from a Chart of Accounts (COA) structure, where a combination represents a unique concatenation of accounting flexfield segments. In Release 12.1.1 and 12.2.2 this table serves as the central reference point for the entire subledger and ledger architecture: accounts payable, accounts receivable, fixed assets, inventory, purchasing, projects, payroll, and the Subledger Accounting (XLA) engine all resolve their accounting distribution targets to a single numeric surrogate key, CODE_COMBINATION_ID, held in this table.

Because the table is referenced by hundreds of foreign keys across almost every financial and supply-chain module, it functions as the authoritative “hub” of the accounting dimension. In Data Vault modeling terms, the ETRM metadata classifies this object as hub-leaning: CODE_COMBINATION_ID is the stable business key that the rest of the model can attach to, making it an excellent candidate for a Data Vault hub with dependent descriptive detail (posting flags, enablement status, active dates) belonging in an adjacent satellite.

Key Information Stored

The physical schema for GL_CODE_COMBINATIONS documents 112 columns. The most operationally important are:

• CODE_COMBINATION_ID — surrogate primary key (GL_CODE_COMBINATIONS_PK) and the value propagated to every referencing subledger table.
• CHART_OF_ACCOUNTS_ID — identifies the accounting flexfield structure that governs the segment layout; combined with the segments it forms the unique index GL_CODE_COMBINATIONS_UK1, the principal business-key candidate.
• SEGMENT1 through SEGMENT30 — the individual accounting flexfield segment values; the first several are typically the configured balancing and natural-account segments, while higher numbers support up to thirty-segment charts.
• ENABLED_FLAG — indicates whether the combination may be used for new transactions or is disabled.
• SUMMARY_FLAG and DETAIL_POSTING_ALLOWED_FLAG — distinguish parent/summary combinations from detail accounts eligible for posting.
• DETAIL_BUDGETING_ALLOWED_FLAG — controls whether the combination accepts budget entries.
• ACCOUNT_TYPE — classifies the combination (asset, liability, equity, revenue, expense, or budget), which drives financial statement placement and retained-earnings processing.
• START_DATE_ACTIVE and END_DATE_ACTIVE — define the period during which the combination is valid.
• TEMPLATE_ID — foreign key to GL_SUMMARY_TEMPLATES, linking a combination to a summary account template.
• REVALUATION_ID — foreign key to GL_REVALUATIONS, recording revaluation associations.
• DESCRIPTION, ATTRIBUTE1–ATTRIBUTE10, CONTEXT, SEGMENT_ATTRIBUTE1–SEGMENT_ATTRIBUTE42, REFERENCE1–REFERENCE5 — descriptive flexfield storage and user-defined reference columns.
• PRESERVE_FLAG, REFRESH_FLAG, JGZZ_RECON_FLAG — control flags specific to combination maintenance and reconciliation.
• ALTERNATE_CODE_COMBINATION_ID — used during account restructuring to redirect a superseded combination.

The surrogate key is CODE_COMBINATION_ID; the documented unique index GL_CODE_COMBINATIONS_U1 covers CODE_COMBINATION_ID, and the business-key candidate GL_CODE_COMBINATIONS_UK1 spans CHART_OF_ACCOUNTS_ID plus SEGMENT1 through SEGMENT30.

Common Use Cases and Queries

Typical applications of this table include resolving account descriptions for journal and subledger reporting, validating account availability before transaction entry, and populating account-dimension hierarchies for financial analysis.

Resolving a CCID to its human-readable account:

• SELECT code_combination_id, segment1||'.'||segment2||'.'||segment3||'.'||segment4||'.'||segment5 account FROM gl_code_combinations WHERE code_combination_id = :p_ccid;

Locating all enabled detail combinations for a given chart of accounts, commonly used by AutoAllocation, validation, and interface programs:

• SELECT * FROM gl_code_combinations WHERE chart_of_accounts_id = :p_coa AND enabled_flag = 'Y' AND summary_flag = 'N' AND detail_posting_allowed_flag = 'Y';

Joining a subledger distribution to its account description:

• SELECT d.dist_code_combination_id, g.segment1, g.segment2, g.segment3 FROM ap_invoice_distributions_all d, gl_code_combinations g WHERE d.dist_code_combination_id = g.code_combination_id;

Common reporting scenarios include chart-of-accounts listings, invalid or disabled-account audits, and tracing which subledger objects reference a specific combination when planning account revaluations.

Related Objects

GL_CODE_COMBINATIONS participates in an exceptionally broad set of relationships. The most significant, drawn from documented foreign-key metadata, include:

• GL_SUMMARY_TEMPLATES — referenced via GL_CODE_COMBINATIONS.TEMPLATE_ID; defines summary account templates.
• GL_REVALUATIONS — referenced via GL_CODE_COMBINATIONS.REVALUATION_ID.
• GL_JE_LINES — references this table via CODE_COMBINATION_ID; carries the account for every journal line.
• GL_BALANCES — references CODE_COMBINATION_ID; stores period balances per account combination.
• AP_INVOICE_DISTRIBUTIONS_ALL — references this table through DIST_CODE_COMBINATION_ID, PRICE_VAR_CODE_COMBINATION_ID, and RATE_VAR_CODE_COMBINATION_ID.
• AR_DISTRIBUTIONS_ALL — references CODE_COMBINATION_ID and REF_DIST_CCID for receivable accounting.
• MTL_MATERIAL_TRANSACTIONS — references DISTRIBUTION_ACCOUNT_ID, ENCUMBRANCE_ACCOUNT, and other inventory accounting columns.
• FA_DISTRIBUTION_ACCOUNTS — references numerous CCID columns (e.g., DEPRN_EXPENSE_ACCOUNT_CCID, ASSET_COST_ACCOUNT_CCID) for asset accounting.
• XLA_ANALYTICAL_BALANCES, XLA_CONTROL_BALANCES, AX_SLE_LINES — Subledger Accounting objects that reference CODE_COMBINATION_ID, reflecting the central role of the CCID in the R12 accounting engine.

Because virtually every accounting distribution table in EBS carries a CCID column pointing here, GL_CODE_COMBINATIONS is the single most referenced table in the financials data model and an essential anchor for any EBS reporting or data-warehouse solution.