Search Results per_qualification_types_vl




Overview
Explore in AI Chat

Overview

PER_QUALIFICATION_TYPES_VL is a multilingual (ML) view owned by the APPS schema within the Oracle E-Business Suite Human Resources (PER) product family. It exposes qualification type definitions maintained in Oracle HRMS alongside their language-specific translated names. In a multi-language EBS environment, translatable descriptive columns are not stored on the base entity table; they reside in a separate translation table keyed by language. The "_VL" suffix denotes a view that joins the base (non-translated) definition table with its translation table and restricts the translation rows to the session language. This gives consumers a single flattened result set combining language-independent attributes with the translated NAME for the current user's language.

The view is reported as VALID in both ETRM 12.1.1 and 12.2.2, and because it is defined in the APPS schema it is the object normally referenced by forms, concurrent programs, PL/SQL packages, and ad hoc reporting rather than the underlying base and translation tables directly.

Underlying Base Objects

The ETRM metadata documents two referenced objects, both encountered in the APPS schema as synonyms: PER_QUALIFICATION_TYPES and PER_QUALIFICATION_TYPES_TL. The view text joins these on QUALIFICATION_TYPE_ID:

  • PER_QUALIFICATION_TYPES supplies the language-independent attributes: the surrogate key, category classification, rank, the 30 INFORMATIONn flexfield segments, the INFORMATION_CATEGORY context, the DFF ATTRIBUTEn columns, the OBJECT_VERSION_NUMBER, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).
  • PER_QUALIFICATION_TYPES_TL supplies the translated NAME, filtered with the predicate T.LANGUAGE = USERENV('LANG') so that exactly one translation row — that of the session language — is returned per qualification type.

The join is an equality on QUALIFICATION_TYPE_ID, and the view additionally surfaces the ROWID of the base table row as ROW_ID to support row-level operations and Form Builder block association.

Key Columns

  • QUALIFICATION_TYPE_ID — primary key of the qualification type; the join key and the value referenced by foreign keys elsewhere in HRMS.
  • NAME — the translated qualification type name, sourced from the TL table for the session language. This is the primary user-facing descriptor.
  • CATEGORY / INFORMATION_CATEGORY — classification attributes used to group qualification types.
  • RANK — ordering attribute used to sequence qualification types.
  • INFORMATION1 … INFORMATION30 — the descriptive flexfield (DFF) segment columns for the qualification type.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1 … ATTRIBUTE20 — the corresponding DFF context and attribute columns.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework and PL/SQL APIs.
  • ROW_ID — the base table ROWID, exposed for Framework/Forms integration.
  • WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit reporting.

Common Use Cases and Queries

The view is used wherever qualification types must be presented in the user's own language — typically in HRMS lookups, applicant and competency reporting, and integrations that map external qualification codes to EBS qualification type identifiers. Because the view already resolves the language, callers do not need to join the translation table themselves.

A representative query listing all qualification types in the current session language:

SELECT qualification_type_id,
       name,
       category,
       rank
FROM   apps.per_qualification_types_vl
ORDER  BY name;

A bilingual listing that retrieves each qualification type in a specific language (for example US English) can be built by joining the base and translation tables directly, since the view hard-codes USERENV('LANG'); using the view is the correct approach when the reporting session language is the desired one. For validation or integration extracts, filtering on the audit columns or the DFF context is common:

SELECT qualification_type_id,
       name,
       information_category,
       information1
FROM   apps.per_qualification_types_vl
WHERE  attribute_category IS NOT NULL;

In all cases the view delivers a single, de-duplicated row per qualification type, preserving the multilanguage abstraction while keeping query logic simple.