Results for “mn_opts_rqd_num”

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

Overview

The BEN_PL view is a foundational data dictionary object within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, owned by the APPS schema. It exposes plan-level configuration and processing rules that govern how a benefits plan behaves during enrollment, eligibility evaluation, dependent designation, and claims processing. In EBS 12.1.1 and 12.2.2, BEN_PL functions as a reporting and integration surface over the underlying BEN_PL_F base table, presenting the same columns through a stable, query-friendly interface. Because the view is fully valid and defined in the APPS schema, it is safe for use in custom concurrent programs, BI Publisher data models, and inbound/outbound interface extracts. It is most relevant to benefits administrators, implementation consultants, and developers who need to read plan metadata without directly touching the base table or its date-tracked structures.

Underlying Base Objects

The documented definition of BEN_PL references two base objects: BEN_PL_F (a synonym) and FND_SESSIONS (a synonym). BEN_PL_F is the primary datastore holding plan definitions, including effective dating and attribute values. FND_SESSIONS supplies session context used by EBS date-tracked views to resolve the correct effective-dated row for the current runtime session. As a result, BEN_PL behaves as a session-aware projection: queries executed through the view return the plan row appropriate to the caller's effective date and session parameters, rather than the entire history. This design ensures that reporting and integration consumers see the same point-in-time plan configuration the application itself would use.

Key Columns

BEN_PL exposes a wide array of plan attributes. Core identity and dating columns include PL_ID, PL_CD, NAME, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. Enrollment and coverage control columns include ENRT_MTHD_CD, ENRT_CD, ENRT_CVG_STRT_DT_CD, ENRT_CVG_END_DT_CD, MN_CVG_RL, MN_OPTS_RQD_NUM, MX_OPTS_ALWD_NUM, MX_CVG_RL, and MX_CVG_ALWD_AMT. Beneficiary and dependent handling is represented by ALWS_QDRO_FLAG, ALWS_QMCSO_FLAG, BNF_DOB_RQD_FLAG, BNF_CTFN_RQD_FLAG, DPNT_DSGN_CD, DPNT_CVG_STRT_DT_CD, and DPNT_CVG_END_DT_CD. Financial and claims processing attributes include BNF_INCRMT_AMT, BNF_DFLT_BNF_CD, CMPR_CLMS_TO_CVG_OR_BAL_CD, FRFS_APLY_FLAG, and IMPTD_INCM_CALC_CD. Together these columns define the operational rules applied during enrollment and benefit administration.

Common Use Cases and Queries

Typical uses include validating plan setup before open enrollment, extracting plan metadata for data warehousing, and auditing enrollment method and coverage rules. The following sample queries reflect standard patterns:

• List active plans by code and name:

SELECT pl_id, pl_cd, name FROM apps.ben_pl WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date;

• Retrieve enrollment and coverage rules for a specific plan:

SELECT pl_cd, enrt_mthd_cd, enrt_cvg_strt_dt_cd, mn_cvg_rl, mx_opts_alwd_num FROM apps.ben_pl WHERE pl_cd = 'MED01';

• Identify QDRO and QMCSO-enabled plans:

SELECT pl_id, name, alws_qdro_flag, alws_qmcso_flag FROM apps.ben_pl WHERE alws_qdro_flag = 'Y';

Because BEN_PL is session-aware, custom code should filter by effective dates where historical or future-dated records are required, and should always query the view rather than the base table to preserve supported access patterns.