Results for “process_run_type”

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

Overview

HR_SUMMARY_RUN_VALUES_V is a reporting view owned by the APPS schema within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is defined as a join across three objects: HR_SUMMARY_PROCESS_RUN, HR_SUMMARY_ITEM_USAGE (implemented via HR_SUMMARY_ITEM_TYPE_USAGE), and HR_SUMMARY_ITEM_VALUE. The view presents a denormalized, flat record of summary process runs together with the item-level numeric values captured against each run, allowing consumers to resolve a process run and its associated values in a single query rather than joining three separate objects.

The view is predominantly used in HRMS reporting and integration contexts where summary results — such as totals, counts, or computed metrics generated by a summary process — must be extracted per run and per item type. Because it exposes PROCESS_RUN_ID directly, it also serves as the principal entry point for queries filtered by process_run_id, the term commonly used by developers who search for this object.

Underlying Base Objects

The view text identifies three referenced objects and one package dependency:

• HR_SUMMARY_PROCESS_RUN (PR) — supplies the process run header, including NAME, PROCESS_TYPE, PROCESS_RUN_ID, TEMPLATE_ID, and BUSINESS_GROUP_ID.
• HR_SUMMARY_ITEM_TYPE_USAGE (ITU) — supplies the item-level usage definition referenced by the run's template, contributing SEQUENCE_NUMBER and ITEM_TYPE_USAGE_ID.
• HR_SUMMARY_ITEM_VALUE (IV) — supplies the actual recorded values: NUMVALUE1, NUMVALUE2, and ITEM_VALUE_ID.
• HR_GENERAL (PACKAGE) — invoked through HR_GENERAL.GET_BUSINESS_GROUP_ID to restrict results to the caller's current business group via an NVL predicate.

The joins are: PR.PROCESS_RUN_ID = IV.PROCESS_RUN_ID, PR.TEMPLATE_ID = ITU.TEMPLATE_ID, and ITU.ITEM_TYPE_USAGE_ID = IV.ITEM_TYPE_USAGE_ID. The business group predicate applies the multi-tenant security context automatically.

Key Columns

• PROCESS_RUN_NAME — the descriptive NAME of the summary process run.
• PROCESS_RUN_TYPE — the PROCESS_TYPE classification of the run.
• PROCESS_RUN_ID — the unique identifier for the run; the primary filtering key for extraction queries.
• SEQUENCE_NUMBER — ordering attribute from the item type usage, controlling display or processing order of items.
• ITEM_VALUE1 / ITEM_VALUE2 — numeric value slots (NUMVALUE1, NUMVALUE2) holding the summarized results.
• ITEM_VALUE_ID — the surrogate key of the underlying item value row.

Common Use Cases and Queries

Typical scenarios include auditing the values produced by a specific summary run, comparing values across runs of the same process type, and feeding summarized HR metrics into downstream extracts. Because the view filters on business group implicitly, it is safe to consume from concurrent programs and reports without additional security predicates.

Retrieve all values for a known run:

• SELECT process_run_name, process_run_type, sequence_number, item_value1, item_value2 FROM hr_summary_run_values_v WHERE process_run_id = :process_run_id ORDER BY sequence_number;

List recent runs of a given type with their values:

• SELECT process_run_id, process_run_name, sequence_number, item_value1 FROM hr_summary_run_values_v WHERE process_run_type = :type ORDER BY process_run_id, sequence_number;

Aggregate totals per run:

• SELECT process_run_id, SUM(item_value1) total1, SUM(item_value2) total2 FROM hr_summary_run_values_v GROUP BY process_run_id;