Search Results ben_batch_elig_info




Overview
Explore in AI Chat

Overview

The BEN_BATCH_ELIG_INFO table is a core data object within the Oracle E-Business Suite (EBS) Advanced Benefits (BEN) module, specifically versions 12.1.1 and 12.2.2. It functions as a transactional log or staging table that temporarily stores eligibility determination results generated during batch processing runs. Its primary role is to capture the outcome of automated eligibility evaluations for benefits, plans, or other program enrollments for one or many participants. This enables the system to efficiently process large volumes of eligibility checks asynchronously, separate from real-time transactions, and provides an auditable record of the batch run's decisions for reporting, troubleshooting, and subsequent action processing.

Key Information Stored

The table's structure is designed to record the essential details of each eligibility evaluation performed in a batch. The primary key, BATCH_ELIG_ID, is a unique system-generated identifier for each record in this log. A critical foreign key column is BENEFIT_ACTION_ID, which links the eligibility result to a specific action defined in the BEN_BENEFIT_ACTIONS table, such as an enrollment or termination. While the provided metadata does not list all columns, typical data stored includes the person or assignment ID being evaluated, the specific plan or benefit type ID, the effective date of the evaluation, the determined eligibility status (e.g., Eligible or Ineligible), and relevant timestamps for the batch run. This creates a snapshot of the "if-then" logic outcome from the complex eligibility rules engine for each processed case.

Common Use Cases and Queries

This table is central to post-batch analysis and reconciliation. Common use cases include auditing batch eligibility results to verify correct rule execution, generating reports on populations deemed eligible or ineligible for a specific benefit offering, and troubleshooting errors where batch outcomes differ from expected results. A frequent query pattern involves joining to person or assignment tables to list eligible individuals. For example, to find all employees made eligible for a specific plan in the latest batch, one might query: SELECT ppf.full_name FROM ben_batch_elig_info bei, per_all_people_f ppf WHERE bei.person_id = ppf.person_id AND bei.plan_id = :p_plan_id AND bei.status = 'ELIGIBLE' AND bei.benefit_action_id = :p_batch_action_id;. Administrators also query this table to clean up or archive records from completed batch processes.

Related Objects

The BEN_BATCH_ELIG_INFO table has a documented foreign key relationship with the BEN_BENEFIT_ACTIONS table, which is fundamental to its operation. The relationship is defined as follows:

  • Foreign Key To: BEN_BENEFIT_ACTIONS
  • Join Column: BEN_BATCH_ELIG_INFO.BENEFIT_ACTION_ID references a record in BEN_BENEFIT_ACTIONS.
This relationship ensures that every batch eligibility record is associated with a defined system action, providing context for why the batch was run (e.g., a new benefits open enrollment). The table is also expected to have implicit relationships with core HR tables (such as PER_ALL_PEOPLE_F or PER_ALL_ASSIGNMENTS_F) via person or assignment ID columns, and with benefits definition tables (like BEN_PL_F) via plan or coverage type IDs, although these are not explicitly listed in the provided metadata.