Results for “pay_run_results”

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

Overview

The HR.PAY_RUN_RESULTS table is a core payroll processing object within the Oracle E-Business Suite Payroll (PAY) module. It stores the result of processing a single element entry during a payroll run. Each row represents the outcome of applying an element — such as a salary, deduction, or benefit — to an assignment for a specific payroll period. In EBS 12.1.1 and 12.2.2, this table is central to the payroll run lifecycle, capturing the calculated values, statuses, and processing paths that ultimately feed balances, cost allocation, and payment distribution.

From a data-modeling perspective, the ETRM metadata applies a heuristic Data Vault classification of standalone to this table. This suggests the table largely functions as a satellite-like record anchored to a run result surrogate key, with limited inbound foreign-key dependency compared to pure transactional hubs. The classification is a modeling suggestion rather than a structural requirement, and designers should treat PAY_RUN_RESULTS as an event-oriented satellite capturing processing outcomes at a point in time.

Key Information Stored

The table is owned by the HR schema and contains 15 documented columns. The surrogate primary key is RUN_RESULT_ID, enforced by the PAY_RUN_RESULTS_PK unique index. No separate business-key unique index exists beyond this primary key, so RUN_RESULT_ID is the sole documented unique identifier for a run result.

The most significant business columns include:

• ELEMENT_TYPE_ID — identifies which element was processed for the entry.
• ELEMENT_ENTRY_ID — links to the originating element entry that produced this result.
• ASSIGNMENT_ACTION_ID — ties the result to the assignment action within the payroll run (FK to PAY_ASSIGNMENT_ACTIONS).
• ENTRY_TYPE — classifies whether the entry is a regular, override, or adjustment entry.
• SOURCE_ID / SOURCE_TYPE — identify the source of the processed entry.
• STATUS — the processing state of the run result (for example, processed, unprocessed, or error).
• START_DATE / END_DATE — the effective date range for which the element was processed.
• JURISDICTION_CODE — the legislative jurisdiction governing the processing.
• ENTRY_PROCESS_PATH — records the formula or processing path executed.
• TIME_DEFINITION_ID — FK to PAY_TIME_DEFINITIONS, identifying any time-based definition used.
• LOCAL_UNIT_ID and INSTANCE_ID — contextual identifiers for localization and instance tracking.

Common Use Cases and Queries

PAY_RUN_RESULTS is commonly queried during payroll reconciliation and audit. A frequent pattern joins run results to assignment actions to trace a result back to a specific payroll run and assignment. For example:

• Identifying all calculated results for a payroll run: join PAY_RUN_RESULTS.PAY_ASSIGNMENT_ACTION_ID to PAY_ASSIGNMENT_ACTIONS to filter by assignment and run.
• Reconciling element processing by status: filter on STATUS to isolate errored or unprocessed entries.
• Cost allocation reporting: PAY_COSTS references RUN_RESULT_ID to allocate payroll costs to accounting flexfields.
• Auditing entry processing: PAY_ENTRY_PROCESS_DETAILS references RUN_RESULT_ID to trace how each entry was processed.
• Benefit reimbursement reconciliation: BEN_PRTT_REIMBMT_RECON references RUN_RESULT_ID for participant reimbursement matching.

Related Objects

PAY_RUN_RESULTS participates in several documented relationships:

• PAY_ASSIGNMENT_ACTIONS — referenced via ASSIGNMENT_ACTION_ID; the parent record for the assignment action.
• PAY_TIME_DEFINITIONS — referenced via TIME_DEFINITION_ID.
• PAY_COSTS — references RUN_RESULT_ID, linking results to cost allocations.
• PAY_ENTRY_PROCESS_DETAILS — references RUN_RESULT_ID, capturing entry processing detail.
• BEN_PRTT_REIMBMT_RECON — references RUN_RESULT_ID for benefit reimbursement reconciliation.

Together these dependencies establish PAY_RUN_RESULTS as the pivotal intersection between payroll calculation, costing, and benefits processing in Oracle EBS Payroll.