Results for “hr_item_properties_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_ITEM_PROPERTIES_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, defined within the PER — Human Resources product family. It exposes the presentation and behavioral properties of individual form items used by Oracle EBS self-service and HRMS form-based functionality, including attributes such as alignment, bevel, enabled state, prompt text, default value, and the tooltip_text attribute that commonly drives user-facing guidance on a form field. The view serves as the official readable interface over the item property definitions that the HR framework uses to dynamically render and control form items at runtime.

Because the "_VL" suffix denotes a translated view, HR_ITEM_PROPERTIES_VL returns language-appropriate text for translatable columns while filtering to the session's current language. This makes it the correct object for reporting and integration purposes when display text must be presented in the user's language, and it isolates consumers from the underlying base/translation table split. In Oracle EBS 12.1.1 and 12.2.2, the view is documented as VALID and is registered in ETRM with the base synonyms HR_ITEM_PROPERTIES_B and HR_ITEM_PROPERTIES_TL as its referenced objects.

Underlying Base Objects

The view is defined over two synonyms that resolve to the underlying HR item properties tables:

• HR_ITEM_PROPERTIES_B — the base table holding non-translatable, functional attributes of an item property (geometry, behavior flags, formula references, navigation links, and the WHO columns).
• HR_ITEM_PROPERTIES_TL — the translation table holding language-dependent attributes such as TOOLTIP_TEXT, LABEL, PROMPT_TEXT, DEFAULT_VALUE, and INFORMATION_PROMPT.

The two objects are joined on ITEM_PROPERTY_ID, with the translation row restricted by T.LANGUAGE = USERENV('LANG') so that only the row matching the current session language is returned. This join pattern is the standard EBS VL implementation and means that for a given item property exactly one combined row is exposed per active language.

Key Columns

The view projects identity, layout, behavioral, and translated descriptive columns. Significant columns include:

• ITEM_PROPERTY_ID — the unique key of the item property; joined across both base objects.
• FORM_ITEM_ID / TEMPLATE_ITEM_ID / TEMPLATE_ITEM_CONTEXT_ID — identify the form item and template context to which the property applies.
• TOOLTIP_TEXT — the translated tooltip associated with the item, sourced from HR_ITEM_PROPERTIES_TL; the attribute most often queried by users searching for this view.
• LABEL, PROMPT_TEXT, INFORMATION_PROMPT, DEFAULT_VALUE — other translated text attributes from the TL table.
• ENABLED, VISIBLE, REQUIRED, INSERT_ALLOWED, UPDATE_ALLOWED, QUERY_ALLOWED — functional control flags from the B table.
• ALIGNMENT, BEVEL, HEIGHT, WIDTH, X_POSITION, Y_POSITION, PROMPT_* columns — layout and presentation geometry.
• VALIDATION_FORMULA_ID, INFORMATION_FORMULA_ID and their numbered INFORMATION_PARAMETER_ITEM_IDn / VALIDATION_PARAMETER_ITEM_IDn columns — formula and parameter bindings.
• NEXT_NAVIGATION_ITEM_ID, PREVIOUS_NAVIGATION_ITEM_ID — navigation sequencing.
• ROW_ID and WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical use cases include retrieving the localized prompt, label, and tooltip text for form items, auditing which items are enabled or required, and inspecting layout geometry for troubleshooting form rendering issues. A representative query returning tooltip text for a given form item is:

• SELECT item_property_id, form_item_id, label, prompt_text, tooltip_text
  FROM apps.hr_item_properties_vl
 WHERE form_item_id = :p_form_item_id;
• SELECT form_item_id, label, tooltip_text, enabled, visible, required
  FROM apps.hr_item_properties_vl
 WHERE tooltip_text IS NOT NULL
 ORDER BY form_item_id;

Because the view already applies the USERENV('LANG') filter, queries automatically return text in the session language without an additional language predicate. Consumers should treat the view as read-only and rely on it rather than querying the B and TL tables directly.