Results for “enrt_mthd_meaning”

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

Overview

The BEN_LER_CHG_PGM_ENRT_D view is an Advanced Benefits (BEN) datetrack reporting object owned by the APPS schema. Its documented description — "Life Event - Program Enrollment Date Track View" — identifies its purpose: to expose the date-trackable enrollment configuration records that govern how a participant is automatically enrolled in a program when a life event occurs. The name encodes this directly: LER (life event rule), CHG_PGM_ENRT (change program enrollment), and the trailing _D denoting the datetrack variant that presents the effective-dated form of the underlying _F (date-tracked) entity.

In the Oracle EBS 12.1.1 and 12.2.2 data model, this view serves as the reporting and integration face of BEN_LER_CHG_PGM_ENRT_F. It resolves the numerous coded attributes of the base table into human-readable meanings by joining to HR_LOOKUPS and FF_FORMULAS_F. This makes it the appropriate source for functional extracts, benefit configuration audits, OBIEE/BIP reports, and integration interfaces that require the decoded enrollment method rather than raw lookup codes.

Underlying Base Objects

The view is defined over the following documented base objects:

• BEN_LER_CHG_PGM_ENRT_F (synonym) — the primary date-tracked table holding life event program enrollment rows.
• BEN_LER_F (synonym) — supplies the life event rule name (LER.NAME).
• BEN_PGM_F (synonym) — supplies the program name (PGM.NAME).
• FF_FORMULAS_F (synonym) — joined three times to resolve the auto-enrollment method rule, default enrollment rule, and enrollment rule formula names.
• FND_USER (synonym) — resolves the last-updated-by user.
• HR_LOOKUPS (view) — joined four times to decode the default enrollment code, enrollment code, enrollment method code, current-enrollment-periods-change flag, and the "still eligible cannot change" flag.

All joins except the outer join to FND_USER and the reference tables are outer joins (+), and the formula joins add an effective-date predicate so the correct formula version is returned for the row's EFFECTIVE_START_DATE. HR_API (package) is also documented as referenced.

Key Columns

• ROW_ID — the base table ROWID, used for row identification.
• LER_CHG_PGM_ENRT_ID — primary key of the enrollment configuration row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — datetrack effective dating of the configuration.
• MEANING (aliased from multiple lookups) — decoded values for the enrollment method, default enrollment, and enrollment flags.
• FORMULA_NAME — resolved formula names for the auto-enrollment, default, and enrollment rules.
• NAME — program name (BEN_PGM_F) and life event rule name (BEN_LER_F).
• LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns, with the user ID resolved through FND_USER.

Common Use Cases and Queries

The most frequent requirement is to report which enrollment method meaning (enrt_mthd_meaning) applies to a given life event program enrollment — the very column this view exposes through the ENRT_MTHD lookup alias. A typical query joins the view to BEN_PGM_F and BEN_LER_F to present configuration for a program or life event.

• Auditing life event enrollment configuration per program.
• Reporting decoded enrollment methods for compliance and testing.
• Extracting formula rule mappings for integration to downstream benefit systems.

Sample SQL:

• SELECT ler_chg_pgm_enrt_id, name, enrt_mthd.meaning enrt_mthd_meaning, effective_start_date, effective_end_date FROM apps.ben_ler_chg_pgm_enrt_d WHERE effective_start_date <= SYSDATE AND effective_end_date >= SYSDATE ORDER BY name;