Search Results hxc_template_summary_pk

Overview

HXC.HXC_TEMPLATE_SUMMARY is a transactional table in the Oracle E-Business Suite Time and Labor (HXC) schema that stores summary-level information for Timecard Templates. Timecard Templates provide the reusable structures from which timecards are generated, including the layout, owning resource, default recorded hours, and the recurring period over which the template applies. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are held separately in APPS_TS_TX_IDX.

From a dimensional modeling perspective, the mined relationship data classifies this object heuristically as a standalone structure. That classification is a suggestion rather than a formal Data Vault designation: the only documented foreign key is a reference to HXC_RECURRING_PERIODS via RECURRING_PERIOD_ID, and no other table in the documented dependency set references it. In practice, the unique index on TEMPLATE_ID supports treating the table as a hub-like entity keyed by template, with attribute columns such as TEMPLATE_NAME, DESCRIPTION, and RECORDED_HOURS behaving in a satellite-like manner.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is TEMPLATE_ID (NUMBER(15)), enforced by the unique index HXC_TEMPLATE_SUMMARY_PK. No separate business-key column is documented beyond this identifier; TEMPLATE_ID therefore serves simultaneously as the technical key and the effective template identifier used throughout the schema.

• TEMPLATE_ID — unique template identifier; the primary key column and the principal join key.
• TEMPLATE_OVN — object version number, used for optimistic concurrency control during template updates.
• TEMPLATE_NAME — descriptive name of the timecard template (VARCHAR2 150).
• DESCRIPTION — free-text description of the template (VARCHAR2 150).
• TEMPLATE_TYPE — classification of the template, distinguishing template behavior (VARCHAR2 150).
• RECORDED_HOURS — default number of hours recorded against the template.
• LAYOUT_ID — reference to the timecard layout used by the template; indexed by HXC_TEMPLATE_SUMMARY_FK2.
• RESOURCE_ID — the resource that owns or is associated with the template; indexed by HXC_TEMPLATE_SUMMARY_FK1.
• LAST_UPDATED_BY_RESOURCE_ID — the resource credited with the most recent modification.
• RECURRING_PERIOD_ID — the only documented foreign key, referencing HXC_RECURRING_PERIODS.
• BUSINESS_GROUP_ID — multi-tenant partition key separating data by business group.
• START_TIME / STOP_TIME — the effective window for which the template summary applies.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing all templates for a business group, retrieving the layout and owning resource for a template, and identifying templates tied to a recurring period for scheduling or payroll processing. Query patterns commonly filter on BUSINESS_GROUP_ID for multi-org isolation and on RESOURCE_ID to obtain a resource's template set.

The canonical extraction uses the documented query text:

• SELECT TEMPLATE_ID, TEMPLATE_NAME, TEMPLATE_TYPE, RECORDED_HOURS, LAYOUT_ID, RESOURCE_ID FROM HXC.HXC_TEMPLATE_SUMMARY WHERE BUSINESS_GROUP_ID = :p_bg_id;
• Join to HXC_RECURRING_PERIODS on HXC_TEMPLATE_SUMMARY.RECURRING_PERIOD_ID = HXC_RECURRING_PERIODS.RECURRING_PERIOD_ID to resolve period attributes.
• Order by TEMPLATE_NAME to present a resource's available templates in a selection list.

Related Objects

The documented dependency data identifies the following significant relationships:

• HXC.HXC_RECURRING_PERIODS — referenced through RECURRING_PERIOD_ID; defines the recurrence definition associated with a template.
• APPS.HXC_TEMPLATE_SUMMARY — the APPS-layer synonym or view exposing the table to application code and reports.
• HXC_TEMPLATE_SUMMARY_PK — unique index on TEMPLATE_ID, supporting direct lookups by template.
• HXC_TEMPLATE_SUMMARY_FK1 — non-unique index on RESOURCE_ID, used for resource-based template retrieval.
• HXC_TEMPLATE_SUMMARY_FK2 — non-unique index on LAYOUT_ID, supporting layout-driven queries.
• HXC_TEMPLATE_DETAILS — the companion detail table (referenced conceptually through TEMPLATE_ID) holding line-level template content; note that no explicit FK is documented between the two in the metadata supplied.

Because only the RECURRING_PERIOD_ID foreign key is documented, integration work should verify any additional parent references at implementation time rather than assuming referential enforcement.