Search Results pay_run_result_values

Overview

The PAY_RUN_RESULT_VALUES table is a core transactional table within the Oracle E-Business Suite Payroll module (PAY). It serves as the definitive repository for the calculated monetary and non-monetary results generated from processing a single element entry during a payroll run. For each input value defined for an element, this table stores the final computed figure, such as a payment amount, hours worked, or a rate. Its primary role is to persist the granular output of the payroll calculation engine, forming the essential link between an employee's earnings or deduction entries (run results) and their specific calculated values. This data is foundational for generating payroll registers, costing reports, and payslips, and is critical for audit trails and retroactive payroll processing.

Key Information Stored

The table's structure is centered on uniquely identifying a specific calculated result and its value. The primary key is a composite of RUN_RESULT_ID and INPUT_VALUE_ID. The RUN_RESULT_ID column links to the PAY_RUN_RESULTS table, identifying the specific instance of an element entry processed in a payroll run. The INPUT_VALUE_ID column links to the PAY_INPUT_VALUES_F table, defining what type of data is stored (e.g., "Pay Value", "Units", "Rate"). The most critical column is typically the RESULT_VALUE column, which holds the actual calculated number. Other supporting columns may include contexts for legislative or reporting purposes, creation dates, and identifiers for the source action that generated the value, though these are not detailed in the provided metadata excerpt.

Common Use Cases and Queries

A primary use case is the extraction of payroll results for reporting, such as creating a detailed payroll register. Analysts and developers query this table to retrieve all payment and deduction amounts for a specific payroll run or employee. Another critical use is in cost allocation, as the table feeds into the PAY_COSTS table. Common SQL patterns involve joining to PAY_RUN_RESULTS, PAY_ELEMENT_ENTRIES_F, and PAY_INPUT_VALUES_F to get a human-readable report. For example, to find an employee's regular earnings from a specific payroll run, one would join PAY_RUN_RESULT_VALUES to PAY_RUN_RESULTS via RUN_RESULT_ID, filter by the relevant element name via PAY_ELEMENT_ENTRIES_F, and select the RESULT_VALUE where the INPUT_VALUE_ID corresponds to "Pay Value".

Related Objects

The table maintains integral relationships with other key payroll tables, as indicated by its foreign keys. Its primary relationship is with PAY_RUN_RESULTS (via RUN_RESULT_ID), which provides the header-level context for the element entry. It is also linked to PAY_INPUT_VALUES_F (via INPUT_VALUE_ID) to describe the meaning of the stored result. Crucially, the documented foreign key relationship shows that PAY_RUN_RESULT_VALUES is a parent table to PAY_COSTS. The PAY_COSTS table references PAY_RUN_RESULT_VALUES using the composite key of RUN_RESULT_ID and INPUT_VALUE_ID, meaning the calculated result values are directly used to generate payroll cost distributions. This relationship is essential for transferring payroll results to the General Ledger.