Results for “ben_clpse_lf_evt”

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

Overview

The view APPS.BEN_CLPSE_LF_EVT is a reporting and integration object within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It exposes the collapse life event rule configuration, presenting the rows of the underlying BEN_CLPSE_LF_EVT_F table in a date-effective, session-aware manner. The view is an "event" or "rule" construct rather than a transactional object: it defines how a life event causes one or more benefits to collapse or be re-evaluated at the plan level, and it records the sequence of conditional logic that governs that behaviour.

Because the view filters on the current effective date obtained from FND_SESSIONS, it returns only the configuration row that is active for the user's session. This makes it suitable for runtime benefit processing, concurrent-program logic, and reporting that must reflect the configuration in force at a given point in time rather than the full historical record.

Underlying Base Objects

The view is defined over two referenced base objects:

• BEN_CLPSE_LF_EVT_F (SYNONYM) — the primary, date-tracked table holding the collapse life event definitions. All business columns are sourced from this table, aliased CLP.
• FND_SESSIONS (SYNONYM) — the Applications session table, used to derive the effective date for the current session via USERENV('SESSIONID').

The effective-date predicate restricts output to rows where EFFECTIVE_START_DATE <= session effective date and EFFECTIVE_END_DATE >= session effective date. Consequently, the view behaves as a single-active-row projection over an effective-dated (DateTrack) table, and callers should not assume the view returns historical or future-dated configuration.

Key Columns

• CLPSE_LF_EVT_ID — Primary key of the collapse life event rule.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DateTrack effective dating range.
• BUSINESS_GROUP_ID — Owning business group for multi-tenant partitioning.
• SEQ — Sequence determining evaluation order within the rule.
• LER1_ID … LER10_ID — Ten slots, each referencing a life event rule (LER) that participates in the collapse logic.
• BOOL1_CD … BOOL9_CD — The user's search term bool9_cd maps to the ninth boolean condition code in the rule chain. These columns carry the boolean/operator codes that combine with the corresponding LER references to evaluate the rule expression.
• EVAL_CD, EVAL_RL, EVAL_LER_ID, EVAL_LER_DET_CD, EVAL_LER_DET_RL — Control the evaluation type, the rule applied, and the specific life event rule detail used to evaluate the collapse.
• TLRNC_DYS_NUM — Tolerance in days applied during evaluation.
• CLP_ATTRIBUTE_CATEGORY and CLP_ATTRIBUTE1 … CLP_ATTRIBUTE30 — Descriptive flexfield segments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Standard WHO and concurrency columns.

Common Use Cases and Queries

Typical uses include verifying which collapse rule is active for a session, diagnosing why a life event collapsed or did not collapse a plan, and extracting configuration for documentation or migration. Because the view is session-filtered, direct SQL from a non-EBS session may return no rows or a stale effective date.

• List active collapse rules:

  SELECT CLPSE_LF_EVT_ID, SEQ, LER1_ID, BOOL1_CD, LER9_ID, BOOL9_CD
  FROM   APPS.BEN_CLPSE_LF_EVT
  ORDER BY SEQ;

• Inspect the boolean chain for a specific rule:

  SELECT SEQ, LER1_ID, BOOL1_CD, LER2_ID, BOOL2_CD,
         LER9_ID, BOOL9_CD, LER10_ID
  FROM   APPS.BEN_CLPSE_LF_EVT
  WHERE  CLPSE_LF_EVT_ID = :p_id;

• Join to evaluation detail to trace how the rule resolves:

  SELECT CLPSE_LF_EVT_ID, EVAL_CD, EVAL_RL, EVAL_LER_ID,
         EVAL_LER_DET_CD, TLRNC_DYS_NUM
  FROM   APPS.BEN_CLPSE_LF_EVT;

When troubleshooting the search term bool9_cd, note that this column only holds meaning in combination with LER9_ID; the pair defines the ninth conditional branch of the collapse rule.