Search Results ben_ler_chg_pl_nip_enrt_f




Overview
Explore in AI Chat

Overview

BEN_LER_CHG_PL_NIP_ENRT_F is a transactional configuration table in the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to determine which plans are not included in a program enrollment when a life event is processed. In practical terms, the table stores the rules that drive the "change plan / not in program enrollment" behavior during a Life Event (LER) — that is, which plans should be offered, defaulted, or auto-enrolled when an employee experiences a qualifying life event and the target plan does not already belong to the employee's current program enrollment.

From a heuristic Data Vault modeling perspective, this object is classified as standalone. It is not a hub, link, or satellite in the classic sense because the mined foreign-key structure did not surface a strong parent/child FK dependency; it behaves as a self-contained rule table keyed by its own surrogate identifier and effective dating. The table is date-tracked (effective start/end dates), which is characteristic of Oracle's date-effective configuration tables used by the Benefits engine during enrollment processing.

Key Information Stored

The table carries 53 documented columns. The most significant are summarized below.

Common Use Cases and Queries

Typical scenarios include validating which plans a life event should present, auditing default enrollment rules, and reconciling enrollment outcomes against configuration.

  • Retrieve active rules for a business group and life event for a given effective date, filtering on LER_ID and current date rather than the surrogate key.
  • Report plans flagged for auto-enrollment (AUTO_ENRT_MTHD_RL) or default (DFLT_FLAG).
  • Check whether an existing enrollment should block a change using CRNT_ENRT_PRCLDS_CHG_FLAG and STL_ELIG_CANT_CHG_FLAG.

A representative query pattern filters by business group and effective window:

  • SELECT ler_chg_pl_nip_enrt_id, ler_id, pl_id, tco_chg_enrt_cd, enrt_mthd_cd, dflt_flag FROM ben.ben_ler_chg_pl_nip_enrt_f WHERE business_group_id = :p_bg AND sysdate BETWEEN effective_start_date AND effective_end_date;

Because the table is date-effective, queries should always constrain on both effective dates to return the intended rule version.

Related Objects

The metadata establishes only the standalone classification, so related objects are inferred from the rule semantics and shared columns:

These joins let administrators trace a life-event enrollment outcome back to the specific plan-not-in-program rule that produced it.