Search Results enrt_method_code

Overview

The view APPS.BEN_LER_CHG_PTIP_ENRT_D is a date-tracked reporting object within the Oracle Advanced Benefits (BEN) module. Its documented description is "Life Event Plan Type in Program Enrollment Date Track View," which defines its purpose: to present, in a single flattened result set, the enrollment method and rules that apply when a life event causes a participant's plan type enrollment to change within a program. The "_D" suffix and the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns identify it as a Date Track (DT) view, meaning it resolves the temporal validity of the underlying rows relative to the effective dates stored in the base tables.

Objects of this family are not used by the core application runtime for transaction processing. Instead, they serve reporting, extracts, and integration interfaces that must read the configuration of life-event-driven plan type enrollment rules without duplicating the Date Track join logic. Because the view is owned by APPS and marked VALID in the ETRM 12.2.2 metadata, it is safe to reference from custom concurrent programs, BI Publisher data models, and SQL*Plus extracts in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view is defined over the following documented objects:

• BEN_LER_CHG_PTIP_ENRT_F — the driving base table holding life event / plan type enrollment change rows, aliased LCT.
• BEN_LER_F — the life event definition table, aliased LER; supplies the life event name.
• BEN_PTIP_F — the plan type in program table, aliased PTIP; the bridge between the enrollment change row and the plan type.
• BEN_PL_TYP_F — the plan type definition table, aliased PLTYP; supplies the plan type name.
• FND_USER — the application user table, aliased FUSER; supplies the user name of the last updater.
• HR_GENERAL — a package whose DECODE_LOOKUP function resolves coded lookup values into their display meanings.

All joins to the referenced base tables are outer joins (denoted by the (+) operator). Each join is Date Track-aware: the driving row's EFFECTIVE_START_DATE must fall between the referenced row's start and end dates, ensuring the correct temporal version of the life event, plan type in program, and plan type records is returned.

Key Columns

• LER_CHG_PTIP_ENRT_ID — primary identifier of the enrollment change row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date Track validity window of the row.
• ENRT_METHOD_CODE — the enrollment method, derived from ENRT_MTHD_CD and decoded through the BEN_ENRT_MTHD lookup. This is the column most commonly targeted by the search term "enrt_method_code".
• ENROLLMENT_CODE — decoded from ENRT_CD via the BEN_ENRT lookup, indicating the enrollment type (for example, elect or waive).
• DEFAULT_FLAG, DEFAULT_ENRT_CD, DEFAULT_ENRT_RULE — default enrollment behaviour, with the flag and code decoded through the YES_NO and BEN_DFLT_ENRT lookups respectively.
• CRNT_ENRT_PRCLDS_CHG_FLAG — decoded yes/no flag indicating whether current enrollment precludes a change.
• STL_ELIG_CANT_CHG_FLAG — decoded yes/no flag indicating whether still-eligible participants cannot change.
• TCO_CHG_ENRT_CD — decoded through BEN_TCO_CHG_ENRT, controlling what happens to the existing enrollment.
• PLAN_TYPE_NAME, LER_NAME — descriptive names from the plan type and life event tables.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — audit columns from the base row and FND_USER.

Common Use Cases and Queries

Typical uses include auditing enrollment method configuration, validating that life event rules are temporally consistent, and feeding downstream extracts with decoded lookup values so that no further lookup joins are required.

To find all enrollment methods configured for a life event change:

SELECT ler_name,
       plan_type_name,
       enrollment_code,
       enrt_method_code,
       effective_start_date,
       effective_end_date
FROM   apps.ben_ler_chg_ptip_enrt_d
WHERE  TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
ORDER  BY ler_name, plan_type_name;

To inspect default enrollment behaviour for a specific plan type:

SELECT ler_chg_ptip_enrt_id,
       ler_name,
       enrt_method_code,
       default_flag,
       default_enrt_cd,
       default_enrt_rule
FROM   apps.ben_ler_chg_ptip_enrt_d
WHERE  plan_type_name = :p_plan_type
AND    effective_start_date = :p_effective_date;

Because the view applies HR_GENERAL.DECODE_LOOKUP, callers receive displayable values directly; no additional joins to FND_LOOKUP_VALUES are necessary, and the date-track joins are already resolved by the view definition.