Results for “item_type_usage”

30 results




Overview
Explore in AI Chat

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

Overview

APPS.HR_SUMMARY_ITEM_TYPE_USAGE is a reporting and integration view in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is not a standalone entity; rather, it is a filtered presentation of the generic HR_SUMMARY table, exposing only those rows whose TYPE discriminator equals 'ITEM_TYPE_USAGE'. The view therefore serves as a denormalized, business-friendly window onto a subset of HR summary records that relate to item type usage within the Oracle HRMS data model.

Because HR_SUMMARY is designed as a flexible, extensible container for summary-type information, individual consumers are isolated from unrelated row types by dedicated views such as this one. The view's principal role is to make the item_type_usage summary data available for concurrent programs, Oracle Application Framework (OAF) pages, Oracle Forms blocks, and third-party integrations without exposing the polymorphic nature of the underlying table. In release 12.2.2 the metadata records the owner as APPS and the sole referenced base object as HR_SUMMARY (SYNONYM), confirming the view is a thin, read-oriented projection.

Underlying Base Objects

The view is defined entirely over HR_SUMMARY, referenced through its APPS synonym. Its defining text is a simple projection with a fixed predicate:

No joins are performed. Consequently, the view inherits the storage characteristics, indexing, and business-group security behavior of HR_SUMMARY. All DML against the view is limited by Oracle's restrictions on views containing ROWID and by the underlying table's own constraints.

Key Columns

The columns map directly onto the generic HR_SUMMARY model, where numeric, text, and foreign-key slots are reused according to the row type. For ITEM_TYPE_USAGE rows the following are significant:

  • ROWID: Physical row identifier, useful for update/delete targeting and for diagnostics.
  • ID_VALUE: The primary logical identifier of the summary record.
  • BUSINESS_GROUP_ID: The business group (operating unit) that owns the record; drives multitenancy and security filtering.
  • OBJECT_VERSION_NUMBER: Optimistic locking token used by the OAF framework.
  • NUM_VALUE1 / TEXT_VALUE1: Generic numeric and text carriers populated with item-type-specific values.
  • FK_VALUE1 / FK_VALUE2: Foreign-key slots pointing to related entities referenced by the usage definition.
  • TEXT_VALUE7: An additional text attribute used for this summary type.
  • Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN provide standard EBS who/when auditing.

Common Use Cases and Queries

Typical consumers use the view to enumerate item type usage summaries for a business group, to drive LOVs, or to reconcile HRMS configuration data. Because the type filter is applied internally, callers need not reference the discriminator column.

Sample query to list usage rows for a business group:

  • SELECT id_value, business_group_id, num_value1, text_value1, fk_value1, fk_value2 FROM apps.hr_summary_item_type_usage WHERE business_group_id = :p_bg_id ORDER BY id_value;

Sample query to retrieve a single record with audit information:

  • SELECT id_value, num_value1, text_value1, last_update_date, last_updated_by FROM apps.hr_summary_item_type_usage WHERE id_value = :p_id;

Sample query to detect recently modified rows for integration polling:

  • SELECT id_value, object_version_number, last_update_date FROM apps.hr_summary_item_type_usage WHERE last_update_date >= :p_since_date ORDER BY last_update_date;

These patterns are consistent with the documented view text and provide a stable interface even if the internal layout of HR_SUMMARY is extended in future patches.