Search Results pay_temp_object_actions_pk

Overview

PAY_TEMP_OBJECT_ACTIONS is a payroll module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, the table "holds details of an object that is to be processed." It functions as a transient staging or work table within the Oracle Payroll processing architecture, capturing the discrete object-level actions that the payroll engine must evaluate and execute during a payroll run. Rather than storing the permanent payroll results themselves, it holds the action instructions and processing state for individual objects, allowing the payroll process to chunk, sequence, and track work across parallel or iterative runs.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone. This reflects that the table has a single foreign key relationship to PAY_PAYROLL_ACTIONS and no dependent child tables documented in the metadata. In dimensional or Data Vault terms, it behaves most like a satellite attached to the payroll action context, capturing descriptive processing state and sequence/status attributes rather than acting as a hub or a link between multiple business entities.

Key Information Stored

The table is documented with eight physical columns. The most consequential are:

• OBJECT_ACTION_ID — The surrogate primary key, defined by the constraint PAY_TEMP_OBJECT_ACTIONS_PK. It uniquely identifies each object action record and is the column most commonly used for direct row access and joins.
• OBJECT_ID — Identifies the specific object (for example, an assignment, element entry, or run result reference) that the action targets. Together with OBJECT_TYPE, this forms the principal business-key candidate describing what is being acted upon.
• OBJECT_TYPE — Classifies the nature of the OBJECT_ID reference, allowing the payroll engine to interpret the object consistently during processing.
• PAYROLL_ACTION_ID — The foreign key referencing PAY_PAYROLL_ACTIONS. This ties each object action to its parent payroll action, establishing the processing context and grouping all object actions belonging to the same run or action.
• ACTION_STATUS — Records the current processing state of the object action, enabling the payroll engine to identify what remains unprocessed, in progress, or complete.
• CHUNK_NUMBER — Supports partitioning of work into chunks, which is significant for parallel processing and restartability of payroll runs.
• ACTION_SEQUENCE — Defines the order in which object actions are to be processed, ensuring deterministic execution.
• OBJECT_VERSION_NUMBER — The standard Oracle EBS optimistic locking column, used to detect concurrent modifications to a row during transaction processing.

Common Use Cases and Queries

Typical use cases center on monitoring payroll processing progress. A common query joins the table to PAY_PAYROLL_ACTIONS to list all object actions for a given payroll action and inspect their status:

• SELECTING object actions by parent action: SELECT object_action_id, object_id, object_type, action_status, chunk_number, action_sequence FROM pay_temp_object_actions WHERE payroll_action_id = :action_id ORDER BY action_sequence;
• Status distribution reporting: aggregating ACTION_STATUS to gauge how many objects remain pending versus complete within a chunked run.
• Chunk-level diagnostics: grouping by CHUNK_NUMBER to identify chunk skew or stalled chunks during parallel payroll processing.
• Troubleshooting restarts: inspecting rows by OBJECT_ID and OBJECT_TYPE to determine whether a specific object was successfully processed before a run was interrupted.

Because this table is transient, reports typically operate within the lifecycle window of an active or recently completed payroll action rather than as a long-term historical source.

Related Objects

• PAY_PAYROLL_ACTIONS — The parent table referenced by the PAYROLL_ACTION_ID foreign key; join on pay_temp_object_actions.payroll_action_id = pay_payroll_actions.payroll_action_id. This is the primary relationship documented in the FK metadata.
• PAY_TEMP_OBJECT_ACTIONS_PK — The primary key constraint on OBJECT_ACTION_ID, defining row uniqueness.
• PAY_RUN_RESULTS and PAY_ASSIGNMENT_ACTIONS — Closely related payroll processing tables often referenced through the OBJECT_ID/OBJECT_TYPE semantics during run evaluation.
• PAY_PAYROLL_RUNS / PAY_ACTION_INFORMATION — Supporting objects that contextualize payroll action processing and parameters.
• Payroll concurrent programs and APIs — Payroll run and action submission processes populate and consume this staging table as part of the processing pipeline.