Search Results update_budget

Overview

APPS.PQH_BUDGETS_API is a public PL/SQL API package belonging to the Oracle E-Business Suite Public Sector / Human Resources budgeting component (PQH product family). It provides the programmatic interface for creating, maintaining, and removing budget definitions used by position control and related HR budgeting processes. In the Oracle EBS 12.1.1 and 12.2.2 releases, the package is classified as an API, meaning that customer extensions, forms, and concurrent programs are intended to call it directly rather than performing DML against the underlying PQH_BUDGETS table. The package encapsulates validation, surrogate key generation, object version management, and WHO-column maintenance, ensuring that budget records satisfy the integrity constraints expected by downstream budgeting, position control, and General Ledger transfer routines.

Key Procedures and Functions

The ETRM metadata documents three procedures within the package body:

• CREATE_BUDGET — Inserts a new budget definition into PQH_BUDGETS. It accepts the full set of budget attributes, including business group, start organization, organization structure version, budgeted entity code, budget style code, budget name, period set name, budget start and end dates, GL budget name, PSB budget flag, transfer-to-GL and transfer-to-Grants flags, status, budget unit identifiers and aggregates, position control flag, valid grade required flag, currency code, default budget set identifier, and effective date. The procedure returns the generated budget identifier and the object version number, and supports a validation-only mode in which all business rules are executed without committing data.
• UPDATE_BUDGET — Modifies an existing budget record. This is the procedure most commonly searched for by developers integrating with the budgeting tables. It applies the same attribute set as creation and relies on the object version number for optimistic locking, preventing lost updates when concurrent sessions edit the same budget.
• DELETE_BUDGET — Removes a budget definition, subject to the referential and business validation rules enforced by the package.

Each procedure follows the standard EBS API conventions: a p_validate boolean flag for rollback-based testing, IN parameters with defaults for optional attributes, and OUT NOCOPY parameters returning primary keys and version numbers. Error conditions are signalled through the standard FND_MSG_PUB / APPS.FND_API exception mechanism.

Tables Accessed

The package reads and writes the PQH_BUDGETS table through the APPS synonym. This is the single documented table reference and is the primary persistence point for all budget definitions manipulated by the three procedures. CREATE_BUDGET performs the insert, UPDATE_BUDGET performs the update, and DELETE_BUDGET performs the delete. The object version number column in this table underpins the optimistic locking strategy used by the update path.

Usage Notes

In typical deployments, PQH_BUDGETS_API is invoked from the Oracle Forms-based budgeting and position control screens delivered with the Public Sector / HR product set. Concurrent programs that seed or migrate budget definitions may also call the API. Because the package is classified as an API, custom PL/SQL should invoke CREATE_BUDGET, UPDATE_BUDGET, and DELETE_BUDGET rather than writing directly to PQH_BUDGETS; the API metadata records that four other packages reference this API, confirming its role as a shared integration point. When calling from custom code, set p_validate to TRUE during testing to exercise validations without persisting data, capture the returned budget identifier for subsequent operations, and always store the returned object version number so that later updates can be issued with correct locking semantics.