Search Results check_mrtl_sts_elig

Overview

APPS.BEN_CAGR_CHECK_ELIGIBILITY is a PL/SQL package in the Oracle E-Business Suite Benefits module (Oracle Advanced Benefits, sometimes referred to as OAB). It provides the rule-evaluation engine that determines whether a participant satisfies the various eligibility criteria attached to a compensation object, life event, or benefit program. In practical terms, this package answers the question "does this person, in this role, with these attributes, pass the eligibility test?" and returns a boolean indicator that the calling process can act upon.

The package sits within the eligibility subsystem alongside BEN_EVALUATE_ELIG_PROFILES. Where BEN_EVALUATE_ELIG_PROFILES orchestrates the overall eligibility evaluation for a person or group of persons, BEN_CAGR_CHECK_ELIGIBILITY houses the granular, criterion-by-criterion checks. This separation of concerns keeps the higher-level evaluator focused on sequencing and caching, while the detailed validation logic is encapsulated here. The object metadata confirms a bidirectional relationship: BEN_CAGR_CHECK_ELIGIBILITY references BEN_EVALUATE_ELIG_PROFILES (through BEN_CEP_CACHE), and BEN_EVALUATE_ELIG_PROFILES in turn calls BEN_CAGR_CHECK_ELIGIBILITY.

The presence of BEN_CEP_CACHE as a dependency indicates the package participates in the Benefits person/eligibility caching mechanism, which is used to avoid repeated, expensive eligibility evaluations during a given transaction or batch run.

Key Procedures and Functions

The package exposes eleven documented procedures, each targeting a discrete eligibility dimension:

• CHECK_CAGR_ELIG_PROFILES — the principal entry point that drives evaluation of the compensation-object eligibility profiles associated with a participant.
• CHECK_GNDR_ELIG — validates gender-based eligibility rules.
• CHECK_MRTL_STS_ELIG — validates marital-status eligibility rules.
• CHECK_DSBLTY_CTG_ELIG, CHECK_DSBLTY_RSN_ELIG, CHECK_DSBLTY_DGR_ELIG — evaluate disability eligibility by category, reason, and degree respectively.
• CHECK_SUPPL_ROLE_ELIG — evaluates eligibility based on the person's role as a supported dependent or related party.
• CHECK_QUAL_TITL_ELIG — evaluates eligibility based on qualifications or titles held.
• CHECK_PSTN_ELIG — evaluates eligibility based on position.
• CHECK_PRBTN_PERD_ELIG — evaluates eligibility relative to a probation period.
• CHECK_SP_CLNG_PRG_ELIG — evaluates eligibility tied to a special closing program.

Each routine is a self-contained predicate. Callers invoke only the checks relevant to the profile configuration, allowing the evaluator to short-circuit and avoid unnecessary database work.

Tables Accessed

The package reads from several HR and Benefits tables (via APPS synonyms):

• PER_DISABILITIES_F — supplies disability category, reason, and degree data used by the three disability checks.
• PER_QUALIFICATIONS — provides qualification records for CHECK_QUAL_TITL_ELIG.
• PER_ROLES — supplies role information for CHECK_SUPPL_ROLE_ELIG and related role-based tests.
• PLITBLM — a generic lookup/table that supports configuration and reference data used during evaluation.

Because eligibility determinations are read-only assessments, the package predominantly performs SELECTs against these tables. Any write activity would be confined to the Benefits cache (BEN_CEP_CACHE) rather than to the source HR tables.

Usage Notes

This package is not intended to be invoked directly by end users or custom code. It is called internally by BEN_EVALUATE_ELIG_PROFILES during Benefits eligibility processing triggered from the Benefits enrollment forms, the Participation and Eligibility concurrent processes, life-event processing, and batch eligibility runs. Its results feed the list of compensation objects and plans for which a participant is determined eligible.

Customizations should avoid modifying this package, as it is a standard Oracle-owned object. Developers needing to extend eligibility logic should instead define eligibility profiles through the Benefits setup UI. The package is referenced by exactly one other package, confirming its role as a supporting, dependency-driven component rather than a public API. Any troubleshooting of eligibility discrepancies should begin with the profile configuration and the BEN_CEP_CACHE contents rather than with this package's internals.