Search Results hxc_template_summary




Overview
Explore in AI Chat

Overview

HXC_TEMPLATE_SUMMARY is a table owned by the HXC schema within the Oracle E-Business Suite Time and Labor Engine product. Its documented purpose is to serve as a Template Summary Table, meaning it stores header-level definitions for timecard and time entry templates used by the Time and Labor module. In Oracle EBS 12.1.1 and 12.2.2, the HXC schema is the core repository for time collection, template configuration, and time calculation metadata. This table occupies the configuration layer: it defines what a template is, how it is laid out, which recurring period governs it, and under which business group it is valid, rather than storing transactional timecard rows themselves.

The ETRM data vault classification for this object is standalone, derived heuristically from its foreign key structure. In Data Vault modeling terms this suggests the table behaves primarily as a hub-like or reference entity: it is keyed by a single surrogate identifier, is not dependent on a parent transactional link, and references only one other table. Modelers should treat it as a configuration or definition hub rather than a transactional link table.

Key Information Stored

The table contains 13 documented columns. The most significant are summarized below.

  • TEMPLATE_ID — the surrogate primary key. It is the single column of the unique index HXC_TEMPLATE_SUMMARY_PK and is the only documented business-key candidate, making it the authoritative join key for dependents.
  • TEMPLATE_NAME and DESCRIPTION — the user-facing identity and explanatory text for the template, used in list-of-values queries and reporting.
  • TEMPLATE_OVN — the object version number, the standard EBS optimistic-locking and concurrency column, incremented on each update.
  • TEMPLATE_TYPE — classifies the template (for example, by the kind of time entry or layout behavior it supports), driving how the Time and Labor engine applies it.
  • LAYOUT_ID — identifies the associated timecard or page layout used to render the template.
  • RECORDED_HOURS — indicates whether hours are captured directly, a configuration flag affecting how time is entered against the template.
  • RECURRING_PERIOD_ID — the sole documented foreign key, referencing HXC_RECURRING_PERIODS, and tying the template to the recurring period that governs its scheduling.
  • RESOURCE_ID and LAST_UPDATED_BY_RESOURCE_ID — the owning resource and the resource that last modified the template, supporting ownership and audit reporting.
  • BUSINESS_GROUP_ID — the multi-tenant partition key, essential for filtering in any multi-organization query.
  • START_TIME and STOP_TIME — the effective start and end timestamps bounding the template's validity.

Common Use Cases and Queries

Typical uses include auditing template configuration, reporting which templates are active for a business group, and tracing which recurring period or layout a template depends on. A common pattern joins the summary to its recurring period:

SELECT t.template_id, t.template_name, t.template_type, r.recurring_period_id
FROM hxc_template_summary t, hxc_recurring_periods r
WHERE t.recurring_period_id = r.recurring_period_id
AND t.business_group_id = :p_bg_id;

Because START_TIME and STOP_TIME define validity, date-effective reporting should constrain on those columns. The TEMPLATE_TYPE and RECORDED_HOURS columns support gap analysis of configuration coverage across business groups. All queries should filter on BUSINESS_GROUP_ID to respect EBS multi-tenancy.

Related Objects

  • HXC_RECURRING_PERIODS — referenced through RECURRING_PERIOD_ID; the only documented foreign key relationship.
  • HXC_TEMPLATE_SUMMARY_PK — the unique index on TEMPLATE_ID that enforces primary-key uniqueness.
  • Layout objects referenced by LAYOUT_ID — the layout definition used to render the template.
  • Resource objects referenced by RESOURCE_ID and LAST_UPDATED_BY_RESOURCE_ID — the HXC resource definitions for ownership and audit.
  • Timecard and time entry tables — downstream transactional tables that consume the template identified by TEMPLATE_ID.
  • Time and Labor configuration and validation APIs — server-side logic in the HXC module that reads this table when resolving template behavior.