Search Results process_run

Overview

APPS.HR_SUMMARY_PROCESS_RUN is a filtered database view defined in the Oracle E-Business Suite APPS schema. It exposes a single logical subset of the HR_SUMMARY table, restricted to rows where the discriminator column TYPE equals the literal value 'PROCESS_RUN'. In Oracle EBS 12.1.1 and 12.2.2, HR_SUMMARY functions as a generic, extensible repository that stores heterogeneous summary records for many different Oracle HRMS features, each distinguished by the TYPE column. The view therefore acts as a stable, purpose-specific read interface for process-run summary data, shielding consumers from the underlying polymorphic storage model.

The object is a view rather than a table, and it carries no independent storage, indexes, or triggers. It is owned by APPS and is not itself a base object; the documentation lists HR_SUMMARY as a synonym reference in the calling environment. This design supports both reporting and integration: Oracle EBS reports, concurrent programs, and external interfaces can query HR_SUMMARY_PROCESS_RUN without reimplementing the TYPE filter, improving readability and reducing the risk of inconsistent predicates. Matching column names across the view and base table allow straightforward use in joins to other HRMS entities such as business groups and process identifiers.

Underlying Base Objects

The view is defined over a single documented base object, HR_SUMMARY, referenced through a synonym in APPS. The defining SQL selects ROWID along with the columns ID_VALUE, BUSINESS_GROUP_ID, OBJECT_VERSION_NUMBER, TEXT_VALUE2, FK_VALUE1, TEXT_VALUE1, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, applying the predicate TYPE = 'PROCESS_RUN'. Because all columns are drawn from one table, the view is inherently updatable where Oracle permits, though it is normally consumed read-only. The OBJECT_VERSION_NUMBER column supports optimistic locking semantics inherited from the base table.

Key Columns

• ROWID — Physical row identifier from HR_SUMMARY; useful for diagnostics and duplicate detection.
• ID_VALUE — Primary surrogate identifier for the summary record; typically the process run reference.
• BUSINESS_GROUP_ID — Business group partitioning key, enabling multi-tenant style filtering within a single installation.
• OBJECT_VERSION_NUMBER — Version counter used for optimistic locking and change detection.
• TEXT_VALUE1, TEXT_VALUE2 — Generic character attributes holding the payload specific to process-run summaries.
• FK_VALUE1 — Foreign key value linking the row to another entity, commonly a run identifier or parent record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who last changed the row and when.
• CREATED_BY, CREATION_DATE — Creation audit attributes for traceability.

Common Use Cases and Queries

Typical scenarios include retrieving the summary state of HRMS process runs, reconciling run results across business groups, and populating custom reports or interfaces that require process-run metadata. Because the view is pre-filtered, joins and predicates remain concise. A basic query returning run summaries for a business group is:

• SELECT id_value, business_group_id, text_value1, text_value2, fk_value1, creation_date FROM apps.hr_summary_process_run WHERE business_group_id = :p_business_group_id;
• SELECT id_value, object_version_number, last_update_date, last_updated_by FROM apps.hr_summary_process_run WHERE fk_value1 = :p_run_id ORDER BY last_update_date;
• SELECT COUNT(*) FROM apps.hr_summary_process_run WHERE creation_date >= TRUNC(SYSDATE) - 1;

In each case the TYPE = 'PROCESS_RUN' predicate is implicit, so callers avoid hardcoding the discriminator. For performance, note that the underlying table must be filtered efficiently; joins to HR_ALL_ORGANIZATION_UNITS or run-log tables should be keyed on BUSINESS_GROUP_ID and ID_VALUE or FK_VALUE1. Where the base table's indexes cover the discriminator and identifier columns, the view is suitable for operational reporting and integration lookups in both EBS 12.1.1 and 12.2.2.