Results for “ben_prtt_enrt_rslt_d”

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

Overview

BEN_PRTT_ENRT_RSLT_D is an APPS-owned database view within the Oracle E-Business Suite Advanced Benefits (BEN) module. It exposes participant enrollment results in a denormalized, descriptive form suitable for reporting, extracts, and integration scenarios. The view is designated as "Retrofitted," reflecting that it was re-engineered to align with the multi-org and effective-dating conventions applied across later EBS releases, including 12.1.1 and 12.2.2. Because the underlying enrollment result data is stored with coded values and surrogate identifiers, this view resolves those codes into human-readable meanings through joins to lookup views and descriptive tables. It is read-only and intended primarily for query access rather than transactional processing.

Underlying Base Objects

The view is defined over the following documented base objects:

• BEN_PRTT_ENRT_RSLT_F — the primary participant enrollment result table, providing the driving rows.
• BEN_PER_IN_LER — the participant-in-life-event-rule association, supplying life event rule context.
• BEN_LER_F, BEN_PGM_F, BEN_PL_F, BEN_PL_TYP_F, BEN_PTIP_F — benefit program, plan, plan type, and plan type-in-program descriptive tables.
• PER_ALL_PEOPLE_F — supplies the participant's full name.
• FND_USER — provides the user name of the last updater.
• FND_CURRENCIES_VL — resolves the unit of measure into a benefit currency.
• HR_LOOKUPS — supplies meanings for enrollment method, override reason, suspended flag, covered flag, benefit type, non-monetary flag, compensation level, no-longer-eligible flag, and result status.
• HR_API — a package referenced in the view metadata for effective-dating logic.

All joins are outer joins, preserving enrollment result rows even when dependent descriptive data is missing.

Key Columns

• ROW_ID, PRTT_ENRT_RSLT_ID — row identifier and the enrollment result primary key.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the effective-dating range of the enrollment record.
• FULL_NAME — the participant's full name from PER_ALL_PEOPLE_F.
• NAME — populated from program, plan, plan type, life event rule, and currency tables.
• PTIP_STAT_CD — plan type-in-program status code.
• BNFT_AMT — the benefit amount elected.
• ORGNL_ENRT_DT, ERLST_DEENRT_DT — original enrollment and earliest deemed enrollment dates.
• ENRT_CVG_STRT_DT, ENRT_CVG_THRU_DT, ENRT_OVRID_THRU_DT — coverage start, coverage through, and override through dates.
• MEMANING columns — resolved meanings for enrollment method, override reason, suspended flag, covered flag, benefit type, non-monetary indicator, compensation level, eligibility status, and result status.
• BNFT_ORDR_NUM — benefit ordering sequence.
• LAST_UPDATE_DATE, USER_NAME — audit fields identifying the last change and the responsible user.

Common Use Cases and Queries

Typical uses include enrollment reconciliation reports, coverage audits, and downstream extracts. A representative query retrieves active enrollment results for a participant:

• SELECT prtt_enrt_rslt_id, full_name, name, bnft_amt, enrt_cvg_strt_dt, enrt_cvg_thru_dt
• FROM apps.ben_prtt_enrt_rslt_d
• WHERE full_name = :p_name
• AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Because the view already resolves lookups and descriptive names, it is well suited to BI Publisher data models and ad hoc queries where coded values would otherwise require extensive decoding joins.