Search Results per_shared_types_vl




Overview
Explore in AI Chat

Overview

PER_SHARED_TYPES_VL is a validation (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. As its documented description states, the object is "used to support user-interface." In Oracle EBS naming conventions, a "_VL" suffix denotes a view that joins a base (untranslated) entity table with its corresponding translation table ("_TL") and filters the translation rows by the session language using the USERENV('LANG') function. This design enables Oracle Forms, OAF pages, and other UI components to retrieve language-appropriate descriptive text without embedding language-specific logic in the calling code.

In the context of Oracle EBS 12.1.1 and 12.2.2, PER_SHARED_TYPES_VL therefore serves primarily as a presentation-layer access point rather than an analytical reporting object. It exists to centralize multilingual access to shared type definitions used across the HRMS suite, allowing the application tier to resolve names in the user's active language. Because it abstracts the underlying translation join, the view is a dependable interface for any custom code, concurrent program, or integration that must reference shared type data by its localized name.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

  • PER_SHARED_TYPES (aliased SHT) — the transactional base table holding the shared type records, including identifiers, business group, lookup information, and the thirty generic INFORMATIONn columns.
  • PER_SHARED_TYPES_TL (aliased STT) — the translation table supplying the language-dependent SHARED_TYPE_NAME.

The join condition is SHT.SHARED_TYPE_ID = STT.SHARED_TYPE_ID combined with STT.LANGUAGE = USERENV('LANG'). This inner join guarantees that only rows with a translation in the current session language are returned, and only the translated name column (SHARED_TYPE_NAME) is sourced from the TL table. All remaining columns originate from PER_SHARED_TYPES, and the view additionally exposes SHT.ROWID as ROW_ID to provide a row identifier usable by the UI framework. This structure is the standard EBS multilanguage pattern: one physical row in the base table plus N language rows in the TL table project to a single logical row per language.

Key Columns

  • ROW_ID — the physical ROWID of the PER_SHARED_TYPES row, used by Form Builder blocks for row identification.
  • SHARED_TYPE_ID — the primary identifier linking the base and translation records.
  • BUSINESS_GROUP_ID — the business group that owns the shared type, enabling multi-organization filtering.
  • LOOKUP_TYPE and SYSTEM_TYPE_CD — classification values that associate the record with a lookup and a system type code.
  • SHARED_TYPE_NAME — the language-dependent display name retrieved from PER_SHARED_TYPES_TL; the only translated column exposed.
  • INFORMATION1 through INFORMATION30 — thirty generic, flexibly-purposed attribute columns whose meaning depends on the shared type usage.
  • INFORMATION_CATEGORY — categorizes the information stored in the INFORMATIONn columns.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, plus OBJECT_VERSION_NUMBER for optimistic locking and change tracking.

Common Use Cases and Queries

Typical use cases include retrieving localized shared type names for display, populating list-of-values sources, driving concurrent program parameters, and joining to HRMS setup data where a business-readable name is required. The view is well-suited to lookups that must respect the NLS language setting. A representative query retrieving all shared types for a business group, ordered by localized name, is:

SELECT shared_type_id, business_group_id, lookup_type, system_type_cd, shared_type_name FROM apps.per_shared_types_vl WHERE business_group_id = :p_business_group_id ORDER BY shared_type_name;

A targeted lookup by classification is equally common:

SELECT shared_type_id, shared_type_name, information_category FROM apps.per_shared_types_vl WHERE lookup_type = :p_lookup_type;

Because the view enforces a language filter, results automatically reflect the language of the executing session; no additional NLS handling is required in the caller. When performing bulk reporting across all languages, developers should query PER_SHARED_TYPES_TL directly rather than relying on the VL view.