Search Results ben_elp_info_types




Overview
Explore in AI Chat

Overview

BEN_ELP_INFO_TYPES is a configuration table in the BEN (Advanced Benefits) product within Oracle E-Business Suite, holding the definitions of Eligibility Information Types. Each row represents a distinct category of eligibility information — such as an employee's assignment attributes, compensation details, or personal characteristics — that the eligibility engine can evaluate when determining whether a person qualifies for a benefit program, plan type, or plan.

Because the table functions as a controlled reference list of allowable information types rather than as a transactional or associative entity, a Data Vault modeling heuristic would classify it as a standalone object, most consistent with a reference hub. The metadata's relationship mining confirms this classification: the table has no documented foreign key relationships to other BEN tables, and its primary key (BEN_ELP_TYPE_INFO_TYPES_PK on INFORMATION_TYPE) serves as the sole business identifier for each information type definition.

Key Information Stored

The table contains 15 documented columns in the ETRM 12.2.2 schema. The most significant are:

  • INFORMATION_TYPE — the primary key and business-key candidate, uniquely identifying each eligibility information type (for example, an assignment attribute or a personal characteristic).
  • DESCRIPTION — the user-facing name of the information type, used in configuration forms and reports.
  • ACTIVE_INACTIVE_FLAG — controls whether the information type is available for selection in eligibility setup; inactive types remain referenced historically but cannot be used in new definitions.
  • MULTIPLE_OCCURENCES_FLAG — indicates whether the information type can appear more than once in an eligibility rule or criteria group.
  • LEGISLATION_CODE — restricts the information type to a specific legislation or country, enabling global implementations to localize eligibility criteria.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the standard concurrent request and program audit columns recording the process that created or last modified the row.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications framework (OAF) to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the WHO columns providing a full audit trail.

The primary key is a natural (business) key on INFORMATION_TYPE rather than a generated surrogate; there is no separate abstract ID column documented.

Common Use Cases and Queries

Typical usage centers on eligibility configuration validation and reporting against the eligibility engine. Administrators query this table to confirm which information types are active and legislation-appropriate before building or troubleshooting eligibility rules. A common pattern retrieves the active list for a given legislation:

SELECT information_type, description, multiple_occurences_flag
FROM ben.ben_elp_info_types
WHERE active_inactive_flag = 'Y'
AND legislation_code = :p_legislation;

Because INfORMATION_TYPE often appears as a stored code on eligibility criteria and derived-factor tables, joins are performed on that column to resolve the descriptive text. Auditing queries frequently filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent configuration changes, and concurrent-program reconciliation uses PROGRAM_ID and REQUEST_ID to trace how each information type was loaded or seeded.

Related Objects

The ETRM relationship mining classifies BEN_ELP_INFO_TYPES as standalone with no documented foreign keys, so related objects are inferred from the functional role of INFORMATION_TYPE as a code shared with eligibility-definition entities rather than from enforced constraints. The most significant related objects include:

  • BEN_ELIG_INFO_TYPES — the eligibility-side reference of information types available for criteria definitions.
  • BEN_ELIG_DPNT_OT_PL_F and related BEN_ELIG_*_F tables — eligibility rule definitions that store information type codes as criteria.
  • BEN_ELIGY_PRFL and BEN_ELIGY_PRFL_F — eligibility profiles where information type selections drive criteria rows.
  • BEN_PGM_F, BEN_PL_F, and BEN_PL_TYP_F — program, plan, and plan type definitions whose eligibility is evaluated using these information types.
  • FF_FORMULAS_F / FF_FORMULA_TYPES — fast formula definitions that reference information type codes when computing derived eligibility factors.

These relationships are functional join paths on INFORMATION_TYPE rather than enforced referential constraints.