Search Results pay_costs




Overview
Explore in AI Chat

Overview

The PAY_COSTS table is a core data repository within the Oracle E-Business Suite Payroll module (PAY). It serves as the definitive ledger for storing detailed cost information generated during payroll processing. Its primary role is to capture the financial distribution of earnings and deductions across various cost centers, accounts, and projects, as defined by an organization's cost allocation flexfield. This table is populated as a result of payroll runs and is fundamental for financial accounting, cost analysis, and the generation of costing reports that interface with Oracle General Ledger and Projects.

Key Information Stored

The table links payroll results to specific cost allocations and holds the associated monetary values. While the full column list is not detailed in the provided metadata, the foreign key relationships reveal its critical structure. The central identifier is the COST_ID (Primary Key). Essential foreign key columns include ASSIGNMENT_ACTION_ID, which ties the cost record to a specific payroll process instance for an assignment; RUN_RESULT_ID and INPUT_VALUE_ID, linking to the specific payroll element entry and its value that incurred the cost; and COST_ALLOCATION_KEYFLEX_ID, which stores the accounting flexfield combination (e.g., Cost Center, Account, Project) to which the cost is charged. The table also contains columns for the calculated cost value, potentially the date-effective cost code, and other supporting attributes.

Common Use Cases and Queries

This table is central to payroll-to-general ledger reconciliation and project costing. Common operational and reporting scenarios include extracting the full cost breakdown for a completed payroll run, analyzing labor costs by department or project, and troubleshooting cost posting issues. A typical query joins PAY_COSTS to related assignment, person, and costing flexfield tables. For example, to retrieve cost details for a specific payroll action, one might use a pattern such as:

  • SELECT pc.cost_id, ppf.full_name, prrv.result_value, pc.costed_value, pcak.concatenated_segments
  • FROM pay_costs pc
  • JOIN pay_assignment_actions paa ON pc.assignment_action_id = paa.assignment_action_id
  • JOIN per_all_people_f ppf ON paa.assignment_id = ppf.person_id
  • JOIN pay_run_result_values prrv ON pc.run_result_id = prrv.run_result_id AND pc.input_value_id = prrv.input_value_id
  • JOIN pay_cost_allocation_keyflex pcak ON pc.cost_allocation_keyflex_id = pcak.cost_allocation_keyflex_id
  • WHERE paa.payroll_action_id = :p_payroll_action_id;

Related Objects

As indicated by the foreign keys, PAY_COSTS has integral relationships with several key payroll tables. It is a child of PAY_ASSIGNMENT_ACTIONS, which tracks payroll processing steps, and PAY_RUN_RESULT_VALUES, which holds the calculated payroll amounts. Its link to PAY_COST_ALLOCATION_KEYFLEX provides the accounting context. Crucially, it is referenced as a parent table by PSP_PAYROLL_LINES in the Oracle Projects module, demonstrating its role in transferring labor costs to project accounting. Other related objects typically include views like PAY_COSTING_DETAILS_V and APIs used for cost retrieval and validation within payroll processes.