Results for “per_contact_info_types_tl”

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

Overview

PER_CONTACT_INFO_TYPES_TL is a translation table in the Oracle E-Business Suite Human Resources (PER) product, residing in the HR schema. It stores the language-specific, translated descriptions of the extra information types that may be recorded against a contact relationship. In Oracle EBS, contact relationships allow a person or party to be associated with contacts, and each such association may carry additional attribute values grouped under an "information type." While the base (non-translated) definition of these information types lives in PER_CONTACT_INFO_TYPES_B, the _TL table supplies the language-dependent DESCRIPTION text keyed by LANGUAGE, enabling multilingual display of those types throughout the application.

The ETRM metadata classifies this object heuristically as standalone, meaning it has no foreign key dependencies mined from the database. Phrased as a modeling suggestion, this aligns with a Data Vault satellite pattern: the table holds descriptive, descriptive-attribute content attached to a business key (INFORMATION_TYPE plus LANGUAGE) rather than acting as a hub or link between entities. The translation nature of the row set reinforces this, as each record provides context-dependent descriptive text for a parent business concept.

Key Information Stored

The table is defined with 10 documented columns. The most significant are:

• INFORMATION_TYPE — the business identifier of the information type. Together with LANGUAGE it forms the documented primary key PER_CONTACT_INFO_TYPES_TL_PK, and appears first in the unique index PER_CONTACT_INFO_TYPES_TL_PK.
• LANGUAGE — the language code for the translated row, the second component of the primary and unique keys.
• SOURCE_LANG — the source language from which the translation was derived, used by the EBS multilingual (MLS) framework.
• DESCRIPTION — the translated descriptive text presented to users for the information type, the core payload of this satellite-style table.
• ZD_EDITION_NAME — the editioning column used by the Online Patching / EBR (Edition-Based Redefinition) infrastructure in Release 12.2. It is included in the unique index PER_CONTACT_INFO_TYPES_TL_PK (INFORMATION_TYPE, LANGUAGE, ZD_EDITION_NAME), making it part of the effective business-key candidate.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard "Who" audit columns tracking the most recent change to each translated row.
• CREATED_BY, CREATION_DATE — the standard audit columns recording initial row creation.

Because the table is an MLS (_TL) translation store, the surrogate/business-key distinction is important: the documented PK is composed of INFORMATION_TYPE and LANGUAGE, both foreign-key-style attributes to the base table, whereas ZD_EDITION_NAME participates in the unique index but is an editioning artifact rather than a user-facing key. No separate single-column surrogate key is documented; the key is a composite of business attributes.

Common Use Cases and Queries

Typical uses involve rendering contact information type descriptions in the user's session language, joining translated text to base definitions, and reporting on available information types for a given contact relationship.

• Listing information types in session language: join PER_CONTACT_INFO_TYPES_B (base) to PER_CONTACT_INFO_TYPES_TL (this table) on INFORMATION_TYPE, filtering by LANGUAGE using the EBS language environment (e.g., USERENV('LANG') or a bind variable).
• Reporting translations: select INFORMATION_TYPE, LANGUAGE, SOURCE_LANG, and DESCRIPTION to audit which languages are populated, and to identify missing translations (types with a base row but no _TL row for a locale).
• Edition-aware queries in 12.2: since ZD_EDITION_NAME participates in the unique index, queries under Online Patching may need to account for the active edition, though application views typically abstract this requirement.
• Integration/reference data: downstream code resolving display labels for contact extra information joins directly to DESCRIPTION by INFORMATION_TYPE and LANGUAGE.

Related Objects

The following objects most significantly reference or depend on PER_CONTACT_INFO_TYPES_TL, joined on the documented key columns:

• PER_CONTACT_INFO_TYPES_B — the base (non-translated) table; joined on INFORMATION_TYPE.
• PER_CONTACT_INFO_TYPES_VL — the MLS view that exposes base and translated columns together, joining on INFORMATION_TYPE and LANGUAGE.
• PER_CONTACT_INFO_TYPES — related base/entity views or objects resolving information type definitions.
• PER_CONTACT_RELATIONSHIPS — the contact relationship entity whose extra information instances are typed by the parent information type.
• PER_CONTACT_INFO — the instance table holding actual extra information values against a contact relationship, referencing the information type.

These objects collectively support the contact information model, with the _TL table supplying the multilingual descriptive layer that the views and application pages surface to end users.