Results for “key_type_usage”

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

Overview

APPS.HR_SUMMARY_KEY_TYPE_USAGE is a supplementary view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema. Its registered FND Design Data identifier is PER.HR_SUMMARY_KEY_TYPE_USAGE, confirming that it belongs to the Human Resources (PER) product family. The view operates with a status of VALID in the ETRM repository. Its stated purpose is to simplify forms coding within the Oracle HRMS application. Oracle explicitly cautions that this is a "supplementary view used to simplify forms coding," and warns that it "may change dramatically in subsequent minor or major releases." Accordingly, the object is not intended for direct customer queries or data manipulation, and any custom dependency on its structure carries upgrade risk.

From a functional standpoint, the view exposes the relationship between summary key types and the item type usages they are associated with, together with the valid key type identifier. This makes it relevant to HRMS summary and reporting configurations where key type usage must be validated and linked.

Underlying Base Objects

The ETRM metadata documents the sole referenced base object as HR_SUMMARY, resolved through an APPS synonym. The dependency listing also records that APPS.HR_SUMMARY_KEY_TYPE_USAGE is referenced by two packaged components: HRSUMREP and HR_COPY_GSP. This dependency pattern indicates the view is consumed by summary reporting logic and by GSP (Global Support/installation) copy routines rather than by direct end-user transactions. Because the documented underlying source is HR_SUMMARY, the view can be understood as a curated projection over the summary data model, surfacing the key type usage rows needed by the forms and packages that depend on it.

Key Columns

• ROW_ID (ROWID) — The physical row identifier.
• KEY_TYPE_USAGE_ID (NUMBER, 15) — System-generated primary key for the key type usage record.
• BUSINESS_GROUP_ID (NUMBER, 15) — Foreign key to HR_ORGANIZATION_UNITS; establishes the business group context for multi-tenant HR data.
• OBJECT_VERSION_NUMBER (NUMBER) — Optimistic locking column; increments by one on each update.
• ITEM_TYPE_USAGE_ID (NUMBER, 15) — Identifies the associated item type usage.
• VALID_KEY_TYPE_ID (NUMBER, 15) — Identifies the valid key type. This is the column most relevant to the user search term "valid_key_type_id."
• SEEDED_DATA (VARCHAR2, 240) — Identifies seeded (Oracle-delivered) versus user-defined data.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard audit tracking.

Common Use Cases and Queries

Typical usage involves joining business group and item type usage information to interpret valid key type assignments. The canonical query supplied in the ETRM documentation is:

• SELECT ROW_ID, KEY_TYPE_USAGE_ID, BUSINESS_GROUP_ID, OBJECT_VERSION_NUMBER, ITEM_TYPE_USAGE_ID, VALID_KEY_TYPE_ID, SEEDED_DATA, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE FROM APPS.HR_SUMMARY_KEY_TYPE_USAGE;

A practical filtered variant to locate the valid key type for a given item type usage would add WHERE ITEM_TYPE_USAGE_ID = :item_type_usage_id and constrain BUSINESS_GROUP_ID to isolate the correct business group. Investigators tracing the VALID_KEY_TYPE_ID column should remember Oracle's explicit warning: the view is for forms support only and may change across releases, so production integrations should instead query the underlying HR_SUMMARY structures or supported public APIs.