Results for “glfv_gl_accounts”

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

Overview

GLFV_GL_ACCOUNTS is a read-only Oracle EBS view owned by the APPS schema and registered under the General Ledger (GL) product family. It is a "flexfield value" (FV) view, meaning it is purpose-built to feed the Oracle EBS Flexfields value-set and key-flexfield infrastructure rather than to serve as a general-purpose reporting object. In 12.1.1 and 12.2.2, such views are referenced by the Flexfields engine through the column aliases that carry embedded directives, allowing the accounting flexfield (GL#) to resolve and validate account code combinations as flexfield values.

The view presents a single row per GL code combination, joined to the descriptive flexfield definition of the accounting chart of accounts. Its primary roles are to expose account code combinations for key flexfield validation, to support the flexfield value-selection UI, and to supply account attributes that the General Ledger and subledger modules use during data entry and reporting.

Underlying Base Objects

The documented view text defines GLFV_GL_ACCOUNTS over two base objects:

• GL_CODE_COMBINATIONS (aliased GL_ACCOUNT) — the central General Ledger table that stores every valid account code combination, its structure assignment, dates, and posting/budgeting flags.
• FND_ID_FLEX_STRUCTURES_TL (aliased CHART_OF_ACCOUNTS_TL) — the translatable definition table for key flexfield structures, supplying the chart of accounts name.

The two are joined on GL_ACCOUNT.CHART_OF_ACCOUNTS_ID = CHART_OF_ACCOUNTS_TL.ID_FLEX_NUM, filtered to the current session language (USERENV('LANG')), application 101 (General Ledger), and the GL# flexfield code. A security predicate (_SEC:GL:NULL, GL_ACCOUNT.CODE_COMBINATION_ID IS NOT NULL) enforces row-level access. The view is declared WITH READ ONLY.

Key Columns

• ACCOUNT_ID — the underlying CODE_COMBINATION_ID; exposed with the _KF:ACCOUNT alias indicating the key-flexfield identifier.
• CHART_OF_ACCOUNTS_ID — identifier of the accounting structure to which the combination belongs.
• CHART_OF_ACCOUNTS_NAME — localized structure name from FND_ID_FLEX_STRUCTURES_TL.
• ACCOUNT_TYPE — lookup-driven account type (asset, liability, expense, etc.).
• DESCRIPTION — the account combination description.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — active date range of the combination.
• ENABLED_FLAG, ALLOW_POSTING_FLAG, ALLOW_BUDGETING_FLAG, SUMMARY_FLAG, PRESERVE_FLAG — lookup-backed Yes/No or summary indicators controlling whether the account may be posted to, budgeted against, or preserved.
• _DF — descriptive-flexfield reference (_DF:SQLGL:GL_CODE_COMBINATIONS:GL_ACCOUNT), used by the flexfield framework to resolve the account's descriptive flexfield context.

Common Use Cases and Queries

Because it is a flexfield value view, GLFV_GL_ACCOUNTS is normally consumed by the Flexfields engine rather than directly by end users. Consultants nonetheless query it for validation and diagnostics.

Listing postable accounts for a chart of accounts:

SELECT account_id, chart_of_accounts_name, description
FROM   apps.glfv_gl_accounts
WHERE  allow_posting_flag = 'Y'
AND    sysdate BETWEEN start_effective_date AND NVL(end_effective_date, sysdate);

Checking summary versus detail accounts:

SELECT account_id, summary_flag, enabled_flag
FROM   apps.glfv_gl_accounts
WHERE  summary_flag = 'SUM';

Typical scenarios include verifying that a code combination is enabled and within its effective dates before interfaces post to it, auditing which accounts permit budgeting, and tracing the chart-of-accounts name for a given combination. Reviewers should note that the view is read-only and subject to GL security, so results reflect only the rows the querying responsibility is permitted to see.