Search Results pay_payment_costs_pk

Overview

PAY_PAYMENT_COSTS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual cost distribution lines that are generated when a payroll payment is processed, allocating the monetary value of a payment across one or more accounts. Each row represents a single accounting cost entry—a debit or credit against a general ledger account—associated with a payment action or a pre-payment. The table therefore acts as the payroll-side bridge between calculated net pay and the accounting entries that are ultimately transferred to Oracle General Ledger.

From a dimensional modeling perspective, the ETRM heuristic Data Vault classification is standalone. In other words, the mined foreign-key structure does not collapse into a classic hub, link, or satellite pattern; the table is best modeled as an independent fact-style entity whose grain is one cost line per payment. Modelers who apply Data Vault techniques should treat PAY_PAYMENT_COSTS as a standalone table rather than forcing it into a hub-and-satellite construct.

Key Information Stored

The table is documented with 14 columns in ETRM 12.2.2. The surrogate primary key is PAYMENT_COST_ID, enforced by the unique index PAY_PAYMENT_COSTS_PK. Because this is the only documented unique index, PAYMENT_COST_ID is the sole documented business-key candidate; there is no separate natural key recorded in the metadata.

• PAYMENT_COST_ID — Surrogate primary key uniquely identifying each cost line.
• ACCOUNT_ID — Identifier of the account to which the cost is distributed.
• ACCOUNT_TYPE — Classification of the account (for example, the type of distribution target).
• VALUE — The monetary amount of the cost line.
• CURRENCY_CODE — Currency in which VALUE is expressed.
• DEBIT_OR_CREDIT — Indicator of whether the line is a debit or a credit.
• ACCOUNTING_DATE — Date on which the cost line is recognized for accounting.
• ASSIGNMENT_ACTION_ID — Foreign key to PAY_ASSIGNMENT_ACTIONS, linking the cost to the payroll action that produced it.
• PRE_PAYMENT_ID — Foreign key to PAY_PRE_PAYMENTS, linking the cost to a pre-payment where applicable.
• ASSIGNMENT_ID — Identifier of the assignment (employee/assignment) associated with the cost.
• TRANSFER_TO_GL_FLAG — Flag indicating whether the line has been (or should be) transferred to General Ledger.
• SOURCE_TYPE — The originating source category of the cost line.
• SOURCE_ACTION_ID and SOURCE_ID — Identifiers pointing back to the originating source action and source record.

Common Use Cases and Queries

The most frequent use of PAY_PAYMENT_COSTS is in payroll reconciliation and general ledger transfer reporting. Payroll and finance analysts reconcile accumulated payment costs against the amounts submitted to GL, using ACCOUNTING_DATE, VALUE, DEBIT_OR_CREDIT, and TRANSFER_TO_GL_FLAG. A typical pattern retrieves all cost lines for a given action:

• SELECT payment_cost_id, account_id, value, currency_code, debit_or_credit FROM pay_payment_costs WHERE assignment_action_id = :action_id;
• SELECT * FROM pay_payment_costs WHERE transfer_to_gl_flag = 'N' AND accounting_date < :period_end; — identifies cost lines not yet transferred to GL.
• Join to PAY_ASSIGNMENT_ACTIONS on ASSIGNMENT_ACTION_ID to report costs by action and assignment for audit or costing analysis.
• Join to PAY_PRE_PAYMENTS on PRE_PAYMENT_ID to trace pre-payment related costs.

Reporting scenarios include cost center distribution analysis (grouping VALUE by ACCOUNT_ID and CURRENCY_CODE), period-end accrual checks (filtering by ACCOUNTING_DATE), and verification that debit and credit lines balance within a payment.

Related Objects

PAY_PAYMENT_COSTS participates in a small set of documented foreign-key relationships. The most significant related objects are:

• PAY_ASSIGNMENT_ACTIONS — Referenced via ASSIGNMENT_ACTION_ID; the parent payroll action that generated the cost lines.
• PAY_PRE_PAYMENTS — Referenced via PRE_PAYMENT_ID; associates costs with pre-payment records.

Because the table is classified as standalone, no other tables reference PAY_PAYMENT_COSTS through a documented foreign key. Its ASSIGNMENT_ID and ACCOUNT_ID columns logically relate to assignment and account entities elsewhere in the HR and GL schemas, and downstream interfaces (such as the payroll GL transfer process) consume the table's contents based on TRANSFER_TO_GL_FLAG. Analysts should confirm the actual join semantics against the specific payroll configuration in use.