Search Results template_items_pst




Overview
Explore in AI Chat

Overview

The APPS.HR_TEMPLATE_ITEM_INFO package body is a server-side PL/SQL utility within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically associated with the Oracle Forms-based template configuration framework. Its principal business function is to resolve and expose the detailed definition of individual template items that make up a form template. A "template item" represents a configurable element of an Oracle Forms screen — such as a field, radio button, or informational prompt — along with its presentation and behavioural attributes.

The package is classified under the ETRM taxonomy as OTHER, reflecting that it is an internal supporting object rather than a formally published public API. Its header comment (hrtiminf.pkb 120.0) indicates a long-standing object, largely stable since release 12.0, and reused unchanged across 12.1.1 and 12.2.2. The package is not referenced by any other packaged API, confirming its role as a terminal (leaf) utility consumed primarily by the Forms layer or by custom extensions.

Key Procedures and Functions

Two documented program units are exposed by this package body:

  • TEMPLATE_ITEMS — Populates and returns the collection of template items for a given form template. The body declares a global cursor csr_template_items that is parameterised by application_id, form_id, and form_template_id, and which joins template item definitions to their underlying item, window, canvas, and tab-page metadata. A persistent global variable (g_template_items) and an associated form_template_id cache hold the result set, allowing repeated lookups for the same template to be served without re-querying the database.
  • TEMPLATE_ITEMS_PST — Provides a persistent ("PST") variant of the template-item retrieval, maintaining its own state through variables such as g_template_items_pst, g_form_template_id_pst, and g_index_number_pst. This variant supports indexed access into a cached collection, which is characteristic of Oracle Forms record-group or LOV population patterns where ordered retrieval is required.

No parameter lists are documented; the members are described here by purpose only to avoid speculative signatures.

Tables Accessed

The package reads from a well-defined set of HR configuration tables, accessed through APPS synonyms. The cursor joins HR_TEMPLATE_ITEMS_B (the base template item definitions) against HR_FORM_ITEMS_B, HR_FORM_WINDOWS_B, HR_FORM_CANVASES_B, and HR_FORM_TAB_PAGES_B to resolve the full item name, item type, window, canvas, and tab-page context. Presentation and behaviour attributes (alignment, bevel, case restriction, format mask, height, prompt styling, enabled/insert flags) are drawn from HR_ITEM_PROPERTIES_B and its translated counterpart HR_ITEM_PROPERTIES_TL. Navigation and informational relationships are resolved through self-referential calls to HR_FORM_ITEM_INFO.full_item_name. Tab-page associations are supplied by HR_TEMPLATE_ITEM_TAB_PAGES and HR_TEMPLATE_TAB_PAGES_B, while HR_FORM_TEMPLATES_B anchors the template itself. PLITBLM, the standard Oracle Forms built-in library synonym, indicates dependence on Forms server timing/synchronisation facilities.

Usage Notes

This package is invoked at runtime by the Oracle Forms-based HR template administration and end-user screens whenever the definition of a template's items must be rendered or validated. Because it maintains module-level global state and caches the last-resolved template, it is best suited to session-scoped, sequential invocation rather than concurrent reuse within a single session. The absence of references from other packaged APIs means custom code may call it directly, but developers should treat it as an internal implementation object: signatures and behaviour are not guaranteed across patches. In 12.2.2 with the newer Forms/OAF hybrid architecture, such objects continue to support the classic Forms-based template configuration path, and any custom use should be validated against both 12.1.1 and 12.2.2 environments to confirm the underlying table structures remain compatible.