Search Results ben_pbb_ler




Overview
Explore in AI Chat

Overview

BEN_PBB_LER is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM documentation as an "OTHER" API type. The package name follows the Oracle Advanced Benefits (BEN) naming convention, where the "LER" segment designates the Life Event Registry — the subsystem responsible for detecting, recording, and processing life events that drive eligibility and enrollment changes in participant benefit plans. The "PBB" prefix indicates the package belongs to the Plan/Benefit Base processing tier of the Advanced Benefits architecture, where it serves as a validation and coordination layer for life event records before they are consumed by the broader life event processing engine.

The package holds a VALID status in the ETRM repository for both 12.1.1 and 12.2.2, confirming it is a supported and compiled component of the standard benefits installation. Its business function is to evaluate life event records against participant personal information, contact relationships, and related-person change data, ensuring that only legitimately qualified life events propagate into enrollment and eligibility processing.

Key Procedures and Functions

The documented interface exposes a single callable unit: LER_CHK. Based on its naming and the table footprint, LER_CHK performs life event validation checking — an internal verification routine that evaluates whether a given life event (LER) record satisfies the business rules required for further processing. It operates against the life event registry foundation tables and their associated participant-information and related-person context tables to determine whether the event is valid, complete, and eligible for downstream handling. The routine supports the broader life event trigger mechanism rather than being an end-user facing API, and no formal parameter list is published in the ETRM metadata.

Tables Accessed

BEN_PBB_LER reads from a focused set of applications tables through APPS synonyms:

  • BEN_LER_F — the core life event registry table, providing the primary life event record under evaluation.
  • BEN_LER_PER_INFO_CS_LER_F and BEN_PER_INFO_CHG_CS_LER_F — participant personal information change criteria associated with the life event, used to confirm that the event is driven by a qualifying personal data change.
  • BEN_LER_RLTD_PER_CS_LER_F and BEN_RLTD_PER_CHG_CS_LER_F — related-person change criteria, used when the life event involves a dependent, spouse, or other related participant.
  • BEN_PTNL_LER_FOR_PER — stores potential life events detected for a participant, which the check routine validates before promotion to a full life event.
  • PER_CONTACT_RELATIONSHIPS — the HRMS contact relationship table, used to resolve the relationship between the participant and the related person involved in the event.
  • FND_SESSIONS — the concurrent/forms session context table, used to obtain runtime session information during validation.
  • DUAL — used for scalar evaluations and lightweight PL/SQL logic.

Usage Notes

BEN_PBB_LER is an internal implementation package and is not intended for direct invocation by customers or integrators. It is referenced by BEN_DT_TRGR_HANDLE, the date-tracker trigger handler that drives scheduled life event detection and processing in Advanced Benefits, and by itself (internal recursion or mutual calls within the package body). This dependency chain indicates that BEN_PBB_LER is invoked automatically during life event processing, typically when a participant's personal information or related-person data changes and the system must determine whether a qualifying life event has occurred. It may be reached from the Benefits life event concurrent processes or forms workflows rather than from a standalone submission. Because it is an unsupported internal package, custom code should not call LER_CHK directly; implementers requiring life event validation logic should use the documented Advanced Benefits public APIs instead, and any modification to this package would be overwritten by patching.