Search Results pay_run_results_s




Overview
Explore in AI Chat

Overview

PAY_RUN_RESULT_PKG is an Oracle Applications (APPS) PL/SQL package body that encapsulates the core business logic for creating and maintaining payroll run results within Oracle Payroll. A run result is the atomic record of a processed element entry for an assignment during a specific payroll run, capturing the calculated value produced by a payroll formula. This package provides the programmatic interface through which payroll processing, retroactive recalculation, costing, and balance feeds persist those computed values into the PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES tables.

The package is classified as OTHER and is not a public, externally documented API, meaning it is intended primarily for internal consumption by the payroll engine, related payroll packages, and validated extensions rather than general customer development. Its dependency list confirms tight coupling with both the payroll schema (PAY_RUN_RESULTS, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, PAY_RUN_RESULT_VALUES) and shared Oracle EBS services such as HR_CURRENCY_PKG, GL_CURRENCY_API, HR_DYNSQL, HR_UTILITY, PAY_CORE_UTILS, and FND_NUMBER for currency conversion, dynamic SQL generation, and numeric formatting.

Key Procedures and Functions

  • CREATE_RUN_RESULT — Creates a payroll run result record for a given assignment and element entry, persisting the outer record in PAY_RUN_RESULTS with the run, assignment, element type, and status context needed for downstream processing.
  • CREATE_RUN_RESULT_DIRECT — Creates a run result directly, bypassing the standard element entry pathway. This is typically used for indirect or system-generated results where no processed element entry row exists.
  • CREATE_INDIRECT_RR — Creates an indirect run result, used when an element generates results that are not the product of a direct formula evaluation but instead derived from another element or balance (for example, employer-level or summary elements).
  • MAINTAIN_RR_VALUE — Inserts, updates, or reconciles the detailed value rows in PAY_RUN_RESULT_VALUES that are attached to a parent run result. It maintains the linkage between a run result and its input values, ensuring that value changes are reflected consistently.
  • GET_RESULT_VALUE — Retrieves the value of a run result (or a specific associated input value) so that callers can inspect, reuse, or propagate the computed figure without re-executing the originating formula.

Tables Accessed

The package reads and writes PAY_RUN_RESULTS, the master run result table, together with the PAY_RUN_RESULTS_S sequence used to generate primary keys. PAY_RUN_RESULT_VALUES stores the detailed values linked to each run result and is maintained by MAINTAIN_RR_VALUE. Input and element context is drawn from PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_TYPES_F, and PAY_INPUT_VALUES_F, allowing the package to determine which element an entry belongs to and which input values must be captured. PER_TIME_PERIODS and PER_BUSINESS_GROUPS supply the payroll period and business group context, and DUAL is used for scalar queries and sequence lookups. Currency-related dependencies (GL_CURRENCY_API, HR_CURRENCY_PKG) are used when monetary values require conversion or validation.

Usage Notes

PAY_RUN_RESULT_PKG is invoked by the Oracle Payroll processing engine during the calculation, retro-pay, and costing phases of a payroll run. It is referenced by four other database objects in the ETRM dependency chain, indicating that sibling payroll packages call into it rather than accessing PAY_RUN_RESULTS directly. It is not attached to a self-service or professional forms block, nor is it exposed as a concurrent program entry point. Because it is classified as OTHER rather than a public API, custom code that invokes its procedures should treat the interface as unsupported and subject to change across 12.1.1 and 12.2.2; supported integrations should instead use documented payroll APIs such as PAY_ELEMENT_ENTRY_API or the payroll run result APIs where available. Direct DML against PAY_RUN_RESULTS remains inadvisable because this package also maintains sequencing, value rows, and currency handling that a manual insert would not replicate.