Search Results aei_attribute




Overview
Explore in AI Chat

Overview

APPS.BEN_DET_WAIT_PERD_CMPLTN is a PL/SQL package body within the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. Its name reflects its single, narrowly scoped business purpose: Determine Waiting Period Completed Date. The package computes the calendar date on which a participant's waiting period concludes for a given eligibility or plan enrollment context. Waiting periods are a common benefits design element in which an employee becomes eligible only after completing a defined interval of service, employment, or other qualifying condition; this package resolves that interval into a concrete end date used by downstream eligibility and enrollment processing.

The source header records a long maintenance history beginning in 1999, with numbered revisions that document the evolution of the package's behavior. Notable fixes include the introduction of fnd_date.canonical_to_date for formula calls, addition of the business group identifier to the benutils.formula invocation, conditional fetching of plan data only when a plan identifier is supplied, and several corrections concerning inheritance of waiting period codes and retrieval of prior-period/plan waiting period data. This history indicates the package is a mature, stable component in the Benefits calculation chain.

Key Procedures and Functions

The ETRM metadata documents a single entry point: MAIN. Consistent with the package's stated purpose, MAIN drives the determination of the waiting period completion date. It orchestrates retrieval of the participant's assignment and period-of-service information, resolution of the applicable waiting period rule and its associated code, invocation of the Benefits formula or calculation logic where required, and return of the computed completion date to the calling process. Earlier revisions note that benefit assignment data is read from aei_information fields rather than aei_attribute fields, that waiting period codes may be inherited, and that the routine first consults Benefits assignment data and falls back to the core HR assignment when a Benefits assignment cannot be found. MAIN encapsulates these behaviors so that eligibility and enrollment engines obtain a consistent completion date.

Tables Accessed

The package reads from a defined set of applications synonyms:

  • PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, and PER_PERIODS_OF_SERVICE — supply the participant, assignment, and service dates against which a waiting period is measured.
  • PER_ASSIGNMENT_EXTRA_INFO — provides the aei_information attribute values, explicitly identified in the history as the correct source of Benefits assignment data.
  • BEN_PL_F and BEN_OIPL_F — provide plan and plan-in-organization information when a plan identifier is supplied.
  • BEN_PRTN_ELIG_F and BEN_ELIG_TO_PRTE_RSN_F — provide participation eligibility records and the reasons linking eligibility to participation, supporting resolution of the applicable waiting period rule.
  • HR_LOCATIONS_ALL — supports location-based eligibility and calculation context.
  • PLITBLM — the standard Benefits table used for translated or message-related lookups.

Usage Notes

BEN_DET_WAIT_PERD_CMPLTN is an internal Benefits calculation package rather than a public user-facing API; its ETRM classification is OTHER, and the metadata records that it is referenced by one other package, indicating it is invoked from within the Benefits eligibility and enrollment processing chain rather than directly from a form or standalone concurrent program. Typical invocation occurs when the Benefits engine must evaluate whether an eligible person has satisfied a waiting period, most often as a subordinate call from eligibility determination, participation processing, or a Benefits formula that requests the completion date. Custom code should not call MAIN directly unless the calling context reproduces the environment and parameters the package expects. Because the package resolves dates relative to person, assignment, and period-of-service data, retesting is advisable after any change to those records or to the underlying waiting period configuration.