Search Results ben_rltd_per_chg_cs_ler_f

Overview

The table BEN_RLTD_PER_CHG_CS_LER_F is an Oracle Advanced Benefits (BEN) configuration table within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description — "Related person life event causes participant life event" — identifies it as the mapping entity that defines which life events occurring on a related person (such as a spouse, dependent, or beneficiary) will trigger a life event for the participant themselves. This relationship is central to benefits eligibility processing, since a participant may experience a qualifying event indirectly through changes in a related person's status or coverage.

The table follows the standard Oracle EBS "_F" (Foundation / date-tracked) naming convention, meaning it is an effective-dated table with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns that support temporal versioning of configuration rows. The metadata assigns a heuristic Data Vault classification of standalone, meaning no foreign key dependencies are mined from the physical structure. In Data Vault modeling terms, this would be treated as an independent reference table rather than a hub, link, or satellite, though the effective-dating pattern is analogous to a satellite's change-tracking behavior.

Key Information Stored

The table contains 49 documented columns. The primary key BEN_RLTD_PER_CHG_CS_LER_F_PK comprises three columns: RLTD_PER_CHG_CS_LER_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. The same three columns form the sole unique index, which is also the business-key candidate. In practice, RLTD_PER_CHG_CS_LER_ID is the surrogate identifier for a single mapping rule, while the effective date pair represents the business-key temporal component that distinguishes versions of the rule over time.

The remaining columns fall into several functional groups:

• Rule identifiers and labels: NAME and WHATIF_LBL_TXT provide the human-readable rule name and the text label used in what-if life event simulation screens.
• Change semantics: OLD_VAL and NEW_VAL hold the prior and resulting values associated with the related person change that drives the participant event.
• Source provenance: SOURCE_TABLE and SOURCE_COLUMN document the originating table and column from which the related person change is detected.
• Relationship marker: RLTD_PER_CHG_CS_LER_RL stores the relationship reference linking the mapping to the related person context.
• Overrides control: RULE_OVERRIDES_FLAG indicates whether downstream rule overrides are permitted for this mapping.
• Descriptive flexfield: The RCL_ATTRIBUTE_CATEGORY and RCL_ATTRIBUTE1 through RCL_ATTRIBUTE30 columns constitute a 30-segment descriptive flexfield (DFF) used to capture client-specific configuration attributes.
• Standard audit columns: BUSINESS_GROUP_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER support multi-organization security, concurrency control, and auditing.

Common Use Cases and Queries

The most frequent use case is auditing which related-person events are configured to cascade into participant life events within a given business group. A representative query retrieves active mappings as of a specific date:

• SELECT rltd_per_chg_cs_ler_id, name, whatif_lbl_txt, old_val, new_val FROM ben.ben_rltd_per_chg_cs_ler_f WHERE business_group_id = :p_bg_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY name;

Configuration analysts often join this table to life event definitions to verify the full cause-and-effect chain during implementation or regression testing of a benefits plan setup. The SOURCE_TABLE and SOURCE_COLUMN columns are useful in data lineage reporting, allowing teams to trace how a related person change originates. The RULE_OVERRIDES_FLAG column supports queries that identify which mappings permit plan-level customization versus those that are globally enforced. The DFF attributes are frequently queried in client-specific reporting when implementations have stored custom metadata in RCL_ATTRIBUTE1 and beyond.

Related Objects

Because the metadata classifies this table as standalone with no mined foreign key relationships, join dependencies are established through logical (not enforceable) relationships. The following objects are most significant in practice:

• BEN_LER_F — the life event reasons table, logically joined via RLTD_PER_CHG_CS_LER_ID and life event code references.
• BEN_PL_F and BEN_PGM_F — plan and program definitions that consume life event processing outcomes.
• BEN_PER_LER_F — participant life event occurrences generated when a related person change matches a configured rule.
• BEN_RLTD_PER_F — related person records whose changes provide the triggering context referenced by RLTD_PER_CHG_CS_LER_RL.
• BEN_LER_RLTD_PER_CHG_F — the inverse mapping that expresses participant-to-related-person change direction.
• Life event APIs such as BEN_LIFE_EVENT_API and the Life Events concurrent processes that read these mappings during event detection.

Administrators should treat BEN_RLTD_PER_CHG_CS_LER_F as configuration data, modifying it through the Advanced Benefits setup UI rather than direct DML, to preserve effective-date integrity and audit columns.