Search Results gl_budorg_bc_options




Overview
Explore in AI Chat

Overview

GL_BUDORG_BC_OPTIONS is a General Ledger configuration table in Oracle E-Business Suite (12.1.1 and 12.2.2) that stores Budgetary Control option settings scoped to a specific budget organization and funding budget version. It is one of the supporting tables behind the Budgetary Control feature set in Oracle GL, which governs how funds availability checking, tolerance enforcement, and budget boundary behavior are applied during transaction entry and posting. Each row effectively defines a rule context: for a given budget range (RANGE_ID) and funding budget version (FUNDING_BUDGET_VERSION_ID), the table records the level at which funds are checked, the amount basis used for the check, and how boundary conditions are treated.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. No foreign key dependencies were identified, so it is best modeled as an independent reference/satellite-style configuration entity rather than a hub or link. Practically, it behaves as a keyed options record whose natural identity is the composite (RANGE_ID, FUNDING_BUDGET_VERSION_ID).

Key Information Stored

The table contains 10 documented columns. The composite primary key, enforced by GL_BUDORG_BC_OPTIONS_PK and mirrored by the unique index GL_BUDORG_BC_OPTIONS_U1, is (RANGE_ID, FUNDING_BUDGET_VERSION_ID). These two columns are the business-key candidates and identify which budget organization range is being configured and against which funding budget version the control applies.

  • RANGE_ID — Part of the composite key; references the budget organization range whose budgetary control behavior is being defined.
  • FUNDING_BUDGET_VERSION_ID — Part of the composite key; identifies the budget version that funds the range and against which availability is evaluated.
  • FUNDS_CHECK_LEVEL_CODE — Determines the level at which funds availability is validated (for example, account, detail, or summary level behavior).
  • AMOUNT_TYPE — Specifies the monetary basis used for the funds check, such as budget, encumbrance, or actual amounts.
  • BOUNDARY_CODE — Controls how boundary conditions are interpreted when a transaction reaches or exceeds the budget limit.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard WHO audit columns recording the last modification and its session context.

Common Use Cases and Queries

Typical uses include validating Budgetary Control configuration after setup, diagnosing funds-check failures at posting, and auditing option changes across budget versions. A common reporting pattern retrieves all options for a given range:

  • SELECT RANGE_ID, FUNDING_BUDGET_VERSION_ID, FUNDS_CHECK_LEVEL_CODE, AMOUNT_TYPE, BOUNDARY_CODE FROM GL.GL_BUDORG_BC_OPTIONS WHERE RANGE_ID = :p_range_id;
  • Joining to budget organization and budget version definitions to display human-readable names alongside the codes.
  • Comparing option rows across two funding budget versions to confirm consistent control settings before a budget rollover.
  • Auditing recent configuration changes using LAST_UPDATED_BY and LAST_UPDATE_DATE filters.

Related Objects

Because the ETRM metadata classifies this object as standalone, direct foreign-key relationships are not documented. The most significant dependencies are conceptual and join-key based: