Results for “hr_summary_valid_key_type”

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

Overview

HR_SUMMARY_VALID_KEY_TYPE is a VALID view owned by the APPS schema within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Functionally, it exposes information about the key types that may be used by a particular item type, a relationship central to Oracle HRMS Summary and Extensible Flexfield configuration. The view is one of the standard filtered views built over the HR_SUMMARY entity, in which each summary row is classified by a TYPE discriminator column. This particular view restricts that set to rows where TYPE equals 'VALID_KEY_TYPE', giving callers a stable, semantically named window onto the subset of summary records that define legal key-type assignments. Because it follows the standard date-tracked, multi-tenant pattern (BUSINESS_GROUP_ID, OBJECT_VERSION_NUMBER, audit columns), the view is safe to consume in reports, concurrent programs, OAF pages, and integration extracts without needing to know the underlying discriminator value. Users searching for key_type_id will find this view is the principal published path to that attribute in the HRMS summary model.

Underlying Base Objects

The ETRM 12.2.2 metadata documents exactly one referenced base object: the synonym HR_SUMMARY. The view text confirms this dependency with a direct projection of columns from HR_SUMMARY where TYPE = 'VALID_KEY_TYPE':

• ROWID is re-labeled in the view's column list as ROW_ID, providing a physical row locator for the summary record.
• ID_VALUE, FK_VALUE1, FK_VALUE2, TEXT_VALUE7 and BUSINESS_GROUP_ID supply the generic attribute slots that the summary model uses to hold type-specific data.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY and CREATION_DATE provide concurrency control and audit tracking inherited from the base entity.

Note that the implemented view text is generic over the HR_SUMMARY table and the column list presented in the data dictionary is the semantically resolved form for the 'VALID_KEY_TYPE' type — the names VALID_KEY_TYPE_ID, ITEM_TYPE_ID, KEY_TYPE_ID and SEEDED_DATA map onto the generic ID_VALUE/FK_VALUE/TEXT_VALUE slots. Third-party queries should therefore prefer the view rather than reading HR_SUMMARY directly, since the discriminator filter and column semantics are maintained by Oracle.

Key Columns

• ROW_ID — physical ROWID of the underlying HR_SUMMARY row; useful for direct row access and de-duplication.
• VALID_KEY_TYPE_ID — surrogate identifier of the valid key-type record; the primary business key of each row.
• BUSINESS_GROUP_ID — operating business group (legal employer) partition; mandatory for multi-org-aware queries.
• OBJECT_VERSION_NUMBER — optimistic locking token; must be honored by any DML against the base record.
• ITEM_TYPE_ID — the item type to which the key type is being related; the "particular item type" referenced in the object description.
• KEY_TYPE_ID — the key type itself; this is the column surfaced to users searching for key_type_id.
• SEEDED_DATA — flag distinguishing Oracle-seeded rows from customer-defined rows; seeded rows should not be deleted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN / CREATED_BY / CREATION_DATE — standard WHO audit columns for traceability and delta extraction.

Common Use Cases and Queries

Typical scenarios include validating that a chosen key type is permitted for an item type before creating summary data, generating configuration listings for an HRMS implementation, and extracting seeded versus customer-defined valid key types for audit. Because the view is business-group partitioned, queries should always constrain BUSINESS_GROUP_ID. A representative query joining the view to the item type and key type entities follows:

SELECT v.VALID_KEY_TYPE_ID, v.ITEM_TYPE_ID, v.KEY_TYPE_ID, v.SEEDED_DATA FROM APPS.HR_SUMMARY_VALID_KEY_TYPE v WHERE v.BUSINESS_GROUP_ID = :p_business_group_id AND v.ITEM_TYPE_ID = :p_item_type_id ORDER BY v.KEY_TYPE_ID;

For delta extracts, filter on LAST_UPDATE_DATE: SELECT KEY_TYPE_ID, ITEM_TYPE_ID, LAST_UPDATE_DATE FROM APPS.HR_SUMMARY_VALID_KEY_TYPE WHERE BUSINESS_GROUP_ID = :p_bg_id AND LAST_UPDATE_DATE >= :p_since;

To separate Oracle-seeded configuration from customer extensions: SELECT SEEDED_DATA, COUNT(*) FROM APPS.HR_SUMMARY_VALID_KEY_TYPE WHERE BUSINESS_GROUP_ID = :p_bg_id GROUP BY SEEDED_DATA; The view is read-only in practice; all maintenance is performed against the HR_SUMMARY base entity through the supported HRMS APIs.