Search Results gl_bc_option_details




Overview
Explore in AI Chat

Overview

The GL_BC_OPTION_DETAILS table is a core data object within the Oracle E-Business Suite General Ledger (GL) module, specifically for versions 12.1.1 and 12.2.2. It serves as a critical junction table that defines the application of budgetary control rules. Budgetary control is a financial discipline within Oracle EBS that enforces spending limits by comparing transaction amounts against predefined budgets. This table's primary role is to associate specific budgetary control options (which define the ruleset) with the precise combination of journal entry source and category to which those rules should be applied. This granular association allows for flexible and targeted enforcement of budgetary policies across different types of financial transactions.

Key Information Stored

The table stores the linkage between a budgetary control configuration and the transactional contexts it governs. Its structure is defined by a composite primary key, ensuring a unique rule for each source and category combination under a given option. The most significant columns are:

  • BC_OPTION_ID: A foreign key referencing the GL_BC_OPTIONS table. This identifies the specific budgetary control option (rule set) being applied.
  • JE_SOURCE_NAME: The name of the journal entry source (e.g., 'Payables', 'Receivables', 'Spreadsheet') to which the budgetary control option applies.
  • JE_CATEGORY_NAME: The name of the journal entry category (e.g., 'Invoice', 'Payment', 'Miscellaneous') within the specified source to which the option applies.

Common Use Cases and Queries

This table is central to queries analyzing or troubleshooting the setup of budgetary control. A common administrative task is to review all journal sources and categories that have budgetary control enabled. The following sample SQL retrieves this information, joining to the translated categories table for clarity:

SELECT gbod.BC_OPTION_ID, gbod.JE_SOURCE_NAME, gbod.JE_CATEGORY_NAME, gjct.NAME CATEGORY_DESCRIPTION
FROM GL.GL_BC_OPTION_DETAILS gbod,
GL.GL_JE_CATEGORIES_TL gjct
WHERE gjct.JE_CATEGORY_NAME = gbod.JE_CATEGORY_NAME
AND gjct.LANGUAGE = USERENV('LANG')
ORDER BY gbod.JE_SOURCE_NAME, gbod.JE_CATEGORY_NAME;

Another critical use case is during implementation or modification of budgetary control, where this table is populated or updated via the application's budgetary control forms to define the scope of enforcement for new or existing budget options.

Related Objects

GL_BC_OPTION_DETAILS maintains documented foreign key relationships with two primary tables, as per the provided ETRM metadata:

  • GL_BC_OPTIONS: This is the parent table for the budgetary control rule set. The relationship is defined by GL_BC_OPTION_DETAILS.BC_OPTION_ID = GL_BC_OPTIONS.BC_OPTION_ID. This join retrieves the master control option details (like name, description, and overall budget).
  • GL_JE_CATEGORIES_TL: This is the translated descriptions table for journal categories. The relationship is defined by GL_BC_OPTION_DETAILS.JE_CATEGORY_NAME = GL_JE_CATEGORIES_TL.JE_CATEGORY_NAME. This join is used to display the user-friendly category name in reports and inquiries.

While not listed in the provided excerpt, this table is intrinsically linked to the GL_JE_SOURCES_TL table for source descriptions and is fundamental to the engine that performs budgetary checks during journal entry.