Results for “hr_summary_key_type”

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

Overview

HR_SUMMARY_KEY_TYPE is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. Its purpose is to expose the set of "key types" available to the Global Summary Process (GSP). When the GSP executes, it dynamically constructs and runs a SQL statement that may contain one or more group by clauses; each of these grouping specifications is referred to as a "key". HR_SUMMARY_KEY_TYPE enumerates the key types that the GSP can use for this grouping and summarization behaviour.

Because it is a view rather than a base table, HR_SUMMARY_KEY_TYPE does not store data in its own right. It is a filtered presentation of recorded key definitions, presented alongside descriptive lookup information so that consumers can obtain both the internal key type identifier and a user-meaningful label. Within EBS reporting and integration, the view serves as a lightweight, denormalized access point for the key types configured for summarization, allowing report writers and extensions to reference valid GSP key types without querying the underlying transactional summary table directly.

Underlying Base Objects

The documented metadata for ETRM 12.2.2 lists the referenced base objects as HR_API (PACKAGE), HR_LOOKUPS (VIEW) and HR_SUMMARY (SYNONYM). The view text confirms this relationship: it joins HR_SUMMARY (accessed through its synonym) to HR_LOOKUPS, selecting summary rows whose TYPE is KEY_TYPE and matching their TEXT_VALUE1 against lookup codes in HR_LOOKUPS. HR_API is referenced as part of the PER API infrastructure that governs access to Human Resources data.

The join is constrained by two predicates on the lookup side: L.APPLICATION_ID = 800 and L.LOOKUP_TYPE = 'GSP_KEY_TYPE'. This limits the exposed rows exclusively to those summary records that correspond to valid GSP key type lookups. Note that the documented column list includes ROW_ID, KEY_TYPE_ID, BUSINESS_GROUP_ID, OBJECT_VERSION_NUMBER, NAME, TITLE, KEY_FUNCTION, SEEDED_DATA and standard WHO audit columns, whereas the supplied view text selects S.ROWID and related descriptive attributes such as ID_VALUE, TEXT_VALUE1, TEXT_VALUE6, TEXT_VALUE7 and MEANING. The difference reflects the underlying HR_SUMMARY structure and the lookup-based derivation of the view's logical columns.

Key Columns

• ROW_ID / ROWID — The physical row identifier of the underlying HR_SUMMARY record from which the key type is derived.
• KEY_TYPE_ID (ID_VALUE) — The identifier of the key type, carrying the internal value of the record.
• BUSINESS_GROUP_ID — The business group to which the key type definition belongs, providing multi-tenant partitioning within HR.
• NAME / TITLE (TEXT_VALUE1, TEXT_VALUE6, TEXT_VALUE7) — Descriptive attributes of the key type, with TEXT_VALUE1 acting as the lookup code matched to HR_LOOKUPS.
• MEANING — The user-facing meaning resolved from HR_LOOKUPS for the corresponding GSP key type lookup code.
• KEY_FUNCTION / SEEDED_DATA / OBJECT_VERSION_NUMBER — Definitional and concurrency-control attributes associated with the key type.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY and CREATION_DATE, tracking creation and modification of the source record.

Common Use Cases and Queries

Typical usage involves identifying the valid key types for the GSP, validating configuration before running summarization, and joining the view to lookup or summary data within reports. A representative query retrieving all configured key types with their descriptive meanings is:

• SELECT key_type_id, name, meaning, business_group_id FROM apps.hr_summary_key_type ORDER BY name;
• SELECT h.key_type_id, h.meaning FROM apps.hr_summary_key_type h WHERE h.business_group_id = :p_bg_id;
• SELECT h.name, l.meaning FROM apps.hr_summary_key_type h, apps.hr_lookups l WHERE h.meaning = l.meaning AND l.lookup_type = 'GSP_KEY_TYPE' AND l.application_id = 800;

These patterns support configuration validation, reporting against summarization groupings, and integration logic that must resolve a key type code to its attached meaning before invoking the Global Summary Process.