Results for “item_value_id”

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

Overview

The HR_SUMMARY_KEY_VALUES_ESTAB_V view is a reporting and integration construct within the Oracle E-Business Suite Human Resources (PER) product family. It belongs to the APPS schema and is documented as VALID across EBS 12.1.1 and 12.2.2. The view resolves human resources summary key values that are specifically associated with the Establishment key type, pairing each establishment organization with the identifier of the item value that carries that establishment's summary data.

In Oracle HRMS, the summary key value framework stores flexible, keyed attributes for an organization or business group. The HR_SUMMARY_KEY_TYPE view defines the available key categories (for example, ESTABLISHMENT), while HR_SUMMARY_KEY_VALUE stores the individual values keyed against those categories. The HR_SUMMARY_KEY_VALUES_ESTAB_V view isolates the ESTABLISHMENT category and joins it to organization units, presenting a flattened result of organization name plus the corresponding item value identifier. This makes the underlying key/value structure directly consumable by fast formulas, reports, and external integrations without requiring the caller to reconstruct the join logic themselves.

Underlying Base Objects

The view is defined over three primary sources plus supporting packages, as documented in the ETRM metadata:

• HR_SUMMARY_KEY_VALUE (VIEW) — the alias KV, supplying the item value identifier and the key type linkage.
• HR_SUMMARY_KEY_TYPE (VIEW) — the alias KT, supplying the key type name used to filter to 'ESTABLISHMENT'.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — the alias ORG, supplying the organization name and organization identifier used to match the summary key value's NAME.
• HR_GENERAL (PACKAGE) — invoked through HR_GENERAL.GET_BUSINESS_GROUP_ID to enforce business group isolation.
• HR_API (PACKAGE) — referenced as part of the supporting HRMS infrastructure.

The join is driven by equality between KV.KEY_TYPE_ID and KT.KEY_TYPE_ID, a filter on KT.NAME = 'ESTABLISHMENT', and a textual match between KV.NAME and the character representation of ORG.ORGANIZATION_ID. The business group predicate KV.BUSINESS_GROUP_ID = NVL(HR_GENERAL.GET_BUSINESS_GROUP_ID, KV.BUSINESS_GROUP_ID) restricts results to the caller's session business group when one is set, otherwise returning values across business groups.

Key Columns

• KEY_VALUE_ESTABLISHMENT — the name of the establishment organization unit, returned from HR_ALL_ORGANIZATION_UNITS.NAME. This is the human-readable label for the establishment.
• ITEM_VALUE_ID — the identifier of the summary key value record associated with that establishment, sourced from HR_SUMMARY_KEY_VALUE.ITEM_VALUE_ID. This identifier can be used to retrieve or join to the actual value payload in the HR summary structures.

Note that only two columns are exposed. The view deliberately projects a minimal result set, omitting internal identifiers such as KEY_TYPE_ID and BUSINESS_GROUP_ID, which remain available in the underlying base views if needed.

Common Use Cases and Queries

This view is typically used when application logic or custom reporting must determine which establishments exist and obtain the item value reference for each, without traversing the summary key framework manually. Representative uses include HRMS reporting on establishment-level summary data, validation logic inside fast formulas, and integration extracts that feed downstream payroll or statutory reporting.

A basic query lists all establishments visible to the current business group session:

• SELECT key_value_establishment, item_value_id FROM apps.hr_summary_key_values_estab_v;

A more targeted query filters to a single establishment by name and returns its item value identifier:

• SELECT item_value_id FROM apps.hr_summary_key_values_estab_v WHERE key_value_establishment = :p_establishment_name;

Because the view resolves business group context through HR_GENERAL.GET_BUSINESS_GROUP_ID, callers operating in a secured session receive only the establishments relevant to that business group. When invoked without a business group context, the predicate degrades to a self-comparison and returns values across all business groups, which should be accounted for in any reporting logic that assumes business group isolation.