Search Results native_language




Overview
Explore in AI Chat

Overview

AMS_PERSON_LANG_V is a Marketing (AMS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the languages that a person speaks, reads, or writes, drawing from the Oracle Trading Community Architecture (TCA) model that underpins party and contact data across EBS. The view is documented as VALID and serves as a reporting and integration layer over the person language data maintained in TCA.

Unlike the base table, the view applies a restrictive filter. It returns only records where the primary language indicator is set to 'Y', the related party has an active status of 'A', and the party type is 'PERSON'. The result is a focused list of each active person's designated primary language, making the view well suited to language-based segmentation, correspondence, and marketing targeting rather than exhaustive language proficiency reporting.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms:

  • HZ_PERSON_LANGUAGE — the TCA table holding language usage records for persons, including proficiency levels and the primary language flag.
  • HZ_PARTIES — the TCA master party table providing party type and status for filtering.

The view joins these on PARTY_ID (HPL.PARTY_ID = HP.PARTY_ID) and applies the filters PRIMARY_LANGUAGE_INDICATOR = 'Y', HP.STATUS = 'A', and HP.PARTY_TYPE = 'PERSON'. Because the join is restricted to the primary language only, the view returns at most one row per qualifying person under normal data conditions, effectively presenting a single preferred language per active person.

Key Columns

  • LANGUAGE_USE_REFERENCE_ID — unique identifier for the language usage record.
  • PARTY_ID — the TCA party identifier linking back to HZ_PARTIES and other party-related objects.
  • LANGUAGE_NAME — the name of the language the person uses.
  • NATIVE_LANGUAGE — the person's native language.
  • PRIMARY_LANGUAGE_INDICATOR — flag denoting the primary language; always 'Y' in this view.
  • READS_LEVEL — proficiency level for reading.
  • SPEAKS_LEVEL — proficiency level for speaking.
  • WRITES_LEVEL — proficiency level for writing.

Together these columns provide the party identifier, the language identity, and the proficiency profile for reading, speaking, and writing.

Common Use Cases and Queries

Because the view is filtered to primary languages of active persons, it is commonly used to drive language-appropriate communications and to build audience segments in marketing and service applications. Typical scenarios include selecting contacts for translated campaigns, defaulting correspondence language, and validating that a person has a designated primary language.

A representative query retrieving the primary language for a specific party:

  • SELECT party_id, language_name, native_language, reads_level, speaks_level, writes_level FROM apps.ams_person_lang_v WHERE party_id = :p_party_id;

A query listing persons by a specific language for segmentation purposes:

  • SELECT party_id, language_name FROM apps.ams_person_lang_v WHERE language_name = 'SPANISH';

Analysts should note that the view filters on primary language and active person status. Queries requiring all languages a person uses, inactive parties, or non-person party types must access HZ_PERSON_LANGUAGE and HZ_PARTIES directly, since the view intentionally narrows the dataset to active persons and their single primary language.