Search Results pay_run_results




Overview
Explore in AI Chat

Overview

The PAY_RUN_RESULTS table is a core transactional table within the Oracle E-Business Suite Payroll module (PAY). It serves as the definitive repository for the output generated from processing a single element entry during a payroll run. Each row in this table represents the calculated result for a specific element, such as regular earnings, a deduction, or a tax, for a specific assignment within a specific payroll run. The table is fundamental to the payroll engine's operation, storing the raw, detailed results that are later aggregated and transferred to other modules for costing, payment, and reporting. Its integrity is critical, as it directly feeds downstream financial and HR processes.

Key Information Stored

While the provided metadata does not list specific columns, based on its role and standard Oracle Payroll architecture, the PAY_RUN_RESULTS table typically contains several key types of data. The primary key is RUN_RESULT_ID, a unique system-generated identifier for each result record. Essential foreign key columns include ASSIGNMENT_ID, linking the result to the employee assignment; ELEMENT_ENTRY_ID, linking to the source element entry that was processed; and RUN_RESULT_ID of a parent result for hierarchical calculations. Crucially, it stores the calculated monetary AMOUNT or RATE, the UNITS (e.g., hours), and the processed DATE_EARNED. Status and context columns, such as STATUS (e.g., 'P', 'PA'), and links to the payroll RUN_ID and ACTION_SEQUENCE for auditing are also standard.

Common Use Cases and Queries

This table is central to payroll troubleshooting, audit reporting, and data extraction. A common use case is investigating the detailed results of a payroll run for an employee to verify calculations. Analysts often join this table to PAY_ELEMENT_ENTRIES_F and PER_ALL_PEOPLE_F to get element and person details. For example, a query to retrieve all run results for a specific payroll run might pattern: SELECT prr.run_result_id, prr.assignment_id, prr.element_entry_id, prr.amount, prr.units, pee.element_type_id FROM pay_run_results prr, pay_element_entries_f pee WHERE prr.element_entry_id = pee.element_entry_id AND prr.run_id = :p_run_id;. Another critical use is sourcing data for custom gross-to-net reports, where PAY_RUN_RESULTS provides the granular line items before they are rolled up into final pay values.

Related Objects

  • PAY_ELEMENT_ENTRIES_F: The source entries that are processed to create run results.
  • PAY_ASSIGNMENT_ACTIONS & PAY_PAYROLL_ACTIONS: These action tables provide the context (run, retro, etc.) and audit sequence for the results.
  • PAY_COSTS: Stores costed results derived from the amounts in PAY_RUN_RESULTS.
  • PAY_RUN_RESULT_VALUES: A child table that stores the individual input/output values for each run result, providing further calculation detail.
  • Key APIs: The PAY_RUN_RESULTS_API package is typically used for validated updates or queries on this table within custom programs.