Results for “key_type_usage_id”

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

Overview

HR_SUMMARY_KEY_TYPE_USAGE is an APPS-owned database view within the PER (Human Resources) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes a filtered, semantically meaningful subset of the generic HR_SUMMARY flexfield-style storage table, presenting rows where the TYPE discriminator equals 'KEY_TYPE_USAGE'. Conceptually, the view identifies which particular key types should be included within the SQL statement generated for an Item Type when that Item Type is processed within a particular Template. This places the view squarely in the machinery that drives the HR Summary / Total Compensation style reporting framework, where a Template orchestrates the generation of a SQL statement, an Item Type describes a unit of data to be reported, and one or more key types define the input or grouping values that must appear in the generated query.

Because the view exposes a stable, well-named column set rather than the internal FK_VALUE1 / FK_VALUE2 / TEXT_VALUE7 naming of the base table, it is the preferred access point for reports, extracts, and integration code that must reason about key type inclusion rules without depending on the underlying generic storage layout.

Underlying Base Objects

The only documented base object referenced by the view is HR_SUMMARY, itself exposed in APPS through a synonym. The view text is a simple projection over that table:

• SELECT ROWID, ID_VALUE, BUSINESS_GROUP_ID, OBJECT_VERSION_NUMBER, FK_VALUE1, FK_VALUE2, TEXT_VALUE7, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE FROM HR_SUMMARY WHERE TYPE = 'KEY_TYPE_USAGE'

The implication is that HR_SUMMARY is a polymorphic or "summary-type" table that stores multiple logical entities, discriminated by TYPE. The view does not join to any additional object; all contextual referencing is achieved through the foreign-key columns FK_VALUE1 and FK_VALUE2, which are surfaced in the view's column list under descriptive names such as ITEM_TYPE_USAGE_ID and VALID_KEY_TYPE_ID. There is therefore a strict one-to-one mapping between qualifying HR_SUMMARY rows and rows in this view, with no aggregation, deduplication, or filtering other than the TYPE predicate.

Key Columns

The view's exposed columns provide the identifying and auditing attributes of each key type usage record:

• ROW_ID — the physical ROWID of the underlying HR_SUMMARY row; useful for surgical updates or diagnostics.
• KEY_TYPE_USAGE_ID — the primary identifier for the usage record, mapped from ID_VALUE.
• BUSINESS_GROUP_ID — the HR business group (legislative) context, essential for multi-organization filtering.
• OBJECT_VERSION_NUMBER — optimistic locking version used by the AOL/BC4J layer during concurrent updates.
• ITEM_TYPE_USAGE_ID — foreign key (mapped from FK_VALUE1) to the item type usage definition that this key type participates in.
• VALID_KEY_TYPE_ID — foreign key (mapped from FK_VALUE2) to the key type that must be included in the generated SQL for the associated item type and template.
• SEEDED_DATA — flag indicating whether the row is Oracleseed data, which should not be modified or deleted by customers.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Who columns for auditing.

Common Use Cases and Queries

Typical usage includes diagnosing why a particular key type does or does not appear in a generated summary report, auditing seeding integrity, and building extracts for custom reports that migrate HR Summary template definitions between environments.

• List all usages for a key type:

  SELECT key_type_usage_id, business_group_id, item_type_usage_id, valid_key_type_id, seeded_data
  FROM   apps.hr_summary_key_type_usage
  WHERE  valid_key_type_id = :p_key_type_id
  AND    business_group_id = :p_business_group_id
  ORDER BY item_type_usage_id;

• Audit seeded vs. customer data:

  SELECT seeded_data, COUNT(*)
  FROM   apps.hr_summary_key_type_usage
  GROUP BY seeded_data;

• Detect orphaned or recently changed rows:

  SELECT key_type_usage_id, last_update_date, last_updated_by
  FROM   apps.hr_summary_key_type_usage
  WHERE  last_update_date > SYSDATE - 7
  ORDER BY last_update_date DESC;

Because the view is unrestricted by business group or date, callers should always supply a BUSINESS_GROUP_ID predicate to avoid cross-legislative data leakage, and should treat SEEDED_DATA = 'Y' rows as read-only when planning any data fix or migration.