Results for “mx_cvg_wcfn_mlt_num”

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

Overview

BEN_LER_BNFT_RSTRN_D is an APPS-owned reporting view in the Oracle Advanced Benefits (BEN) module. It presents benefit restriction rules defined at the Life Event Reason (LER) level, exposing the effective-dated configuration rows of the base table BEN_LER_BNFT_RSTRN_F together with decoded lookup meanings, formula names, plan and life event reason names, and audit information. Because it denormalizes coded identifiers into readable values, the view is the primary source for reporting on how benefit restrictions are applied when a life event is processed.

The "D" suffix denotes the descriptive (display) variant of the underlying restriction entity, distinguishing it from key or validation views. In Oracle EBS 12.1.1 and 12.2.2, it is used by the Benefits forms, by concurrent programs that evaluate life event restrictions, and by customer or partner reporting built on the BEN schema.

Underlying Base Objects

The view is defined over the following documented objects:

• BEN_LER_BNFT_RSTRN_F – the base table holding life event reason benefit restriction records, including all MAX/MIN coverage amounts, increments, multipliers, and flags.
• BEN_LER_F – the life event reason definition, supplying LER.NAME.
• BEN_PL_F – the plan definition, supplying PL.NAME.
• FF_FORMULAS and FF_FORMULAS_F – the FastFormula registry used to resolve coverage amounts, coverage increments, and the default-to-assignment-pending-certification formula.
• FND_USER – resolves LAST_UPDATED_BY to a user identity.
• HR_LOOKUPS – decoded via outer joins for the lookup types BEN_CVG_INCR_R_DECR_ONLY, BEN_UNSSPND_ENRT, BEN_DFLT_TO_ASN_PNDG_CTFN, and YES_NO.
• HR_API – the HR API package referenced by the view's dependency chain.

All joins to FND_USER, HR_LOOKUPS, BEN_LER_F, BEN_PL_F, and the formula objects are outer joins, ensuring that restriction rows are returned even when a lookup code or formula is not yet populated.

Key Columns

• LER_BNFT_RSTRN_ID, ROW_ID – primary key and row identifier for the restriction record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE – date-tracked validity of each rule.
• MX_CVG_ALWD_AMT, MX_CVG_INCR_ALWD_AMT, MX_CVG_INCR_WCF_ALWD_AMT – maximum coverage, maximum coverage increment, and maximum coverage increment waiving coverage fields.
• MX_CVG_WCFN_AMT, MX_CVG_MLT_INCR_NUM, MX_CVG_MLT_INCR_WCF_NUM, MX_CVG_WCFN_MLT_NUM – waiving coverage amounts and multiplier counts.
• MN_CVG_AMT – minimum coverage amount.
• FORMULA_NAME columns – resolved names for MX_CVG.FORMULA_NAME, MN_CVG.FORMULA_NAME, and DFLT_TO_ASN_PNDG_CTFN2.FORMULA_NAME.
• Meaning columns – decoded text for the YES_NO flags (NO_MX_CVG_AMT_APLS, NO_MN_CVG_INCR_APLS, NO_MX_CVG_INCR_APLS), CVG_INCR_R_DECR_ONLY, UNSSPND_ENRT, and DFLT_TO_ASN_PNDG_CTFN.
• LER.NAME, PL.NAME – life event reason and plan names.
• LAST_UPDATE_DATE, LAST_UPDATED_BY – audit columns.

Common Use Cases and Queries

Typical uses include auditing life event restriction setups, verifying which FastFormula drives each coverage calculation, and building extracts for benefits configuration reviews or data migration validation.

List active restrictions for a life event reason:

• SELECT ler_name, pl_name, mx_cvg_alwd_amt, mn_cvg_amt, formula_name FROM ben_ler_bnft_rstrn_d WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date AND ler_name = :p_ler_name;

Trace formula usage across restriction rules:

• SELECT formula_name, COUNT(*) FROM ben_ler_bnft_rstrn_d GROUP BY formula_name;

Review decoded restriction behavior flags:

• SELECT ler_name, pl_name, cvg_incr_r_decr_only, unsspnd_enrt, dflt_to_asn_pndg_ctfn FROM ben_ler_bnft_rstrn_d;

Because the view joins FF_FORMULAS and FF_FORMULAS_F, it is frequently the starting point for validating that every restriction rule resolves to a valid compiled formula before a payroll or enrollment run.