Search Results pay_quickpay_exclusions




Overview
Explore in AI Chat

Overview

PAY_QUICKPAY_EXCLUSIONS 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 stores the list of element entries that must be excluded from a QuickPay run. QuickPay is the concurrent process used to calculate a subset of payroll element entries for a single assignment outside of the normal payroll cycle, and this table allows payroll administrators to suppress specific entries that would otherwise be processed. The table operates as a dependent child of the assignment action framework, keyed by both the element entry and the assignment action that governs the QuickPay execution.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. This is a modeling suggestion rather than a documented warehouse design: because PAY_QUICKPAY_EXCLUSIONS carries descriptive and audit attributes tied to a parent business key (the assignment action), it behaves like a satellite surrounding the PAY_ASSIGNMENT_ACTIONS hub rather than an independent hub or a pure link table.

Key Information Stored

The table contains seven documented columns. The composite primary key, PAY_QUICKPAY_EXCLUSIONS_PK, is defined over two columns, ELEMENT_ENTRY_ID and ASSIGNMENT_ACTION_ID, making the pair the surrogate and business-key candidate simultaneously. The most significant columns are:

  • ELEMENT_ENTRY_ID — Identifies the specific element entry (a line of pay, deduction, or information element) that is to be excluded from processing. This is the core business identifier of the record.
  • ASSIGNMENT_ACTION_ID — References the assignment action under which the exclusion applies; it links the exclusion to a QuickPay execution context within PAY_ASSIGNMENT_ACTIONS.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification, used for audit and incremental extraction.
  • LAST_UPDATED_BY — User who performed the last update.
  • LAST_UPDATE_LOGIN — Login session associated with the last update.
  • CREATED_BY — User who created the exclusion record.
  • CREATION_DATE — Timestamp when the record was inserted.

The audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) follow the standard EBS WHO-column convention and are present on virtually all transactional tables, but they are secondary to the two key columns for functional use.

Common Use Cases and Queries

The primary use case is diagnosing why a particular element entry was not calculated during a QuickPay run. Payroll administrators and support analysts query this table to confirm exclusions before re-running QuickPay. A typical query joins the exclusions to their parent assignment action:

  • List all exclusions for a given assignment action: SELECT element_entry_id, assignment_action_id FROM pay_quickpay_exclusions WHERE assignment_action_id = :action_id;
  • Identify which element entries are suppressed for an assignment before reprocessing.
  • Audit who configured exclusions and when, using CREATED_BY and CREATION_DATE.
  • Reconcile exclusion records against PAY_ASSIGNMENT_ACTIONS to detect orphaned or stale entries.

Reporting use cases include pre-QuickPay validation reports that warn administrators of pending exclusions, and post-run variance analysis comparing expected versus excluded element entries.

Related Objects

The table participates in a small but tightly coupled relationship set centered on the assignment action framework:

  • PAY_ASSIGNMENT_ACTIONS — The immediate parent; joined on ASSIGNMENT_ACTION_ID. This is the only documented foreign key.
  • PAY_ELEMENT_ENTRIES — Logical parent of ELEMENT_ENTRY_ID, supplying the element entry detail being excluded.
  • PAY_ELEMENT_ENTRY_VALUES — Provides the input values associated with the excluded entries.
  • PAY_RUN_RESULTS — Used to confirm which results were produced when exclusions were applied.
  • PAY_PAYROLL_ACTIONS — Supplies the payroll action context for the assignment action.
  • QuickPay concurrent program and PAY_ASSIGNMENT_ACTION APIs — Consume this table at runtime to determine suppression behavior.

Together these objects support the end-to-end QuickPay calculation and troubleshooting workflow.