Search Results igsfv_person_language

Overview

IGSFV_PERSON_LANGUAGE is a read-only Oracle EBS view owned by the APPS schema and delivered as part of the IGS – Student System product family. It exposes the language proficiencies recorded against a party — specifically the languages a person speaks, reads, and writes — joined to core party identification data and to the Oracle National Language Support (NLS) language definition. The view name and its "FV" convention indicate a formatted, presentation-oriented view intended for inquiry, reporting, and integration rather than for direct transactional maintenance.

In the 12.1.1 and 12.2.2 releases the object carries a VALID status in ETRM, confirming it is a supported, documented database object. Because the underlying data originates in the Oracle Trading Community Architecture (TCA) person language model, the view is the practical bridge between TCA party records and the IGS Student System's language requirements. Users who search on hz_person_language are typically seeking the base table; IGSFV_PERSON_LANGUAGE is the reporting layer that surfaces the same information with descriptions and readable reference values already resolved.

Underlying Base Objects

The view text in the ETRM documentation defines IGSFV_PERSON_LANGUAGE over three base objects:

• HZ_PERSON_LANGUAGE (alias HPL) — the TCA table holding language-use rows for a party, including the language code, usage levels, and native/primary indicators. This is the primary base table and the object referenced by the common search term hz_person_language.
• HZ_PARTIES (alias HP) — the TCA party master, joined on PARTY_ID to supply party number and party name.
• FND_LANGUAGES (alias FL) — the NLS language table, joined on LANGUAGE_NAME = LANGUAGE_CODE to resolve the NLS language identifier.

The join is a straightforward equi-join on PARTY_ID and LANGUAGE_CODE, and the view is declared WITH READ ONLY, so it cannot be used for DML. ETRM lists no additional referenced base objects beyond these three.

Key Columns

• LANGUAGE_USE_REFERENCE_ID — primary key of the underlying HZ_PERSON_LANGUAGE row.
• PARTY_ID / PERSON_IDENTIFIER — the party identifier; the documented column list exposes PERSON_IDENTIFIER while the view text selects PARTY_ID.
• PERSON_NUMBER, PERSON_NAME — party number and formatted party name from HZ_PARTIES.
• LANGUAGE_NAME — the language code recorded for the person.
• NATIVE_LANGUAGE and PRIMARY_LANG_INDICATOR — Yes/No flags decoded through IGS_LOOKUP_VALUES, indicating whether the language is native and whether it is the person's primary language.
• READS_LEVEL, SPEAKS_LEVEL, WRITES_LEVEL — proficiency levels for reading, speaking, and writing.
• LANGUAGE_DESC (NLS_LANGUAGE) — the NLS language description from FND_LANGUAGES.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is used in student and person reporting where language proficiency must be presented with readable descriptions, and in integrations that must export party language data without re-implementing the TCA-to-NLS joins.

To list all languages for a party:

SELECT person_number, person_name, language_name, language_desc,
       reads_level, speaks_level, writes_level
FROM   apps.igsfv_person_language
WHERE  party_id = :p_party_id;

To find persons whose primary language is a given code:

SELECT person_number, person_name, language_desc
FROM   apps.igsfv_person_language
WHERE  primary_lang_indicator = 'Y'
AND    language_name = 'ES';

Because the view is read-only and pre-joins party and NLS data, it is preferable to querying HZ_PERSON_LANGUAGE directly when descriptive output is required.