Results for “action_type_description”

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

Overview

BEN_PRTT_ENRT_ACTN_D is an APPS-owned database view within the Oracle Advanced Benefits (BEN) module. Its name, PRTT_ENRT_ACTN_D, denotes "Participant Enrollment Action — Denormalized." The view consolidates participant enrollment action records from BEN_PRTT_ENRT_ACTN_F and joins them to the surrounding benefits configuration and eligibility context so that a single row presents a human-readable picture of an action a participant must complete as part of a life event or enrollment cycle. Rather than exposing only raw identifiers and lookup codes, the view resolves foreign keys into descriptive names such as the option, program, plan, plan type, life event, and action type, and it resolves the responsible dependent's full name.

Because the "action_type_name" column is central to the view, it is the attribute most frequently searched by implementers and report developers. It surfaces ACTNTYP.NAME, the descriptive name of the action type assigned to a participant's enrollment action, allowing users to identify whether a participant is required to, for example, provide evidence of insurability, designate a beneficiary, or complete an election. The companion column ACTION_TYPE_DESCRIPTION provides the longer explanation.

Underlying Base Objects

The documented base objects referenced by the view are: BEN_ACTN_TYP, BEN_ELIG_CVRD_DPNT_F, BEN_LER_F, BEN_OIPL_F, BEN_OPT_F, BEN_PER_IN_LER, BEN_PGM_F, BEN_PL_F, BEN_PL_TYP_F, BEN_PRTT_ENRT_ACTN_F, BEN_PRTT_ENRT_RSLT_F, FND_SESSIONS, FND_USER, HR_LOOKUPS, PER_ALL_PEOPLE_F, and the HR_API package. All BEN objects and PER_ALL_PEOPLE_F are accessed through synonyms in the APPS schema; HR_LOOKUPS is a view; HR_API is a package used by the view definition.

The driving table is BEN_PRTT_ENRT_RSLT_F (alias PEN), the participant enrollment result, joined to BEN_PRTT_ENRT_ACTN_F (alias PEA) on PRTT_ENRT_RSLT_ID. Configuration tables BEN_OIPL_F, BEN_OPT_F, BEN_PGM_F, BEN_PL_F, BEN_PL_TYP_F, and BEN_LER_F are outer-joined so that incomplete or partially defined enrollment contexts still return rows. BEN_ACTN_TYP is outer-joined via ACTN_TYP_ID to supply the action type name. BEN_PER_IN_LER and BEN_ELIG_CVRD_DPNT_F link the action to the life event and the covered dependent, with PER_ALL_PEOPLE_F outer-joined to resolve the dependent's name. HR_LOOKUPS supplies the YES_NO meaning for RQD_FLAG, and FND_SESSIONS and FND_USER provide session and last-updated-by context.

Key Columns

• PRTT_ENRT_ACTN_ID — Primary identifier of the participant enrollment action.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective bounds of the action, also used to correlate the current FND session date.
• ACTION_TYPE_NAME — Name from BEN_ACTN_TYP; the primary descriptive attribute for classifying the required action.
• ACTION_TYPE_DESCRIPTION — Longer description of the action type.
• OPTION_NAME, PROGRAM_NAME, PLAN_NAME, PLAN_TYP_NAME, LIFE_EVENT_NAME — Resolved configuration context for the enrollment.
• DPNT_PERSON_NAME — Full name of the covered dependent associated with the action.
• RQD_MEANING — YES/NO meaning indicating whether the action is required.
• CMPLTD_DT, DUE_DT — Completion and due dates used to track status and timeliness.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Audit columns, with LAST_UPDATED_BY resolved via FND_USER.

Common Use Cases and Queries

The view is typically used for operational reporting on pending or completed enrollment actions, particularly where a report must describe actions in business terms rather than codes.

Listing incomplete required actions by action type:

• SELECT action_type_name, option_name, plan_name, dpnt_person_name, due_dt FROM apps.ben_prtt_enrt_actn_d WHERE cmpltd_dt IS NULL AND rqd_meaning = 'Yes' ORDER BY due_dt;

Grouping actions by type for a workload summary:

• SELECT action_type_name, COUNT(*) FROM apps.ben_prtt_enrt_actn_d GROUP BY action_type_name ORDER BY 2 DESC;

Because the view uses FND_SESSIONS and USERENV('SESSIONID'), it is effectively session-aware and is best queried interactively or from within an EBS session context. In 12.1.1 and 12.2.2 the structure is consistent, though query plans may differ due to the 12.2 Online Patching editioning views on the underlying tables.