Search Results ben_ecd_ler




Overview

BEN_ECD_LER is an Oracle Applications (APPS) PL/SQL package belonging to the Oracle Advanced Benefits (OAB) module of Oracle E-Business Suite. Its status is documented as VALID in both the 12.1.1 and 12.2.2 releases, and its API classification within the ETRM repository is listed as OTHER, indicating that it is an internal engine component rather than a public, externally supported API.

The package name and its dependency footprint indicate that it operates within the Life Event Registry (LER) processing framework. Life events drive eligibility re-evaluation and enrollment result regeneration in OAB — for example, marriage, birth, hire, or termination trigger changes that must be detected against a participant's recorded life events and related persons. BEN_ECD_LER provides the run-time logic that evaluates whether life event data satisfies the conditions defined for a given event, and it is invoked by the trigger-handling layer rather than called directly by end users. The "ECD" prefix aligns the object with the event-change-detection family of packages that support the Benefits enrollment cycle.

Key Procedures and Functions

Only one documented entry point is exposed: LER_CHK. Based on the documented metadata, LER_CHK performs the life event check — that is, it evaluates life event and participant information to determine whether the conditions associated with a life event have been met. It is not a public API with a published signature; it is consumed internally by the Benefits trigger and event processing stack.

  • LER_CHK — Validates or checks life event (LER) criteria for a participant. Its exact parameter list is not documented in the ETRM record and should not be assumed.

No other procedures or functions are documented for this package. Callers should obtain the actual signature from the package specification in the target environment before attempting any dependency.

Tables Accessed

The package reads from and writes to the following tables through APPS synonyms. Access patterns reflect its role in life event evaluation and enrollment result processing:

  • BEN_LER_F — The Life Event Registry master table; supplies the life event definitions and processing rules being checked.
  • BEN_PTNL_LER_FOR_PER — Potential life events for a person; the primary input set that LER_CHK evaluates.
  • BEN_LER_PER_INFO_CS_LER_F, BEN_LER_RLTD_PER_CS_LER_F, BEN_PER_INFO_CHG_CS_LER_F, BEN_RLTD_PER_CHG_CS_LER_F — The person-information and related-person change tables that hold the criteria columns (CS) used to determine whether a participant's or related person's data change satisfies a life event.
  • BEN_PRTT_ENRT_RSLT_F — Participant enrollment results, potentially read or updated as a consequence of a validated life event.
  • PER_CONTACT_RELATIONSHIPS — HR contact/relationship data used to resolve related persons (dependents, spouses, beneficiaries) within the life event context.
  • FND_SESSIONS — Oracle Application Object Library session context, used to establish environment and session attributes during execution.
  • DUAL — Utility access for scalar evaluations.

Usage Notes

BEN_ECD_LER is not intended for direct invocation from forms, concurrent programs, or customer extensions. The documented dependency graph shows that it is referenced by BEN_DT_TRGR_HANDLE and is self-referenced within the BEN_ECD_LER package body, confirming it is a subordinate component of the date-trigger handling mechanism. It is therefore executed implicitly during life event processing — typically when the Benefits engine processes a date-tracked trigger that requires validation of life event criteria.

Custom code should not call LER_CHK directly; the supported integration points for Benefits events are the public OAB APIs. Any modification, tracing, or extension affecting this package should be handled through standard Oracle support channels, since altering internal engine packages can compromise enrollment result integrity and invalidate support. DBAs investigating life event processing issues may trace this package to diagnose why a particular event was or was not detected.