Search Results delete_template

Overview

The APPS.HXC_TEMPLATE_SUMMARY_API package is a public Application Programming Interface belonging to the Oracle Time and Labor (OTL) schema family, identified by the HXC object prefix. It provides a controlled, programmatic mechanism for creating, maintaining, and removing template summary definitions used within the Time and Labor timecard and template infrastructure. Templates in Oracle Time and Labor act as reusable structures that predefine timecard layout, applicable blocks, and associated time attributes, enabling consistent time entry across groups of employees. The package encapsulates the business logic required to manipulate the HXC_TEMPLATE_SUMMARY entity so that callers need not perform direct data manipulation against the underlying tables. By exposing a formal API classification, Oracle permits both internal components and customer extensions to interact with template summary data in a supported manner that preserves data integrity and the integrity of the summary records themselves. The package is documented in ETRM for both the 12.1.1 and 12.2.2 releases, and is referenced by three other packages, indicating it plays a supporting role in a broader set of time and labor operations. It is owned by the APPS schema and is not intended for direct ad hoc invocation outside the prescribed API entry points.

Key Procedures and Functions

The documented interface exposes three procedures, two of which are overloaded under the same name.

• DELETE_TEMPLATE — Removes a template summary identified by its template identifier. This is the procedure most directly associated with the user's search term "delete_template," and it is the supported method for eliminating a template summary record rather than issuing a direct SQL delete against HXC_TEMPLATE_SUMMARY.
• TEMPLATE_DEPOSIT (block and attribute variant) — Persists a template summary using collections of blocks and attributes supplied by the caller. This variant accepts table-type parameters that carry the block and attribute structures to be associated with the template.
• TEMPLATE_DEPOSIT (template identifier variant) — A second overload that performs the deposit operation using a template identifier together with the template object version number, supporting the standard optimistic locking pattern used throughout Oracle EBS APIs.

No additional parameter signatures should be assumed beyond those documented; the overloads exist to accommodate different calling contexts for the same logical deposit operation.

Tables Accessed

The package operates against several documented tables, accessed through APPS synonyms.

• HXC_TEMPLATE_SUMMARY — The primary entity table holding template summary definitions. It is read and written by the deposit procedures and used to locate the record targeted by DELETE_TEMPLATE.
• HXC_BLD_BLK_INFO_TYPES — Supplies block information type definitions referenced when assembling template block content during deposit.
• HXC_TIME_ATTRIBUTES — Holds time attribute definitions associated with templates.
• HXC_TIME_ATTRIBUTE_USAGES — Records where and how time attributes are used, supporting validation and association logic.
• PLITBLM — The standard Oracle Applications PL/SQL table and index-by table storage object, used internally for collection handling.

Usage Notes

HXC_TEMPLATE_SUMMARY_API is typically invoked from Oracle Time and Labor forms, from concurrent programs that build or refresh template definitions, or from custom PL/SQL extensions that must create or delete template summaries in a supported fashion. Developers should never bypass the API to modify HXC_TEMPLATE_SUMMARY directly, as the package maintains dependent block and attribute relationships and enforces the object version number convention. When integrating custom code, callers should supply the correct template identifier and, for the deposit overload, the current object version number to avoid concurrent update conflicts. Because DELETE_TEMPLATE permanently removes the summary, it should be invoked only after confirming that no active timecards or dependent configurations rely on the template. The package's role as a referenced component of three other packages means changes to its behavior can cascade through time and labor processing, warranting careful testing in any upgrade from 12.1.1 to 12.2.2.