Results for “ler_chg_pl_nip_enrt_id”

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

Overview

The BEN_LER_CHG_PL_NIP_ENRT_D view is a reporting and integration object within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It exposes the concept of Life Event Reason (LER) processing rules that govern changes to plan-in-program (PL/NIP) enrollment options in response to a qualifying life event. In functional terms, this view describes, for a given plan and life event reason combination, how the participant's enrollment may be changed — including whether current enrollments may be modified, what the default enrollment code should be, the applicable enrollment method, and auto-enrollment method rules.

The view is defined over the base table BEN_LER_CHG_PL_NIP_ENRT_F through a synonym and represents the documented (ETRM-disseminated) projection of that table. Because the _F suffix indicates an effective-dated, DateTrack-enabled base table, this view preserves the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns and thus supports date-effective reporting. It is commonly consumed by payroll-benefits interfaces, life event processing reports, and custom extracts that need to resolve the enrollment treatment associated with a life event reason.

Underlying Base Objects

The view is defined with a single explicit SELECT from BEN_LER_CHG_PL_NIP_ENRT_F (referenced via a synonym resolved to the same name), aliased as LPE. The relationship is a straight projection: every column in the view maps one-to-one to a column in the base table. No joins, filters, or aggregations are applied, meaning the view does not reduce or transform the underlying rows.

The documented metadata also lists FND_USER (synonym) as a referenced base object. This reference typically arises because the base table's audit columns (LAST_UPDATED_BY, CREATED_BY) are validated against the application user directory; the view text itself does not join to FND_USER, but the dependency exists at the data-model level for user lookups in reporting scenarios.

Key Columns

• LER_CHG_PL_NIP_ENRT_ID — Primary identifier for each life-event-reason/plan enrollment change rule record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DateTrack effective range controlling when the rule is valid.
• BUSINESS_GROUP_ID — The business group (legislative/HR context) to which the rule belongs.
• PL_ID — The plan to which the enrollment change rule applies.
• LER_ID — The life event reason that triggers the rule.
• TCO_CHG_ENRT_CD — Enrollment code used when the participant changes enrollment as a result of the event.
• CRNT_ENRT_PRCLDS_CHG_FLAG — Flag indicating whether the current enrollment precludes further change.
• DFLT_ENRT_CD — Default enrollment code applied when the participant does not actively elect a different option. This is the column most often searched by users investigating the dflt_enrt_cd attribute.
• DFLT_ENRT_RL / DFLT_FLAG — Rule or flag determining default enrollment behavior.
• ENRT_RL / ENRT_CD — Enrollment rule and enrollment code for the rule context.
• STL_ELIG_CANT_CHG_FLAG — Indicates whether still-eligible participants are prevented from changing enrollment.
• ENRT_MTHD_CD / AUTO_ENRT_MTHD_RL — Enrollment method code and the rule governing automatic enrollment.
• LPE_ATTRIBUTE_CATEGORY and LPE_ATTRIBUTE1 through LPE_ATTRIBUTE10 — Descriptive flexfield segments for customer-specific extensions.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical uses include auditing default enrollment behavior for a plan/life-event combination, building life event configuration reports, and supporting data migration or integration extracts. A common query resolves the default enrollment code for a specific plan and life event reason as of a date:

• List active rules for a plan: SELECT PL_ID, LER_ID, DFLT_ENRT_CD, ENRT_MTHD_CD FROM BEN_LER_CHG_PL_NIP_ENRT_D WHERE PL_ID = :p_plan AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;
• Find records where a default enrollment code is set: SELECT LER_CHG_PL_NIP_ENRT_ID, PL_ID, LER_ID, DFLT_ENRT_CD FROM BEN_LER_CHG_PL_NIP_ENRT_D WHERE DFLT_ENRT_CD IS NOT NULL;
• Retrieve auto-enrollment method rules for a life event reason: SELECT LER_ID, ENRT_CD, AUTO_ENRT_MTHD_RL FROM BEN_LER_CHG_PL_NIP_ENRT_D WHERE LER_ID = :p_ler_id;

Because the view exposes the base table verbatim, queries against it are functionally equivalent to querying BEN_LER_CHG_PL_NIP_ENRT_F directly; the view is typically preferred in read-only interfaces to abstract the physical table name and to align with documented ETRM objects.