Results for “ben_determine_actual_premium”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.BEN_DETERMINE_ACTUAL_PREMIUM is a PL/SQL package within the Oracle E-Business Suite Advanced Benefits (Oracle Benefits) module. Its stated purpose, per the package header, is to "determine the actual premium used for rates calculations." In the benefits processing model, a participant may be enrolled in a plan, option, or program whose rate structure is not the one actually charged; premium redirection, imputed income, and other adjustments require the application to resolve the true or "actual" premium before amounts can be calculated. This package encapsulates that resolution logic and stores computed results for downstream use.

The package is owned by APPS and is classified as OTHER in the ETRM repository for release 12.2.2. The header carries the revision marker benacprm.pkh 120.1.12010000.1, and the change history spans from the original creation in April 1997 through the addition of the g_computed_prem_tbl PL/SQL table under bug fix 6330056. Notably, the history records that premium computation was broken into a separate procedure so it could be invoked independently (bug 1166174), and that a p_mode parameter was added in November 2004 so the same routine could serve calculation-only scenarios.

Key Procedures and Functions

• COMPUTE_PREMIUM — The core computation routine. It resolves the actual premium, including total premium changes noted in the package history, and writes the computed value to the package global g_computed_prem_val (of type ben_enrt_prem.val%type) so that callers, particularly in calculation mode, can retrieve the amount without a corresponding ele_chc_id or benefit row being inserted. The addition of g_computed_prem_tbl expands this to handle cases where multiple calculated premium values must be captured. Parameter lists are not enumerated here; the routine accepts the prerequisite values either from existing election context or passed explicitly when the required choice is unavailable.
• MAIN — The entry point that drives the determination process, orchestrating the inputs required by COMPUTE_PREMIUM and controlling the mode of execution.

Tables Accessed

• BEN_ACTL_PREM_F — Stores actual premium rows produced by the determination process, forming the persistent output of the routine.
• BEN_ENRT_PREM and BEN_ENRT_PREM_S — Enrollment premium records and their alternate-key/seed counterpart, supplying the enrolled premium amounts and date-tracked premium definitions against which actual premiums are derived.
• BEN_ELIG_PER_ELCTBL_CHC — The electable choice definition for the person's eligibility record; the authoritative source for which plan or option the participant may and does elect.
• BEN_ENRT_BNFT — Enrollment benefit lines providing the top-level enrollment context.
• BEN_OIPL_F — The organization/plan linkage, used to resolve the plan and related processing attributes.
• PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES — Person, assignment, and assignment status data, used for eligibility, payroll, and location-dependent rate resolution.
• HR_LOCATIONS_ALL and PER_ADDRESSES — Location and address information that can drive geographic rating or jurisdiction-specific premiums.
• PLITBLM — The standard PL/SQL index-by table type used for passing and buffering multiple values internally.

Usage Notes

The package is a server-side engine, not a user-facing screen. It is invoked by Benefits forms and concurrent processes during enrollment processing, rate calculation, and premium/flex credit calculation, and it is referenced by six other packages in the APPS schema. In custom development, it should be called only after the standard enrollment and eligibility APIs have established an electable choice context; callers requiring only a projected amount should use the calculation mode associated with p_mode and read g_computed_prem_val or g_computed_prem_tbl rather than expecting a committed actual premium row. Because the package declares AUTHID CURRENT_USER and accesses many date-tracked and public-synonym objects, custom callers should ensure their session has the appropriate APPS-level privileges and initialization, and should avoid assuming the parameter signature — it has evolved across releases and the ETRM metadata records only the two documented entry points.