Search Results hr_summary_template




Overview
Explore in AI Chat

Overview

The APPS.HR_SUMMARY_TEMPLATE view is a filtered presentation layer within the Oracle E-Business Suite Human Resources (PER) product module. It exposes a curated subset of records from the HR_SUMMARY entity where the TYPE discriminator column equals the literal value 'TEMPLATE'. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration surface for template definitions consumed by the GSP (Generalized Summary Process), which underpins HR summary reporting and archival functionality. The view carries a VALID status in the ETRM data dictionary and is owned by the APPS schema, the standard repository for multi-tenant application objects.

Because the view is defined over an HR_SUMMARY synonym rather than a physical table directly, it inherits the security and access characteristics of the underlying object while restricting the result set to template-typed rows. This makes it a stable, read-oriented target for concurrent programs, XML Publisher reports, and third-party integrations that need to enumerate or inspect summary templates without traversing the full HR_SUMMARY population.

Underlying Base Objects

The documented base object for HR_SUMMARY_TEMPLATE is HR_SUMMARY, exposed to the APPS schema as a SYNONYM. The view text is expressed entirely as a projection over this single source:

All attributes of the template rows are therefore held natively in HR_SUMMARY; the view does not introduce joins, aggregations, or denormalization. Filtering occurs solely on the TYPE column, and the underlying ROWID is passed through unchanged, permitting updatable-view behavior for template-specific modifications where row-level identification is required.

Key Columns

The view exposes the following important columns. Note that the view text aliases several storage columns to semantically meaningful names in the documented column list.

  • ROW_ID / ROWID — The physical row identifier used for direct row access and update addressing.
  • TEMPLATE_ID (ID_VALUE) — The primary identifier of the template record; sourced from the generic ID_VALUE column.
  • BUSINESS_GROUP_ID — The operating business group, essential for multi-organization data isolation and security.
  • OBJECT_VERSION_NUMBER — Optimistic locking token used by the Oracle Applications Framework and PL/SQL APIs to detect concurrent modifications.
  • NAME (TEXT_VALUE1) — The template name or identifying text value.
  • SEEDED_DATA (TEXT_VALUE7) — Indicates whether the template was delivered as seed data by Oracle or created by the customer; governs upgrade and patch behavior.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns capturing record creation.

Common Use Cases and Queries

The view is typically queried to enumerate available templates, to identify seeded versus custom templates before upgrades, or to validate business-group scoping for GSP configuration. A representative query restricting to a business group and non-seeded templates follows:

  • SELECT template_id, name, business_group_id, seeded_data, last_update_date FROM apps.hr_summary_template WHERE business_group_id = :p_bg_id AND NVL(seeded_data,'N') = 'N';
  • SELECT COUNT(*) FROM apps.hr_summary_template; — inventory of all template rows visible in the current session.

Because the view is updatable through ROWID, it may also be used in controlled correction scripts, though changes are ordinarily performed through supported GSP or HR APIs to preserve OBJECT_VERSION_NUMBER consistency and audit integrity.