Search Results hxc_template_summary_pkg




Overview
Explore in AI Chat

Overview

HXC_TEMPLATE_SUMMARY_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that maintains the denormalized summary representation of timecard and time-entry templates used by Oracle Time and Labor (OTL). Within the HXC (Time and Labor) product family, templates are stored as time building blocks in the transactional HXC_TIME_BUILDING_BLOCKS table, which is optimized for hierarchical and attribute-driven processing rather than for list-of-values queries or form-driven browsing. The HXC_TEMPLATE_SUMMARY table provides a flattened, query-efficient projection of the most frequently referenced template attributes—name, description, template type, layout, recurring period, business group, and resource.

This package encapsulates the create, update, and delete maintenance of that summary row so that summary data remains synchronized with the underlying building block. The API is classified as OTHER in the ETRM metadata, meaning it is an internal maintenance API rather than a formally published, externally supported interface; nevertheless, it is referenced by one other package in the application, confirming its role as a shared utility within the OTL template subsystem.

Key Procedures and Functions

The package exposes three documented procedures, all of which are public and operate against a template identifier:

  • INSERT_SUMMARY_ROW — Creates a new row in the template summary table for a template. Its signature accepts the template building block identifier and object version number, together with the descriptive and structural attributes to be denormalized: template name, description, template type, layout identifier, recurring period identifier, business group identifier, and resource identifier.
  • UPDATE_SUMMARY_ROW — Refreshes the existing summary row for the template identified by the supplied template identifier. This is the procedure most commonly located by the search term "update_summary_row"; it is the mechanism by which changes made to the underlying time building block are propagated into the summary table, typically after the template definition has been modified.
  • DELETE_SUMMARY_ROW — Removes the summary row associated with the specified template identifier, maintaining referential consistency when a template is deleted or otherwise made unavailable.

Each procedure is keyed solely on the template identifier (for update and delete) or the template identifier plus object version number (for insert), which is consistent with the OTL convention of carrying OBJECT_VERSION_NUMBER for optimistic locking on time building blocks.

Tables Accessed

Two tables are referenced through APPS synonyms:

  • HXC_TEMPLATE_SUMMARY — The target table for all three procedures. It holds the flattened template attributes and serves as the query-friendly source for template selection and validation. INSERT_SUMMARY_ROW, UPDATE_SUMMARY_ROW, and DELETE_SUMMARY_ROW perform DML against this table.
  • HXC_TIME_BUILDING_BLOCKS — The source of truth for template definitions. It supplies the template identifier and object version number used as the input key, and it is the parent entity whose changes drive the summary maintenance. The dependency is evidenced by the parameter typing against HXC_TIME_BUILDING_BLOCKS.TIME_BUILDING_BLOCK_ID and HXC_TIME_BUILDING_BLOCKS.OBJECT_VERSION_NUMBER.

Usage Notes

Because the package is classified as OTHER and carries a private header comment, it should be treated as an internal API rather than a supported extension point. In standard Oracle Time and Labor flows, INSERT_SUMMARY_ROW, UPDATE_SUMMARY_ROW, and DELETE_SUMMARY_ROW are invoked by the template maintenance logic—Oracle Forms–based template definition screens and their underlying server-side handlers—whenever a template record is created, modified, or removed. The package is also referenced by one other APPS package, which delegates summary synchronization to it rather than duplicating the DML.

Custom code should not call these procedures directly to alter summary rows, because bypassing the standard template maintenance path risks divergence between HXC_TEMPLATE_SUMMARY and HXC_TIME_BUILDING_BLOCKS. Where the metadata is limited—particularly with respect to concurrency handling and any validation performed inside UPDATE_SUMMARY_ROW—behavior should be confirmed against the deployed package body in the specific release (12.1.1 or 12.2.2) before relying on it. Any custom integration should prefer the supported OTL template APIs, treating HXC_TEMPLATE_SUMMARY_PKG as a downstream implementation detail.