Results for “budget_unit3_id”

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

Overview

PQH_CMMTMNT_ENTITIES_V is a PL/SQL view owned by the APPS schema within the Public Sector HR (PQH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the entities associated with commitment budgets and budget versions, presenting them in a denormalized, report-friendly form. The view consolidates budget header information, budget version information, and budget detail records into a single logical row per budgeted entity, decoding internal identifiers into human-readable names through calls to the HR_GENERAL package. Its principal role is to support reporting and integration scenarios where a budget must be related to the organizations or positions it funds. Because the view already resolves coded values such as budget unit identifiers, budgeted entity types, and organization or position names, it is commonly used as a source for concurrent program extracts, BI Publisher data models, and custom OAF or Forms inquiries.

Underlying Base Objects

The ETRM metadata for the 12.2.2 release documents the following referenced base objects:

• PQH_BUDGETS (accessed through a synonym) — the budget header, supplying BUSINESS_GROUP_ID, BUDGET_ID, budget start and end dates, the three budget unit identifiers, and the BUDGETED_ENTITY_CD discriminator.
• PQH_BUDGET_VERSIONS (synonym) — the version rows that carry BUDGET_VERSION_ID and the version effective dates (DATE_FROM, DATE_TO).
• PQH_BUDGET_DETAILS (synonym) — the detail rows holding the entity references: ORGANIZATION_ID when the budgeted entity is an organization, or POSITION_ID when the budgeted entity is a position.
• HR_GENERAL (package) — a helper package invoked by the view text to decode identifiers, notably DECODE_SHARED_TYPE for budget unit names, DECODE_LOOKUP for the PQH_BUDGET_ENTITY lookup, DECODE_ORGANIZATION for organization names, and DECODE_POSITION_LATEST_NAME for position names.

The view is defined as a UNION of two branches, joined on BUDGET_ID between PQH_BUDGETS and PQH_BUDGET_VERSIONS and on BUDGET_VERSION_ID between PQH_BUDGET_VERSIONS and PQH_BUDGET_DETAILS. The first branch filters BUDGETED_ENTITY_CD = 'ORGANIZATION' and projects ORGANIZATION_ID as ENTITY_ID; the second filters BUDGETED_ENTITY_CD = 'POSITION' and projects POSITION_ID as ENTITY_ID. A third UNION branch (truncated in the excerpt) continues the pattern.

Key Columns

• BUSINESS_GROUP_ID — the business group that owns the budget.
• BUDGET_ID, BUDGET_VERSION_ID, BUDGET_DETAIL_ID — the primary keys of the budget, its version, and the detail line.
• BUDGET_DATE_FROM / BUDGET_DATE_TO — the budget start and end dates.
• VERSION_FROM_DATE / VERSION_TO_DATE — the effective dates of the budget version.
• BUDGET_UNIT1_ID, BUDGET_UNIT2_ID, BUDGET_UNIT3_ID and their corresponding BUDGET_UNIT1_NAME, BUDGET_UNIT2_NAME, BUDGET_UNIT3_NAME — the three configurable budget unit identifiers and their decoded names, produced via HR_GENERAL.DECODE_SHARED_TYPE. The column budget_unit1_name is exactly what the view exposes for the first budget unit and is the value typically surfaced in reports and LOVs.
• BUDGETED_ENTITY_CD and BUDGETED_ENTITY_NAME — the entity type code ('ORGANIZATION', 'POSITION', and similar values) decoded through the PQH_BUDGET_ENTITY lookup.
• ENTITY_ID and ENTITY_NAME — the resolved organization or position identifier and its display name.

Common Use Cases and Queries

Typical scenarios include listing the organizations or positions covered by a budget version, extracting budget unit hierarchies for reconciliation, and driving budget versus actual comparisons in PSHR reporting. A simple query retrieving budget unit names alongside entity names is:

SELECT budget_id, budget_version_id,
       budget_unit1_name, budget_unit2_name, budget_unit3_name,
       budgeted_entity_name, entity_id, entity_name
FROM   apps.pqh_cmmtmnt_entities_v
WHERE  business_group_id = :p_business_group_id
AND    budget_id = :p_budget_id;

Because the view performs decoding through HR_GENERAL, queries returning large row sets can incur overhead; filtering by BUSINESS_GROUP_ID, BUDGET_ID, or BUDGET_VERSION_ID is recommended. The view is read-only in practice and should not be used as an update target.