Results for “gl_budget_assignment_pkg”

38 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.GL_BUDGET_ASSIGNMENT_PKG is a server-side PL/SQL package within the Oracle E-Business Suite General Ledger module. Its purpose is to manage the assignment of budget organizations, accounts, and account ranges to budget definitions stored in the GL_BUDGET_ASSIGNMENTS table. These assignments define which accounts a given budget is permitted to cover, forming the foundation of budget entry, budget inquiry, and budgetary control processing. The package encapsulates the data manipulation logic required to create, maintain, validate, and remove budget-to-account assignment records, shielding calling routines from direct DML against the underlying table. In the Oracle EBS 12.1.1 and 12.2.2 releases the package is reported as VALID under the APPS schema and is documented in ETRM with an API classification of OTHER, indicating that it is a supporting (rather than a public, fully supported) API. It operates alongside companion packages such as GL_BUD_ASSIGN_RANGE_PKG and GL_BUDGET_UTILS_PKG, which call its routines when manipulating budget assignment ranges and budget definitions.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions within the package. Their purposes are as follows:

  • CHECK_UNIQUE — Validates that a proposed budget assignment does not duplicate an existing assignment, enforcing uniqueness before an insert or update is committed.
  • DELETE_RANGE_ASSIGNMENTS — Removes assignment records associated with an account range, typically invoked when a range definition is changed or eliminated.
  • DELETE_ASSIGNMENT — Deletes a single budget assignment record for a specific budget and account combination.
  • IS_BUDGET_CALCULATED — Returns a status indicating whether amounts have already been calculated for the budget, allowing callers to prevent modification of assignments that would invalidate calculated data.
  • IS_ACCT_STAT_ENTERABLE — Determines whether an account and its related summary flag combination is enterable for the budget, supporting validation during budget entry.
  • SELECT_COLUMNS — Retrieves the column values of an existing budget assignment record for use by callers.
  • INSERT_ROW — Inserts a new budget assignment row into GL_BUDGET_ASSIGNMENTS.
  • LOCK_ROW — Obtains a row-level lock on an assignment record to serialize concurrent updates.
  • UPDATE_ROW — Updates an existing budget assignment record.
  • DELETE_ROW — Performs the low-level deletion of an assignment row from the table.

Tables Accessed

The package references a single documented table through APPS synonyms: GL_BUDGET_ASSIGNMENTS. This table stores the relationship between budget definitions and the accounts or account ranges they encompass. The package reads from it in SELECT_COLUMNS, IS_BUDGET_CALCULATED, IS_ACCT_STAT_ENTERABLE, and CHECK_UNIQUE, and writes to it through INSERT_ROW, UPDATE_ROW, DELETE_ROW, DELETE_ASSIGNMENT, and DELETE_RANGE_ASSIGNMENTS. Because budget assignment controls which accounts participate in a budget, correct maintenance of this table is essential to budget entry and reporting integrity.

Usage Notes

GL_BUDGET_ASSIGNMENT_PKG is not intended for direct invocation by end users but is called by Oracle EBS forms, concurrent programs, and other PL/SQL packages during budget definition and maintenance. ETRM shows it is referenced by three packages: GLF02220_PKG, GL_BUDGET_UTILS_PKG, and GL_BUD_ASSIGN_RANGE_PKG. GL_BUD_ASSIGN_RANGE_PKG in particular relies on the row-level insert, update, delete, and lock routines when processing assignment ranges. Because these routines bypass the higher-level validation and locking that the Oracle Forms layer normally applies, custom code should invoke the package with the same sequence of locking, uniqueness checking, and commit management used by the standard budget forms. Developers extending budget functionality should treat the package as an internal dependency and validate behavior against the specific 12.1.1 or 12.2.2 patch level in use.