Results for “ben_lee_rsn_d”

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

Overview

The BEN_LEE_RSN_D view is a read-only dictionary object owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits (BEN) module. It is a descriptive (non-date-tracked) view over the "Length of Enrollment Reason" entity, which defines the rules governing how long an enrollment, coverage, or rating period persists for a given enrollment cycle. The view exposes configuration metadata used by the Benefits enrollment engine to determine start and end dates for coverage and rating periods, together with lag/lead rules and processing grace windows.

For implementers and technical consultants, the view serves as a convenient, flattened read interface that avoids navigating the underlying "_F" (base table) directly and applies no row-level filtering by default beyond what the base table provides. It is commonly referenced in benefit data extraction, configuration audits, and integration interfaces that need to surface enrollment-cycle timing rules. The object is documented in ETRM as VALID for 12.1.1 and 12.2.2 and is classified as Oracle Proprietary, Confidential Information.

Underlying Base Objects

The view is defined as a direct projection of the BEN_LEE_RSN_F synonym, with no joins, unions, or aggregation applied. The documented DDL is a straightforward SELECT ... FROM BEN_LEE_RSN_F LEN that aliases the base entity as LEN and returns all of its functional and administrative columns in full.

• BEN_LEE_RSN_F (SYNONYM) — the primary base object supplying every column exposed by the view. It stores the length-of-enrollment reason definition records, keyed by LEE_RSN_ID and effective-dated via EFFECTIVE_START_DATE / EFFECTIVE_END_DATE.
• FND_USER (SYNONYM) — referenced indirectly through the audit columns CREATED_BY and LAST_UPDATED_BY, which store user IDs resolvable against FND_USER for who-did-what reporting.

Because the view adds no transformation logic, any DML restrictions, row-level security from Business Group (BUSINESS_GROUP_ID), and multi-org behavior are inherited from the base table.

Key Columns

The columns most relevant to enrollment setup and to the search term enrt_cvg_end_dt_cd are summarized below.

• LEE_RSN_ID — primary key of the length-of-enrollment reason record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — effective-dating range for the rule definition.
• BUSINESS_GROUP_ID — owning Business Group, used for multi-org scoping.
• POPL_ENRT_TYP_CYCL_ID — the enrollment type cycle to which the rule applies.
• LER_ID — the length-of-enrollment rule foreign key linking the reason to its rule definition.
• ENRT_CVG_END_DT_CD / ENRT_CVG_STRT_DT_CD — codes determining how coverage end and start dates are derived; paired with ENRT_CVG_END_DT_RL and ENRT_CVG_STRT_DT_RL to express the relative offset values.
• ENRT_PERD_STRT_DT_CD / ENRT_PERD_END_DT_CD and their _RL counterparts — how the enrollment period boundaries are calculated.
• ENRT_PERD_DET_OVRLP_BCKDT_CD — controls backdating for overlapping enrollment period details.
• RT_STRT_DT_CD / RT_END_DT_CD and _RL columns — rating period start and end derivation rules.
• CLS_ENRT_DT_TO_USE_CD — identifies which date (e.g., coverage start, enrollment period start) to use when processing a life event.
• ADDL_PROCG_DYS_NUM, DYS_AFTR_END_TO_DFLT_NUM, DYS_NO_ENRL_NOT_ELIG_NUM, DYS_NO_ENRL_CANT_ENRL_NUM — numeric grace and processing window attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical scenarios include validating how coverage end dates are computed for a plan cycle, auditing configurations across Business Groups, and extracting rule data into downstream reporting. A representative query isolating the coverage end-date rule is:

SELECT lee_rsn_id, popl_enrt_typ_cycl_id, enrt_cvg_end_dt_cd, enrt_cvg_end_dt_rl
FROM apps.ben_lee_rsn_d
WHERE enrt_cvg_end_dt_cd IS NOT NULL
AND business_group_id = :p_bg_id
AND TRUNC(SYSDATE) BETWEEN effective_start_date AND NVL(effective_end_date, TRUNC(SYSDATE));

To join audit information to user names, combine the view with FND_USER on last_updated_by = user_id. For configuration audits, aggregate by POPL_ENRT_TYP_CYCL_ID to detect cycles lacking a defined coverage end-date rule. Because the view is effectively-dated, always constrain queries to the current effective range unless historical analysis is required.