Results for “hr_summary_run”

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

Overview

HR_SUMMARY_RUN is a filtering view owned by the APPS schema in Oracle E-Business Suite, defined over the HR_SUMMARY base table. It exposes only those rows for which the discriminator column TYPE equals the literal value 'RUN'. In Oracle EBS 12.1.1 and 12.2.2, HR_SUMMARY is a generic multi-purpose storage table within the PER (Human Resources) product that holds heterogeneous summary records distinguished by TYPE. The HR_SUMMARY_RUN view presents the subset used for run-oriented summary data, making it the appropriate access point for reports, concurrent programs, and integrations that must isolate run records from other HR_SUMMARY content.

The view carries no business logic beyond its WHERE predicate. It performs no joins, aggregations, or transformations, so its behaviour is identical in 12.1.1 and 12.2.2. All filtering and interpretation of the underlying records remain the responsibility of the consuming report or interface. Because the view is a simple projection of HR_SUMMARY, it inherits the same tablespace, security, and index characteristics as the base table, and it remains VALID in both releases.

Underlying Base Objects

The view is defined solely over HR_SUMMARY, referenced through the public synonym HR_SUMMARY in the APPS schema. No additional tables, views, or PL/SQL functions participate in its definition. The relationship is strictly one-to-many in the sense that each HR_SUMMARY row of TYPE 'RUN' surfaces through the view, while rows of every other TYPE are excluded. Because the base object is a synonym, the view is schema-independent in the standard APPS configuration and can be referenced directly by custom code running against the APPS account.

Key Columns

• ROW_ID — the pseudo-column ROWID, providing a physical locator for the underlying HR_SUMMARY row.
• RUN_ID — exposed in the view column list; maps from the ID_VALUE column in the SELECT list and identifies the run record.
• BUSINESS_GROUP_ID — the HR business group that owns the summary record.
• OBJECT_VERSION_NUMBER — the optimistic locking version counter maintained by the underlying table.
• TEXT_VALUE1 — a generic character payload column whose meaning is determined by the run context.
• NUM_VALUE1 / NUM_VALUE2 — generic numeric payload columns; NUM_VALUE1 is a common search target and typically stores the primary numeric metric associated with the run summary.
• YEAR — the reporting or processing year to which the run summary relates.
• COMPANY_ID — the legal or reporting company associated with the record.
• ESTABLISHMENT_ID — the establishment placing the record within the HR organization structure.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard WHO audit tracking.

Common Use Cases and Queries

The view is typically consumed where run summary data must be reported or extracted without processing non-run HR_SUMMARY rows. Typical scenarios include reconciliation of run statistics by business group and year, extraction of run metrics such as NUM_VALUE1 into downstream reporting, and audit queries over the WHO columns. A representative query is:

SELECT run_id, business_group_id, year, num_value1, num_value2
FROM apps.hr_summary_run
WHERE business_group_id = :p_business_group_id
AND year = :p_year;

Because the view is unfiltered beyond TYPE = 'RUN', queries should always constrain business group, year, or run identifiers to avoid full-table scans. Join the view to HR_ALL_ORGANIZATION_UNITS or HR_OPERATING_UNITS using BUSINESS_GROUP_ID or COMPANY_ID to enrich output with descriptive names, and join to PER_ALL_PEOPLE_F via CREATED_BY or LAST_UPDATED_BY for user attribution. When the exact semantic of TEXT_VALUE1, NUM_VALUE1, or NUM_VALUE2 is required, inspect the code path that inserts the corresponding HR_SUMMARY rows, since the column meanings are contextual rather than fixed.