Results for “hr_summary_run_parameter_value”

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

Overview

HR_SUMMARY_RUN_PARAMETER_VALUE is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the PER (Human Resources) product family. It presents a filtered, denormalized projection of records held in the HR_SUMMARY table, restricted to rows whose TYPE column equals the literal value 'RUN_PARAMETER_VALUE'. In the Oracle HRMS data model, HR_SUMMARY is a generic summary/persisted-attribute store used to hold miscellaneous structured records that do not warrant their own dedicated table, and the TYPE discriminator segregates those records into logical groups. This view exposes only the subset that represents parameter values captured for a summary run, allowing concurrent programs, extracts, and integrations to read run parameter data without being exposed to the full breadth of HR_SUMMARY content.

The object is marked VALID in ETRM and is available in both EBS 12.1.1 and 12.2.2. It is a read-only construct: no DML is defined against the view, and all maintenance occurs against the underlying HR_SUMMARY rows.

Underlying Base Objects

The view is defined over a single referenced base object, HR_SUMMARY, which is accessed through a SYNONYM in the APPS schema. HR_SUMMARY is the physical repository of the summary records; the view applies a constant predicate on the TYPE column so that only 'RUN_PARAMETER_VALUE' rows are visible. Because the view text selects ROWID alongside the business columns, each row retains a stable addressable identifier tied to its HR_SUMMARY parent record. The relationship is therefore one of simple projection and filtering: every row in HR_SUMMARY_RUN_PARAMETER_VALUE corresponds to exactly one row in HR_SUMMARY, and no joins or aggregations are introduced by the view definition.

Key Columns

• ROW_ID — the ROWID of the underlying HR_SUMMARY row, exposed through the SELECT ROWID clause.
• RUN_PARAMETER_VALUE_ID / ID_VALUE — the primary identifier for the run parameter value record (ID_VALUE in the view text).
• BUSINESS_GROUP_ID — the HR business group (enterprise) that owns the record, the principal multi-tenancy discriminator in HRMS.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency token used by the HRMS framework.
• PARAMETER_ID / FK_VALUE1 — foreign key reference to the parameter definition; FK_VALUE2 carries a secondary foreign key.
• ITEM_TYPE_USAGE_ID — links the record to its item type usage context.
• TEXTVALUE / TEXT_VALUE1 — text-typed parameter value.
• NUMVALUE / NUM_VALUE1 — numeric-typed parameter value.
• DATEVALUE / DATE_VALUE1 — date-typed parameter value; this is the column relevant to searches for "date_value1".
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried to retrieve the parameters supplied to a summary run, to audit when a value was captured, or to feed downstream extracts. A date-driven lookup, which is the pattern implied by a search on date_value1, is shown below.

• Retrieve date-valued parameters within a business group for a given window:

SELECT RUN_PARAMETER_VALUE_ID,
       BUSINESS_GROUP_ID,
       PARAMETER_ID,
       DATE_VALUE1,
       TEXT_VALUE1,
       NUM_VALUE1
FROM   APPS.HR_SUMMARY_RUN_PARAMETER_VALUE
WHERE  BUSINESS_GROUP_ID = :p_business_group_id
AND    DATE_VALUE1 BETWEEN :p_from_date AND :p_to_date
ORDER BY DATE_VALUE1;

• Inspect all parameter values recorded by a specific user, using the audit columns:

SELECT RUN_PARAMETER_VALUE_ID, PARAMETER_ID,
       TEXT_VALUE1, NUM_VALUE1, DATE_VALUE1,
       LAST_UPDATE_DATE, LAST_UPDATED_BY
FROM   APPS.HR_SUMMARY_RUN_PARAMETER_VALUE
WHERE  LAST_UPDATED_BY = :p_user_id
AND    TRUNC(LAST_UPDATE_DATE) = TRUNC(SYSDATE);

Because the view maps generic columns (FK_VALUE1, TEXT_VALUE1, NUM_VALUE1, DATE_VALUE1) to logical attributes, consumers should resolve PARAMETER_ID against the parameter definition to determine which physical column holds the meaningful value. Reads should always filter on BUSINESS_GROUP_ID to respect HRMS partitioning and security, and should not be used for direct DML.