Results for “gl_budorg_bc_options_v”

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

Overview

GL_BUDORG_BC_OPTIONS_V is an APPS-owned reporting view in the Oracle E-Business Suite General Ledger module. It exposes budget organization Budgetary Control options in a denormalized, user-friendly form, resolving the underlying code columns into their descriptive lookup meanings and resolving the funding budget version identifier into a budget name. The view is defined over the transactional table GL_BUDORG_BC_OPTIONS and joins to GL_BUDGET_VERSIONS and GL_LOOKUPS to present readable values. In ETRM 12.2.2 the view is documented as VALID with referenced base objects GL_BUDORG_BC_OPTIONS (SYNONYM), GL_BUDGET_VERSIONS (SYNONYM), and GL_LOOKUPS (VIEW). Because the view is a read-only projection, it is intended for inquiry, reporting, and integration extraction rather than for direct DML.

Underlying Base Objects

The view is defined with an outer-join construction. GL_BUDORG_BC_OPTIONS (aliased BCO) is the driving object and supplies the ROWID, range definition, check level, amount type, boundary code, and the funding budget version identifier. GL_BUDGET_VERSIONS (aliased BV) is outer-joined on BV.BUDGET_VERSION_ID(+) = BCO.FUNDING_BUDGET_VERSION_ID to translate the identifier into BUDGET_NAME. GL_LOOKUPS is joined twice in outer-join form: alias L resolves AMOUNT_TYPE against LOOKUP_TYPE = 'PTD_YTD', and alias L2 resolves BOUNDARY_CODE against LOOKUP_TYPE = 'BOUNDARY_TYPE'. The outer joins ensure that a row is returned even when a matching budget version or lookup value is absent, which is important for completeness of budgetary control configuration reporting.

Key Columns

• ROW_ID — the ROWID of the underlying GL_BUDORG_BC_OPTIONS row; useful for row-level identification and troubleshooting.
• RANGE_ID — identifier of the budget range definition to which the budgetary control option applies.
• FUNDS_CHECK_LEVEL_CODE — code indicating the level at which funds availability is enforced (for example, absolute or advisory).
• AMOUNT_TYPE — the amount basis used for the check; SHOW_AMOUNT_TYPE provides its meaning from the PTD_YTD lookup.
• BOUNDARY_CODE — the boundary handling code; SHOW_BOUNDARY provides its meaning from the BOUNDARY_TYPE lookup.
• FUNDING_BUDGET_VERSION_ID — the identifier of the budget version designated as the funding budget.
• FUNDING_BUDGET_NAME — the budget version name (BV.BUDGET_NAME) corresponding to FUNDING_BUDGET_VERSION_ID; this is the column most relevant to searches for "funding_budget_name."
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

The view supports reporting on budgetary control configuration by budget organization and range, and is particularly useful when the funding budget must be reported by name rather than by internal version identifier. A typical query lists the options for a given range:

SELECT range_id, funding_budget_name, show_amount_type, show_boundary, funds_check_level_code FROM gl_budorg_bc_options_v ORDER BY range_id;

To locate configuration tied to a specific funding budget by name:

SELECT range_id, funding_budget_version_id, funding_budget_name FROM gl_budorg_bc_options_v WHERE funding_budget_name = :budget_name;

Because FUNDING_BUDGET_NAME arrives through an outer join, rows with an unresolved funding budget version return a null name; a diagnostic query can isolate these gaps using WHERE funding_budget_version_id IS NOT NULL AND funding_budget_name IS NULL. Such gaps indicate a funding budget version reference that does not resolve to an existing GL_BUDGET_VERSIONS row and should be investigated before relying on the configuration for funds checking.