Search Results ben_ptd_lmt_f

Overview

The BEN_PTD_LMT_F table is a core data structure within the Oracle E-Business Suite (EBS) Advanced Benefits (BEN) module. It serves as a repository for tracking cumulative period-to-date (PTD) limits for contributions or distributions. This table is essential for managing benefit plans that have defined periodic ceilings, such as annual maximum contribution limits for a Flexible Spending Account (FSA) or a Health Savings Account (HSA). Its role is to store the running totals of amounts used against these limits for participants, ensuring that plan rules and regulatory compliance are maintained throughout the specified period. As a date-effective table (indicated by the '_F' suffix and the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns), it maintains a historical record of limit accumulations, allowing the system to accurately calculate available balances based on the effective date of a transaction.

Key Information Stored

The table's primary purpose is to record cumulative totals against defined limits. The key columns, as indicated by the metadata, include PTD_LMT_ID, which uniquely identifies a period-to-date limit record. The EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns define the date range for which the cumulative total is valid, a standard pattern for tracking historical data in EBS. A critical foreign key is COMP_LVL_FCTR_ID, which links to the BEN_COMP_LVL_FCTR table. This relationship associates the cumulative limit with a specific compensation level factor, which is a rule component used to calculate or define the limit amount based on an employee's compensation, such as a percentage of salary. While the provided metadata does not list all columns, typical data stored would include the cumulative amount used (e.g., CONTRIBUTED_AMOUNT), the period type (e.g., Calendar Year, Plan Year), the associated person, plan, and the specific limit being tracked.

Common Use Cases and Queries

The primary use case is real-time validation during benefit enrollment or payroll processing to prevent over-contributions. For example, before processing a payroll deduction for an FSA, the system queries this table to retrieve the participant's year-to-date total and checks it against the plan's annual maximum. Common reporting involves generating statements for participants showing their used and remaining balances. A typical SQL pattern for retrieving an active record for a specific person and plan would be:

• SELECT ptd.contributed_amount, ptl.limit_amount FROM ben_ptd_lmt_f ptd, ben_ptd_lmt_ptl_f ptl WHERE ptd.person_id = :p_person_id AND ptd.pl_ptd_lmt_id = ptl.pl_ptd_lmt_id AND sysdate BETWEEN ptd.effective_start_date AND ptd.effective_end_date AND ptl.limit_name = 'ANNUAL_FSA_LIMIT';

Administrative queries often summarize totals across populations for plan compliance audits.

Related Objects

The most directly related object, as documented, is the BEN_COMP_LVL_FCTR table, linked via the COMP_LVL_FCTR_ID foreign key. This table defines the compensation-based factors that may determine the limit's value. The BEN_PTD_LMT_F table is also intrinsically linked to benefit plan definition tables, such as BEN_PL_PTD_LMT_F (Plan Period to Date Limit), which stores the master definition of the limit (e.g., the maximum annual amount). The cumulative data in BEN_PTD_LMT_F is populated and updated by key benefits processing engines and APIs, particularly during payroll reconciliation and enrollment processes, which would reference this table to fetch and update running totals.