Results for “whatif_lbl_txt”

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

Overview

BEN_PER_INFO_CHG_CS_LER_D is an APPS-owned database view within the Oracle Advanced Benefits (BEN) product family, delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes configuration data for "person information change" Life Event Rules (LER) used by the Benefits Life Events engine. Specifically, it presents the criteria rows that define when a life event rule should fire based on a change to person information, capturing the source table, source column, and the old versus new value comparison that drives the rule evaluation. The view is a reporting and integration convenience layer: rather than querying the underlying flexfield-style base table directly, external programs, custom reports, and data extracts can consume a pre-joined, user-friendly projection of the rule criteria.

The name suffix "_D" (detail) and its column set indicate that its purpose is diagnostic and audit-oriented — it is designed to answer questions such as "what criteria did this life event rule contain, and which value transition triggered it?" This is why the OLD_VAL and NEW_VAL columns, the subject of the user's search, are central to the object.

Underlying Base Objects

The view is defined over three documented objects, all of which are synonyms or views in the APPS schema:

• BEN_PER_INFO_CHG_CS_LER_F (SYNONYM) — the "_F" (form/flexfield) base table that stores the per-information change criteria rows for each life event rule. This is the primary source of all columns.
• FF_FORMULAS_F (SYNONYM) — the Oracle FastFormula repository table, joined to resolve the rule identifier (PER_INFO_CHG_CS_LER_RL) to a FORMULA_NAME.
• FND_USER_VIEW (VIEW) — the standard EBS user directory view, outer-joined on LAST_UPDATED_BY to resolve the user name of the last modifier.

The joins are all outer joins, so rows persist even when the referenced formula or user cannot be resolved, which is important for audit completeness. Formula resolution is additionally bounded by the effective dates of the formula record.

Key Columns

• PER_INFO_CHG_CS_LER_ID — primary key of the criteria row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the criterion row.
• NAME — descriptive name of the criteria entry.
• WHATIF_LBL_TXT — label text displayed in the "What If" analysis user interface.
• OLD_VAL — the prior value of the monitored person attribute prior to the change; used for comparison against the new value to determine whether the rule fires.
• NEW_VAL — the resulting value of the person attribute after the change.
• SOURCE_COLUMN / SOURCE_TABLE — the database column and table whose change is being monitored.
• RULE_OVERRIDES_FLAG — indicates whether the rule permits manual override of the determined outcome.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns; LAST_UPDATED_BY is resolved to a user name via FND_USER_VIEW.
• FORMULA_NAME / PER_INFO_CHG_CS_LER_RL_NAME — the formula that encapsulates the rule's processing logic.

Common Use Cases and Queries

Typical uses include auditing life event rule configuration, documenting value-transition criteria for benefits enrolment testing, and extracting criteria for migration or comparison between environments. The following query lists criteria and their triggering value transitions:

SELECT per_info_chg_cs_ler_id, name, source_table, source_column, old_val, new_val, formula_name FROM ben_per_info_chg_cs_ler_d WHERE effective_start_date <= SYSDATE AND effective_end_date >= SYSDATE ORDER BY name;

To locate rules that respond to a specific attribute change, filter on SOURCE_COLUMN. To audit recently modified rules, filter on LAST_UPDATE_DATE. Because the view retains effective-dated rows, always constrain by date or select the latest row per ID to avoid duplicate results when reporting current configuration.