Results for “home_language_cd”

14 results




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

Overview

IGS_PE_LANGUAGE_CD_V is a validation view belonging to the IGS – Student System (Obsolete) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to supply the valid values for the home_language_cd attribute of PERSON_STATISTICS, the descriptive flexfield-style entity that captures personal and demographic statistics for learners, applicants, and related parties. In the ETRM metadata for 12.2.2, the object is described as "Valid values for person_statistics home_language_codes" and is explicitly flagged as Not implemented in this database, indicating that the view exists as documented metadata but is not deployed in the current instance.

Functionally, the view acts as a superset language-code lookup. It merges the institution-maintained language code table with generic Oracle lookup values, producing a single unified list suitable for validation lists of values (LOVs), concurrent program parameters, and integration payloads that must resolve a home language against approved codes. Because the underlying module is obsolete, the view should be treated primarily as a reference object for legacy reporting and migration analysis rather than a target for new development.

Underlying Base Objects

The view text is a UNION ALL of two sources. The first branch selects from IGS_PE_LANGUAGE_CD, the IGS language code table, exposing LANGUAGE_CD, DESCRIPTION, CLOSED_IND, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). These rows are hard-coded with the literal source value 'LANGUAGE CODE'.

The second branch selects from IGS_LOOKUP_VALUES where LOOKUP_TYPE = 'PE_LANGUAGES' and ENABLED_FLAG = 'Y', mapping LOOKUP_CODE to the code, MEANING to the description, and supplying literal defaults: 'N' for the closed indicator, an empty source string, and NULLs for all audit columns. Consequently, lookup-sourced rows carry no creation or update tracking, while table-sourced rows carry a meaningful source label. The ETRM record documents no referenced base objects, so the view's dependency chain is understood solely from its SQL text.

Key Columns

  • HOME_LANGUAGE_CD — Although the documented column list begins with HOME_LANGUAGE_CD, the projected select lists LANGUAGE_CD / LOOKUP_CODE positionally into the first column, which the person-statistics validation treats as the home language code. This is the value stored in PERSON_STATISTICS.HOME_LANGUAGE_CD.
  • DESCRIPTION — The human-readable language name, drawn from LANGUAGE_CD.DESCRIPTION or LOOKUP_VALUES.MEANING.
  • CLOSED_IND — Indicates whether the language code has been closed to new use; lookup-sourced rows are always 'N'.
  • SOURCE — Distinguishes rows originating from the language code table ('LANGUAGE CODE') from lookup-derived rows (empty).
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide WHO tracking for table rows and NULL for lookup rows.

Common Use Cases and Queries

Typical usage includes validating or translating the stored home language code, populating LOVs for person-statistics entry forms, and reconciling legacy language data during migration. A representative query listing only active, non-closed languages is:

SELECT home_language_cd, description, source
FROM igs_pe_language_cd_v
WHERE NVL(closed_ind,'N') = 'N'
ORDER BY description;

To join stored statistics to their language descriptions:

SELECT ps.person_id, ps.home_language_cd, v.description
FROM person_statistics ps, igs_pe_language_cd_v v
WHERE ps.home_language_cd = v.home_language_cd (+);

Because the metadata states the view is not implemented in the 12.2.2 database, these queries should be confirmed against the target instance before use. Where the view is absent, equivalent results can be assembled directly from IGS_PE_LANGUAGE_CD and IGS_LOOKUP_VALUES using the same UNION ALL logic.