Search Results gl_code_combinations_v

Overview

GL_CODE_COMBINATIONS_V is a foundational reporting view in the Oracle E-Business Suite General Ledger module, owned by the APPS schema and defined over the core accounting flexfield table. In release 12.1.1 and 12.2.2, it exposes the full set of account code combinations — the individual chart-of-accounts segments that determine how transactions are posted, budgeted, and reported. The view presents every segment column (SEGMENT1 through SEGMENT30), the associated description, enabled and summary flags, and the enabled date range, making it the principal read-only interface through which subledgers, concurrent programs, and custom reports resolve a CODE_COMBINATION_ID to its underlying account string.

Unlike the base table, this view joins lookup information to derive a descriptive account type, and it is the object most commonly referenced when a form or report needs to validate or display an account. For developers searching on "refresh_flag," it is important to note that GL_CODE_COMBINATIONS_V carries no refresh_flag column in its documented structure; it is a straight projection of the base table plus a lookup join, and it should not be confused with flexfield compilation or summary-template refresh operations.

Underlying Base Objects

The documented base objects for the view are:

• GL_CODE_COMBINATIONS (referenced through a SYNONYM) — the master table holding all valid and invalid account code combinations, their segment values, enabled/summary status, and descriptive flexfield attributes.
• GL_LOOKUPS (a VIEW) — used to translate the stored ACCOUNT_TYPE value into a user-readable SHOW_ACCOUNT_TYPE description.

Because the view is a simple projection, inserts and updates against it are not supported; DML must target GL_CODE_COMBINATIONS directly. The view inherits the base table's validation logic, so CODE_COMBINATION_ID values returned are those that already exist in the chart of accounts.

Key Columns

• ROW_ID / CODE_COMBINATION_ID — the unique identifier for each account combination.
• CHART_OF_ACCOUNTS_ID — the chart of accounts to which the combination belongs.
• SEGMENT1 … SEGMENT30 — the individual account segments (e.g., Company, Account, Cost Center).
• ACCOUNT_TYPE / SHOW_ACCOUNT_TYPE — the functional classification (A = Asset, L = Liability, O = Owner's Equity, R = Revenue, E = Expense) and its descriptive lookup text.
• ENABLED_FLAG and SUMMARY_FLAG — indicate whether the combination is active and whether it is a summary (parent) account.
• DETAIL_POSTING_ALLOWED_FLAG and DETAIL_BUDGETING_ALLOWED_FLAG — control whether detailed entries may be posted or budgeted.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range for the combination.
• DESCRIPTION, ATTRIBUTE1–10, CONTEXT, and SEGMENT_ATTRIBUTE1–5 — descriptive flexfield attributes associated with the combination.

Common Use Cases and Queries

Typical scenarios include resolving an account string for a subledger journal line, listing all enabled detail posting accounts for a chart of accounts, and validating user-entered accounts. Examples:

1. Retrieve enabled detail posting accounts:

SELECT code_combination_id, segment1, segment2, segment3, description FROM gl_code_combinations_v WHERE chart_of_accounts_id = :coa_id AND enabled_flag = 'Y' AND summary_flag = 'N';

2. Join to a subledger distribution line:

SELECT a.code_combination_id, a.segment1, a.segment2, a.account_type FROM gl_code_combinations_v a, gl_je_lines l WHERE a.code_combination_id = l.code_combination_id AND l.je_header_id = :header_id;

3. List accounts by account type:

SELECT code_combination_id, description, show_account_type FROM gl_code_combinations_v WHERE account_type = 'E' AND enabled_flag = 'Y';

Because the view performs a lookup join, production queries should filter on CHART_OF_ACCOUNTS_ID and ENABLED_FLAG to reduce the result set and to satisfy EBS access controls.