Search Results ben_dt_trgr_handle




Overview
Explore in AI Chat

Overview

BEN_DT_TRGR_HANDLE is an Oracle Applications (APPS) package body within the Oracle Benefits module of Oracle E-Business Suite. Its name, combining "DT" (date-track) and "TRGR" (trigger), reflects its role as a date-track trigger handler: it encapsulates the logic that responds to date-track events on Benefits-related records, ensuring that changes to a person, assignment, person type usage, period of service, or enrollment result propagate consistently through the benefits data model.

In Oracle EBS, date-tracked entities such as PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_PERIODS_OF_SERVICE maintain multiple dated row versions rather than overwriting records. Changes to these base HR records can invalidate benefits eligibility, enrollment results, and balances. BEN_DT_TRGR_HANDLE centralizes the procedural response to those changes, acting as a coordination layer between the core HR date-track infrastructure (DT_API, HR_API) and the Benefits processing routines. The package is classified as a non-API (OTHER) utility package rather than a public integration API, and it is referenced by approximately twenty other database objects in the APPS schema, indicating it is invoked internally by a range of Benefits programs and packages.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions, grouped by the date-tracked entity they process. No parameter lists are published, so only their functional intent is described here.

  • PERSON — Handles date-track events affecting a person record in PER_ALL_PEOPLE_F, triggering any required downstream benefits reevaluation.
  • ASSIGNMENT — Processes date-track changes to assignment rows in PER_ALL_ASSIGNMENTS_F, which drive eligibility and enrollment outcomes.
  • PERSON_TYPE_USAGES — Responds to changes in person type usage records, since person types determine which benefits programs and plans apply.
  • PERIODS_OF_SERVICE — Handles date-track events on period-of-service records, which influence service-based eligibility and accrual logic.
  • BNFTS_BAL — Coordinates date-track handling for benefits balance records held in BEN_PER_BNFTS_BAL_F.
  • ELIG_CVRD_DPNT — Processes date-track events for eligible covered dependents (BEN_ELIG_CVRD_DPNT_F), reflecting dependent relationship changes.
  • PRTT_ENRT_RSLT — Handles date-track changes affecting participant enrollment results in BEN_PRTT_ENRT_RSLT_F, the central record of who is enrolled in what.

Each entry point isolates the logic for one date-tracked entity, then delegates to shared Benefits utilities and APIs such as BENUTILS, BEN_ASSIGNMENT_API, BEN_ASSIGNMENT_INTERNAL, and the various LER (legislative/regulatory) helper packages (BEN_ASG_LER, BEN_ECD_LER, BEN_PBB_LER, BEN_PEN_LER, BEN_PPF_LER).

Tables Accessed

The package references the following tables through APPS synonyms: BEN_ELIG_CVRD_DPNT_F, BEN_PER_BNFTS_BAL_F, and BEN_PRTT_ENRT_RSLT_F on the Benefits side; and PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_CONTACT_RELATIONSHIPS, PER_PERIODS_OF_SERVICE, PER_PERSON_TYPES, and PER_PERSON_TYPE_USAGES_F on the core HR side. Benefits tables are read and, where the trigger logic requires it, updated to re-evaluate dependents, balances, and enrollment results. The HR tables are read to determine the state of the person, assignment, service period, and person-type usage after a date-track operation, and to identify which Benefits records require adjustment. PER_CONTACT_RELATIONSHIPS is consulted to resolve dependent and beneficiary relationships.

Usage Notes

BEN_DT_TRGR_HANDLE is not intended for direct invocation by end users or external integrations. It is invoked internally when date-track operations occur on the underlying HR and Benefits entities — for example, through hiring, termination, transfer, or assignment update processing that affects a participant's benefits posture. It is also reachable from Benefits configuration and enrollment flows in the Oracle Benefits forms and from concurrent processes that perform date-track maintenance. Custom code should not call this package directly; instead, customers should use the supported Benefits APIs (such as BEN_ASSIGNMENT_API and BEN_PRTT_ENRT_RSLT_F-based APIs) and allow the date-track trigger infrastructure to drive BEN_DT_TRGR_HANDLE. Because the package body is marked VALID and is referenced by numerous APPS objects, modifications are overwritten by patching; any customer extension should be implemented outside the APPS schema.