Results for “propagate_version_changes”

8 results




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

Overview

PQH_BDGT is the budget maintenance package within the Oracle EBS Public Sector / Human Resources budgeting subsystem. It provides the server-side PL/SQL logic that underpins position and budget management functionality, allowing application forms and concurrent processes to create and maintain budget structures along three hierarchical levels: budget versions, budget details (lines), and budget periods. The package is declared AUTHID CURRENT_USER, meaning its unqualified object references and privilege checks execute under the invoking schema's security context rather than that of the package owner. This is significant in a shared APPS environment because it lets the calling form or program operate on the same synonyms and grants it already holds, avoiding definer's-rights conflicts.

The central design theme of the package is propagation: when a user enters or revises a monetary or unit value at one level of the budget hierarchy, the corresponding totals must be rolled forward or backward through the other levels. PQH_BDGT encapsulates this arithmetic and validation so that every entry point enforces the same rules.

Key Procedures and Functions

  • PROPAGATE_VERSION_CHANGES — propagates value and configuration changes made at the budget-version level. It accepts a change mode, the budget version identifier, the budget style code, new unit values, per-unit precision, and aggregation settings, and returns the version status plus three availability indicators as OUT NOCOPY parameters.
  • PROPAGATE_BUDGET_CHANGES — performs the equivalent propagation at the budget-detail (line) level, taking a budget detail identifier, new unit values, precision and aggregation parameters, and returning three availability flags.
  • PROPAGATE_PERIOD_CHANGES — the procedure associated with the search term propagate_period_changes. It propagates changes made to an individual budget period, driven by a change mode and a budget period identifier, along with new period unit values, precision settings, and three availability OUT NOCOPY parameters. This is the finest-grained of the three propagation routines.
  • INSERT_BUDGET_DETAIL — creates a new budget detail row. Its signature exposes the budget version identifier plus optional organization, job, position, and grade identifiers, reflecting the position-management context in which budget lines are defined.
  • UPDATE_BUDGET_DETAIL — modifies an existing budget detail record.
  • BGV_DATE_VALIDATION — validates date ranges associated with a budget version, ensuring that period boundaries do not conflict.
  • GL_POST — posts the completed budget data into General Ledger.

Tables Accessed

All four tables are referenced through APPS synonyms. PQH_BUDGET_VERSIONS stores the version header that PROPAGATE_VERSION_CHANGES and BGV_DATE_VALIDATION operate on. PQH_BUDGET_DETAILS holds the individual budget lines written by INSERT_BUDGET_DETAIL and UPDATE_BUDGET_DETAIL and adjusted by PROPAGATE_BUDGET_CHANGES. PQH_BUDGET_PERIODS contains the period-level breakdown manipulated by PROPAGATE_PERIOD_CHANGES. PQH_BUDGET_SETS provides the grouping construct that ties versions together for validation and posting purposes.

Usage Notes

PQH_BDGT is an internal application-programming interface rather than a public one. It is normally invoked indirectly: Oracle HRMS budget and position management forms call these procedures when a user commits a budget entry, and concurrent programs that build or post budgets call them in batch. GL_POST in particular is designed for posting runs. Because the package is classified OTHER in ETRM and only two other packages reference it, customizations should treat it as a stable internal dependency: extend the forms or wrap the package rather than modifying it, and be aware that the OUT NOCOPY availability parameters must be supplied for propagation calls to complete successfully.