Results for “eval_cd”

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

Overview

BEN_CLPSE_LF_EVT_F is a configuration table in the Oracle Advanced Benefits (BEN) product module, owned by the BEN schema. It is valid in both Oracle EBS 12.1.1 and 12.2.2. The table's documented purpose is to define which life event should be collapsed—that is, which single event the application should recognize and process—when a participant experiences multiple life events on the same date. This is a critical control point for benefits eligibility and enrollment processing, because Oracle Advanced Benefits evaluates life events to determine whether a participant may change elections, add or drop dependents, or modify coverage. Without a collapse rule, simultaneous life events could trigger conflicting or redundant processing logic.

The table carries 67 documented columns and is classified as standalone under the heuristic Data Vault classification mined from its foreign key structure. Under the Kimball-style modeling convention, this table is best understood as a configuration/master reference table rather than a transactional hub, link, or satellite, though the standalone classification suggests no formal FK dependencies were detected in the documented schema.

Key Information Stored

The primary key BEN_CLPSE_LF_EVT_F_PK is composed of three columns: CLPSE_LF_EVT_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. This composite key is date-effective, meaning the table supports versioned configuration that changes over time. CLPSE_LF_EVT_ID serves as the surrogate identifier for a collapse life event definition. BUSINESS_GROUP_ID scopes the record to a specific business group, enabling multi-tenant configuration.

The EVAL_LER_ID and EVAL_LER_DET_CD columns drive the core evaluation logic: they identify the life event reason (LER) that should be evaluated and the detail code governing how the evaluation proceeds. LER1_ID through LER10_ID (ten columns) and BOOL1_CD through BOOL9_CD (nine columns) form a Boolean rule matrix—each LER position pairs with a Boolean indicator, allowing the collapse rule to combine multiple life event reasons using Boolean logic. EVAL_CD identifies the evaluation type, EVAL_RL holds the evaluation rule reference, EVAL_LER_DET_RL holds the evaluation detail rule reference, and TLRNC_DYS_NUM specifies a tolerance window in days for matching same-date events. SEQ provides ordering. The 30 CLP_ATTRIBUTE columns reserve descriptive flexfield (DFF) segments for customer-defined extension data. Standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, plus OBJECT_VERSION_NUMBER for optimistic locking, round out the structure.

Common Use Cases and Queries

Implementers query this table to audit which life events collapse into a single processing event. A typical reporting query retrieves active collapse rules for a business group:

• SELECT c.CLPSE_LF_EVT_ID, c.EVAL_LER_ID, c.EVAL_CD, c.TLRNC_DYS_NUM FROM BEN.BEN_CLPSE_LF_EVT_F c WHERE c.BUSINESS_GROUP_ID = :p_bg_id AND SYSDATE BETWEEN c.EFFECTIVE_START_DATE AND c.EFFECTIVE_END_DATE ORDER BY c.SEQ;
• Join to the life event reason table to resolve LER1_ID through LER10_ID into readable names for a rule documentation report.
• Identify configuration gaps where EVAL_LER_DET_CD is null, which may indicate incomplete setup.
• Compare date-effective versions across EFFECTIVE_START_DATE/EFFECTIVE_END_DATE boundaries to reconstruct historical collapse behavior during a benefits audit.

Troubleshooting simultaneous life events often starts here, because an incorrect or missing collapse rule produces unexpected enrollment outcomes.

Related Objects

Because the metadata classifies this table as standalone, documented foreign key relationships are absent, but functional dependencies remain significant. The most relevant related objects include BEN_LER_F, which holds life event reasons referenced by EVAL_LER_ID and LER1_ID through LER10_ID; BEN_LER_DET_F, which holds LER detail codes referenced by EVAL_LER_DET_CD; BEN_LIF_EVT_F, which stores actual participant life events processed against these rules; and BEN_PGM_F, which supplies program context. The BEN_LER_RL and BEN_LER_DET_RL rule tables back the EVAL_RL and EVAL_LER_DET_RL references. Benefits administrators typically maintain this configuration through the Oracle Advanced Benefits setup forms, and the BEN_PROCESS_LIFE_EVENTS concurrent program consumes the collapse definitions at runtime to determine enrollment eligibility.