Results for “unit2_percent”

4 results




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

Overview

APPS.PQH_BDGT is the budget-management package body within the Oracle E-Business Suite Public Sector/HR (PQH) product family. It encapsulates the core business logic used to create, maintain, and propagate changes across budget versions, budget details, and budget periods for position and organization budgeting. In Oracle EBS 12.1.1 and 12.2.2, the package is registered with the API classification OTHER, indicating that it is an internal implementation unit rather than a formally published public API, although it is referenced by two other packages and is therefore part of the shared budget processing framework.

The package centers on the concept of a budget version, which stores hierarchical unit values (units 1, 2, and 3), their associated precision and aggregation attributes, and derived percentage and availability figures. The unit3_percent column, referenced in the cursor defined in PROPAGATE_VERSION_CHANGES, is one of the derived distribution percentages maintained against each budget detail row.

Key Procedures and Functions

The documented package body exposes seven procedures and functions:

  • GET_BGV_BUDGET — a function that resolves the parent budget identifier for a given budget version, reading from PQH_BUDGET_VERSIONS.
  • PROPAGATE_VERSION_CHANGES — the central routine that applies budget version-level changes down to the detail records. It accepts change mode, budget version identifier, budget style code, new unit1/unit2/unit3 values, precision and aggregation settings for each unit, and returns status plus available amounts for each unit. It locks and updates the unit values, percentages, and available columns.
  • PROPAGATE_BUDGET_CHANGES — applies budget-level modifications across the associated budget structures.
  • PROPAGATE_PERIOD_CHANGES — cascades period-level adjustments to the affected budget periods and details.
  • INSERT_BUDGET_DETAIL — creates new budget detail rows, initialising the unit values, percentages, and availability fields.
  • UPDATE_BUDGET_DETAIL — modifies existing budget detail records.
  • BGV_DATE_VALIDATION — validates date ranges associated with budget versions and periods.
  • GL_POST — posts budget amounts to the General Ledger, bridging budget maintenance and financial accounting.

Tables Accessed

The package operates on four documented tables, all accessed through APPS synonyms:

  • PQH_BUDGET_VERSIONS — stores version headers, including budget identifier and status; read and updated during propagation and validation.
  • PQH_BUDGET_DETAILS — the primary working table, holding unit values, value type codes, percentages (including budget_unit3_percent), available amounts, object version numbers, and GL status. Selections are made with FOR UPDATE to preserve concurrency control.
  • PQH_BUDGET_PERIODS — holds period-level budget records affected by period change propagation.
  • PQH_BUDGET_SETS — stores budget set definitions used when aggregating or propagating budget changes.

Usage Notes

PQH_BDGT is typically invoked indirectly rather than called directly by end users. It is referenced by two other packages within the budget subsystem and is exercised through budget maintenance forms (such as the Budget Version and Budget Detail windows) and associated concurrent programs that perform mass propagation or GL posting. The p_change_mode parameter in PROPAGATE_VERSION_CHANGES supports differing propagation behaviours, allowing callers to indicate whether changes are pushed to details, periods, or both. Because the package locks detail rows during propagation, custom extensions should invoke it from within a controlled transaction and avoid overlapping updates on the same budget version. The GL_POST procedure should be scheduled carefully, as it interfaces with General Ledger and affects downstream financial reporting. Customisations should treat APPS.PQH_BDGT as an internal, upgrade-sensitive object and prefer wrapping calls in site-specific APIs rather than modifying the package body.