Results for “ler_attribute1”

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

Overview

BEN_LER is an APPS-owned database view in the Oracle Advanced Benefits (BEN) module, exposed for reporting and integration against Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents the "learned/eligibility rule" definition records stored in the Advanced Benefits configuration tables, resolving the underlying base table BEN_LER_F through a date-effective filter. The name reflects the "Learned Eligibility Rule" concept, and the view's association with the column LER_EVAL_RL — the string matched by the user search term "ler_eval_rl" — confirms that this view is the primary access path for eligibility rule evaluation logic.

The view is defined so that only rows whose effective date range brackets the current application session's effective date are returned. This makes BEN_LER a session-aware view: the WHERE clause joins to FND_SESSIONS on USERENV('SESSIONID') and compares EFFECTIVE_START_DATE and EFFECTIVE_END_DATE against the session's EFFECTIVE_DATE. As a result, callers automatically see the rule version in force on the business date the session is operating under, rather than the latest or system-date version.

Underlying Base Objects

Per the documented 12.2.2 metadata, BEN_LER is defined exclusively over two referenced objects, both resolved as synonyms in the APPS schema:

• BEN_LER_F — the base table holding the learned eligibility rule definitions, including the datetracked effective start and end dates. All columns selected by BEN_LER originate from this table (aliased LER).
• FND_SESSIONS — the standard EBS sessions table, used solely to obtain the effective business date associated with the current USERENV('SESSIONID').

The defining SELECT projects the full LER column set — key identifiers, codes, flags, 30 descriptive attribute pairs, audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER), and the date-effective columns. The view therefore provides a public, session-filtered interface over BEN_LER_F, insulating consumers from the datetrack predicate.

Key Columns

• LER_ID — primary key identifying the learned eligibility rule.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — datetrack range delimiting the rule version; these drive the session filter.
• LER_EVAL_RL — the eligibility evaluation rule expression, the core logic evaluated at enrollment or qualification time; this is the column most frequently referenced when searching "ler_eval_rl".
• NAME / SHORT_NAME / SHORT_CODE — human-readable identification of the rule.
• TYP_CD — the rule type classification.
• CK_RLTD_PER_ELIG_FLAG — indicates whether related-person eligibility checking is enabled.
• CM_APLY_FLAG, OVRIDG_LE_FLAG, QUALG_EVT_FLAG — control flags governing rule application, override behavior, and qualifying events.
• WHN_TO_PRCS_CD — the processing point at which the rule is invoked.
• LER_STAT_CD — status code of the rule (active/inactive).
• TMLNS_* and OCRD_DT_DET_CD — timeline evaluation and occurrence-date determination settings.
• LER_ATTRIBUTE1–30, DESC_TXT — descriptive flexfield segments and free-text description.

Common Use Cases and Queries

BEN_LER supports eligibility rule diagnostics, configuration migration, and custom reporting. Typical queries retrieve the active rule version for a session or trace how a particular rule is defined:

SELECT ler_id, name, ler_eval_rl, ler_stat_cd
FROM apps.ben_ler
WHERE ler_stat_cd = 'A';

To inspect evaluation logic for a specific rule by name:

SELECT name, ler_eval_rl, effective_start_date, effective_end_date
FROM apps.ben_ler
WHERE name LIKE :rule_name;

Because the view enforces the session-effective predicate, no additional datetrack handling is required. Note that outside an active EBS session context (for example, in a standalone SQL*Plus connection without an initialized FND_SESSIONS row), the subquery may return no rows; in such cases, query BEN_LER_F directly and apply explicit date filters.