Search Results ben_ptd_bal_typ_f




Overview
Explore in AI Chat

Overview

The BEN_PTD_BAL_TYP_F table is a core data object within the Oracle E-Business Suite Advanced Benefits (BEN) module. It functions as a definitional table that stores the valid balance types tracked on a period-to-date (PTD) basis. In the context of compensation and benefits management, a period-to-date balance represents an accumulating total for a specific benefit or compensation element (e.g., vacation hours accrued, bonus paid) within a defined time period, such as a payroll period, quarter, or fiscal year. This table is effective-dated, as indicated by the '_F' suffix and the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, allowing for the historical tracking of balance type definitions as they change over time. Its primary role is to serve as a master reference for configuring and calculating various employee benefit and compensation balances.

Key Information Stored

The table's structure centers on identifying a balance type and its temporal validity. The primary key is a composite of PTD_BAL_TYP_ID and EFFECTIVE_START_DATE. The PTD_BAL_TYP_ID is the unique identifier for a specific period-to-date balance type definition. The EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns define the date range during which that particular definition is active and valid for use. A critical foreign key column is COMP_LVL_FCTR_ID, which links the balance type to a specific compensation level factor defined in the BEN_COMP_LVL_FCTR table. This relationship is essential for determining the compensation basis or level (e.g., salary, grade) against which the balance calculation may be performed.

Common Use Cases and Queries

This table is primarily referenced during the setup and administration of benefit plans and compensation components. Common use cases include configuring a new accrual plan (like sick leave) that requires tracking a PTD balance, or generating reports that list all active balance types. A typical administrative query would retrieve all currently effective balance types along with their associated compensation level factors. A sample SQL pattern for such a report would be:

  • SELECT ptd.PTD_BAL_TYP_ID, ptd.COMP_LVL_FCTR_ID, clf.NAME, ptd.EFFECTIVE_START_DATE
  • FROM BEN_PTD_BAL_TYP_F ptd, BEN_COMP_LVL_FCTR clf
  • WHERE SYSDATE BETWEEN ptd.EFFECTIVE_START_DATE AND NVL(ptd.EFFECTIVE_END_DATE, SYSDATE)
  • AND ptd.COMP_LVL_FCTR_ID = clf.COMP_LVL_FCTR_ID
  • AND SYSDATE BETWEEN clf.EFFECTIVE_START_DATE AND NVL(clf.EFFECTIVE_END_DATE, SYSDATE);

This table is also integral to the background engine calculations that populate actual employee balance records.

Related Objects

The BEN_PTD_BAL_TYP_F table has documented foreign key relationships with other core Benefits tables. The primary relationship, as per the provided metadata, is with the BEN_COMP_LVL_FCTR table. The join is performed on the column BEN_PTD_BAL_TYP_F.COMP_LVL_FCTR_ID, which references the compensation level factor. This links each period-to-date balance type definition to a specific method of calculating compensation levels. While not listed in the provided excerpt, it is standard for this definition table to be referenced by transactional tables that store the actual calculated balance amounts for employees, such as those with names like BEN_PTD_BALANCES_F or similar, which would use PTD_BAL_TYP_ID as a foreign key.