Results for “benbv_ler_chg_pgm_enrt_v”

17 results




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

Overview

BENBV_LER_CHG_PGM_ENRT_V is a read-only Oracle EBS Advanced Benefits (BEN) view owned by the APPS schema. It presents the configuration that determines how a specific life event reason (LER) affects the enrollment election changes a participant may or may not make to a program. In effect, it answers the question: "For this life event reason, what changes to a given program enrollment are permitted, defaulted, or automatically applied?"

The view is a business-facing, denormalized projection of the underlying setup table. Because it exposes decoded lookup values (rather than raw codes) and enforces business group security, it is intended for reporting, integration extracts, and validation queries rather than for direct transactional writes. The "BV" naming convention signals a business view over the base table BEN_LER_CHG_PGM_ENRT_F, and the version is consistent with the 12.1.1 and 12.2.2 EBS releases.

The view text includes a descriptive flexfield token ('_DF:BEN:BEN_LER_CHG_PGM_ENRT_F:LGE'), meaning any DFF segments defined on the base table are surfaced through the view for reporting tools that recognize the token.

Underlying Base Objects

The view is defined exclusively over the base table BEN_LER_CHG_PGM_ENRT_F (exposed in APPS through a synonym), aliased as LGE. The base table is a date-tracked (datetrack) table, indicated by the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE and the "_F" suffix. This means that all business rules concerning a life event reason's impact on program enrollment changes are versioned by effective date, allowing the same logical record to have different values across time.

The view also calls the package HR_BIS, specifically the function BIS_DECODE_LOOKUP, to translate stored codes into their lookup meanings for displays such as DFLT_ENRT_CD_M, ENRT_CD_M, and ENRT_MTHD_CD_M. Security is enforced within the WHERE clause: LGE.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, LGE.BUSINESS_GROUP_ID), restricting rows to the querying user's security profile business group when one is set, and returning all business groups otherwise. The view is declared WITH READ ONLY, so it cannot be used as a DML target.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which enrollment changes are allowed for each life event reason across programs, validating setup before or after configuration migration, and feeding downstream integration extracts with decoded values. Because the view enforces business-group security automatically, it is well suited to multi-tenant reporting environments.

  • Retrieve all change rules for a specific life event reason and program:

SELECT l.pgm_id, l.ler_id, l.enrt_cd_M, l.enrt_mthd_cd_M, l.stl_elig_cant_chg_flag_M, l.effective_start_date, l.effective_end_date FROM apps.benbv_ler_chg_pgm_enrt_v l WHERE l.ler_id = :ler_id AND l.pgm_id = :pgm_id AND TRUNC(SYSDATE) BETWEEN l.effective_start_date AND NVL(l.effective_end_date, TRUNC(SYSDATE)+1);

  • List all rules where a still-eligible participant cannot change enrollment:

SELECT l.ler_id, l.pgm_id, l.stl_elig_cant_chg_flag_M FROM apps.benbv_ler_chg_pgm_enrt_v l WHERE l.stl_elig_cant_chg_flag = 'Y';

  • Join to program and life event reason tables to produce a descriptive report of permitted enrollment changes for a business group.

Because the view is READ ONLY and date-tracked, queries should always include an effective-date predicate to return only the currently active rule version.