Search Results ben_prtt_enrt_result_api




Overview
Explore in AI Chat

Overview

APPS.BEN_PRTT_ENRT_RESULT_API is a public PL/SQL API within the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. Its name derives from "Participant Enrollment Result," and it serves as the authoritative programmatic interface for creating, maintaining, and removing participant enrollment result records that link a participant to the benefits in which they are enrolled. Enrollment results are the persistent outcome of benefit processing: whereas elections capture a participant's intent, the enrollment result captures the actual coverage, premium, rate, and covered dependent records that drive payroll deduction, carrier transmission, and reporting. This package therefore acts as the controlled gateway through which enrollment results are written, protecting the underlying tables from direct, unvalidated DML.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions covering the full enrollment lifecycle:

Tables Accessed

The API operates against Benefit core and flexfield tables accessed through APPS synonyms:

Usage Notes

BEN_PRTT_ENRT_RESULT_API is an internal Benefits engine API invoked by the enrollment processing framework rather than called directly by end users. Its dependency list confirms that it is referenced by twenty-nine other packages, including BEN_ENROLLMENT_PROCESS, BEN_MANAGE_DEFAULT_ENRT, BEN_MANAGE_LIFE_EVENTS, BEN_AUTOMATIC_ENROLLMENTS, BEN_CLOSE_ENROLLMENT, and BEN_PROC_COMMON_ENRT_RSLT. It is also the target of the HRDPP_* PL/SQL batch loader entry points (HRDPP_CREATE_PRTT_ENRT_RESULT, HRDPP_UPDATE_PRTT_ENRT_RESULT, HRDPP_DELETE_PRTT_ENRT_RESULT), which support data-pump style loading of enrollment data. It depends on HR_API for person-level validation and STANDARD for standard PL/SQL behavior. Custom code can call this package, but doing so bypasses several framework-level validations and should be undertaken only with a clear understanding of the enrollment result data model; for most integrations the supported approach is to raise enrollment through the standard enrollment process or the HRDPP data loader, allowing this API to be invoked in its intended sequence.