Search Results hr_template_items




Overview
Explore in AI Chat

Overview

The HR_TEMPLATE_ITEMS view is an APPS-owned, VALID database object residing in the PER – Human Resources product module of Oracle E-Business Suite. It is classified as a VIEW and its documented purpose is to present "template item definition and translated properties." In practical terms, the object combines the structural definition of a template item with the language-dependent presentation and behavior attributes attached to that item, so consumers can read a single denormalized row per template item without performing the translation join themselves.

Because the object is a view rather than a table, it is not an update target in the conventional sense; it is intended primarily for reporting, inquiry, and integration extraction. Its most immediate role is to support forms and template personalization logic in Oracle HRMS, where template items control how fields appear, behave, and respond to user input. The view is equally useful to downstream reporting tools and interfaces that must inspect the configuration of a template without navigating the base entities. The presence of the INSERT_ALLOWED column, the attribute most closely associated with the original search, reflects the view's role in surfacing item-level behavioral controls alongside the core identity of the template item.

Underlying Base Objects

The ETRM 12.2.2 metadata documents two referenced base objects: HR_ITEM_PROPERTIES_VL (a VIEW) and HR_TEMPLATE_ITEMS_B (a SYNONYM). The view text confirms an outer join between them, expressed as P.TEMPLATE_ITEM_ID (+) = I.TEMPLATE_ITEM_ID. This means every row from HR_TEMPLATE_ITEMS_B is retained, and matching translated property rows are attached where they exist.

The driving table is HR_TEMPLATE_ITEMS_B, aliased I, which supplies the item identity and audit columns: ROWID, TEMPLATE_ITEM_ID, OBJECT_VERSION_NUMBER, FORM_TEMPLATE_ID, FORM_ITEM_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE. The joined view HR_ITEM_PROPERTIES_VL, aliased P, is the translated (_VL) presentation of item properties, supplying ALIGNMENT, BEVEL, DEFAULT_VALUE, ENABLED, INSERT_ALLOWED, UPDATE_ALLOWED, QUERY_ALLOWED, REQUIRED, VISIBLE, and the extensive PROMPT_*, VALIDATION_*, INFORMATION_*, and positional attributes. Because the properties side is an outer-joined _VL object, template items without a property row remain visible with null property values.

Key Columns

  • ROW_ID — the ROWID of the underlying HR_TEMPLATE_ITEMS_B row; useful for direct table access and row identification.
  • TEMPLATE_ITEM_ID — primary identifier for the template item and the join key to the translated properties.
  • OBJECT_VERSION_NUMBER — optimistic locking version, useful for detecting stale reads in integrations.
  • FORM_TEMPLATE_ID / FORM_ITEM_ID — the form template and form item to which the template item belongs.
  • INSERT_ALLOWED, UPDATE_ALLOWED, QUERY_ALLOWED, REQUIRED, ENABLED, VISIBLE — the behavioral controls governing whether a user may insert, update, or query the item and whether it is required, enabled, and visible.
  • PROMPT_TEXT, LABEL, TOOLTIP_TEXT, INFORMATION_PROMPT — translated display text presented to the user.
  • DEFAULT_VALUE, FORMAT_MASK, VALIDATION_FORMULA_ID, VALIDATION_PARAMETER_ITEM_ID1–5 — defaulting, formatting, and validation configuration.
  • ALIGNMENT, BEVEL, HEIGHT, WIDTH, X_POSITION, Y_POSITION, PROMPT_* — layout and prompt positioning attributes.
  • NEXT_NAVIGATION_ITEM_ID / PREVIOUS_NAVIGATION_ITEM_ID — navigation chaining between items.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

A frequent requirement is to inspect which items permit insertion within a given form template, which maps directly to the INSERT_ALLOWED attribute carried from the properties side of the join.

SELECT template_item_id,
       form_template_id,
       form_item_id,
       insert_allowed,
       update_allowed,
       query_allowed,
       required,
       enabled,
       visible
FROM   apps.hr_template_items
WHERE  form_template_id = :p_template_id
AND    NVL(insert_allowed, 'N') = 'Y'
ORDER  BY template_item_id;

Another common scenario is auditing navigation chaining and layout for reporting or documentation of a template's design:

SELECT template_item_id,
       prompt_text,
       label,
       x_position,
       y_position,
       next_navigation_item_id,
       previous_navigation_item_id
FROM   apps.hr_template_items
WHERE  form_template_id = :p_template_id
ORDER  BY x_position, y_position;

Integration and reconciliation use cases typically extract item identity and audit data to compare against staging or legacy configurations:

SELECT template_item_id,
       object_version_number,
       last_update_date,
       last_updated_by
FROM   apps.hr_template_items
WHERE  last_update_date >= :p_since_date;

Because the view is defined over a _VL translation view, querying it in a multilingual environment returns the property text appropriate to the session language, making it suitable for user-facing reports. Consumers should nonetheless remember the outer join: where no property row exists, INSERT_ALLOWED and its siblings are null, and NVL handling is advisable when testing behavioral flags.