Search Results template_windows




Overview
Explore in AI Chat

Overview

APPS.HR_TEMPLATE_WINDOW_INFO is a PL/SQL package body belonging to the Oracle E-Business Suite HR (Human Resources) module, specifically the Oracle Forms-based template architecture used by the self-service and professional forms infrastructure. Its documented source header (hrtwninf.pkb 120.0) indicates it is a long-standing component that has been part of the Oracle Forms personalization and template framework since at least the 11i era, and remains shipped in both EBS 12.1.1 and 12.2.2.

The business purpose of this package is to expose metadata about the windows that belong to a given form template. In Oracle EBS, a form template (HR_FORM_TEMPLATES_B) defines the overall look, layout, and configuration of an Oracle Forms window hierarchy. Each template can contain one or more template windows (HR_TEMPLATE_WINDOWS_B) that correspond to physical form windows. This package assembles the template-to-window mapping together with window display properties such as height, width, X/Y position, title, and the generic INFORMATION1 through INFORMATION30 attribute columns. The result is a cached, in-memory structure of template window information that callers—typically form-level PL/SQL libraries and the template-rendering engine—can query at runtime rather than repeatedly issuing SQL against the underlying tables.

The package is classified in ETRM as API classification OTHER, meaning it is an internal support package rather than a public, supported business API. It is referenced by zero other documented packages, which confirms its role as a low-level helper consumed indirectly through the forms template infrastructure.

Key Procedures and Functions

  • TEMPLATE_WINDOWS — The primary documented routine. It populates and/or returns the global collection g_template_windows (typed as t_template_windows) by executing the strongly typed cursor csr_template_windows. That cursor joins the window property translation and base tables, the template window table, and the form window table, filtered by application ID, form ID, and form template ID, with the language restricted via userenv('LANG'). The routine therefore serves as the accessor that retrieves template window metadata for a specified form template.
  • TEMPLATE_WINDOWS_PST — A companion routine, conventionally suffixed _PST in Oracle EBS to denote population/cache-initialization logic (a pattern common in HRMS form template packages). It is responsible for seeding or reconstructing the package-level global state—particularly the g_form_template_id and g_template_windows globals—so that subsequent calls to TEMPLATE_WINDOWS return data for the correct form template.

No parameter lists are documented, and per the source excerpt the cursor parameters are typed against hr_form_templates_b columns for application ID, form ID, and form template ID.

Tables Accessed

  • HR_FORM_TEMPLATES_B — The form template definition table; supplies the template identifier and is the anchor for the query filters.
  • HR_FORM_WINDOWS_B — Maps physical form windows to the application and form; supplies the window name.
  • HR_TEMPLATE_WINDOWS_B — Associates template windows with a form template and a form window; the central join table.
  • HR_WINDOW_PROPERTIES_B — Stores the base display properties (height, width, X/Y position, information attributes) for each template window.
  • HR_WINDOW_PROPERTIES_TL — The translation table supplying the language-specific window title, joined with an outer join on userenv('LANG').
  • PLITBLM — An Oracle Forms/PL/SQL built-in table referenced within the package, typically for table-driven manipulation or display logic rather than business data.

Usage Notes

HR_TEMPLATE_WINDOW_INFO is an internal infrastructure package and is not intended for direct invocation by customer code, concurrent programs, or standard public APIs. It is invoked indirectly by the Oracle Forms template framework whenever a form template must render or enumerate its constituent windows—for example, when an EBS form is launched under a configured template, or when the Forms personalization and template engine needs to resolve window geometry and titles. Because it exposes no documented public API contract and has no documented dependents, customizations should avoid calling it directly; the internal structure and global variables may change without notice in patched releases. The SQL logic uses outer joins throughout to tolerate missing translation or property rows, which reflects the defensive design typical of forms-rendering support code in both 12.1.1 and 12.2.2. Where localization is enabled, the conditional join on userenv('LANG') ensures titles appear in the session language when a translation exists, falling back gracefully otherwise.