Results for “chart_of_accounts_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.GLFV_GL_ACCOUNTS is a read-only Oracle EBS view that exposes General Ledger accounting flexfield combinations—commonly referred to as chart of accounts values—in a form suitable for reporting, integration, and inquiry. The view combines the code combination definition maintained in GL_CODE_COMBINATIONS with the descriptive flexfield structure definition held in FND_ID_FLEX_STRUCTURES_TL, thereby presenting each account code combination alongside the name of the chart of accounts structure it belongs to. The view is declared WITH READ ONLY, confirming that it is intended purely for query consumption; no DML is possible against it.

The view is frequently confused with the conceptual "chart_of_accounts_tl" search term because it joins to FND_ID_FLEX_STRUCTURES_TL using the GL# flexfield code and application 101, producing the language-specific structure name (ID_FLEX_STRUCTURE_NAME). The view itself, however, is an account-level listing, not a chart-level listing. Its role in EBS 12.1.1 and 12.2.2 is as a stable, security-aware access point to the segment values underlying any balance, journal, or subledger inquiry.

Underlying Base Objects

The ETRM metadata documents the view as defined over two base objects:

• GL_CODE_COMBINATIONS GL_ACCOUNT — the primary source, supplying the CODE_COMBINATION_ID, CHART_OF_ACCOUNTS_ID, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, ACCOUNT_TYPE, ENABLED_FLAG, DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG, SUMMARY_FLAG, and PRESERVE_FLAG columns.
• FND_ID_FLEX_STRUCTURES_TL CHART_OF_ACCOUNTS_TL — the translated flexfield structure table, supplying ID_FLEX_STRUCTURE_NAME.

The join condition is GL_ACCOUNT.CHART_OF_ACCOUNTS_ID = CHART_OF_ACCOUNTS_TL.ID_FLEX_NUM, restricted to CHART_OF_ACCOUNTS_TL.APPLICATION_ID = 101 (General Ledger), ID_FLEX_CODE = 'GL#', and LANGUAGE = USERENV('LANG'), so only the structure name in the session language is returned. The view also carries a virtual security predicate ('_SEC:GL:NULL,GL_ACCOUNT.CODE_COMBINATION_ID') and a key flexfield reference ('_KF:SQLGL:GL#:GL_ACCOUNT'), reflecting the standard EBS Flexfield Views conventions that drive value-set validation and data access security in the Oracle Forms and OAF runtime.

Key Columns

• CODE_COMBINATION_ID — unique identifier of the account combination within GL_CODE_COMBINATIONS; the primary join key to journal lines and balances.
• CHART_OF_ACCOUNTS_ID — identifies the chart of accounts (accounting flexfield structure) to which the combination belongs.
• ID_FLEX_STRUCTURE_NAME — the language-specific name of the chart of accounts structure, resolved from FND_ID_FLEX_STRUCTURES_TL.
• DESCRIPTION — description of the account combination.
• START_DATE_ACTIVE / END_DATE_ACTIVE — active date range for the combination.
• ENABLED_FLAG, DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG, PRESERVE_FLAG — Yes/No flags translated through GL_LOOKUPS, indicating whether the account may be used, posted to, budgeted against, or preserved.
• SUMMARY_FLAG — decoded as DTL or SUM to indicate detail versus summary account status.
• ACCOUNT_TYPE — the account type lookup description (Asset, Liability, Expense, Revenue, etc.).

Common Use Cases and Queries

Typical scenarios include listing enabled accounts for a given structure, validating posting eligibility, and joining to balance or journal tables. Because the view returns the structure name in the session language, it also supports multilingual reporting without additional translation joins.

SELECT code_combination_id,
       id_flex_structure_name,
       description,
       account_type,
       enabled_flag
  FROM apps.glfv_gl_accounts
 WHERE chart_of_accounts_id = 50390
   AND enabled_flag = 'Y';

The view can be joined to GL_BALANCES on CODE_COMBINATION_ID to summarize period activity by account type, or filtered by NVL(END_DATE_ACTIVE, SYSDATE) to isolate currently effective combinations. Because the view is read-only and applies the EBS flexfield security predicate, results are automatically restricted to the value sets and hierarchies the querying responsibility is permitted to see.