Search Results enb_adjustments




Overview
Explore in AI Chat

Overview

The APPS.BEN_EFC_ADJUSTMENTS package is an internal Oracle E-Business Suite Advanced Benefits (OLTP) PL/SQL construct that supports the processing of Element and Function Cost (EFC) adjustments within the BEN schema. It belongs to the Benefits functional family and is classified under API classification OTHER, indicating it is a supporting internal package rather than a published public API. Its principal business purpose is to construct, populate, and validate the data structures that feed the EFC enrollment and premium adjustment processing performed during benefits life events, enrollment, and rate determination. In EBS 12.1.1 and 12.2.2 it is present with a VALID status.

The package works alongside BEN_DETERMINE_RATES and BEN_MANAGE_LIFE_EVENTS, and it produces records that are consumed by the self-referencing overloads BEN_EFC_ADJUSTMENTS and BEN_EFC_ADJUSTMENTS1, as well as by BEN_EFC_REPORTING and BEN_EFC_VALIDATION. This places it in the middle of the benefit calculation pipeline, bridging eligibility/enrollment facts with the rate and cost results returned to the user interface and the reporting layer.

Key Procedures and Functions

The documented interface exposes 16 procedures and functions, which divide naturally into three groups.

  • DETECT* procedures — DETECTAPPERROR, DETECTWHOINFO, DETECTPILINFO, DETECTBCOLROWINFO, DETECTEPEENBINFO, DETECTVAPROINFO, DETECTROUNDINFO, DETECTCONVINFO and DETECTINVASG. These routines inspect the enrollment/premium context and detect specific conditions — application errors, WHO-column metadata, PIL (plan-in-list) information, benefit column/row descriptors, EPE enrollment benefit values, variable-rate profile information, rounding rules, currency conversion details, and invalid assignments. Each returns or signals the presence or state of that attribute so downstream logic can react accordingly.
  • Session and validation support — INSERT_FNDSESSION_ROW inserts a row into the FND session structure used to track the current processing context; INSERT_VALIDATION_EXCEPTIONS persists validation exceptions raised during adjustment detection so they can be surfaced or audited.
  • Adjustment calculation routines — PEP_ADJUSTMENTS, EPO_ADJUSTMENTS, ENB_ADJUSTMENTS, EPR_ADJUSTMENTS and ECR_ADJUSTMENTS. These correspond to the adjustment categories used in EFC processing: person eligibility/plan (PEP), person option (EPO), enrollment benefit (ENB), enrollment premium (EPR) and enrollment coverage/rate (ECR). Each routine computes or recomputes the relevant adjusted amounts and writes them back into the benefit processing structures.

Tables Accessed

The package reads and writes through APPS synonyms for the following base tables. Design-time and eligibility data come from BEN_ELIG_PER_F, BEN_ELIG_PER_OPT_F, BEN_ELIG_PER_ELCTBL_CHC, BEN_EFC_EXCLUSIONS and BEN_VRBL_RT_PRFL_F. Enrollment and premium facts are drawn from BEN_ENRT_BNFT and BEN_ENRT_PREM, with actual premium and rate data supplied by BEN_ACTL_PREM_F, BEN_ACTL_PREM_VRBL_RT_F, BEN_ACTY_BASE_RT_F, BEN_ACTY_VRBL_RT_F and BEN_BNFTS_BAL_F. Calculation method metadata is retrieved from BEN_CVG_AMT_CALC_MTHD_F and BEN_COMP_LVL_FCTR, and assignment context is sourced from PER_ALL_ASSIGNMENTS_F. These tables collectively supply the coverage amounts, variable rates, compensation factors and balances required to derive adjusted cost figures.

Usage Notes

BEN_EFC_ADJUSTMENTS is not intended for direct customer invocation; it is invoked internally by the Benefits engine whenever EFC adjustments must be derived during enrollment, life-event processing, or rate recalculation. Its public-facing entry points are the overloaded BEN_EFC_ADJUSTMENTS and BEN_EFC_ADJUSTMENTS1 packages, and its output is consumed by BEN_EFC_REPORTING for display and by BEN_EFC_VALIDATION for consistency checks. Custom code should treat this package as read-only and avoid calling it directly, because its signatures and internal logic are not part of Oracle's supported API surface. Any change to underlying tables, eligibility rules, or calculation methods that affects EFC data will be reflected automatically when the package executes, so no client-side modification is required. When troubleshooting adjustment discrepancies, DBAs typically trace execution through the DETECT* routines and the INSERT_VALIDATION_EXCEPTIONS call to identify which validation condition produced the exception.