Results for “pay_run_result_values_v3”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_RUN_RESULT_VALUES_V3 is a reporting view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. Its documented purpose is to display all result values produced by the payroll calculation engine in a sparse matrix configuration. In payroll processing, only a subset of element input values is typically populated for any given run result, producing a sparse data set rather than a fully populated grid. This view resolves that sparsity by invoking a server-side function to materialize the actual computed result value for each run result and input value combination, rather than storing pre-computed values in a physical table.

The view serves as a denormalized access point over the core payroll result, input value, assignment action, and payroll action entities. Because the RESULT_VALUE column is derived at query time through the PAY_RUN_RESULT_PKG.GET_RESULT_VALUE function, the view reflects the current state of payroll calculations and is not a snapshot. This makes it suitable for operational reporting, reconciliation, and integration extracts where up-to-date calculated values are required. The view is marked VALID in the ETRM repository and is available in both 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over four synonyms of base tables plus one PL/SQL package, all resolved in the APPS schema:

• PAY_RUN_RESULTS (PRR) — the driving table holding one row per element run result, including RUN_RESULT_ID, ELEMENT_TYPE_ID, ASSIGNMENT_ACTION_ID, and JURISDICTION_CODE.
• PAY_INPUT_VALUES_F (PIV) — the input value definitions for each element type, joined to run results on ELEMENT_TYPE_ID and date-ranged against the payroll action effective date.
• PAY_ASSIGNMENT_ACTIONS (PAA) — links each run result to its parent assignment action via ASSIGNMENT_ACTION_ID.
• PAY_PAYROLL_ACTIONS (PPA) — supplies the parent payroll action, its EFFECTIVE_DATE, and the BUSINESS_GROUP_ID passed to the result value function.
• PAY_RUN_RESULT_PKG — the package whose GET_RESULT_VALUE function computes the RESULT_VALUE at runtime.

The join path is strictly hierarchical: run results to input values by element type, run results to assignment actions, assignment actions to payroll actions, and finally the payroll action effective date constrained within the input value's effective date range. This ensures that only input values valid at the time of the payroll action are considered.

Key Columns

• RUN_RESULT_ID — the unique identifier of the element run result, inherited from PAY_RUN_RESULTS. Serves as the primary correlation key for joining back to payroll result data.
• INPUT_VALUE_ID — the identifier of the input value definition from PAY_INPUT_VALUES_F. Together with RUN_RESULT_ID it forms the logical key of each matrix cell.
• RESULT_VALUE — the calculated value returned by PAY_RUN_RESULT_PKG.GET_RESULT_VALUE for the given run result and input value, qualified by jurisdiction code, input value name, and business group. This is the derived measure of primary interest.

Common Use Cases and Queries

Typical uses include generating element-level payroll registers, reconciling calculated earnings and deductions, and feeding downstream integrations that require raw result values without traversing the balance model.

• Retrieving all populated results for a specific run result.
• Reporting calculated values aggregated by input value across a payroll action.
• Joining to PAY_RUN_RESULTS for assignment-level reporting.

Sample query returning results for a specific run result:

SELECT rrv.RUN_RESULT_ID, rrv.INPUT_VALUE_ID, rrv.RESULT_VALUE FROM APPS.PAY_RUN_RESULT_VALUES_V3 rrv WHERE rrv.RUN_RESULT_ID = :p_run_result_id ORDER BY rrv.INPUT_VALUE_ID;

Because RESULT_VALUE is computed per row through a PL/SQL function call, queries against large payroll populations can incur significant execution cost. Restricting by RUN_RESULT_ID or by joining to a filtered PAY_RUN_RESULTS set is recommended for performance.