Results for “speaks_level”

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

Overview

IGS_PE_LANGUAGES_V is a view historically shipped with the Oracle IGS (Student System) product family, which is now classified as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents person-level language information — the languages an individual speaks, reads, writes, and comprehends, along with proficiency levels and native/primary language flags — in a denormalized, report-ready form. Its role is to join the transactional person-language records held in the Trading Community Architecture (TCA) tables to the descriptive lookup values that give those records human-readable meanings, and to the language code descriptions maintained in the FND language views.

The ETRM metadata records the object as not implemented in the reference database, meaning it is a legacy definition retained for documentation purposes rather than an active database object in a current 12.2.2 instance. This is consistent with the obsolescence of the IGS product line, whose functionality was progressively superseded by Oracle Student System / Campus Solutions and by native TCA person-profile features.

Underlying Base Objects

Although the ETRM metadata lists no formally documented base objects, the view text itself reveals the exact FROM and WHERE clauses. The view is defined over four underlying objects:

• HZ_PERSON_LANGUAGE (aliased L) — the TCA table holding one row per language associated with a party, including proficiency levels, native language flag, and standard WHO columns.
• FND_LANGUAGES_VL (aliased FL) — the multilingual language-code view, joined on L.LANGUAGE_NAME = FL.LANGUAGE_CODE to supply the language description.
• FND_LOOKUP_VALUES (aliased L1, L2, L3, L4) — four outer-joined instances of the lookup table, each resolving one proficiency level (spoken comprehension, speaking, writing, reading) against the lookup type HZ_LANGUAGE_PROFICIENCY.

All four lookup joins are outer joins (indicated by the (+) operator), constrained to VIEW_APPLICATION_ID = 222 and SECURITY_GROUP_ID = 0, and filter on USERENV('LANG') so that lookup meanings are returned in the session language.

Key Columns

• ROW_ID — the ROWID of the base HZ_PERSON_LANGUAGE row, exposed as a unique identifier.
• PARTY_ID — the party (person) to whom the language record belongs.
• LANGUAGE_NAME / DESCRIPTION — the language code and its resolved description from FND_LANGUAGES_VL.
• NATIVE_LANGUAGE and PRIMARY_LANGUAGE_INDICATOR — flags identifying the person's native and primary languages.
• READS_LEVEL, SPEAKS_LEVEL, WRITES_LEVEL, UNDERSTANDS_LEVEL — proficiency codes; SPOKEN_COMPREHENSION_LEVEL is aliased to UNDERSTANDS_LEVEL.
• UNDERSTANDS_LEVEL_DESC, SPEAKS_LEVEL_DESC, WRITES_LEVEL_DESC, READS_LEVEL_DESC — the descriptive meanings resolved from FND_LOOKUP_VALUES.
• STATUS, OBJECT_VERSION_NUMBER — record status and optimistic-locking version.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard WHO/audit columns. WH_UPDATE_DATE is returned as a NULL placeholder.

Common Use Cases and Queries

The view is typically used for reporting on the linguistic profile of a person, for populating registration or admissions screens, and for integrating language data into downstream systems. A representative query follows:

SELECT party_id,
       language_name,
       description,
       native_language,
       primary_language_indicator,
       understands_level_desc,
       speaks_level_desc,
       reads_level_desc,
       writes_level_desc
FROM   igs_pe_languages_v
WHERE  party_id = :p_party_id
ORDER  BY primary_language_indicator DESC, language_name;

Because the view is documented as obsolete and not implemented, developers migrating to 12.2.2 should query HZ_PERSON_LANGUAGE directly, joining FND_LANGUAGES_VL and FND_LOOKUP_VALUES as the view does, since the underlying TCA structures remain supported even though the IGS wrapper view does not.