Results for “per_in_ler”

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

Overview

APPS.BEN_PRTT_ENRT_RSLT_D is a reporting view in Oracle EBS Advanced Benefits (OLTP) that presents participant enrollment results in a denormalized, human-readable form. Its name follows the BEN "_D" convention, indicating a display-oriented view: rather than exposing raw foreign keys and lookup codes, it joins to the underlying base tables and decodes identifiers into descriptive names. The view exposes one row per distinct participant enrollment result record, keyed internally by PRTT_ENRT_RSLT_ID and bounded by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. It is defined with an outer-join pattern throughout (the "(+)" syntax), so a result row is returned even when a related person, program, plan, plan type, option, or lookup value is missing. In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as a read-only reporting and integration surface for enrollment data, and it is the object that surfaces the PER_IN_LER concept through the BEN_PER_IN_LER table and its associated status lookup, BEN_PER_IN_LER_STAT.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects: BEN_PRTT_ENRT_RSLT_F, BEN_PER_IN_LER, BEN_LER_F, BEN_PGM_F, BEN_PL_F, BEN_PL_TYP_F, BEN_PTIP_F, FND_CURRENCIES_VL, FND_USER, HR_LOOKUPS, and PER_ALL_PEOPLE_F. The central driving table is BEN_PRTT_ENRT_RSLT_F (aliased PEN), which supplies the enrollment result identifier, effective dates, benefit amount, enrollment dates, and all lookup-code flags. BEN_PER_IN_LER (aliased PER_IN_LER) is joined to resolve the "person in life event" record and its status, which the view decodes through BEN_PER_IN_LER_STAT. BEN_PGM_F, BEN_PL_F, BEN_PL_TYP_F, and BEN_PTIP_F provide program, plan, plan type, and plan-in-program names. BEN_LER_F supplies the life event reason name. HR_LOOKUPS is joined multiple times, each with a distinct LOOKUP_TYPE, to translate flags and codes into meaning text. FND_USER and PER_ALL_PEOPLE_F resolve the last updater and participant name. HR_API is also listed as a referenced object, reflecting the package context in which the underlying data is maintained.

Key Columns

The view exposes identity, status, and descriptive columns. PEN.ROWID is surfaced as ROW_ID, and PRTT_ENRT_RSLT_ID is the primary enrollment result key. EFFECTIVE_START_DATE and EFFECTIVE_END_DATE provide date-effective context, while ORGNL_ENRT_DT, ENRT_CVG_STRT_DT, ENRT_CVG_THRU_DT, ENRT_OVRID_THRU_DT, and ERLST_DEENRT_DT capture the enrollment chronology. Descriptive columns include PERSON.FULL_NAME, PGM.NAME, PL.NAME, PL_TYP.NAME, and LER.NAME. Status and flag decodes include PTIP.PTIP_STAT_CD, BEN_PER_IN_LER_STAT.MEANING (the PER_IN_LER status), PRTT_ENRT_RSLT_STAT.MEANING, and MEANING values derived from HR_LOOKUPS for SSPNDD, PRTT_IS_CVRD, ENRT_MTHD, ENRT_OVRIDN, ENRT_OVRID_RSN, BNFT_TYP, BNFT_NNMNTRY, NO_LNGR_ELIG, and comp_lvl. Financial and classification attributes include PEN.BNFT_AMT and BNFT.NAME (resolved via FND_CURRENCIES_VL on UOM/currency), plus PEN.BNFT_ORDR_NUM and LAST_UPDATE_DATE with FUSER.USER_NAME.

Common Use Cases and Queries

The view is typically used for enrollment auditing, benefits reporting, and downstream extracts where decoded values are preferred over coded identifiers. A representative query retrieves current enrollment results for a participant with their life event and PER_IN_LER status:

• SELECT ROW_ID, PRTT_ENRT_RSLT_ID, FULL_NAME, NAME, BNFT_AMT, BEN_PER_IN_LER_STAT.MEANING FROM BEN_PRTT_ENRT_RSLT_D.
• Filter by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to isolate date-effective intervals.
• Filter by PERSON.FULL_NAME or the decoded plan/program name for targeted reporting.
• Join PRTT_ENRT_RSLT_ID back to BEN_PRTT_ENRT_RSLT_F when raw codes are required alongside decoded values.

Because the view uses outer joins, consumers should treat columns from BEN_PER_IN_LER and the various HR_LOOKUPS as nullable and apply NVL or outer-join semantics where completeness of descriptive data is required.