Search Results ben_acty_base_rt_f




Overview

The BEN_ACTY_BASE_RT_F table is a core data structure within the Oracle E-Business Suite Advanced Benefits (BEN) module. It serves as the repository for defining and storing the specific values or rates associated with activities that are linked to benefit plans or options. This table is essential for the configuration and execution of benefit calculations, enabling the system to apply precise monetary or percentage-based rules to participant activities. Its role is critical in translating plan design logic into actionable data used during enrollment, life event processing, and compensation-related benefit determinations. As a date-effective table (indicated by the '_F' suffix and the EFFECTIVE_START_DATE/EFFECTIVE_END_DATE columns), it maintains a historical record of how these activity values change over time, supporting complex temporal business rules.

Key Information Stored

The table's primary purpose is to store the linkage between an activity and its associated calculation value. The key columns, as indicated by the provided metadata, include the surrogate primary key ACTY_BASE_RT_ID and the date-effective range columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, which form the composite primary key with ACTY_BASE_RT_ID. Crucially, the table stores foreign key references to other benefit configuration entities. The COMP_LVL_FCTR_ID and TTL_COMP_LVL_FCTR_ID columns link to the BEN_COMP_LVL_FCTR table, allowing the activity rate to be associated with specific compensation level factors. Furthermore, the COST_ALLOCATION_KEYFLEX_ID column links to the PAY_COST_ALLOCATION_KEYFLEX table, enabling the allocation of costs associated with the activity to specific accounting flexfields.

Common Use Cases and Queries

A primary use case is generating reports on the configured values for benefit activities, often for audit or plan analysis purposes. For instance, a benefits administrator may need to list all active activity base rates for a specific plan component. A common SQL pattern involves joining this table to related configuration tables to get descriptive information. When troubleshooting enrollment calculations, technical consultants may query this table to verify the values being applied for a participant's specific effective date. Sample queries often utilize the date-effective structure to find the valid record for a given point in time, using a condition such as SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE. This table is central to any data fix or migration script that modifies the underlying values driving benefit computations.

Related Objects

The BEN_ACTY_BASE_RT_F table has defined foreign key relationships with several other key tables in the EBS data model, as documented in the provided metadata:

  • BEN_COMP_LVL_FCTR: Joined via BEN_ACTY_BASE_RT_F.COMP_LVL_FCTR_ID. This relationship ties the activity rate to a specific compensation level factor definition.
  • BEN_COMP_LVL_FCTR: Also joined via BEN_ACTY_BASE_RT_F.TTL_COMP_LVL_FCTR_ID. This links to a separate, potentially total-based, compensation level factor.
  • PAY_COST_ALLOCATION_KEYFLEX: Joined via BEN_ACTY_BASE_RT_F.COST_ALLOCATION_KEYFLEX_ID. This connects the activity value to the General Ledger cost accounting structure.

These relationships indicate that data in BEN_ACTY_BASE_RT_F is dependent on valid entries in these referenced tables and is a child object within the broader benefits configuration hierarchy.