Search Results check_overlaps

Overview

APPS.GL_SUMMARY_BC_OPTIONS_PKG is a General Ledger package that maintains the budget control option rows stored in GL_SUMMARY_BC_OPTIONS. These rows define the funding budget version, template, funds check level, debit/credit indicator, amount type, and boundary code used when summary accounts and summary templates participate in budgetary control. The package is therefore part of the infrastructure that allows summary-level budget checking to be configured against a specific budget version and template.

The package body carries version information from the 12.1.1 code line (glistbcb.pls 120.4.12010000.1) and remains documented for 12.2.2 under the same object name and APPS owner, with an API classification of OTHER. It exposes a small, focused interface rather than a broad public API, and it is referenced by one other package.

Key Procedures and Functions

• INSERT_ROW — Inserts a new budget control option row into GL_SUMMARY_BC_OPTIONS. The declaration accepts the row identifier as an IN OUT NOCOPY parameter together with the option attributes: funds check level code, debit/credit code, amount type, boundary code, template identifier, funding budget version identifier, and the standard WHO audit columns (last update date, last updated by, created by, creation date, last update login).
• LOCK_ROW — Obtains a row-level lock on an existing GL_SUMMARY_BC_OPTIONS record so that concurrent maintenance or validation does not interleave with an in-flight update.
• INSERT_BC_OPTIONS — Provides the higher-level entry point used to create budget control option data for a summary template, coordinating the underlying inserts.

The body also declares two private cursors. The cursor relevant to the search term check_overlaps joins GL_BUDGETS, GL_BUDGET_VERSIONS, GL_SUMMARY_BC_OPTIONS, and GL_PERIOD_STATUSES twice to detect whether a candidate funding budget version's valid period range overlaps the range already associated with the same template. Overlap is expressed as NOT (previous last period precedes the new first period OR previous first period follows the new last period), with application_id 101 and matching ledger_id enforced for both period status joins. A second cursor selects existing rows from GL_SUMMARY_BC_OPTIONS for a given template and funding budget version. Overlap detection is the key integrity rule enforced during insertion: budget control options for one template must not be bound to two budget versions whose effective period ranges intersect.

Tables Accessed

• GL_SUMMARY_BC_OPTIONS — The primary table; rows are inserted, locked, and queried through the rowid and template/budget version cursors.
• GL_BUDGETS and GL_BUDGET_VERSIONS — Supply first and last valid period names and the version-to-budget-version mapping used in overlap checking.
• GL_GL_LEDGERS — Provides the ledger context required to join period statuses correctly.
• GL_PERIOD_STATUSES — Supplies effective_period_num values for both compared budget versions; the package uses these numeric period positions to determine range overlap.
• GL_SUMMARY_TEMPLATES — Relates the option row to the summary template being configured.
• DUAL — Used as the driving row for the EXISTS-based overlap probe.

Usage Notes

The package is invoked from Oracle EBS forms and concurrent processing that configure summary budgetary control, and may be called from custom code that programmatically creates budget control option rows. Customizations should preserve the overlap rule enforced by the private check_overlaps cursor, because inserting a funding budget version whose effective period range conflicts with an existing option for the same template will bypass a control the application relies upon. Because INSERT_ROW takes an IN OUT NOCOPY rowid and expects WHO audit values to be passed explicitly, callers should obtain those values from the standard EBS auditing conventions before invoking it.