Search Results pay_contributing_payments_n1




Overview
Explore in AI Chat

Overview

The HR.PAY_CONTRIBUTING_PAYMENTS table is a core Oracle Payroll (PAY) data object that stores rolled-up payment information. Its purpose is to record which contributed pre-payments feed into a consolidated or aggregated pre-payment, thereby linking individual payroll processing results to the payment that ultimately disburses them. The table resides in the APPS_TS_TX_DATA tablespace in the HR schema and is exposed to the Applications layer through the FND Design Data object PAY.PAY_CONTRIBUTING_PAYMENTS, with synonyms owned by both APPS and PUBLIC. It is a VALID object in both Oracle EBS 12.1.1 and 12.2.2.

Reflecting the mined foreign-key structure, the object is best modeled as a standalone or link-style construct rather than a true Data Vault hub or satellite. It carries no descriptive attributes of its own; its four columns are all foreign-key references to other master data, so a Data Vault treatment would place it as a link connecting the payroll action, assignment action, and pre-payment hubs. This classification is a heuristic modeling suggestion derived from the FK density, not a documented repository classification.

Key Information Stored

The table is deliberately narrow, holding only four documented columns. Each column is a foreign key into another PAY entity:

The documented unique index PAY_CONTRIBUTING_PAYMENTS_N3 spans CONTRIBUTING_PRE_PAYMENT_ID, making it the strongest business-key candidate within the supplied metadata. Because no dedicated surrogate primary-key column is documented, the table is effectively a key-based intersection. Three non-unique indexes support access paths: PAY_CONTRIBUTING_PAYMENTS_N1 on PAYROLL_ACTION_ID, PAY_CONTRIBUTING_PAYMENTS_N2 on ASSIGNMENT_ACTION_ID, and PAY_CONTRIBUTING_PAYMENTS_N4 on PRE_PAYMENT_ID. All indexes reside in the APPS_TS_TX_IDX tablespace; the table uses PCTFREE 10.

Common Use Cases and Queries

The principal use case is tracing how individual payroll runs and assignment actions roll up into a single disbursement. Payroll reconciliation reports join this table to PAY_PRE_PAYMENTS to show the constituent amounts behind a consolidated payment. Payment audit queries use ASSIGNMENT_ACTION_ID to find every assignment whose results were paid by a given pre-payment, supporting investigation of over- or under-payments. The N1, N2, and N4 indexes make action-driven and payment-driven lookups efficient.

A representative access pattern follows the documented query text, filtered by the receiving pre-payment:

  • SELECT PAYROLL_ACTION_ID, ASSIGNMENT_ACTION_ID, CONTRIBUTING_PRE_PAYMENT_ID, PRE_PAYMENT_ID FROM HR.PAY_CONTRIBUTING_PAYMENTS WHERE PRE_PAYMENT_ID = :p_pre_payment_id; — lists all contributing payments rolled into a consolidated pre-payment.
  • SELECT CONTRIBUTING_PRE_PAYMENT_ID FROM HR.PAY_CONTRIBUTING_PAYMENTS WHERE PAYROLL_ACTION_ID = :p_action_id; — retrieves contributions for a specific payroll action via the N1 index.
  • SELECT ASSIGNMENT_ACTION_ID FROM HR.PAY_CONTRIBUTING_PAYMENTS WHERE CONTRIBUTING_PRE_PAYMENT_ID = :p_id; — uses the unique N3 index.

Related Objects

The documented dependencies confirm three parent tables referenced through foreign keys, plus the APPS and PUBLIC synonym layers:

  • HR.PAY_PRE_PAYMENTS — referenced twice, through PRE_PAYMENT_ID and CONTRIBUTING_PRE_PAYMENT_ID; the primary parent for payment aggregation logic.
  • HR.PAY_PAYROLL_ACTIONS — referenced through PAYROLL_ACTION_ID; links contributions to the payroll run action.
  • HR.PAY_ASSIGNMENT_ACTIONS — referenced through ASSIGNMENT_ACTION_ID; links contributions to assignment-level processing.
  • APPS.PAY_CONTRIBUTING_PAYMENTS and PUBLIC.PAY_CONTRIBUTING_PAYMENTS — synonyms through which the object is accessed by the Applications schema and public users.

The table itself does not reference any database object beyond these parents, and it is the terminating point of the rollup relationship, meaning no documented child tables depend on it.