Search Results dr_cr_code




Overview
Explore in AI Chat

Overview

GL_SUMMARY_BC_OPTIONS_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the configuration options that govern summary-level budgetary control processing for a given summary account template. The view is a thin, direct projection of the GL_SUMMARY_BC_OPTIONS table; it does not aggregate, join, or transform data. Its role is to present budgetary control settings — funds check level, debit/credit indicator, amount type, and boundary code — together with the funding budget version identifier that determines which budget is consulted during funds checking. Because the object is stored in APPS and carries a VALID status, it is a supported read interface for reporting tools, extensions, and integrations that must inspect or validate summary account budgetary control setup. The name suffix "_V" does not imply a versioned or multi-org secured view; it is simply the public interface name over the base table.

Underlying Base Objects

The view is defined over a single object: the synonym GL_SUMMARY_BC_OPTIONS, which resolves to the APPS.GL_SUMMARY_BC_OPTIONS table. The view text confirms a one-to-one mapping, with every projected column prefixed by the table alias BCO. The ROWID of the base table row is surfaced as the ROW_ID column, which allows tools that require a pseudo-key (such as Oracle Forms or certain ETL routines) to identify rows uniquely even though the base table may not expose an equivalent surrogate key. No WHERE clause, DISTINCT, function call, or outer join appears in the view definition, so row counts and column values are identical to the underlying table. Because the view is a synonym-based wrapper and not a snapshotted or materialized object, any update to GL_SUMMARY_BC_OPTIONS is immediately visible. In 12.2.2 the same metadata is documented, with GL_SUMMARY_BC_OPTIONS listed as the referenced base object.

Key Columns

  • ROW_ID — the base table ROWID, used as a pseudo-primary key for record identification.
  • TEMPLATE_ID — foreign key to the summary account template that these budgetary control options apply to.
  • FUNDS_CHECK_LEVEL_CODE — the level at which funds checking is performed for the template (for example, absolute, advisory, or none).
  • DR_CR_CODE — indicates whether the option applies to debit or credit transactions.
  • AMOUNT_TYPE — the amount basis used during funds checking (for example, entered, accounted, or project amount).
  • BOUNDARY_CODE — defines how boundary or range accounts are treated when the summary template is evaluated.
  • FUNDING_BUDGET_VERSION_ID — the identifier of the budget version against which funds availability is checked for the template. This is the column most frequently referenced in integration and validation queries, and it links the summary option row to the budget definition used as the funding source.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN provide standard EBS audit and concurrency information.

Common Use Cases and Queries

Typical use cases include auditing summary account funds-check configuration, resolving the budget version used for a template, and migrating or comparing budgetary control setup across environments.

  • Locate the funding budget version for a template:
    SELECT TEMPLATE_ID, FUNDING_BUDGET_VERSION_ID, FUNDS_CHECK_LEVEL_CODE FROM APPS.GL_SUMMARY_BC_OPTIONS_V WHERE TEMPLATE_ID = :template_id;
  • List all templates configured for a specific funds check level:
    SELECT TEMPLATE_ID, AMOUNT_TYPE, BOUNDARY_CODE FROM APPS.GL_SUMMARY_BC_OPTIONS_V WHERE FUNDS_CHECK_LEVEL_CODE = 'A';
  • Reconcile the view against its base table, since no transformation is applied:
    SELECT COUNT(*) FROM APPS.GL_SUMMARY_BC_OPTIONS_V;

Developers should query the view rather than the table where a supported interface is preferred, and should always qualify the object with the APPS schema.