Results for “pqh_pc_org_summary_v”

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

Overview

PQH_PC_ORG_SUMMARY_V is an APPS-owned database view within the Public Sector HR (PQH) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to provide a Position Control organization summary for reporting. The view consolidates position control hierarchy information with budget version and budget detail data so that report developers and integrators can retrieve, in a single flattened result set, the budget measurement types and amounts associated with positions organized by organization and hierarchy level.

Because it is a view rather than a base table, it exposes no independent storage; it is a read-only projection whose contents are derived at query time from the underlying budget and position control structures. It is intended primarily as a reporting and integration surface rather than a transactional object, and consumers should treat all columns as derived values reflecting the currently effective budget version.

Underlying Base Objects

The ETRM metadata for this view lists the following referenced objects: FND_PROFILE (PACKAGE), HR_GENERAL (PACKAGE), PQH_BUDGETS_V (VIEW), PQH_BUDGET_DETAILS (SYNONYM), PQH_BUDGET_VERSIONS (SYNONYM), PQH_POSN_CTL_HIERARCHY_V (VIEW), PQH_PSF_BUS (PACKAGE), and PQH_UTILITY (PACKAGE).

The documented view text confirms the core join structure. PQH_POSN_CTL_HIERARCHY_V supplies the organization and hierarchy context (row number, hierarchy level, business group, organization name and identifier, and the position control enabled flag). PQH_BUDGETS_V supplies budget definition attributes, including BUDGET_UNIT1, BUDGET_UNIT2, and their identifiers, together with BUDGET_ID and BUDGETED_ENTITY_CD. PQH_BUDGET_VERSIONS provides the versioning envelope (BUDGET_ID, BUDGET_VERSION_ID, DATE_FROM, DATE_TO). PQH_BUDGET_DETAILS provides the position-level budget lines (POSITION_ID, ORGANIZATION_ID, and the BUDGET_UNIT1_VALUE / BUDGET_UNIT2_VALUE columns).

The join predicates require that the budget version be effective as of HR_GENERAL.EFFECTIVE_DATE, that organization identifiers match between the hierarchy and the budget details, that the relevant budget unit value and POSITION_ID be non-null, and that BUDGETED_ENTITY_CD equal 'POSITION'. The view is constructed as a UNION: the first branch projects BUDGET_UNIT1 as the measurement type, and a second branch projects BUDGET_UNIT2. This union structure is why the column is named generically as BUDGET_MEASUREMENT_TYPE rather than referencing a specific budget unit.

Key Columns

• ROW_NUM — Ordering/hierarchy sequence derived from PQH_POSN_CTL_HIERARCHY_V.
• HIERARCHY_LEVEL — Depth of the organization within the position control hierarchy.
• BUSINESS_GROUP_NAME / BUSINESS_GROUP_ID — Business group context for the organization.
• ORGANIZATION_NAME / ORGANIZATION_ID — The organization to which the position and budget lines belong.
• PC_ENABLED_FLAG — Indicates whether position control is enabled for the organization.
• POSITION_NAME / POSITION_ID — Position identity, with the name resolved through HR_GENERAL.DECODE_POSITION_LATEST_NAME.
• BUDGET_MEASUREMENT_TYPE — The budget unit (BUDGET_UNIT1 in the first union branch, BUDGET_UNIT2 in the second) that the row's amount is expressed in.
• BUDGET_UNIT_ID — Identifier of the corresponding budget unit, mapped from BUDGET_UNIT1_ID or BUDGET_UNIT2_ID.

Common Use Cases and Queries

The view is typically used to produce organization-level position control budget reports, to feed downstream integration or analytics extracts, and to reconcile budgeted amounts against position control hierarchies. A representative query filtering on the measurement type column is:

• SELECT organization_name, position_name, budget_measurement_type, budget_unit_id FROM apps.pqh_pc_org_summary_v WHERE pc_enabled_flag = 'Y' ORDER BY row_num;
• SELECT hierarchy_level, organization_id, COUNT(*) position_count FROM apps.pqh_pc_org_summary_v WHERE business_group_id = :p_business_group_id GROUP BY hierarchy_level, organization_id;
• SELECT * FROM apps.pqh_pc_org_summary_v WHERE budget_measurement_type = :p_budget_unit AND organization_id = :p_org_id;

Because the measurement type is derived from a union of two budget units, queries that constrain budget_measurement_type implicitly select only those rows where the corresponding budget unit value is populated and the position is defined. Reports requiring both units for a single position will return multiple rows, one per populated unit.