Results for “per_qualifications_vl”

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

Overview

PER_QUALIFICATIONS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and exposes qualification records maintained against a person, including academic achievements, professional certifications, licences, and professional body memberships. Its design follows the standard Oracle EBS MLS pattern: translatable descriptive attributes are stored in a language-specific "_TL" table, while transactional and foreign-key attributes remain in the base entity table. The "_VL" suffix denotes that the view returns only the rows matching the session language, determined by USERENV('LANG'). This makes the view the primary read interface for qualification data in forms, concurrent programs, BI Publisher reports, and interface extracts, since it presents the correct translated title and associated descriptive text without requiring application code to join the translation table explicitly.

Underlying Base Objects

The entity-relationship documentation for 12.2.2 records two referenced base objects, both accessed through APPS synonyms: PER_QUALIFICATIONS and PER_QUALIFICATIONS_TL. The view text joins these aliased as B and T respectively on QUALIFICATION_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'). All mandatory, non-translatable columns — identifiers, dates, amounts, flexfield attributes, and descriptive flexfield segments — are drawn from PER_QUALIFICATIONS. Translatable text columns such as TITLE, GRADE_ATTAINED, REIMBURSEMENT_ARRANGEMENTS, TRAINING_COMPLETED_UNITS, LICENSE_RESTRICTIONS, AWARDING_BODY, GROUP_RANKING, MEMBERSHIP_CATEGORY, and PROFESSIONAL_BODY_NAME are sourced from PER_QUALIFICATIONS_TL. The join is a equijoin on QUALIFICATION_ID and is therefore expected to return one row per qualification per installed language, filtered to one language at runtime.

Key Columns

The view exposes the following significant columns, among others in the full select list:

• ROW_ID — the ROWID of the base PER_QUALIFICATIONS row, used by the Oracle Forms "ROWID" block construct for updateable queries.
• QUALIFICATION_ID — primary key of the qualification record and the join key to the translation table.
• BUSINESS_GROUP_ID — the HR business group that owns the record; critical for multi-organization security.
• PERSON_ID — the person to whom the qualification belongs; join key to PER_PEOPLE_F and related person views.
• TITLE — translatable title of the qualification, award, or membership.
• STATUS — current status of the qualification record.
• AWARDED_DATE, START_DATE, END_DATE, EXPIRY_DATE, PROJECTED_COMPLETION_DATE — lifecycle dates used for validity and renewal reporting.
• MEMBERSHIP_NUMBER and MEMBERSHIP_CATEGORY — professional body membership reference and its translatable category, which is the column users typically search when looking for membership_category.
• PROFESSIONAL_BODY_NAME — name of the awarding or professional institution.
• QUALIFICATION_TYPE_ID and ATTENDANCE_ID — foreign keys to qualification type and the source training attendance.
• ATTRIBUTE1–ATTRIBUTE20 and QUA_INFORMATION1–QUA_INFORMATION20 — descriptive flexfield attribute and global segment columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include professional membership registers, certification expiry tracking, training-to-qualification reconciliation, and HR data extracts. The following query lists memberships by category for a business group:

SELECT v.person_id, v.title, v.professional_body_name, v.membership_number, v.membership_category, v.expiry_date FROM apps.per_qualifications_vl v WHERE v.business_group_id = :p_business_group_id AND v.membership_category IS NOT NULL ORDER BY v.professional_body_name, v.membership_number;

Activities due to expire within a period can be selected with the same view filtering on EXPIRY_DATE or END_DATE. Because the view is defined with a USERENV predicate, it should always be queried rather than the _TL table directly, and reporting tools must ensure the session language is set so that translations resolve as expected.