Results for “bc_option_id”

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

Overview

GL_BC_OPTIONS is a General Ledger configuration table that stores budgetary control options in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Budgetary control governs whether expenditures, encumbrances, and funds reservations are validated against available budget balances before a transaction is approved or posted. The options captured in this table define the operating parameters applied when the Budgetary Control engine evaluates a transaction, including the level at which control is enforced and the tolerance behavior configured for the ledger.

From a dimensional modeling perspective, the mined foreign key structure classifies this object as hub-leaning. In Data Vault terms, GL_BC_OPTIONS behaves as a hub: it holds the durable, uniquely identified business concept — a named budgetary control option set — while descriptive and rule-specific attributes are distributed to dependent satellite structures such as GL_BC_OPTION_DETAILS. This is a heuristic classification suggested by the relationship data, not a physical constraint enforced by the database.

Key Information Stored

The documented physical schema contains 25 columns. The most significant are:

• BC_OPTION_ID — the surrogate primary key, enforced by GL_BC_OPTIONS_PK. It uniquely identifies each budgetary control option record and is the column referenced by dependent tables.
• BC_OPTION_NAME — the user-facing name of the option set, serving as a business-key candidate through unique index GL_BC_OPTIONS_UK1 / GL_BC_OPTIONS_U2.
• DESCRIPTION — free-text explanation of the option's purpose, useful for documentation and reporting.
• ZD_EDITION_NAME — the edition identifier used in the 12.2.2 online patching (adop) architecture, enabling edition-based redefinition of configuration rows. It participates in both GL_BC_OPTIONS_U1 (BC_OPTION_ID, ZD_EDITION_NAME) and GL_BC_OPTIONS_U2 (BC_OPTION_NAME, ZD_EDITION_NAME).
• LAST_UPDATE_DATE, LAST_UPDATED_BY — the standard WHO audit columns identifying when and by whom the record was last changed.
• CREATION_DATE, CREATED_BY — the standard WHO audit columns capturing record creation.
• LAST_UPDATE_LOGIN — the login identifier associated with the most recent update.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) container. These fifteen attribute columns allow customers to extend the table without a schema change; the values are surfaced through the budgetary control setup DFF.

The distinction between the surrogate key (BC_OPTION_ID) and the business-key candidates (BC_OPTION_NAME, alone or combined with ZD_EDITION_NAME) is important: foreign keys reference the surrogate, while user interfaces and interfaces typically resolve the name.

Common Use Cases and Queries

Typical scenarios include reporting the budgetary control configuration of a ledger, auditing changes to control options, and joining option headers to their detail rows for a complete setup picture. A representative query lists configured options with their descriptive text:

• SELECT bc_option_id, bc_option_name, description FROM gl_bc_options ORDER BY bc_option_name;
• SELECT h.bc_option_name, d.* FROM gl_bc_options h, gl_bc_option_details d WHERE h.bc_option_id = d.bc_option_id; — joins the header to the detail records that carry the rule-level attributes.
• SELECT bc_option_name, last_update_date, last_updated_by FROM gl_bc_options WHERE last_update_date > :p_since; — an audit-oriented query for tracking recent configuration changes.
• In 12.2.2, filter on ZD_EDITION_NAME (for example, WHERE zd_edition_name = 'ORA$BASE') to select the running edition and avoid duplicate rows introduced by online patching.

Related Objects

• GL_BC_OPTION_DETAILS — the principal dependent table. Its column GL_BC_OPTION_DETAILS.BC_OPTION_ID is a foreign key to GL_BC_OPTIONS, forming a header-to-detail relationship that carries the individual budgetary control rules.
• GL_BC_OPTIONS_PK — the primary key constraint on BC_OPTION_ID that guarantees uniqueness of each control option.
• GL_BC_OPTIONS_UK1 / GL_BC_OPTIONS_U2 — unique index enforcing the business key on BC_OPTION_NAME.
• GL_BC_OPTIONS_U1 — unique index on BC_OPTION_ID and ZD_EDITION_NAME, supporting the edition-aware access pattern in 12.2.2.
• Budgetary control setup forms and concurrent programs in the GL module that read and validate these options when processing funds checking.

The table is small but configuration-critical: any change to a row propagates directly into how General Ledger enforces budget availability across the applications that post to it.