Results for “hr_summary_key_value”

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

Overview

HR_SUMMARY_KEY_VALUE is an APPS-owned view within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a filtered subset of the HR_SUMMARY table, specifically those rows whose TYPE column equals the literal value 'KEY_VALUE'. The view is registered as VALID in the ETRM repository, confirming that its definition resolves cleanly against the underlying synonym and that it is available for use in reporting and integration scenarios.

The view is designed to store and present the values of "key types" that identify individual summary data items used in Oracle HRMS. A typical example is a headcount summary line that must be uniquely identified by a combination of attributes such as an Employee Category of 'Cadre' paired with a Gender of 'Male'. Rather than persisting those identifying attributes as free-text, HR_SUMMARY_KEY_VALUE materializes them as key/value pairs, allowing downstream summary calculations to be partitioned and reported accurately. Because the view surfaces the identifying keys separately from the summarized measures, it is a useful access point for anyone building extracts, audits, or reconciliations around HR summary data structures.

Underlying Base Objects

The documented base object for this view is the HR_SUMMARY synonym, which resolves to the corresponding table owned by the APPS schema. HR_SUMMARY is a generic summary storage table that serves multiple summary categories, distinguished by the TYPE column. HR_SUMMARY_KEY_VALUE does not introduce its own physical storage; it is a restricting projection over HR_SUMMARY, adding a WHERE TYPE = 'KEY_VALUE' predicate so that callers see only key-definition rows.

Because the view is defined over a synonym, the object compiles against the standard APPS synonym namespace, which is the expected pattern for seeded HRMS database objects in both 12.1.1 and 12.2.2. Changes to the HR_SUMMARY table structure propagate to the view at recompile time, and customers should avoid altering the base table directly.

Key Columns

The view text selects a defined set of columns from HR_SUMMARY. Important ones include:

• ROWID — the physical row identifier of the underlying HR_SUMMARY row; exposed as ROW_ID in the documented column list.
• ID_VALUE — the primary identifier value for the key/value record (KEY_VALUE_ID).
• BUSINESS_GROUP_ID — the HR business group that owns the summary data item, essential for multi-organization partitioning.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column.
• FK_VALUE1, FK_VALUE2 — foreign key references to the dimension values (for example, employee category, gender) that make up the key.
• TEXT_VALUE1 — a textual representation of the key value where applicable.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns.

The documented logical column list additionally exposes KEY_VALUE_ID, KEY_TYPE_ID, ITEM_VALUE_ID, and NAME, which describe the type of key and the specific item value being referenced.

Common Use Cases and Queries

Typical uses include verifying how a headcount or assignment summary has been keyed, extracting dimension breakdowns for HR analytics, and reconciling summary results back to their identifying attributes.

SELECT key_value_id,
       business_group_id,
       fk_value1,
       fk_value2,
       text_value1,
       name
FROM   apps.hr_summary_key_value
WHERE  business_group_id = :p_business_group_id;

To join key definitions to their summary rows, query the base table in parallel with the key type identifier:

SELECT k.key_value_id,
       s.type,
       k.text_value1
FROM   apps.hr_summary_key_value k,
       apps.hr_summary           s
WHERE  k.business_group_id = s.business_group_id
AND    k.key_value_id      = s.id_value;

Because the view enforces the 'KEY_VALUE' type filter, developers do not need to add that predicate manually, reducing the risk of accidentally including measure rows. Access should be restricted to the APPS schema or a privileged reporting user, consistent with Oracle's proprietary and confidential classification for this object.