Search Results ast_person_language_v




Overview
Explore in AI Chat

Overview

AST_PERSON_LANGUAGE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AST (TeleSales) product family. It presents person-level language proficiency information held against trading community parties. The view denormalizes the base language records stored in HZ_PERSON_LANGUAGE and enriches them with two lookup sources: the language description from FND_LANGUAGES_VL and the status meaning from AR_LOOKUPS. Users searching on the term "hz_person_language" are typically directed to this view because it is the supported, business-friendly interface over the underlying TCA (Trading Community Architecture) table.

Because the view is defined in the APPS schema and references only other APPS-owned or synonym-wrapped objects, it can be queried directly from SQL*Plus, BI Publisher, Oracle Reports, or any external integration layer without additional grants, provided the calling user has SELECT privilege on the view. In EBS 12.1.1 and 12.2.2 the view is reported as VALID, and no editioning or online patching complications are documented for it beyond the standard APPS synonym behavior in 12.2.2.

Underlying Base Objects

The view is constructed from three documented referenced objects:

  • HZ_PERSON_LANGUAGE (SYNONYM) — the primary source, supplying all language-use rows for a party, including the party identifier, language name, proficiency levels, status, and who-columns.
  • FND_LANGUAGES_VL (VIEW) — joined on LANGUAGE_NAME = LANGUAGE_CODE to retrieve the FND.DESCRIPTION, i.e., the installed language description rather than the raw code.
  • AR_LOOKUPS (VIEW) — outer-joined on LOOKUP_TYPE = 'REGISTRY_STATUS' and LOOKUP_CODE = STATUS to resolve the STATUS_MEANING, so that statuses without a matching lookup still return a row.

The join to AR_LOOKUPS is an outer join (indicated by the (+) operator in the documented view text), while the join to FND_LANGUAGES_VL is an inner join. The WHERE clause restricts output to rows whose STATUS is 'A' (active) or 'I' (inactive), which means any other status value present in the base table is filtered out of the view entirely. ROWID is projected from HZ_PERSON_LANGUAGE, allowing the view to be used as a key-preserved source for certain update operations subject to the usual restrictions.

Key Columns

Common Use Cases and Queries

Typical uses include TeleSales agent screens that display a contact's languages, multilingual campaign targeting, and data-quality extracts that reconcile TCA language records. A basic query listing active languages for a party:

  • SELECT party_id, language_name, description, primary_language_indicator, reads_level, speaks_level, writes_level, status_meaning FROM apps.ast_person_language_v WHERE party_id = :p_party_id AND status = 'A';
  • Language distribution across a customer base: SELECT language_name, description, COUNT(*) FROM apps.ast_person_language_v WHERE status = 'A' GROUP BY language_name, description ORDER BY 3 DESC;
  • Identifying primary-language records for segmentation: SELECT party_id, language_name FROM apps.ast_person_language_v WHERE primary_language_indicator = 'Y' AND status = 'A';

Because the view filters on STATUS IN ('A','I'), reports requiring other statuses must query HZ_PERSON_LANGUAGE directly and perform their own lookups against FND_LANGUAGES_VL and AR_LOOKUPS. Queries should also avoid selecting ROW_ID into application logic, as ROWIDs are not stable across table reorganizations.