Search Results pay_quickpay_inclusions




Overview
Explore in AI Chat

Overview

PAY_QUICKPAY_INCLUSIONS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a control table that records the association between a specific assignment action (a QuickPay run) and the individual element entries that are eligible to be processed within that run. In other words, it defines the inclusion set — the list of element entries that QuickPay will actually consider when executing a fast, single-assignment payroll calculation.

QuickPay is Oracle Payroll's mechanism for running payroll for a single assignment outside the normal payroll run cycle, typically used for advance payments, terminations, adjustments, or ad-hoc calculations. Because a QuickPay run must operate on a defined subset of element entries rather than an entire payroll, PAY_QUICKPAY_INCLUSIONS provides the essential scoping mechanism that links each running assignment action to the exact element entries being processed.

From a Data Vault modeling perspective, the mined metadata classifies this object as satellite-leaning. This reflects its character as a narrow, attribute-bearing child record attached to a parent transaction (the assignment action) rather than a standalone hub or a many-to-many link. The table carries a date- and context-sensitive association that is dependent on the parent action, consistent with satellite behavior.

Key Information Stored

The documented 12.2.2 physical schema for HR.PAY_QUICKPAY_INCLUSIONS contains only two columns, both of which are significant:

  • ASSIGNMENT_ACTION_ID — The foreign key referencing PAY_ASSIGNMENT_ACTIONS. This identifies the specific assignment action (the QuickPay run instance) to which the inclusion record belongs. It is the principal business-key and parental reference, and it is also the column participating in the documented foreign key constraint to PAY_ASSIGNMENT_ACTIONS.
  • ELEMENT_ENTRY_ID — Identifies the individual element entry (from the payroll element entries construct) that is included in the QuickPay run. This column captures the granular payroll input being processed.

Together, ASSIGNMENT_ACTION_ID and ELEMENT_ENTRY_ID form the effective composite identifier for each inclusion row. In the documented schema there is no separately enumerated surrogate primary key column beyond these two; the natural business key is the combination of the assignment action and the element entry. Because the table is so narrow, it behaves as a pure association/control record — its value lies in the pairing it enforces rather than in additional descriptive attributes.

Common Use Cases and Queries

Typical scenarios involving PAY_QUICKPAY_INCLUSIONS include auditing which element entries were processed in a given QuickPay action, reconciling QuickPay results against expected element inclusions, and troubleshooting QuickPay runs that produced unexpected or missing results.

A common query joins the inclusion table to its parent action to trace processing scope:

  • SELECT qpi.assignment_action_id, qpi.element_entry_id FROM pay_quickpay_inclusions qpi WHERE qpi.assignment_action_id = :p_action_id;
  • Joining to PAY_ASSIGNMENT_ACTIONS to retrieve the assignment and action context for a given QuickPay run.
  • Reporting on the number of element entries included per QuickPay action to validate scope before or after processing.

These patterns are frequently used during payroll parallel-run validation, post-run reconciliation, and diagnostic investigation when an element entry appears not to have been processed by a QuickPay execution.

Related Objects

The following objects are most relevant to PAY_QUICKPAY_INCLUSIONS based on the documented foreign key relationships and its role in the Payroll module:

  • PAY_ASSIGNMENT_ACTIONS — The parent table referenced by ASSIGNMENT_ACTION_ID; represents the assignment-level payroll action (including QuickPay runs).
  • PAY_ELEMENT_ENTRIES — The source of ELEMENT_ENTRY_ID, holding the individual element entries that can be included.
  • PAY_ELEMENT_TYPES and PAY_ELEMENTS — Define the elements behind the referenced entries.
  • PAY_PAYROLL_ACTIONS — Provides the payroll run context in which assignment actions and inclusions are grouped.
  • PAY_RUN_RESULTS — Stores the calculated output generated when included entries are processed.
  • PAY_ASSIGNMENT_ACTION_STATUSES — Tracks the status of the parent action through the QuickPay lifecycle.

These objects, together with PAY_QUICKPAY_INCLUSIONS, form the core join path for analyzing and validating QuickPay processing in Oracle Payroll.