Search Results gl_account




Overview
Explore in AI Chat

Overview

APPS.GLBV_GL_ACCOUNTS is a read-only Oracle EBS view that exposes GL code combination (accounting flexfield) definitions in a Business Intelligence/OBIA-compatible format. It is defined with the WITH READ ONLY clause, meaning no DML is permitted against the object. The view presents one row per accounting flexfield combination stored in GL_CODE_COMBINATIONS and is used primarily for reporting, BI Publisher extracts, Oracle Business Intelligence Applications (OBIA) ETL, and flexfield-aware data integration.

The prefix "GLBV" is characteristic of OBIA GL business-view objects. The view's role is to surface the segment values, descriptive attributes, and enabled/active flags of GL accounts in a form that downstream reporting layers can consume without issuing hints or security predicates directly against GL_CODE_COMBINATIONS.

Underlying Base Objects

The ETRM-extracted SQL shows a single source object: GL_CODE_COMBINATIONS, aliased as GL_ACCOUNT. No intermediate objects or joins are documented. Every column in the view maps directly to a column on GL_CODE_COMBINATIONS, with the exception of the injected BIO/OBIA directives described below.

The WHERE clause contains '_SEC:GL:NULL,GL_ACCOUNT.CODE_COMBINATION_ID' IS NOT NULL. This is a virtual predicate interpreted by the OBIA/OBIEE session security layer, not a literal SQL predicate. It instructs the security engine to apply the GL security profile against CODE_COMBINATION_ID and evaluates to a non-null condition; hence the literal string is always "IS NOT NULL" while the BIO layer enforces row-level segregation. Because the predicate is dependent on a security context, the view is not safe to query from a context where that BIO layer is absent — without it, no filtering occurs.

Key Columns

  • CODE_COMBINATION_ID — surrogate primary key joining the account to GL_BALANCES, GL_JE_LINES, and other transaction tables.
  • '_KF:SQLGL:GL#:GL_ACCOUNT' — a key-flexfield (KF) directive that instructs the OBIA layer to resolve the concatenated accounting flexfield segments for the row.
  • CHART_OF_ACCOUNTS_ID — identifies the chart of accounts (structure) to which the combination belongs.
  • '_LA:GL_ACCOUNT.ACCOUNT_TYPE:GL_LOOKUPS:ACCOUNT TYPE:DESCRIPTION' — lookup-attribute directive that resolves ACCOUNT_TYPE through GL_LOOKUPS to the descriptive meaning (e.g., Asset, Liability, Revenue, Expense).
  • DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE — free-text description and the active date range of the account.
  • ENABLED_FLAG, DETAIL_POSTING_ALLOWED_FLAG, DETAIL_BUDGETING_ALLOWED_FLAG, PRESERVE_FLAG — each exposed through a lookup-attribute (LA) directive resolving YES/NO to MEANING.
  • DECODE(SUMMARY_FLAG,'N','DTL','SUM') — LA directive that converts the summary flag into 'DTL' (detail) or 'SUM' (summary).

Columns prefixed with '_LA:' or '_KF:' are not physical SQL expressions in the ordinary sense; they are BIO metadata tokens substituted at runtime by the Oracle BI server or OBIA extractor.

Common Use Cases and Queries

Typical uses include generating account listings for GL reporting, resolving ACCOUNT_TYPE classifications, validating enabled/detail-posting status, and feeding OBIA GL data warehouses. A straightforward query selecting documented physical columns is:

  • SELECT code_combination_id, chart_of_accounts_id, description, enabled_flag, start_date_active, end_date_active FROM apps.glbv_gl_accounts;
  • Filter enabled accounts: SELECT code_combination_id, description FROM apps.glbv_gl_accounts WHERE enabled_flag = 'Y';
  • Join to balances: SELECT a.code_combination_id, a.description, b.period_name, b.begin_balance_dr FROM apps.glbv_gl_accounts a, apps.gl_balances b WHERE a.code_combination_id = b.code_combination_id;

Because the view is read-only and carries a virtual security predicate, direct SQL access is normally restricted to the APPS schema or accounts granted the appropriate GL security profile. End users typically reach it through OBIA dashboards or OBIEE subject areas rather than by querying directly.