Search Results hr_form_templates_vl




Overview
Explore in AI Chat

Overview

HR_FORM_TEMPLATES_VL is a valid, translated (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. It exposes the user-facing, language-sensitive attributes of HR form templates — the configuration records that associate an EBS form with a named template used to control how that form is rendered or defaulted at runtime. Because it is a VL view, it joins a language-independent base table (HR_FORM_TEMPLATES_B) with a translation table (HR_FORM_TEMPLATES_TL), filtering translations to the session's language so that each row presents the correct translated template name and description.

In reporting and integration scenarios, the view provides a single, normalized source for form template metadata without requiring callers to manually join the _B and _TL tables or to hard-code language predicates. It is available in Oracle EBS 12.1.1 and 12.2.2 and remains VALID in the ETRM 12.2.2 repository.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the ETRM 12.2.2 metadata:

  • HR_FORM_TEMPLATES_B — the language-independent base table holding the primary key, descriptive, and descriptive flexfield columns.
  • HR_FORM_TEMPLATES_TL — the translation table holding language-specific columns (USER_TEMPLATE_NAME and DESCRIPTION).

The two are joined on FORM_TEMPLATE_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'), which restricts the translation row to the current session language. This is the standard Oracle VL pattern: the "_VL" view is not itself a stored, translatable table but a read-only projection that resolves translations dynamically.

Key Columns

  • ROW_ID — the ROWID of the underlying _B row, used for identifying the physical row in update-through-view operations.
  • FORM_TEMPLATE_ID — the unique identifier (primary key) of the form template.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Forms/ADF layer to detect concurrent updates.
  • APPLICATION_ID — the application that owns the associated form.
  • FORM_ID — the identifier of the form to which the template applies.
  • TEMPLATE_NAME — the internal, language-independent template name (from _B).
  • USER_TEMPLATE_NAME — the translated, user-visible template name (from _TL).
  • DESCRIPTION — the translated description of the template (from _TL).
  • ENABLED_FLAG — indicates whether the template is active.
  • LEGISLATION_CODE — the legislation (country) context in which the template applies.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield (DFF) context and segment columns.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO (audit) columns.

Common Use Cases and Queries

The view is typically queried when administrators or developers need to enumerate the form templates configured for a given form or application, or when building reports or interfaces that must display the translated template name alongside internal identifiers. It is also useful for validation queries before inserting or updating template definitions.

A representative query lists all enabled templates for a specific form, using the translated name for display and the internal name for reference:

  • SELECT form_template_id, template_name, user_template_name, description, enabled_flag FROM hr_form_templates_vl WHERE form_id = :p_form_id AND enabled_flag = 'Y'
  • SELECT form_template_id, user_template_name FROM hr_form_templates_vl WHERE application_id = :p_app_id AND legislation_code = :p_leg ORDER BY user_template_name
  • SELECT COUNT(*) FROM hr_form_templates_vl WHERE form_template_id = :p_id — validating existence prior to update.

Because the LANGUAGE predicate is bound to USERENV('LANG'), queries must run in a session whose language matches the desired translation; otherwise a row may be omitted if no translation exists for that language. Callers requiring all translations regardless of session language should query HR_FORM_TEMPLATES_TL directly. Consistent with Oracle VL semantics, the view is intended for retrieval and display; DML against translations should be directed to the _TL table.