Results for “pay_assignment_actions”

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

Overview

PAY_ASSIGNMENT_ACTIONS is a core transactional table in the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. It records the action or process results that show which assignments have been processed by a specific payroll action or process. In practical terms, each row represents a single assignment processed within a payroll run, quick pay, or similar payroll operation, and serves as the pivot between a payroll action (the run or process) and the assignment being paid. This object is central to payroll processing, costing, balance retrieval, payment reconciliation, and GL transfer.

Under a heuristic Data Vault classification mined from its foreign key structure, PAY_ASSIGNMENT_ACTIONS is best modeled as a hub-leaning entity. It carries a single-column surrogate primary key, ASSIGNMENT_ACTION_ID, and is heavily referenced by downstream tables, which is characteristic of a hub whose key anchors many dependent satellites and links. In a Data Vault design, ASSIGNMENT_ACTION_ID would be the hub business key, while time-variant attributes such as ACTION_STATUS, SECONDARY_STATUS, and the START_DATE/END_DATE pair would populate a satellite.

Key Information Stored

The table contains 20 documented columns. The most significant include:

• ASSIGNMENT_ACTION_ID — the surrogate primary key (PAY_ASSIGNMENT_ACTIONS_PK) that uniquely identifies each processed assignment action.
• ASSIGNMENT_ID — the assignment processed by this action, linking to the payroll assignment entity.
• PAYROLL_ACTION_ID — the parent payroll action (run or process) that generated this record; foreign key to PAY_PAYROLL_ACTIONS.
• ACTION_STATUS and SECONDARY_STATUS — the processing status of the action, used to track completion, errors, or reprocessing.
• PRE_PAYMENT_ID — reference to the resulting pre-payment; foreign key to PAY_PRE_PAYMENTS.
• SOURCE_ACTION_ID — the originating action when this row was created by a reversal or reprocessing.
• TAX_UNIT_ID — the tax unit applicable to the assignment action.
• RUN_TYPE_ID — the run type under which the action executed.
• ACTION_SEQUENCE and CHUNK_NUMBER — processing order and parallelism chunking information.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle framework.
• START_DATE and END_DATE — the effective dating range for the action record.
• SERIAL_NUMBER, OBJECT_ID, OBJECT_TYPE, PROCESS_PATH, LABEL_IDENTIFIER, and INSTANCE_ID — supporting identifiers used for process tracing, de-dup, and diagnostics.

The only documented unique index and business-key candidate is ASSIGNMENT_ACTION_ID; no composite unique key is defined on the table in the supplied metadata.

Common Use Cases and Queries

Typical applications include reconciling payroll run results, retrieving assignments processed by a specific run, tracing errors and reprocessing, and driving payroll reporting.

• List all assignments processed in a run: select ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, ACTION_STATUS from PAY_ASSIGNMENT_ACTIONS where PAYROLL_ACTION_ID = :run_id.
• Filter by status: select * from PAY_ASSIGNMENT_ACTIONS where ACTION_STATUS = 'P' and ACTION_STATUS <> 'C'.
• Join to key dependents: join to PAY_RUN_RESULTS, PAY_COSTS, PAY_ACTION_CONTEXTS, and PAY_RUN_BALANCES on ASSIGNMENT_ACTION_ID, and to PAY_PAYROLL_ACTIONS on PAYROLL_ACTION_ID to obtain run context.
• Trace reversal chains using SOURCE_ACTION_ID to identify the action that was reversed or reprocessed.
• Historical/current views filter on the START_DATE/END_DATE effective range where the row is date-tracked.

As ASSIGNMENT_ACTION_ID is the primary key, it is the correct join key when linking to the many dependent tables described below.

Related Objects

PAY_ASSIGNMENT_ACTIONS sits at the center of a dense relationship network. Significant related objects include:

• PAY_PAYROLL_ACTIONS — the parent action; joined on PAYROLL_ACTION_ID.
• PAY_PRE_PAYMENTS — payments produced by the action; joined on PRE_PAYMENT_ID and ASSIGNMENT_ACTION_ID.
• PAY_RUN_RESULTS — per-assignment run results; joined on ASSIGNMENT_ACTION_ID.
• PAY_COSTS — costing rows for the action; joined on ASSIGNMENT_ACTION_ID.
• PAY_ACTION_CONTEXTS — action context data; joined on ASSIGNMENT_ACTION_ID.
• PAY_RUN_BALANCES and PAY_LATEST_BALANCES — balance snapshots referencing the action; joined on ASSIGNMENT_ACTION_ID.
• PAY_ACTION_INTERLOCKS — locking relationships referencing both LOCKING_ACTION_ID and LOCKED_ACTION_ID.
• PAY_GL_INTERFACE and PAY_XLA_EVENTS — accounting and subledger events driven by the action.

Additional dependents such as PAY_CE_RECONCILED_PAYMENTS, PAY_QUICKPAY_INCLUSIONS/EXCLUSIONS, PAY_ELEMENT_ENTRIES_F, PAY_ENTRY_PROCESS_DETAILS, and PAY_PAYMENT_COSTS further underscore the table's role as a central hub in payroll processing and reporting.