Search Results key_function

Overview

HR_SUMMARY_KEY_TYPE2 is an APPS-owned database view in the Oracle E-Business Suite Human Resources (PER) product module. It exposes a filtered, denormalized projection of the HR_SUMMARY table, restricting rows to those where the TYPE column equals the literal value 'KEY_TYPE'. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status and is shipped under the APPS schema as a standard, seeded dictionary object.

The view presents configuration data describing key types — the classification records that drive key flexfield and key structure behavior in Human Resources and related modules. Because the underlying HR_SUMMARY table stores heterogeneous summary rows distinguished by a TYPE discriminator, HR_SUMMARY_KEY_TYPE2 provides a stable, narrow interface for consumers that need only key type definitions. The trailing numeric suffix in the name ("2") indicates that it is one of several sibling views partitioning HR_SUMMARY by its TYPE value, a common Oracle EBS pattern that lets each logical entity be queried without re-applying the TYPE filter. In reporting and integration contexts, the view serves as a read-only source for extracts, BI Publisher data models, and interface programs that must resolve or validate key type identifiers.

Underlying Base Objects

HR_SUMMARY_KEY_TYPE2 is defined over a single documented base object: the HR_SUMMARY table, exposed to the APPS view through the HR_SUMMARY synonym. The view definition is a simple SELECT from that synonym, projecting selected columns while constraining the result set with the predicate WHERE S.TYPE = 'KEY_TYPE'. No joins, unions, or aggregations are present, so the view is a pure row-and-column filter over its base.

This one-to-many relationship — one physical summary table feeding multiple typed views — means every row visible through HR_SUMMARY_KEY_TYPE2 physically resides in HR_SUMMARY. Consequently, DML against the view is not intended; maintenance of key type definitions occurs through the application's own maintenance forms and APIs, which write to the base table. The view inherits the base object's storage, indexes, and any row-level security or grants configured on HR_SUMMARY. Because the synonym is resolved at runtime, the view remains valid only while that synonym points to the correct underlying table.

Key Columns

• ROW_ID — the ROWID of the underlying HR_SUMMARY row, exposed as an identifier column for the view.
• KEY_TYPE_ID — surrogate primary key identifying the key type record. The SELECT list reads this from S.ID_VALUE.
• BUSINESS_GROUP_ID — the business group (operating unit) that owns the key type, supporting multi-organization partitioning of configuration data.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the application to detect concurrent updates.
• NAME — the user-facing name of the key type, sourced from the S.TEXT_VALUE1 column.
• KEY_FUNCTION — the key function associated with the type, sourced from S.TEXT_VALUE6. This is the attribute of particular interest to callers searching on "key_function".
• SEEDED_DATA — a flag indicating whether the record was delivered by Oracle as seed data (non-customizable) or defined by the customer, sourced from S.TEXT_VALUE7.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard who-column auditing.

The mapping between the view's logical column names and the base table's generic TEXT_VALUE and ID_VALUE columns is significant: HR_SUMMARY stores many attribute types in a shared column set, and this view reassigns meaningful names to the positions relevant to key types.

Common Use Cases and Queries

Typical uses include validating a key type before insert, populating a lookup list in a custom form, and extracting key type configuration into reporting tables. A basic query retrieves all key types for a business group:

• SELECT key_type_id, name, key_function, seeded_data FROM apps.hr_summary_key_type2 WHERE business_group_id = :p_business_group_id;
• SELECT key_type_id, name FROM apps.hr_summary_key_type2 WHERE seeded_data = 'Y' ORDER BY name; — isolates Oracle-seeded key types.
• SELECT key_type_id FROM apps.hr_summary_key_type2 WHERE key_function = :p_key_function AND business_group_id = :p_bg_id; — resolves a specific key function to its type identifier.

Because the view is read-only in practice, it should be used exclusively for SELECT operations. Joins to HR_ALL_ORGANIZATION_UNITS on business_group_id are common to resolve the owning organization. All documented facts above derive from the ETRM 12.2.2 metadata; the view's behavior in 12.1.1 is consistent, as both releases ship the same APPS-owned definition.