Search Results glbv_gl_accounts

Overview

GLBV_GL_ACCOUNTS is a read-only view owned by the APPS schema in Oracle E-Business Suite General Ledger. It is a business view (indicated by the "BV" naming convention) that exposes chart of accounts information for flexfield-enabled reporting and integration across EBS modules. The view derives its data exclusively from GL_CODE_COMBINATIONS and presents account combinations in a form suitable for Oracle Business Intelligence, Web ADI, and other clients requiring a simplified business-facing representation of the accounting flexfield. Because it is created WITH READ ONLY, no DML is permitted against the view; all maintenance occurs directly on the underlying code combination records. The view is registered as VALID in both 12.1.1 and 12.2.2 and belongs to the GL product family.

Underlying Base Objects

The view text references a single base table, GL_CODE_COMBINATIONS, aliased as GL_ACCOUNT within the query. Each row of GL_CODE_COMBINATIONS corresponds to one stored account combination identified by CODE_COMBINATION_ID. GLBV_GL_ACCOUNTS does not join to additional tables; instead, it embeds flexfield and lookup semantics as metadata markers that the EBS framework interprets at runtime. Tokens such as _KF:SQLGL:GL#:GL_ACCOUNT identify the key flexfield context, while _LA: prefixes denote lookup-based display attributes resolved against GL_LOOKUPS. The predicate '_SEC:GL:NULL, GL_ACCOUNT.CODE_COMBINATION_ID' IS NOT NULL enforces security constraints, ensuring that the view returns only account combinations the querying responsibility is authorized to access. No additional documented base objects exist beyond GL_CODE_COMBINATIONS.

Key Columns

• ACCOUNT_ID — Maps to CODE_COMBINATION_ID; the unique identifier of the account combination. The _KF:ACCOUNT marker ties it to the key flexfield structure.
• CHART_OF_ACCOUNTS_ID — Identifies the chart of accounts to which the combination belongs, enabling multi-chart environments.
• DESCRIPTION — Free-form description stored on the code combination.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — The active date range of the account combination.
• ENABLED_FLAG, ALLOW_POSTING_FLAG, ALLOW_BUDGETING_FLAG, SUMMARY_FLAG, PRESERVE_FLAG — Lookup-decoded indicators controlling whether the account may be used for posting, budgeting, summarized reporting, or preserved against purge.

The quoted column names (for example "_LA:ENABLED_FLAG") are runtime substitutions resolved by the EBS lookup framework, presenting translated meaning values in place of raw codes.

Common Use Cases and Queries

GLBV_GL_ACCOUNTS is typically used when a report or integration requires posting-eligible accounts with human-readable attribute labels without joining GL_LOOKUPS manually. A representative query:

• SELECT ACCOUNT_ID, CHART_OF_ACCOUNTS_ID, DESCRIPTION, START_EFFECTIVE_DATE, END_EFFECTIVE_DATE FROM APPS.GLBV_GL_ACCOUNTS WHERE END_EFFECTIVE_DATE IS NULL;
• SELECT ACCOUNT_ID, DESCRIPTION FROM APPS.GLBV_GL_ACCOUNTS WHERE CHART_OF_ACCOUNTS_ID = :coa_id ORDER BY ACCOUNT_ID;

Because the view applies GL security rules through its WHERE clause, results are automatically scoped to the current responsibility's accessible accounts, making it well suited to self-service reporting. For bulk data extraction or join-heavy workloads, direct queries against GL_CODE_COMBINATIONS remain preferable, as the view's embedded metadata tokens may not translate cleanly outside the EBS client runtime.