Search Results gl_summary_bc_options_u1

Overview

GL.GL_SUMMARY_BC_OPTIONS is a General Ledger configuration table that stores budgetary control parameters assigned to individual summary templates within the Oracle E-Business Suite Summary Accounts form. Its role is to persist the funds-checking behavior that applies when a summary account is used in budgetary control processing, effectively binding a summary template to a funding budget version and capturing the control attributes that govern how that combination is evaluated. The table is classified as VALID in the ETRM schema repository and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The FND Design Data reference is SQLGL.GL_SUMMARY_BC_OPTIONS.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone and does not document any foreign key references. This suggests treating GL_SUMMARY_BC_OPTIONS as an independent hub or reference table, with the template and budget version identifiers serving as the natural business keys. The absence of documented foreign keys also implies that referential integrity is enforced at the application layer rather than through database constraints, a common pattern in EBS GL configuration tables.

Key Information Stored

The table is composed of 11 documented columns. The primary key constraint, GL_SUMMARY_BC_OPTIONS_PK, is defined over TEMPLATE_ID and FUNDING_BUDGET_VERSION_ID. The unique index GL_SUMMARY_BC_OPTIONS_U1 replicates this composite key, making both columns the business-key candidates for the table.

• TEMPLATE_ID (NUMBER 15, mandatory) — Summary template defining column; identifies the summary account template to which budgetary control options are attached.
• FUNDING_BUDGET_VERSION_ID (NUMBER 15, mandatory) — Funding budget version defining column; identifies which budget version supplies the funding for funds checking.
• FUNDS_CHECK_LEVEL_CODE (VARCHAR2 30) — Funds checking severity level, determining whether the system enforces absolute, advisory, or no funds checking.
• DR_CR_CODE (VARCHAR2 30) — Debit or credit indicator, specifying the transaction direction to which the budget check applies.
• AMOUNT_TYPE (VARCHAR2, unspecified length) — Amount type such as period-to-date or year-to-date, defining the aggregation basis for the funds check.
• BOUNDARY_CODE (VARCHAR2 30) — Budgetary control time interval end point, defining the period boundary over which the check is evaluated.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard Who columns capturing audit and concurrency information.

Common Use Cases and Queries

The primary use case is configuration review and troubleshooting of summary account budgetary control setups. Administrators and technical consultants query this table to confirm which budget version, checking level, and boundary apply to a given summary template before diagnosing funds-check failures during journal entry or purchase order processing. A representative query joins the template ID to the summary template definitions:

• Retrieve all control options for a template: SELECT * FROM GL.GL_SUMMARY_BC_OPTIONS WHERE TEMPLATE_ID = :p_template_id;
• Identify templates using a specific funding budget version: SELECT TEMPLATE_ID, FUNDS_CHECK_LEVEL_CODE FROM GL.GL_SUMMARY_BC_OPTIONS WHERE FUNDING_BUDGET_VERSION_ID = :p_version_id;
• Audit recently modified configurations using the Standard Who columns ordered by LAST_UPDATE_DATE.

Because the unique index GL_SUMMARY_BC_OPTIONS_U1 covers TEMPLATE_ID and FUNDING_BUDGET_VERSION_ID, equality queries on these two columns resolve with an index unique scan, making lookups efficient. Reporting use cases include producing a matrix of funds-checking levels by template for compliance and audit purposes.

Related Objects

The ETRM dependency metadata states that GL.GL_SUMMARY_BC_OPTIONS does not reference any database object directly, but it is referenced by the APPS synonym GL_SUMMARY_BC_OPTIONS. Key objects related through logical, application-level joins include:

• GL.GL_SUMMARY_TEMPLATES — parent of TEMPLATE_ID; defines the summary account template being configured.
• GL.GL_BUDGET_VERSIONS — parent of FUNDING_BUDGET_VERSION_ID; supplies the funding budget version.
• GL.GL_BUDGETS — budget definition underlying the version referenced above.
• GL.GL_SUMMARY_ACCOUNTS — summary accounts derived from the configured templates.
• APPS.GL_SUMMARY_BC_OPTIONS — the APPS synonym used for runtime access.

These relationships are enforced functionally within the Summary Accounts form rather than through declared foreign keys, which is why ETRM flags the object as standalone in the mined relationship data.