Results for “pay_payroll_actions”

50+ results




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

Overview

PAY_PAYROLL_ACTIONS is the central transaction table in the Oracle E-Business Suite Payroll (PAY) module. Owned by the HR schema and validated in both EBS 12.1.1 and 12.2.2, it holds information about every payroll process executed within the enterprise, including payroll runs, QuickPay runs, reversals, balance adjustments, prepayments, and third-party payment processes. Each row represents a discrete payroll action, capturing the configuration, status, and timing of a single execution event.

From a dimensional modeling perspective, the documented foreign-key structure suggests a satellite-leaning classification. The table is anchored by the surrogate primary key PAYROLL_ACTION_ID but carries numerous descriptive and contextual attributes—status, run type, dates, and report parameters—that behave like satellite payload rather than strict hub keys. It nonetheless functions as a hub in practice, because a broad set of dependent tables (payroll run results, chunk status, assignment actions, and cost allocation output) reference it by PAYROLL_ACTION_ID.

Key Information Stored

The primary key is PAYROLL_ACTION_ID, generated through the PAY_PAYROLL_ACTIONS_PK unique index. This surrogate key is the join point for virtually all payroll run results and cost allocation data. Business-key candidates are limited; the documented unique indexes include PAY_PAYROLL_ACTIONS_PK and a system LOB index (SYS_IL0000042506C00071$$), confirming that PAYROLL_ACTION_ID is the operative identifier.

The most significant columns include:

Common Use Cases and Queries

Typical usage centres on identifying payroll runs, auditing status, and tracing downstream results. A frequent pattern joins this table to PAY_ASSIGNMENT_ACTIONS and PAY_RUN_BALANCES to report run-level totals:

  • Locating all completed payroll runs for a business group and period: filter on ACTION_TYPE, ACTION_STATUS, and TIME_PERIOD_ID.
  • Reconciling costing entries by joining COST_ALLOCATION_KEYFLEX_ID to PAY_COST_ALLOCATION_KEYFLEX.
  • Tracing reversal linkage via TARGET_PAYROLL_ACTION_ID.
  • Monitoring chunk-level progress through PAY_CHUNK_STATUS and PAY_TEMP_OBJECT_ACTIONS.
  • Auditing concurrent program execution by linking REQUEST_ID to FND_CONCURRENT_REQUESTS.

A representative query returns run headers by period. Because ACTION_STATUS values are internal codes, joins to PAY_LOOKUPS or the seeded action-type lookup are recommended for readable output.

Related Objects

The table is heavily referenced. The most significant dependents and parents include:

Parent references include HR_ALL_ORGANIZATION_UNITS, PER_TIME_PERIODS, PAY_CONSOLIDATION_SETS, PAY_ELEMENT_SETS, PAY_ASSIGNMENT_SETS, PAY_PAYMENT_TYPES, PAY_BACKPAY_SETS, PAY_BALANCE_SETS, and PAY_COST_ALLOCATION_KEYFLEX. These relationships make PAY_PAYROLL_ACTIONS the anchor for payroll run analysis and cost allocation reporting across the EBS Payroll module.