Results for “prepayment_action_id”

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

Overview

PAY_PRE_PAYMENTS is a payroll module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores pre-payment details for an assignment, capturing the currency, the amount, and the specific payment method applied to a payroll action. In payroll processing, a pre-payment represents a monetary amount allocated through a payment method ahead of, or in relation to, the standard assignment action flow, and this table is the persistent record of those allocations. The table is documented as VALID in the ETRM repository with twelve physical columns in Release 12.2.2.

Under the supplied heuristic Data Vault classification, PAY_PRE_PAYMENTS is described as hub-leaning. As a modeling suggestion, this indicates that PRE_PAYMENT_ID functions as a durable business key around which dependent attributes and transactional relationships cluster, rather than a purely descriptive satellite. The classification is heuristic and mined from the foreign key structure, so it should be treated as guidance rather than a mandated model.

Key Information Stored

The documented primary key is PAY_PRE_PAYMENTS_PK, defined on the single column PRE_PAYMENT_ID. This surrogate identifier uniquely identifies each pre-payment row and is the only documented unique index and business-key candidate, referenced throughout the payroll schema by dependent tables.

• PRE_PAYMENT_ID — Surrogate primary key, the identifier propagated to child tables that reference this object.
• ASSIGNMENT_ACTION_ID — Foreign key to PAY_ASSIGNMENT_ACTIONS, linking the pre-payment to the assignment-level action being processed.
• PAYROLL_ACTION_ID — Foreign key to PAY_PAYROLL_ACTIONS, tying the pre-payment to the parent payroll action in the run.
• SOURCE_ACTION_ID and PREPAYMENT_ACTION_ID — Action identifiers that record the originating and prepayment action context within payroll processing.
• PERSONAL_PAYMENT_METHOD_ID, ORG_PAYMENT_METHOD_ID, and PAYEES_ORG_PAYMENT_METHOD_ID — Candidate references to the payment method applied, distinguishing personal payment methods from organizational and payee-level organization methods.
• VALUE — The pre-payment amount expressed in the applicable currency.
• BASE_CURRENCY_VALUE — The same amount restated in the base currency, enabling consistent aggregation and reporting.
• ORGANIZATION_ID — Business group or organization identifier used for multi-organization security partitioning.
• EFFECTIVE_DATE — Effective date governing the applicability of the pre-payment record.

Common Use Cases and Queries

Payroll administrators and technical consultants query this table to reconcile pre-payment amounts against assignment actions and payroll runs, to validate that payment methods resolve correctly, and to report on base currency totals across organizations. Because it is a hub-leaning object, it is commonly joined outward to its transactional children when building payment and cost extracts.

A representative query joins the pre-payment to its assignment action and payroll action to list amounts by run:

• SELECT p.PRE_PAYMENT_ID, p.VALUE, p.BASE_CURRENCY_VALUE, a.ASSIGNMENT_ACTION_ID, p.PAYROLL_ACTION_ID FROM PAY_PRE_PAYMENTS p JOIN PAY_ASSIGNMENT_ACTIONS a ON a.ASSIGNMENT_ACTION_ID = p.ASSIGNMENT_ACTION_ID WHERE p.PAYROLL_ACTION_ID = :payroll_action_id;
• Filtering by ORGANIZATION_ID supports multi-org reporting, while joining PAY_PAYMENT_COSTS and PAY_CONTRIBUTING_PAYMENTS on PRE_PAYMENT_ID supports cost distribution and contributing payment analysis.
• Aggregations on BASE_CURRENCY_VALUE by EFFECTIVE_DATE provide trend reporting on pre-payment activity across periods.

Related Objects

The documented foreign key relationships define the most significant dependencies. PAY_PRE_PAYMENTS references PAY_ASSIGNMENT_ACTIONS on ASSIGNMENT_ACTION_ID and PAY_PAYROLL_ACTIONS on PAYROLL_ACTION_ID. In the reverse direction, PAY_ASSIGNMENT_ACTIONS also holds a PRE_PAYMENT_ID reference back to this table, and PAY_COIN_ANAL_ELEMENTS, PAY_PAYMENT_COSTS, and PAY_CONTRIBUTING_PAYMENTS each reference PAY_PRE_PAYMENTS.PRE_PAYMENT_ID. These five tables — PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_COIN_ANAL_ELEMENTS, PAY_PAYMENT_COSTS, and PAY_CONTRIBUTING_PAYMENTS — form the core join surface for queries and extracts involving pre-payment data.