Search Results run_result_id




Overview
Explore in AI Chat

Overview

The HR.PAY_RUN_RESULT_VALUES table is a core transactional table within the Oracle E-Business Suite (EBS) Human Resources (HR) and Payroll modules, specifically in releases 12.1.1 and 12.2.2. It serves as the definitive repository for the calculated or entered values generated during a payroll run for individual element entries. Each time a payroll process executes, it creates run results for earnings, deductions, and other elements. This table stores the specific input values associated with those results, such as the monetary amount for a salary, the number of hours for a time entry, or a calculated tax value. Its primary role is to persist the detailed output of payroll calculations, forming the essential link between an element entry's definition (via INPUT_VALUE_ID) and its processed outcome in a specific payroll run (via RUN_RESULT_ID).

Key Information Stored

The table's structure is designed to capture the critical components of a payroll result value. The primary key is a composite of INPUT_VALUE_ID and RUN_RESULT_ID, ensuring a unique record for each input value of a specific run result. Key columns include:

  • RUN_RESULT_ID: The foreign key to PAY_RUN_RESULTS, identifying the specific payroll calculation instance this value belongs to. This is the primary column for queries tracing all outputs from a single payroll run entry.
  • INPUT_VALUE_ID: The foreign key to PAY_INPUT_VALUES, defining what type of data is stored (e.g., "Pay Value", "Units", "Rate").
  • RESULT_VALUE (VARCHAR2(60)): The actual calculated or entered data, such as '500.00' or '40'.
  • FORMULA_RESULT_FLAG (VARCHAR2): A flag indicating whether the RESULT_VALUE was derived from a Fast Formula calculation, which is crucial for auditing and understanding the source of the value.
  • INSTANCE_ID (NUMBER): An enhancement for Release 12.2 related to Real Application Clusters (RAC) affinity, used for tracking and optimizing database instance sessions.

Common Use Cases and Queries

This table is central to payroll reporting, auditing, and data correction. A primary use case is investigating the detailed breakdown of an employee's payslip or a specific payroll run. For example, to retrieve all calculated values for a particular run result, a query would join PAY_RUN_RESULT_VALUES with PAY_INPUT_VALUES to get descriptive names. Another critical scenario is tracing the origin of costs posted to General Ledger, as cost results are also stored here. A common audit pattern is to identify values calculated by formulas versus those entered manually.

Sample Query: Retrieving all result values for a specific payroll run entry, including the input value name.

SELECT piv.NAME input_value_name,
       prrv.RESULT_VALUE,
       prrv.FORMULA_RESULT_FLAG
FROM   pay_run_result_values prrv,
       pay_input_values piv
WHERE  prrv.run_result_id = :p_run_result_id
AND    prrv.input_value_id = piv.input_value_id
ORDER BY piv.NAME;

Related Objects

PAY_RUN_RESULT_VALUES sits at the intersection of key payroll tables, as defined by its foreign key relationships. It is directly referenced by the following object:

  • PAY_COSTS: The table stores costing results derived from payroll runs. It references PAY_RUN_RESULT_VALUES via the foreign key columns (INPUT_VALUE_ID, RUN_RESULT_ID) to link a specific cost entry back to the original calculated payroll value that generated it. This relationship is fundamental for cost allocation and reconciliation between payroll and financials.

The table itself has two critical foreign key dependencies:

  • PAY_RUN_RESULTS (via RUN_RESULT_ID): The parent record identifying the element entry within a payroll run.
  • PAY_INPUT_VALUES (via INPUT_VALUE_ID): The definition of what the result value represents.
The non-unique index PAY_RUN_RESULT_VALUES_N50 on RUN_RESULT_ID optimizes queries filtering or joining on this highly selective column.