Results for “hz_person_language”

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

Overview

HZ_PERSON_LANGUAGE is a table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the languages that a person speaks, reads, or writes, functioning as a multilingual attribute store for party records in the Trading Community Architecture (TCA) model. Each row associates a party with a language and captures proficiency levels across several communication dimensions.

From a Data Vault modeling perspective, the metadata's FK structure suggests this object behaves as a link table. It connects two distinct hubs — HZ_PARTIES (via PARTY_ID) and FND_LANGUAGES (via LANGUAGE_NAME) — and carries descriptive attributes such as proficiency levels and status flags. Modelers designing a warehouse around TCA data may treat it accordingly, though in EBS it is a standard transactional entity table.

Key Information Stored

The table contains 23 documented columns. The following are the most significant:

• LANGUAGE_USE_REFERENCE_ID — The surrogate primary key (HZ_PERSON_LANGUAGE_PK) and the business-key candidate backed by unique index HZ_PERSON_LANGUAGE_U1. This is the row-level identifier.
• PARTY_ID — Foreign key to HZ_PARTIES, identifying the person whose language record this is.
• LANGUAGE_NAME — Foreign key to FND_LANGUAGES, specifying the language itself.
• NATIVE_LANGUAGE — Flag indicating whether the language is the person's native tongue.
• PRIMARY_LANGUAGE_INDICATOR — Identifies the person's primary language among multiple records.
• READS_LEVEL, SPEAKS_LEVEL, WRITES_LEVEL — Proficiency ratings for reading, speaking, and writing respectively.
• SPOKEN_COMPREHENSION_LEVEL — Proficiency rating for oral comprehension, distinct from speaking ability.
• STATUS — Lifecycle state of the language record.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the TCA APIs.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY_MODULE, APPLICATION_ID, WH_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include CRM multilingual profiling, customer service routing based on language skills, and marketing segmentation. A common query retrieves all languages for a given party, ordered by primary indicator:

• SELECT party_id, language_name, native_language, primary_language_indicator FROM hz_person_language WHERE party_id = :party_id;
• Reporting on language distribution: SELECT language_name, COUNT(*) FROM hz_person_language WHERE primary_language_indicator = 'Y' GROUP BY language_name;
• Linking to parties for a full profile: SELECT p.party_name, l.language_name FROM hz_parties p JOIN hz_person_language l ON p.party_id = l.party_id;

These patterns support contact-center staffing analysis, localization planning, and compliance reporting where language capability is a regulatory concern.

Related Objects

The primary relationships are defined by documented foreign keys:

• HZ_PARTIES — Joined via HZ_PERSON_LANGUAGE.PARTY_ID; the parent party record.
• FND_LANGUAGES — Joined via HZ_PERSON_LANGUAGE.LANGUAGE_NAME; supplies language descriptions and ISO codes.
• HZ_PERSON_PROFILES — Related person-profile table sharing PARTY_ID for extended biographical attributes.
• HZ_CONTACT_POINTS — Contact information associated with the same party for communication preferences.
• HZ_PARTY_SITES — Location data joined through PARTY_ID where locale matters.

Maintenance is typically performed through TCA party APIs rather than direct DML, ensuring OBJECT_VERSION_NUMBER integrity and downstream synchronization.