Results for “dpnt_legv_id_rqd_flag”

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

Overview

BEN_PTIP_X is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BEN (Advanced Benefits) product. In EBS 12.1.1 and 12.2.2 it exposes configuration data for plan types in benefits programs — specifically the row-level attributes that govern enrollment rules, dependent coverage, and eligibility processing. The "_X" suffix indicates an extraction or translated view (typically built on the "_F" base table with a corresponding "_TL" table for language rows), which makes BEN_PTIP_X the recommended read-only interface for reporting, conversions, and integration rather than querying the underlying table directly. Because plan-type setup is date-effective and business-group scoped, this view is central to answering questions about how a given plan type is expected to behave during an enrollment period.

Underlying Base Objects

ETRM documents BEN_PTIP_X as defined over the base object BEN_PTIP_F (referenced through a synonym in the APPS schema). BEN_PTIP_F is the date-effective, business-group-scoped base table storing Plan Type-in-Program rows, keyed in part by PTIP_ID, PROGRAM_ID (PGM_ID), PLAN_TYPE_ID (PL_TYP_ID), and BUSINESS_GROUP_ID. The view text selects exclusively from this base object using the alias CTP (the internal table alias), projecting CTP.* columns for the configuration attributes plus the audit column LAST_UPDATE. In other words, BEN_PTIP_X is a thin, denormalized projection of BEN_PTIP_F with no joins to external tables, so its row cardinality and effective-dating behavior mirror the base table exactly.

Key Columns

• PTIP_ID, PGM_ID, PL_TYP_ID – Primary identifiers linking a plan type to its owning program and business group (BUSINESS_GROUP_ID).
• Effective dating – EFFECTIVE_START_DATE and EFFECTIVE_END_DATE define the validity window for each configuration row.
• Enrollment controls – ENRT_MTHD_CD, ENRT_CD, ENRT_RL, AUTO_ENRT_MTHD_RL, DFLT_ENRT_CD, DFLT_ENRT_DET_RL, RQD_ENRT_PERD_TCO_CD, and RQD_PERD_ENRT_NENRT_VAL / _TM_UOM govern how and when participants enroll.
• Enrollment overrides – MX_ENRD_ALWD_OVRID_NUM (the searched attribute's sibling) and MN_ENRD_RQD_OVRID_NUM set the maximum and minimum enrollment override thresholds allowed per plan type. These are frequently referenced in enrollment validation and troubleshooting long-running or blocked enrollments.
• Dependent coverage flags – DPNT_CVG_NO_CTFN_RQD_FLAG, DPNT_ADRS_RQD_FLAG, DPNT_DOB_RQD_FLAG, DPNT_LEGV_ID_RQD_FLAG, DPNT_CVG_STRT_DT_CD/RL, DPNT_CVG_END_DT_CD/RL, and DRVD_FCTR_DPNT_CVG_FLAG.
• Eligibility and rate flags – ELIG_APLS_FLAG, PRTN_ELIG_OVRID_ALWD_FLAG, TRK_INELIG_PER_FLAG, DRVBL_FCTR_APLS_RTS_FLAG, DRVBL_FCTR_PRTN_ELIG_FLAG.
• Life insurance and status controls – SBJ_TO_SPS_LF_INS_MX_FLAG, SBJ_TO_DPNT_LF_INS_MX_FLAG, USE_TO_SUM_EE_LF_INS_FLAG, PTIP_STAT_CD, WVBL_FLAG, plus 30 CTP_ATTRIBUTE descriptive flexfield columns.

Common Use Cases and Queries

The view is typically queried for benefits configuration audits, enrollment rule validation, and data migration extracts. A common query for locating minimum enrollment override settings (relevant to the search term mn_enrd_rqd_ovrid_num) is:

SELECT ptip_id, pl_typ_id, pgm_id, mn_enrd_rqd_ovrid_num, mx_enrd_alwd_ovrid_num, effective_start_date, effective_end_date FROM apps.ben_ptip_x WHERE business_group_id = :p_bg AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Other practical scenarios include joining BEN_PTIP_X to BEN_PL_TYP_F and BEN_PGM_F to produce a reporting view of plan types with their enrollment constraints, and using the effective-date columns to compare current versus historical rule sets during an audit. Because the view exposes only the base table, any DML must target BEN_PTIP_F through the supported BEN APIs; BEN_PTIP_X should be treated strictly as a read-only reporting surface.