Search Results pay_element_types_f

Overview

The PAY_ELEMENT_TYPES_F table is the core repository for element definitions within Oracle E-Business Suite Payroll. It represents the fundamental building blocks of compensation and benefits, storing the master definitions for all earnings, deductions, employer liabilities, and non-payroll inputs used in payroll processing. As a date-effective table (indicated by the '_F' suffix and the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns), it maintains a full history of changes to each element's definition over time, allowing for accurate retroactive processing and historical reporting. This table is central to the configuration and operation of the payroll engine, as every payroll calculation references the rules and attributes defined here for each applicable element.

Key Information Stored

The table's structure is designed to define an element's identity, classification, processing rules, and validity. The primary key is a composite of ELEMENT_TYPE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, ensuring unique identification of each element definition across time. Critical columns include ELEMENT_NAME, which, combined with BUSINESS_GROUP_ID, LEGISLATION_CODE, and the effective dates, forms a unique key (PAY_ELEMENT_TYPES_F_UK2). Other essential columns define an element's behavior: CLASSIFICATION_ID links to PAY_ELEMENT_CLASSIFICATIONS (e.g., Earnings, Voluntary Deductions), BENEFIT_CLASSIFICATION_ID links to BEN_BENEFIT_CLASSIFICATIONS for benefits-related elements, and PRORATION_GROUP_ID links to PAY_EVENT_GROUPS to control proration rules. Additional columns (implied by standard practice but not listed in the provided metadata) typically govern reporting, taxation, costing, and processing priorities.

Common Use Cases and Queries

This table is frequently queried for configuration audits, troubleshooting, and building custom payroll reports. A common use case is identifying all active elements for a specific business group and classification. A typical query pattern retrieves the current effective definition:

• SELECT element_name, classification_id, processing_type FROM pay_element_types_f WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date AND business_group_id = &bg_id;

Another critical scenario involves analyzing historical changes to an element's definition for audit purposes, joining the table to itself on ELEMENT_TYPE_ID across different effective date ranges. Developers use this table to validate element existence and attributes before creating element entries via the PAY_ELEMENT_ENTRIES_API or during custom fast formula execution. Reporting often joins PAY_ELEMENT_TYPES_F to transactional tables like PAY_RUN_RESULTS to present earnings or deductions with their descriptive names.

Related Objects

PAY_ELEMENT_TYPES_F sits at the center of a key data model. It has direct foreign key relationships to several configuration tables, as documented: PAY_ELEMENT_CLASSIFICATIONS, BEN_BENEFIT_CLASSIFICATIONS, and PAY_EVENT_GROUPS. It is the parent table for PAY_ELEMENT_ENTRIES_F, which stores instances of these elements assigned to employees. The table is heavily referenced by payroll calculation results in PAY_RUN_RESULTS. For custom development, the primary interface is the PAY_ELEMENT_TYPES_API package, which provides procedures for creating and maintaining element definitions. The standard view PAY_ELEMENT_TYPES_F_VL provides a translatable, user-friendly perspective on this data.