Results for “mx_cvg_mlt_incr_num”

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

Overview

The BEN_LER_BNFT_RSTRN view in the APPS schema is a reporting and integration layer within the Oracle Advanced Benefits (BEN) module. It presents restriction rules that control how benefit coverage amounts may be elected for a given plan or plan type, expressed through the Life Event Remark (LER) benefit restriction entity. In Oracle EBS 12.1.1 and 12.2.2 the view is registered as a VALID synonym-based object, meaning it is queried by concurrent programs, forms, and interfaces rather than being a physical table.

Its principal role is to surface date-effective restriction configuration to external consumers—FastFormula contexts, benefits extract processes, and custom reports—without exposing the raw _F table directly. The view is session-aware: the WHERE clause filters rows using FND_SESSIONS.EFFECTIVE_DATE for the current USERENV('SESSIONID'), so callers automatically receive only the restriction record in effect on the session date rather than a full history.

Underlying Base Objects

Two documented base objects are referenced by the view definition:

• BEN_LER_BNFT_RSTRN_F (SYNONYM) — the primary base table holding the effective-dated restriction records (_F denotes the "future/date-tracked" table in the BEN datetrack model). All columns in the view are projected aliased from this table with the LBR alias.
• FND_SESSIONS (SYNONYM) — a subquery against this table supplies the effective date used to constrain EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, implementing datetrack enforcement at the view level.

Because the restriction entity is date-tracked, the view effectively returns a single effective row per LER_BNFT_RSTRN_ID for the current session date, rather than the complete version history.

Key Columns

The projection includes the full restriction rule surface. Notable columns include:

• LER_BNFT_RSTRN_ID — primary identifier of the restriction record; joins to the LER benefit restriction hierarchy.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — datetrack boundaries for the restriction version.
• MN_CVG_AMT — the minimum coverage amount permitted. This is the column most commonly referenced when users search for mn_cvg_amt, and it pairs with MN_CVG_RL to define the minimum-coverage rule.
• MX_CVG_ALWD_AMT, MX_CVG_INCR_ALWD_AMT, MX_CVG_INCR_WCF_ALWD_AMT — maximum coverage and maximum coverage increment ceilings, with the WCF ("without coverage factor") variants.
• MX_CVG_MLT_INCR_NUM, MX_CVG_WCFN_MLT_NUM, MX_CVG_WCFN_AMT — multiplier-based maximum coverage determinants.
• Flags NO_MX_CVG_AMT_APLS_FLAG, NO_MN_CVG_INCR_APLS_FLAG, NO_MX_CVG_INCR_APLS_FLAG — whether the respective minimum/maximum coverage or increment tests are suppressed.
• CVG_INCR_R_DECR_ONLY_CD, LER_ID, PL_ID, PLIP_ID, BUSINESS_GROUP_ID — linkage to the life event, plan, plan-in-plan, and business group contexts.
• Thirty LBR_ATTRIBUTE1–LBR_ATTRIBUTE30 descriptive flexfield columns, plus standard WHO (CREATED_BY, LAST_UPDATED_BY) and OBJECT_VERSION_NUMBER audit columns.

Common Use Cases and Queries

Typical usage includes validating minimum election amounts, reporting restrictions on a plan, and joining restriction data to enrollment results. A representative query retrieving the minimum coverage rule for a plan is:

• SELECT pl_id, mn_cvg_amt, mn_cvg_rl, mx_cvg_alwd_amt FROM apps.ben_ler_bnft_rstrn WHERE ler_id = :p_ler_id AND business_group_id = :p_bg_id;
• SELECT ler_bnft_rstrn_id, mn_cvg_amt FROM apps.ben_ler_bnft_rstrn WHERE no_mx_cvg_amt_apls_flag = 'N';

Because the view applies session-based datetrack filtering, developers should avoid adding their own SYSDATE predicates on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE unless override behavior is intended; doing so can conflict with the built-in FND_SESSIONS logic. When historical or future-dated restriction versions are required, query the base table BEN_LER_BNFT_RSTRN_F directly instead of the view.