Search Results hr_summary_item_type_usage




Overview
Explore in AI Chat

Overview

The HR_SUMMARY_ITEM_TYPE_USAGE view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and classified under the PER (Human Resources) product family. Its documented purpose is to identify the items that will be used by a template every time the GSP process is run. In practical terms, the view exposes the configuration that links summary templates to the specific item types they consume during summary generation. Because the GSP (Summary of Payments / summary generation) process relies on this configuration to determine which items are pulled into a given template run, the view functions as a reporting and integration surface for that setup data. Administrators and technical consultants use it to audit which item types a template depends on, to validate configuration after cloning or patching, and to drive downstream extracts that must mirror the summary process inputs.

Underlying Base Objects

The view is defined over a single documented base object: HR_SUMMARY, referenced through a synonym. Rather than storing item-type-usage rows in a dedicated table, HR_SUMMARY acts as a consolidated, polymorphic store keyed by TYPE. The view filters that store to the subset where TYPE = 'ITEM_TYPE_USAGE', projecting only the columns relevant to item type usage. Consequently, HR_SUMMARY_ITEM_TYPE_USAGE is a filtered, denormalized presentation layer rather than a physical entity, and no data of its own exists independent of HR_SUMMARY. The documented ETRM metadata records HR_SUMMARY (SYNONYM) as the only referenced base object, confirming there are no additional joins to other tables in the view definition.

Key Columns

  • ROWID / ROW_ID - The physical row identifier projected from HR_SUMMARY, used as a surrogate reference.
  • ITEM_TYPE_USAGE_ID - The identifier for the item type usage record; derived from the ID_VALUE column of the base store.
  • BUSINESS_GROUP_ID - The business group that owns the configuration, enforcing multi-tenant separation of HR setup data.
  • SEQUENCE_NUMBER - Ordering attribute controlling how items are processed within the template.
  • NAME - Descriptive name associated with the usage entry.
  • TEMPLATE_ID - Reference to the summary template that will use the item type during the GSP run.
  • ITEM_TYPE_ID - Reference to the item type consumed by the template.
  • SEEDED_DATA - Indicates whether the row was delivered by Oracle as seeded configuration.
  • OBJECT_VERSION_NUMBER - Optimistic locking column for concurrent update control.
  • Audit columns - LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard who-column auditing.

The documented view text also projects underlying storage columns such as ID_VALUE, NUM_VALUE1, TEXT_VALUE1, FK_VALUE1, FK_VALUE2, and TEXT_VALUE7 from HR_SUMMARY; these correspond positionally to attributes such as the usage ID, sequence number, name, template reference, and item type reference in the logical column list.

Common Use Cases and Queries

Typical scenarios include auditing which item types a template requires, verifying seeded versus user-defined usage rows, and reconciling configuration across business groups after a clone or upgrade. Because the view is read-only and filtered, queries are straightforward and do not require knowledge of the polymorphic base table. A representative query retrieves usage rows for a specific template:

  • SELECT item_type_usage_id, template_id, item_type_id, sequence_number, name, seeded_data FROM apps.hr_summary_item_type_usage WHERE template_id = :p_template_id ORDER BY sequence_number;
  • SELECT business_group_id, COUNT(*) FROM apps.hr_summary_item_type_usage GROUP BY business_group_id; to profile usage configuration by business group.
  • SELECT * FROM apps.hr_summary_item_type_usage WHERE seeded_data = 'Y'; to isolate Oracle-seeded entries.

Join the view to HR_SUMMARY_TEMPLATES and item type lookup tables on TEMPLATE_ID and ITEM_TYPE_ID respectively to produce descriptive reports of template-to-item dependencies before executing the GSP process. All access should honor business group security and treat the view strictly as a read-only reporting interface over HR_SUMMARY.