Search Results delete_enrollment

Overview

APPS.BEN_PRTT_ENRT_RESULT_API is the participant enrollment result application programming interface within the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. It encapsulates the business logic required to create, maintain, void, and delete participant enrollment results — the records that represent what a participant has actually elected or been defaulted into under a benefit program, plan, or option. The package is classified as a public API in the ETRM repository and is referenced by twenty-nine other packages, placing it near the center of the Benefits enrollment processing architecture.

The package body carries a header reflecting a long maintenance lineage, with the skeleton originally derived from the bpapiskl.pkb file and revisions logged from May 1998 onward. Early change entries record the evolution of enrollment logic: the addition and subsequent removal of element entry calls, the replacement of a credit ledger routine with pool accumulation, adjustments to coverage end date handling, and the introduction of the prtt_result OVN as an in/out parameter used to determine action items. This history confirms the package's role as a stable, versioned interface rather than a thin wrapper.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions. The enrollment-level entry points include CREATE_ENROLLMENT, UPDATE_ENROLLMENT, VOID_ENROLLMENT, DELETE_ENROLLMENT, and the warning-enabled variant DELETE_ENROLLMENT_W. These operate on the participant's enrollment as a whole, coordinating the underlying benefits, premiums, rates, and coverage records. At the result level, CREATE_PRTT_ENRT_RESULT, UPDATE_PRTT_ENRT_RESULT, and DELETE_PRTT_ENRT_RESULT manage the individual participant enrollment result rows, which is where the searched term "action_items" is most relevant: the result OVN participates in determining action items that the enrollment engine must resolve.

Several routines support dependent and beneficiary processing. UNHOOK_BNF and UNHOOK_DPNT detach benefit and dependent relationships when an enrollment is terminated or restructured. CALC_DPNT_CVG_DT and DETERMINE_DPNT_CVG_DT_CD derive dependent coverage dates and the corresponding date code, reflecting the rule-driven timing that governs dependent eligibility. CHK_COVERAGE_ACROSS_PLAN_TYPES validates that elections spanning more than one plan type do not violate coverage restrictions. GET_BEN_PEN_UPD_DT_MODE returns the update-date processing mode applicable to the benefit record. LCK performs the locking operation used to serialize concurrent modification, and MULTI_ROWS_EDIT handles set-based edits across multiple result rows. UPDATE_PERSON_TYPE_USAGES maintains the person type usage records associated with the enrollment facts.

Tables Accessed

The package reads and writes the core Benefits enrollment tables through APPS synonyms. BEN_ENRT_BNFT, BEN_ENRT_PREM, and BEN_ENRT_RT store the benefit election, premium, and rate rows that constitute the posted enrollment. BEN_ELIG_PER_ELCTBL_CHC, BEN_ELIG_CVRD_DPNT_F, BEN_ELIG_DPNT, and BEN_ACRS_PTIP_CVG_F hold eligibility, electable choice, and covered dependent data used for validation and date derivation. BEN_LER_F, BEN_LER_CHG_DPNT_CVG_F, BEN_LEE_RSN_F, and BEN_LE_CLSN_N_RSTR provide the life event reason, dependent coverage change, and classification restriction context that drives enrollment actions. BEN_BNFT_PRVDD_LDGR_F and BEN_OIPL_F support benefit provided ledger and other input plan line processing, while BEN_ACTY_BASE_RT_F supplies activity-based rate information and BEN_EXT_CHG_EVT_LOG captures external change event logging.

Usage Notes

BEN_PRTT_ENRT_RESULT_API is typically invoked from the Benefits enrollment forms, from lifecycle and life event concurrent programs, and from batch processes that perform default enrollments, coverage recalculation, and open enrollment updates. Because the package is referenced by twenty-nine other packages, custom code should call the documented API entry points rather than updating the underlying BEN tables directly, ensuring that action items, OVN locking, and dependent coverage derivations are applied consistently. When extending enrollment behavior, developers should respect the warning parameters that several procedures expose and honor the result OVN contract, since it governs whether downstream action item determination is triggered.