Results for “eiv_attribute2”

30 results




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

Overview

BEN.BEN_EXTRA_INPUT_VALUES is a table within the Oracle Advanced Benefits (BEN) module. It stores extra input values associated with a standard rate. In Oracle EBS 12.1.1 and 12.2.2, rates used by benefits plan configurations—such as those attached to activity base rates—can be defined with ancillary inputs beyond the primary numeric rate. This table persists those supplementary inputs, capturing textual values, return variable names, and a wide set of descriptive attributes. Its role is to complete the definition of a rate by holding the additional parameters that plan processing, eligibility, or rate calculation logic may consume.

From a data-modeling perspective, the mined relationship metadata classifies BEN_EXTRA_INPUT_VALUES as standalone with a heuristic Data Vault classification of standalone. This should be read as a modeling suggestion rather than a validated warehouse design: the table carries its own surrogate key and does not exhibit a strong foreign-key dependency chain in the documented structure, which means it may be treated as a self-contained satellite-like entity. The single documented unique index, BEN_EXTRA_INPUT_VALUES_PK on EXTRA_INPUT_VALUE_ID, confirms the primary key and no other business-key candidate is documented.

Key Information Stored

The table exposes 44 documented columns. The most significant are:

The surrogate key is distinct from any business key; no alternate unique index is documented beyond the primary key, so business meaning flows through ACTY_BASE_RT_ID, INPUT_VALUE_ID, and the attribute columns rather than a separate unique constraint.

Common Use Cases and Queries

Typical applications include auditing the supplemental inputs behind a standard rate, validating DFF attribute usage, and reporting on rate configuration for benefits plans. A representative query retrieves all extra inputs for a given activity base rate:

  • SELECT EXTRA_INPUT_VALUE_ID, ACTY_BASE_RT_ID, INPUT_VALUE_ID, INPUT_TEXT, RETURN_VAR_NAME FROM BEN.BEN_EXTRA_INPUT_VALUES WHERE ACTY_BASE_RT_ID = :p_base_rt_id;
  • Filtering by business group for multi-organization reporting: WHERE BUSINESS_GROUP_ID = :p_bg_id.
  • Inspecting DFF data: SELECT EIV_ATTRIBUTE_CATEGORY, EIV_ATTRIBUTE1, EIV_ATTRIBUTE2 FROM BEN.BEN_EXTRA_INPUT_VALUES WHERE EXTRA_INPUT_VALUE_ID = :p_id;
  • Trending configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

These patterns support reconciliation of rate definitions and troubleshooting of benefits calculation discrepancies.

Related Objects

Because the documented FK structure marks this table as standalone, joins are driven primarily by the ACTY_BASE_RT_ID and INPUT_VALUE_ID columns rather than by enforced constraints. Significant related objects include: