Results for “per_info_chg_cs_ler_rl”

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

Overview

The view BENBV_PER_INFO_CHG_CS_LER_V is a database object owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits module (product code BEN). In EBS 12.1.1 and 12.2.2, this view functions as a business-facing, secure presentation layer over the underlying person information change rule entity. Its stated purpose, per the ETRM documentation, is to identify a specific change to a column in a table from which life events can be detected when an employee's personal data changes.

Advanced Benefits relies on lifecycle events — marriage, birth of a child, address changes, and similar occurrences — to trigger eligibility recalculation and enrollment opportunities. The metadata that governs which column changes in which source table constitute a detectable life event is captured by the base entity underlying this view. The view exposes that configuration in a normalized, reportable, and integration-friendly form, making it suitable for reporting, data extraction, and interface development without requiring direct access to the flexfield-backed base table structure.

Underlying Base Objects

The view is defined over a single primary base object and one supporting package:

• BEN_PER_INFO_CHG_CS_LER_F (referenced through a synonym) — the core table storing the person information change rules that map source columns to detectable life events. Its trailing _F suffix indicates it is a date-tracked (datetrack-enabled) entity, which is why EFFECTIVE_START_DATE and EFFECTIVE_END_DATE appear in the view.
• HR_BIS (package) — used for two functions: HR_BIS.BIS_DECODE_LOOKUP, a seeded lookup-decoding utility that translates the YES_NO flag into a meaningful display value, and HR_BIS.GET_SEC_PROFILE_BG_ID, which applies the business group security profile.

Because the view selects from the _F table and applies WITH READ ONLY, it is a query-only object. Security is enforced through the predicate WHERE PSL.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, PSL.BUSINESS_GROUP_ID), which restricts returned rows to the caller's permitted business group.

Key Columns

• PER_INFO_CHG_CS_LER_ID — primary identifier for the change rule.
• SOURCE_TABLE and SOURCE_COLUMN — the table and column whose modification is monitored for life-event detection.
• OLD_VAL and NEW_VAL — the before and after values evaluated to determine whether a qualifying change has occurred.
• NAME and WHATIF_LBL_TXT — identifying label and the text used in the "what-if" life-event simulation utility.
• PER_INFO_CHG_CS_LER_RL — a descriptive flexfield reference; "_DF:PSL" denotes the flexfield context.
• RULE_OVERRIDES_FLAG and RULE_OVERRIDES_FLAG_M — indicates whether rule overrides are permitted, with the decoded YES/NO meaning.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — datetrack validity range.
• BUSINESS_GROUP_ID plus the WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE) — audit and security context.

Common Use Cases and Queries

Typical uses include auditing which column changes trigger life events, validating configuration ahead of an upgrade, and feeding external eligibility engines. A representative query follows:

• SELECT per_info_chg_cs_ler_id, name, source_table, source_column, old_val, new_val FROM benbv_per_info_chg_cs_ler_v WHERE source_table = 'PER_PEOPLE_F' ORDER BY name;
• SELECT name, rule_overrides_flag_m FROM benbv_per_info_chg_cs_ler_v WHERE rule_overrides_flag = 'Y';

Because the view is read-only and business-group secured, it is safe to expose through concurrent programs, BI Publisher data models, and outbound interfaces.