Search Results hr_template_items_b_s




Overview
Explore in AI Chat

Overview

The APPS.HR_TEMPLATE_ITEMS_PKG package body is a server-side PL/SQL component in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2) that encapsulates the DML and locking logic for the HR Template Items entity. In Oracle Human Resources, template items represent the individual, configurable elements that make up a form template — the reusable definitions that control which fields, regions, or attributes appear on an HR form and how they behave. Rather than permitting direct manipulation of the underlying base tables, the application routes all maintenance of template item rows through this package, which provides a controlled, consistent interface for insert, update, delete, query-for-update, and bulk-load operations. The package thus enforces data integrity, centralizes WHO-column (audit) handling, and shields callers from the physical schema of the HR template items tables. It has no known dependents among other database objects, indicating it is a leaf-level utility invoked directly by forms, concurrent processes, or migration code rather than being wrapped by higher-level APIs.

Key Procedures and Functions

The package exposes six documented program units:

  • OWNER_TO_WHO — A helper that maps the current session context into the standard WHO audit columns (creation/update user, date, and login), ensuring every row carries consistent audit information.
  • INSERT_ROW — Inserts a new template item record, applying defaulting and WHO-column population.
  • LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) on a specified template item so subsequent modifications occur under concurrency control.
  • UPDATE_ROW — Applies changes to an existing template item row and refreshes the WHO update columns.
  • DELETE_ROW — Removes a template item record from the entity.
  • LOAD_ROW — Performs a bulk or seed-style load operation, used to populate template item rows, typically in setup or data-migration scenarios.

No parameter lists are documented, so signatures should be confirmed against the live package specification before custom invocation.

Tables Accessed

The package reads and writes the following objects (via APPS synonyms):

  • HR_TEMPLATE_ITEMS_B — The base table holding the template item definitions; the primary DML target.
  • HR_TEMPLATE_ITEMS_B_S — The sequence used to generate primary keys for new template item rows; this object is the direct match for the searched name "hr_template_items_b_s".
  • HR_FORM_TEMPLATES_B — The parent form template to which items belong, used to validate the template context.
  • HR_FORM_ITEMS_B — The form item definitions referenced by template items.
  • FND_FORM and FND_APPLICATION — Oracle Application Object Library metadata used to resolve form and application context.
  • FND_MESSAGE — Supplies translatable, standardized error and warning messages.
  • DUAL — Used for scalar evaluations and lookups.

Messages also draw on APP_EXCEPTION and PER_RIC_PKG for error raising and HR utility support.

Usage Notes

Because the package is not referenced by any other database object, it is invoked directly — most commonly by the HR Template Items maintenance form, by concurrent programs that seed or load form templates during implementation, and by custom PL/SQL that needs to create or modify template items programmatically. Callers should invoke LOCK_ROW before UPDATE_ROW or DELETE_ROW to preserve concurrency integrity, and prefer these routines over direct DML on HR_TEMPLATE_ITEMS_B so that WHO columns and validation remain consistent. Custom code should resolve the exact procedure signatures from the package specification shipped with the target patch level (12.1.1 or 12.2.2), since the ETRM metadata does not enumerate parameters.