Search Results language_desc

Overview

IGSFV_PERSON_LANGUAGE is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGSFV_PERSON_LANGUAGE. It exposes the language capabilities recorded against a person — the languages that an individual speaks, reads, and writes — along with the person's identifying attributes and the qualitative or user-defined proficiency levels attached to each language. Because it is implemented as a BI System view rather than a transactional table, it is intended primarily for reporting, extraction, and analytical consumption, presenting already-joined and human-readable data rather than raw foreign keys.

The view's status is VALID in both 12.1.1 and 12.2.2. Its purpose is to flatten the relationship between a person, the languages associated with that person, and the descriptive names of those languages, so that consumers do not need to resolve FND_LANGUAGES lookups themselves. The LANGUAGE_DESC column, which is the term most commonly searched against this object, carries the standard language name (for example, Spanish, Mandarin, or American English) and is documented as a foreign key to the FND_LANGUAGES table.

Underlying Base Objects

The documented ETRM metadata for this view does not list any explicit referenced base objects; the "Referenced base objects" entry is empty and the object catalogue describes it only as a BI System view for "language that person speaks, read and write." In practice the view is constructed within the IGS (Student Systems / Person) product family and resolves against person-language assignment data held in the person foundation tables, joined to FND_LANGUAGES to obtain the descriptive language name.

Two naming conventions in the column list confirm the join strategy. LANGUAGE_NAME and LANGUAGE_DESC are both documented as foreign keys to FND_LANGUAGES, meaning both surface the standard language name; LANGUAGE_DESC is the shorter (30-character) descriptive variant. The person-side attributes — PERSON_IDENTIFIER, PERSON_NUMBER, and PERSON_NAME — derive from the person record, while LANGUAGE_USE_REFERENCE_ID is the unique identifier of the individual language-use record, making it the effective primary key at row level. Because the documented base-object list is absent, integrators should treat the view as the supported interface and avoid assuming a fixed physical table structure beneath it.

Key Columns

• LANGUAGE_USE_REFERENCE_ID (NUMBER, 15) — Unique identifier of the language-use reference; the row-level key.
• PERSON_IDENTIFIER (NUMBER, 15) — Internal person identifier used to join to other person-based views and tables.
• PERSON_NUMBER (VARCHAR2, 30) — The unique, user-facing identification number for the person.
• PERSON_NAME (VARCHAR2, 360) — The person's name.
• LANGUAGE_NAME — Standard name of a language; foreign key to FND_LANGUAGES.
• LANGUAGE_DESC (VARCHAR2, 30) — The standard language name (e.g., Spanish, Mandarin, American English); foreign key to FND_LANGUAGES. This is the column most frequently targeted by ad hoc queries and reports.
• _LA:NATIVE_LANGUAGE (CHAR, 56) — Indicates whether the language is the person's declared native language (Y/N).
• PRIMARY_LANG_INDICATOR (CHAR, 67) — Indicates whether the language is the person's primary day-to-day language (Y/N).
• READS_LEVEL, SPEAKS_LEVEL, WRITES_LEVEL (VARCHAR2, 30 each) — User-defined level number or name describing the person's ability to read, speak, and write the language.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN provide standard audit information.

Common Use Cases and Queries

Typical uses include producing person language profiles for admissions, HR, and student-record reporting; identifying native or primary language speakers for communications and translation planning; and exporting multilingual capability data into downstream BI or integration targets. Because the view already supplies the descriptive language name, reporting queries against LANGUAGE_DESC avoid an explicit join to FND_LANGUAGES.

• List all languages for a person:

  SELECT person_number, person_name, language_desc,
         _LA:NATIVE_LANGUAGE, primary_lang_indicator
  FROM   apps.igsfv_person_language
  WHERE  person_number = :p_person_number;

• Identify native-language speakers of a given language:

  SELECT person_number, person_name, language_desc
  FROM   apps.igsfv_person_language
  WHERE  language_desc = :p_language
  AND    _LA:NATIVE_LANGUAGE = 'Y';

• Report proficiency levels by language:

  SELECT person_number, person_name, language_desc,
         reads_level, speaks_level, writes_level
  FROM   apps.igsfv_person_language
  ORDER  BY person_name, language_desc;

Note that the special column name _LA:NATIVE_LANGUAGE must be quoted or aliased when referenced in SQL, and that standard EBS security applies — query the view under an APPS-responsibility context with the appropriate MO: Operating Unit and security profile.