Results for “gl_bc_option_details”

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

Overview

GL_BC_OPTION_DETAILS is a General Ledger (GL) table in Oracle E-Business Suite that stores budgetary control option details. It belongs to the Budgetary Control feature set, which governs funds checking and funds reservation behavior for journal entries posted against enabled ledger configurations. In Oracle EBS 12.1.1 and 12.2.2, the table operates as a child of GL_BC_OPTIONS, refining the parent budgetary control definition at the level of individual journal source and journal category combinations.

Budgetary control in EBS determines whether transactions are checked against available funds, the level at which the check occurs, and the tolerance thresholds applied when a transaction exceeds the control amount. GL_BC_OPTION_DETAILS carries those per-source, per-category refinements, allowing organizations to apply different funds check levels and tolerances to different transaction streams within the same budgetary control option. The table resides in the GL schema and holds 28 documented columns in the 12.2.2 physical schema.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is a link. This recommendation reflects the table's structure: its primary key combines BC_OPTION_ID, JE_SOURCE_NAME, and JE_CATEGORY_NAME, meaning it associates a parent budgetary control option with the journal source and category context in which that option applies. It functions as an associative construct rather than an independent hub or a descriptive satellite.

Key Information Stored

The table's primary key is GL_BC_OPTION_DETAILS_PK, defined over BC_OPTION_ID, JE_SOURCE_NAME, and JE_CATEGORY_NAME. A unique index, GL_BC_OPTION_DETAILS_U1, is documented over the same three columns, confirming the business-key candidate. The most important columns include:

• BC_OPTION_ID — Surrogate foreign key to the parent budgetary control option in GL_BC_OPTIONS. Identifies which control definition this detail row belongs to.
• JE_SOURCE_NAME — The journal source to which this detail applies, such as Payables or Manual.
• JE_CATEGORY_NAME — The journal category, validated against GL_JE_CATEGORIES_TL, that scopes the detail row.
• FUNDS_CHECK_LEVEL_CODE — Indicates the level at which funds checking is performed (for example, absolute, advisory, or none) for this source/category combination.
• OVERRIDE_AMOUNT — The amount threshold beyond which manual override of a failed funds check is permitted.
• TOLERANCE_PERCENTAGE — Percentage tolerance applied when evaluating funds availability.
• TOLERANCE_AMOUNT — Absolute monetary tolerance applied to the funds check.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns that record who created and last modified the row and when.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield storage used for customer-specific extensions.

Common Use Cases and Queries

Typical reporting retrieves the funds check behavior configured for a given budgetary control option. A common pattern joins the detail table to its parent and to the journal category translations:

• Listing all source/category combinations configured under a specific option: SELECT d.JE_SOURCE_NAME, d.JE_CATEGORY_NAME, d.FUNDS_CHECK_LEVEL_CODE FROM GL_BC_OPTION_DETAILS d WHERE d.BC_OPTION_ID = :option_id.
• Resolving category descriptions: join JE_CATEGORY_NAME to GL_JE_CATEGORIES_TL on the name column to obtain the user-facing category label.
• Auditing tolerance configuration: query OVERRIDE_AMOUNT, TOLERANCE_PERCENTAGE, and TOLERANCE_AMOUNT to verify that funds check tolerances match organizational policy.
• Reconciling budgetary control setup against journal entry activity to diagnose why a given source or category was or was not subjected to funds checking.

Related Objects

• GL_BC_OPTIONS — Parent table; joined on BC_OPTION_ID. Supplies the header-level budgetary control configuration.
• GL_JE_CATEGORIES_TL — Joined on JE_CATEGORY_NAME; provides translated journal category names and descriptions.
• GL_JE_SOURCES_TL — Related by JE_SOURCE_NAME for journal source validation and reporting.
• GL_BC_OPTION_DETAILS_PK / GL_BC_OPTION_DETAILS_U1 — Primary key constraint and unique index enforcing the composite business key.
• GL_BC_OPTIONS_API or configuration forms — Application logic that inserts and maintains detail rows during budgetary control setup.