Results for “run_parameter_value”

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

Overview

APPS.HR_SUMMARY_RUN_PARAMETER_VALUE is a reporting and integration view within the Oracle E-Business Suite human resources schema. It exposes a filtered subset of records from the HR_SUMMARY table, specifically those rows whose TYPE discriminator equals the literal value 'RUN_PARAMETER_VALUE'. In Oracle EBS 12.1.1 and 12.2.2, the HR_SUMMARY table functions as a generic, polymorphic store used to persist heterogeneous summary and parameter data across many feature areas. Rather than creating a dedicated physical table for each category of data, Oracle stores multiple logical entity types in HR_SUMMARY and separates them by the TYPE column. This view provides a stable, semantically meaningful interface over one such category.

The view therefore plays a role analogous to a "virtual table" for run parameter values. It abstracts the physical storage details of the underlying wide table, and by restricting rows to a single TYPE value it lets callers query, join, and report on run parameter values without repeatedly coding the TYPE predicate. It is owned by the APPS schema and is typically accessed through synonyms and grants that allow custom reports, concurrent programs, and integrations to read the data. Because HR_SUMMARY is the only documented base object, the view is lightweight and carries no additional computation beyond the row filter and column projection.

Underlying Base Objects

The view is defined over a single documented base object: HR_SUMMARY, referenced as a synonym. The defining query is a simple SELECT with a WHERE clause:

• HR_SUMMARY — the base table (or synonym) that physically stores the records. All columns projected by the view originate directly from this object.
• Filter predicate — WHERE TYPE = 'RUN_PARAMETER_VALUE' limits the result set to a single logical category of summary records.

No joins, unions, or aggregations are present. Consequently, the view is one-to-one with the qualifying rows of HR_SUMMARY: every row in the view corresponds to exactly one row in the base table where TYPE = 'RUN_PARAMETER_VALUE', and the ROWID exposed by the view is the ROWID of that underlying row.

Key Columns

The view exposes the following columns, taken verbatim from the base table:

• ROWID — pseudo-column identifying the physical row in HR_SUMMARY; useful for direct row access and updates.
• ID_VALUE — the primary identifier for the logical record within its category.
• BUSINESS_GROUP_ID — the operating unit / business group that owns the record, central to multi-organization data security.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column used by the underlying business logic.
• FK_VALUE1, FK_VALUE2 — foreign-key reference columns allowing the summary record to point at related entities.
• TEXT_VALUE1 — character payload for the parameter value.
• NUM_VALUE1 — numeric payload for the parameter value.
• DATE_VALUE1 — date payload for the parameter value.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording when and by whom the row was last modified.
• CREATED_BY, CREATION_DATE — standard WHO creation audit columns.

The three typed value columns (TEXT_VALUE1, NUM_VALUE1, DATE_VALUE1) reflect the generic design: the appropriate column is populated according to the data type of the parameter being stored. The TYPE column itself is not projected, since it is constant for all rows returned by the view.

Common Use Cases and Queries

Typical uses include verifying the parameter values captured for a payroll or summary run, auditing changes to parameter payloads, and joining parameter values back to their owning run or business group. Because the view already filters on TYPE, queries remain simple and readable.

Retrieve all parameter value records for a business group:

SELECT id_value, business_group_id, text_value1, num_value1, date_value1
FROM   apps.hr_summary_run_parameter_value
WHERE  business_group_id = :p_business_group_id;

Locate a specific parameter value by its surrogate identifier:

SELECT id_value, fk_value1, fk_value2, text_value1, num_value1, date_value1
FROM   apps.hr_summary_run_parameter_value
WHERE  id_value = :p_id_value;

Audit recently modified parameter values:

SELECT id_value, last_updated_by, last_update_date, text_value1
FROM   apps.hr_summary_run_parameter_value
WHERE  last_update_date >= SYSDATE - 7
ORDER BY last_update_date DESC;

Join parameter values to their owning run context using the FK columns:

SELECT p.id_value, p.fk_value1, p.num_value1
FROM   apps.hr_summary_run_parameter_value p
WHERE  p.fk_value1 = :p_run_id;

These scenarios illustrate the view's role as a convenient, category-specific window into the generic HR_SUMMARY store, supporting both operational lookups and downstream reporting without requiring callers to manage the TYPE discriminator themselves.