Search Results insert_bc_options




Overview
Explore in AI Chat

Overview

GL_SUMMARY_BC_OPTIONS_PKG is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its stated purpose, per the package header, is "to contain validation and insertion routines for gl_summary_bc_options." The package supports Oracle General Ledger's Summary Accounts and budgetary control configuration by managing the rows that define how budget checking (funds checking) options are applied to summary account templates. The header history shows the package was created in January 2005 by A. Govil, with the added ISetup-facing procedure introduced in December 2006, and the file revision carried the 12.1.1-era identifier (120.2.12010000.1, dated 2008/07/28), which remains valid across 12.1.1 and 12.2.2. The package is classified under ETRM as API type OTHER and is referenced by one other package, confirming it acts as a lower-level utility rather than a form-driven data block handler.

Key Procedures and Functions

The package exposes three documented procedures. All are public and declared in the package specification.

  • Insert_Row — Inserts a new row into GL_SUMMARY_BC_OPTIONS. It accepts an IN OUT NOCOPY ROWID token together with the funds check level code, Dr/Cr code, amount type, boundary code, template identifier, funding budget version identifier, and the standard WHO audit columns (creation date, created by, last update date, last updated by, last update login). The ROWID parameter returns the physical address of the newly inserted row.
  • Lock_Row — Obtains a row-level lock on a selected GL_SUMMARY_BC_OPTIONS row using the supplied ROWID and validates that the caller's column values still match the persisted values, raising an error on concurrent modification. This is the standard EBS optimistic concurrency check.
  • Insert_BC_Options — Documented as the API given to the ISetup API to insert a new row into GL_SUMMARY_BC_OPTIONS. It mirrors the Insert_Row parameter signature, including the ROWID token and audit columns, and exists specifically to provide a supported programmatic entry point for the ISetup migration and setup-copy framework rather than for direct form use.

No functions are declared in the documented metadata.

Tables Accessed

ETRM records the following objects referenced through APPS synonyms:

  • GL_SUMMARY_BC_OPTIONS — The primary target of both insert procedures; stores per-template budgetary control option rows.
  • GL_SUMMARY_TEMPLATES — Defines the summary account templates that the BC options attach to via TEMPLATE_ID.
  • GL_BUDGETS and GL_BUDGET_VERSIONS — Budget definition and version sources used to resolve and validate the funding budget version identifier.
  • GL_LEDGERS — Provides ledger context supporting the funds check level and boundary validation.
  • GL_PERIOD_STATUSES — Supports budget/period validation logic.
  • DUAL — Used for scalar lookups, sequence retrieval, and SYSDATE/WHO column derivation.

Usage Notes

GL_SUMMARY_BC_OPTIONS_PKG is not intended for direct invocation from concurrent programs or user-facing forms. Insert_Row and Lock_Row are called by the General Ledger summary template maintenance forms layer, where Lock_Row performs the concurrency check before an update and Insert_Row materializes new option rows. Insert_BC_Options is the sanctioned interface for the ISetup setup-migration API, allowing budgetary control options to be copied or loaded between environments without bypassing validation. Custom code should invoke Insert_BC_Options rather than performing direct INSERT statements, since the procedure encapsulates validation and WHO audit column population. The IN OUT NOCOPY ROWID parameter must be declared by the caller and is populated on success. Because the package operates on configuration metadata only, it performs no accounting or funds-check posting; the same source (120.2.12010000.1) is shipped in both 12.1.1 and 12.2.2, so no version-specific behavior differences are documented.