Search Results hr_template_item_tab_pages_s

Overview

APPS.HR_TEMPLATE_ITEM_TAB_PAGES_PKG is a metadata management package in the Oracle E-Business Suite Human Resources (HR) application. Its name reflects its domain: the intersection of form template items and the tab pages assigned to them within the Oracle Forms-based template architecture used by HR. In Oracle EBS, HR forms are rendered through a metadata-driven framework in which form templates, windows, canvases, items, tab pages, and their form-level counterparts are defined declaratively. The HR_TEMPLATE_ITEM_TAB_PAGES table, and its shadow/seed table HR_TEMPLATE_ITEM_TAB_PAGES_S, store the association between a template item and the tab pages that apply to that item.

This package body encapsulates the standard Oracle EBS row-handling API pattern — often referred to as a "table handler" package — that provides a controlled, consistent interface for creating, maintaining, and loading rows in the HR_TEMPLATE_ITEM_TAB_PAGES entity. Rather than allowing direct DML against the underlying table, the package exposes a small, well-defined set of entry points that enforce concurrency control, attribute defaulting, and who-column (audit) population. The presence of a LOAD_ROW procedure indicates the package participates in Oracle's seed data and data-migration infrastructure, allowing template definitions to be shipped and loaded consistently across environments and releases.

Key Procedures and Functions

The package body documents six procedures, each serving a specific role in the row management lifecycle:

• OWNER_TO_WHO — Transfers ownership-related identifiers into the standard WHODATUM audit columns, translating the entity owner information into the WHO_* fields maintained on HR tables.
• INSERT_ROW — Inserts a new row into HR_TEMPLATE_ITEM_TAB_PAGES, applying default value logic and populating mandatory audit columns before the physical insert.
• LOCK_ROW — Provides explicit pessimistic concurrency control by locking an existing row, typically used before an update or delete to guarantee data integrity against concurrent sessions.
• UPDATE_ROW — Modifies an existing HR_TEMPLATE_ITEM_TAB_PAGES record, refreshing the WHO_WHO columns and honouring the lock acquired by the caller.
• DELETE_ROW — Removes a row from the entity table after verifying that the operation is permitted and after the row has been locked.
• LOAD_ROW — Performs an idempotent "upsert" style load, checking for an existing record and either inserting or updating as required. This is the procedure used by seed-data loaders and upgrade utilities.

Parameter lists are not reproduced here; callers should reference the package specification for exact argument signatures.

Tables Accessed

The package primarily reads and writes HR_TEMPLATE_ITEM_TAB_PAGES, the base table holding item-to-tab-page associations, and consults HR_TEMPLATE_ITEM_TAB_PAGES_S for seed and definition metadata. It references sibling template tables — HR_TEMPLATE_ITEMS_B, HR_TEMPLATE_CANVASES_B, HR_TEMPLATE_TAB_PAGES_B, and HR_TEMPLATE_WINDOWS_B — to validate and resolve the template structure being configured. Parallel HR_FORM_* tables (HR_FORM_CANVASES_B, HR_FORM_ITEMS_B, HR_FORM_TAB_PAGES_B, HR_FORM_TEMPLATES_B, and HR_FORM_WINDOWS_B) are accessed to reconcile runtime form definitions with template definitions. FND_APPLICATION and FND_FORM supply application and form registration context, while FND_MESSAGE and APP_EXCEPTION provide message text and error-raising services. DUAL and STANDARD are used for trivial PL/SQL constructs, and SYS.STANDARD underpins standard PL/SQL functionality.

Usage Notes

This package is a low-level table handler and is not normally invoked directly by end users or application forms components. It is called by higher-level template and form-definition maintenance routines, by the Oracle Forms-based template designer when item tab-page associations are saved, and by concurrent programs or DataLoad/seed loaders that populate the template metadata during installation, patching, or localization. Customizations that manage HR template metadata should prefer calling INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOAD_ROW rather than issuing direct DML, so that concurrency and audit semantics are preserved. Because the package is not referenced by any other database object, it is effectively a leaf-level utility consumed only by external callers and internal seed infrastructure.