Search Results ben_prtt_enrt_actn




Overview
Explore in AI Chat

Overview

BEN_PRTT_ENRT_ACTN is a view owned by the APPS schema within the Advanced Benefits (BEN) module of Oracle E-Business Suite. It exposes participant enrollment action data — the individual, actionable items that drive a participant through the benefits enrollment process. The view is documented as "Retrofitted," indicating it was introduced or reconstructed to provide a date-effective, session-aware read layer over the underlying transaction table. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration interface for enrollment actions without requiring consumers to understand the base table's date-effective filtering and status logic.

The view applies two layers of business logic that make it well suited to operational reporting. First, it restricts rows to those effective as of the current user's session effective date, using FND_SESSIONS. Second, it suppresses actions linked to participant life-event records whose status is VOIDD or BCKDT, thereby excluding voided or backdated events from normal result sets. This makes the view an authoritative source for "as-of-now" enrollment activity.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through synonyms:

  • BEN_PRTT_ENRT_ACTN_F — the primary, date-effective transactional table holding enrollment action rows. The view aliases it as PEA.
  • BEN_PER_IN_LER — the participant life-event record table, joined via a nullable outer join on PER_IN_LER_ID and BUSINESS_GROUP_ID to apply life-event status filtering.
  • FND_SESSIONS — the framework table supplying the session effective date used in the date-effective predicate.

The join to BEN_PER_IN_LER is an outer join (PIL.PER_IN_LER_ID(+) = PEA.PER_IN_LER_ID), so enrollment actions without an associated life event are preserved. A noteworthy detail is the predicate PIL.BUSINESS_GROUP_ID(+) = PEA.BUSINESS_GROUP_ID+0, which coerces the numeric business group identifier during the join. The life-event filter preserves rows where PER_IN_LER_STAT_CD is either not in ('VOIDD','BCKDT') or is null.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include tracking outstanding required actions by due date, analyzing completed actions by date or plan, and auditing enrollment results tied to life events.

Outstanding required actions:

  • SELECT prtt_enrt_actn_id, due_dt, actn_typ_id FROM ben_prtt_enrt_actn WHERE rqd_flag = 'Y' AND cmpltd_dt IS NULL ORDER BY due_dt;

Completed actions by plan:

  • SELECT pl_bnf_id, COUNT(*) FROM ben_prtt_enrt_actn WHERE cmpltd_dt IS NOT NULL GROUP BY pl_bnf_id;

Actions for a participant life event:

  • SELECT actn_typ_id, tr.* FROM ben_prtt_enrt_actn WHERE per_in_ler_id = :p_ler_id;

Because the view applies session-date effectiveness and life-event status filtering automatically, callers need not repeat that logic. For pre-session or historical comparisons, direct queries against BEN_PRTT_ENRT_ACTN_F may be required.