Results for “pqh_budget_entity”

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

Overview

APPS.PQH_CMMTMNT_ENTITIES_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Public Sector/HR budgeting and commitment accounting product family, delivered through the PQH (Public Sector Human Resources) application, with FND Design Data registered as PQH.PQH_CMMTMNT_ENTITIES_V. The object is documented as status VALID and is classified by Oracle as a "supplementary view used to simplify forms coding," a designation that carries an explicit Oracle warning: customers are not recommended to query or alter data through this view, because its definition may change dramatically in subsequent minor or major releases. Foreign key relationships are not published for the view. Despite that caveat, the object is heavily used internally — it is referenced by PQH_COMMITMENT_PKG and by PQH_ENTITY_ELEMENT_TYPES_V — and it remains a common target of ad hoc reporting on commitment, budget version, and budgeted-entity data for public sector and HR-funded organizations.

Underlying Base Objects

The view is defined over three PQH base objects — PQH_BUDGETS, PQH_BUDGET_DETAILS, and PQH_BUDGET_VERSIONS — each exposed through a synonym in the referenced-objects list, plus the HR_GENERAL packaged API, which supplies the descriptive name resolution logic (the character columns returned at VARCHAR2(4000) length are typical of HR_GENERAL name-formatting lookups rather than stored descriptive columns). The join model is straightforward: PQH_BUDGETS provides the budget header (BUSINESS_GROUP_ID, BUDGET_ID, BUDGET_DATE_FROM, BUDGET_DATE_TO), PQH_BUDGET_VERSIONS supplies the versioning slice (BUDGET_VERSION_ID, VERSION_FROM_DATE, VERSION_TO_DATE), and PQH_BUDGET_DETAILS supplies the line-level budgeted-entity rows (BUDGET_DETAIL_ID, BUDGET_UNIT1_ID through BUDGET_UNIT3_ID, BUDGETED_ENTITY_CD, ENTITY_ID). The view therefore flattens a three-table budget hierarchy into a single denormalized projection combining header, version, and detail context.

Key Columns

• BUSINESS_GROUP_ID — partition key identifying the HR business group; always filter this in multi-organization implementations.
• BUDGET_ID, BUDGET_VERSION_ID, BUDGET_DETAIL_ID — the composite identifier chain linking header, version, and detail rows.
• BUDGET_DATE_FROM / BUDGET_DATE_TO — the budget's effective date range, independent of the version range.
• VERSION_FROM_DATE / VERSION_TO_DATE — the effective-date boundaries of the specific budget version; the search term "version_to_date" maps directly to this column, the upper bound of a version's active window.
• BUDGET_UNIT1_ID/NAME, BUDGET_UNIT2_ID/NAME, BUDGET_UNIT3_ID/NAME — the three budget unit dimensions on the detail row, resolved to VARCHAR2(4000) display names via HR_GENERAL.
• BUDGETED_ENTITY_CD, BUDGETED_ENTITY_NAME — the budgeted entity type/code and its resolved name.
• ENTITY_ID, ENTITY_NAME — the specific entity instance associated with the budget line.

Common Use Cases and Queries

Because VERSION_TO_DATE is the effective end of a budget version, the most frequent pattern is point-in-time version resolution — identifying which version of a budget was in force on a given date. A direct query against the view follows the documented query text:

• Version as of a date: SELECT budget_id, budget_version_id, version_from_date, version_to_date, entity_name FROM apps.pqh_cmmtmnt_entities_v WHERE business_group_id = :p_bg_id AND TRUNC(:p_as_of_date) BETWEEN version_from_date AND NVL(version_to_date, TO_DATE('4712-12-31','YYYY-MM-DD')) ORDER BY budget_id, version_from_date;
• Currently active versions: filter with SYSDATE BETWEEN version_from_date AND NVL(version_to_date, TO_DATE('4712-12-31','YYYY-MM-DD')).
• Entities by budget unit: group on BUDGET_UNIT1_NAME, BUDGET_UNIT2_NAME, and BUDGET_UNIT3_NAME, joining ENTITY_NAME for reporting labels.
• Budget-to-entity reconciliation: compare PQH_BUDGETS and PQH_BUDGET_DETAILS row counts against the view for a given BUDGET_ID to detect orphaned or unversioned detail lines.

Third-party integrations should prefer the underlying PQH_BUDGETS, PQH_BUDGET_VERSIONS, and PQH_BUDGET_DETAILS tables, or the supported PQH_COMMITMENT_PKG API, rather than depending on this view's column list or join semantics.