Search Results insert_org




Overview
Explore in AI Chat

Overview

APPS.GL_BUDGET_ENTITIES_PKG is a server-side PL/SQL package in the Oracle General Ledger (GL) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It provides the core programmatic interface for maintaining budget entities — the definition records that establish which ledgers, organizations, and accounting ranges participate in a given budget. In the Oracle GL data model, budget entities represent the organizational and account-level scope of a budget, and this package encapsulates the logic required to create, validate, lock, and update those entity definitions without requiring callers to manipulate the underlying tables directly.

The package is classified as OTHER in the ETRM API registry rather than as a formally published public API, which indicates that it is an internal implementation package used by other GL budget components rather than a documented extension point for customer customization. Its dependency graph confirms this role: the package is referenced by GL_BUDGET_ASSIGNMENT_PKG, GL_BUDGET_UTILS_PKG, GL_BUD_ASSIGN_RANGE_PKG, IGC_UPGRADE_DATA_R12, and by itself, and it depends only on SYS and STANDARD. This placement at the base of the GL budget dependency chain makes it a foundational utility within the budgeting subsystem.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions within the package. Their names describe their intended roles:

  • CHECK_UNIQUE — validates uniqueness constraints on budget entity data before persistence, preventing duplicate entity definitions.
  • CHECK_FOR_ALL — performs a scope check, typically determining whether an entity applies to all applicable organizations or accounts.
  • HAS_RANGES — reports whether a budget entity has associated assignment ranges, allowing callers to branch on range-based versus direct entity configuration.
  • GET_UNIQUE_ID — generates or retrieves a unique identifier for a new budget entity record.
  • LOCK_ORGANIZATION — obtains a lock on an organization record to serialize concurrent maintenance of entity data.
  • SELECT_COLUMNS — supplies a standard column list used when querying budget entity data, promoting consistency across callers.
  • BUDGET_AND_ACCOUNT_SEG_INFO — retrieves budget and account segment information needed to resolve entity scope.
  • INSERT_ROW — inserts a budget entity row into the base table.
  • INSERT_ORG — inserts organization-level entity information associated with a budget entity.
  • UPDATE_ROW — updates an existing budget entity record.
  • LOCK_ROW — applies row-level locking to a budget entity record to protect it during transactional updates.
  • SUBMIT_ASSIGN_RANGES_REQUEST — submits the concurrent request that assigns budget ranges, delegating bulk range processing to the concurrent manager.
  • SET_BC_TIMESTAMP — maintains the "who" columns and timestamp audit fields on entity records.

Tables Accessed

The package operates against a small, focused set of tables accessed through APPS synonyms. GL_BUDGET_ENTITIES and its companion GL_BUDGET_ENTITIES_S store the budget entity definitions and their translation or secondary rows; these are the primary targets of the insert, update, and lock operations. GL_BUDGET_ASSIGNMENT_RANGES holds the account range assignments associated with budget entities and is the table interrogated by HAS_RANGES and populated by range assignment processing. GL_LEDGERS supplies ledger context used to resolve and validate the budget entity scope. DUAL is used for single-row computations typical of PL/SQL utility logic.

Usage Notes

Because this package is not a published public API, it should be invoked indirectly rather than called from custom code. Its principal consumers are the sibling GL budget packages: GL_BUDGET_ASSIGNMENT_PKG, GL_BUDGET_UTILS_PKG, and GL_BUD_ASSIGN_RANGE_PKG, which wrap its procedures in higher-level budgeting operations. The presence of SUBMIT_ASSIGN_RANGES_REQUEST indicates that range assignment is processed asynchronously through a concurrent program, so callers must expect the request submission pattern rather than immediate completion. The upgrade reference from IGC_UPGRADE_DATA_R12 shows the package also participates in release 12 data migration. Customizations that require budget entity maintenance are best implemented against the documented public GL budget APIs or by composing calls to the wrapping packages, leaving GL_BUDGET_ENTITIES_PKG as an internal dependency whose behavior may change between releases.