Results for “hr_summary_item_value”

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

Overview

HR_SUMMARY_ITEM_VALUE is an Oracle E-Business Suite view owned by the APPS schema and defined within the PER (Human Resources) product family. It exposes a filtered subset of the HR_SUMMARY table, returning only those rows where the TYPE column equals the value ITEM_VALUE. In the Oracle EBS data model, HR_SUMMARY serves as a generic repository for summary-level data associated with HR objects, and the ITEM_VALUE discriminator identifies records that carry the actual measured or captured value for a summary item. The data item represented by a given row may be stored as a numeric, date, or text value, which is why the underlying table provides distinct typed columns rather than a single generic value column.

Because the view presents a stable, named projection of HR_SUMMARY, it is commonly consumed by reports, concurrent programs, and integration interfaces that need to retrieve summary item values without decoding the polymorphic structure of the base table. The view status is VALID, confirming it is compiled and available in the EBS 12.1.1 and 12.2.2 environments documented in the ETRM repository.

Underlying Base Objects

The view is defined exclusively over the HR_SUMMARY base object, which is referenced through a SYNONYM in the documented metadata. The defining SQL applies a single predicate—WHERE TYPE = 'ITEM_VALUE'—against HR_SUMMARY, then projects the relevant columns. No joins, unions, or aggregation are performed; the view is therefore a straight, filtered projection of the base table.

This design means that every row in HR_SUMMARY_ITEM_VALUE corresponds one-to-one with exactly one row in HR_SUMMARY whose TYPE is ITEM_VALUE. All inserts, updates, and deletes affecting the view ultimately operate on HR_SUMMARY, so any DML against the view must satisfy the constraints and mandatory columns of the base table. Because the view is not a key-preserved join construct, it remains updatable for the columns it exposes, subject to standard EBS security and validation rules enforced elsewhere in the HR schema.

Key Columns

The view exposes the following significant columns:

• ROW_ID / ROWID — The physical row identifier of the underlying HR_SUMMARY row, exposed as ROWID in the view text and aliased as ROW_ID in the documented column list.
• ITEM_VALUE_ID (ID_VALUE) — The primary identifier for the item value record.
• BUSINESS_GROUP_ID — The business group that owns the record, used for multi-tenant and security filtering.
• OBJECT_VERSION_NUMBER — The optimistic locking version token maintained by the HR framework.
• PROCESS_RUN_ID — Identifier of the summary process run that produced or last touched the record.
• ITEM_TYPE_USAGE_ID — Links the value to its item type definition, indicating which summary item is being measured.
• TEXT_VALUE1 (TEXTVALUE) — Character representation of the item value, used when the item is textual.
• NUM_VALUE1 / NUM_VALUE2 (NUMVALUE1, NUMVALUE2) — Numeric representations, supporting numeric items and secondary numeric measures.
• DATE_VALUE1 (DATEVALUE) — Date representation for date-typed items.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard EBS audit and who-columns for row traceability.

Common Use Cases and Queries

Typical use cases include HR summary reporting, extract programs, and interfaces that need to publish summary item values to downstream systems or analytics platforms. A basic retrieval of all values for a business group follows:

• SELECT item_value_id, item_type_usage_id, text_value1, num_value1, num_value2, date_value1 FROM apps.hr_summary_item_value WHERE business_group_id = :p_bg_id;

To obtain a numeric measure for a specific process run:

• SELECT item_type_usage_id, num_value1 FROM apps.hr_summary_item_value WHERE process_run_id = :p_run_id AND num_value1 IS NOT NULL;

To retrieve date-typed values updated within a period:

• SELECT item_value_id, date_value1 FROM apps.hr_summary_item_value WHERE date_value1 BETWEEN :p_start AND :p_end;

Because the view filters on TYPE = 'ITEM_VALUE', queries should always qualify by BUSINESS_GROUP_ID, ITEM_TYPE_USAGE_ID, or PROCESS_RUN_ID to leverage the underlying indexes on HR_SUMMARY and avoid full scans. Fiscal and audit extractions should join to the relevant item type usage and business group definitions to translate identifiers into descriptive labels.