Results for “budget_measurement_type”

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

Overview

PQH_ENTITY_ELEMENT_TYPES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PQH (Public Sector HR) product family, which underpins the Enterprise Resource Planning and Budgeting functionality used by public sector and government customers. The view exposes the intersection of commitment entities (budgetable organizational or programmatic entities) with the payroll element types that have been associated with them through budget sets, budget periods, and budget elements. Its purpose is to answer the question: for a given entity, which element types are valid for budgeting, and through which budget measurement unit, such as unit 1 or unit 2, is that budgeting expressed.

The column budgeted_entity_cd, which prompted the search behind this article, appears here as a key descriptive attribute inherited from PQH_CMMTMNT_ENTITIES_V. It carries the short code identifying the entity against which budget amounts are held, complementing the longer budgeted_entity_name. Together these fields allow reports and interfaces to present budgeting data in both coded and human-readable form without requiring the consumer to join back to the commitment entities view.

Underlying Base Objects

The documented referenced objects are HR_GENERAL (a package), PAY_ELEMENT_TYPES (a view), and the synonyms PQH_BUDGET_ELEMENTS, PQH_BUDGET_PERIODS, and PQH_BUDGET_SETS, with the driving source being the view PQH_CMMTMNT_ENTITIES_V. The definition is a UNION ALL-style construct expressed as two SELECT branches combined with UNION, one for budget unit 1 and one for budget unit 2.

Each branch joins PQH_CMMTMNT_ENTITIES_V to PQH_BUDGET_PERIODS on budget_detail_id, then to PQH_BUDGET_SETS on budget_period_id, then to PQH_BUDGET_ELEMENTS on budget_set_id, and finally to PAY_ELEMENT_TYPES on element_type_id. The join chain therefore traverses commitment entity to budget detail to budget period to budget set to budget element to element type. The first branch is filtered by BPR.BUDGET_UNIT1_VALUE IS NOT NULL and maps BUDGET_UNIT1_NAME and BUDGET_UNIT1_ID to the output columns BUDGET_MEASUREMENT_TYPE and BUDGET_UNIT_ID; the second branch applies the analogous logic for unit 2. Date-tracked filtering is enforced through HR_GENERAL.EFFECTIVE_DATE between the entity version from and to dates, and business group context is applied using NVL against HR_GENERAL.GET_BUSINESS_GROUP_ID.

Key Columns

• ELEMENT_NAME / ELEMENT_TYPE_ID — the payroll element type name and its surrogate identifier, sourced from PAY_ELEMENT_TYPES and PQH_BUDGET_ELEMENTS respectively.
• ENTITY_NAME / ENTITY_ID — the name and identifier of the commitment entity being budgeted.
• BUDGETED_ENTITY_CD / BUDGETED_ENTITY_NAME — the code and descriptive name of the budgeted entity; these are the fields most often used for grouping and display in budget reports.
• BUDGET_MEASUREMENT_TYPE / BUDGET_UNIT_ID — the measurement basis (unit 1 or unit 2 name) and its identifier, indicating whether the row was produced from the unit 1 or unit 2 branch of the UNION.

Common Use Cases and Queries

Typical uses include validating which element types may be used against an entity during budget entry, populating LOVs or integration extracts, and reconciling budget setup between commitment entities and element types. Because the view is date-effective filtered, queries should be run with a defined effective date session context.

SELECT budgeted_entity_cd,
       budgeted_entity_name,
       element_name,
       budget_measurement_type
FROM   apps.pqh_entity_element_types_v
WHERE  budgeted_entity_cd = :p_entity_cd
ORDER  BY budgeted_entity_name, element_name;

A second common pattern aggregates eligible element types per entity to confirm setup completeness:

SELECT budgeted_entity_cd,
       COUNT(DISTINCT element_type_id) element_type_count
FROM   apps.pqh_entity_element_types_v
GROUP  BY budgeted_entity_cd
HAVING COUNT(DISTINCT element_type_id) = 0;

Queries should filter on the desired business group implicitly through the HR_GENERAL package context, since the view applies NVL(HR_GENERAL.GET_BUSINESS_GROUP_ID, PCE.BUSINESS_GROUP_ID) to scope rows to the active business group.