Results for “ben_ler_f_tl”

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

Overview

BEN_LER_F_TL is the multilingual translation table for life event reasons within the Oracle Advanced Benefits (BEN) module. In Oracle EBS 12.1.1 and 12.2.2, this table stores the language-specific display text associated with each life event reason defined in the base table BEN_LER_F. Life event reasons drive eligibility processing, enrollment opportunities, and coverage change logic throughout the benefits lifecycle, and the translated values determine how these reasons are presented to end users in their native language.

The table resides in the BEN schema and is documented as VALID in the ETRM 12.2.2 repository. It contains 12 columns and is keyed by the unique index BEN_LER_F_TL_PK, which spans LER_ID, LANGUAGE, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. From a Data Vault modeling perspective, the mined classification is standalone, indicating that the foreign key structure does not reveal a tightly bound parent-child dependency. A modeler would most naturally treat this as a satellite attached to the life event reason hub (BEN_LER_F), carrying descriptive, language-dependent attributes and effective-dated history.

Key Information Stored

The table's primary key (BEN_LER_F_TL_PK) is a composite business key combining LER_ID, LANGUAGE, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. The most significant columns include:

• LER_ID — The life event reason identifier; the join key back to the base BEN_LER_F record.
• LANGUAGE — The NLS language code for the translated text (for example, US, DE, FR), enabling multi-language display.
• NAME — The translated name of the life event reason presented to users.
• TYP_CD — The translated type code descriptor associated with the reason.
• SOURCE_LANG — The source language from which the translation originated, used by the MLS (Multi-Lingual Support) framework.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range governing when the translation row is active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard Oracle WHO audit columns tracking creation and modification.

The surrogate/business key distinction here is carried entirely by the composite unique index; there is no separate single-column surrogate key documented.

Common Use Cases and Queries

Typical reporting and support scenarios retrieve translated reason names for a given language, or audit which languages have been configured for a life event reason. A representative query joining to the base table follows:

• Retrieve translated reason names: SELECT t.LER_ID, t.LANGUAGE, t.NAME FROM BEN.BEN_LER_F_TL t WHERE t.LANGUAGE = 'US' AND SYSDATE BETWEEN t.EFFECTIVE_START_DATE AND t.EFFECTIVE_END_DATE;
• Identify missing translations: compare LER_ID values in BEN_LER_F against BEN_LER_F_TL per LANGUAGE.
• Audit recent changes: filter on LAST_UPDATE_DATE to review translation edits.
• Multi-language reporting: group by LANGUAGE to confirm coverage across all configured languages.

Related Objects

• BEN_LER_F — base, language-independent life event reason table; join on LER_ID.
• BEN_LER_F_TL_PK — unique index enforcing the composite primary key.
• FND_LANGUAGES — reference for valid LANGUAGE and SOURCE_LANG values.
• BEN_LER_F_TL_S (or sequence) — supporting sequence objects where present.
• BEN_LER_F_VL / MLS views — MLS-enabled views surfacing translated NAME values.
• BEN_LER_RULES / eligibility objects — consume LER_ID during benefits eligibility evaluation.
• BEN_PTIP / plan enrollment objects — reference life event reasons in coverage-change processing.

Together these objects position BEN_LER_F_TL as the localized descriptive layer for Advanced Benefits life event processing.