Results for “pay_costs”

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

Overview

PAY_COSTS is a core payroll cost allocation table within the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. It stores the cost details and monetary values associated with payroll run results, enabling organizations to determine where labor costs should be charged across their accounting structures. When payroll processing completes, the costs generated by assignments, elements, and run results must be distributed to the appropriate general ledger accounts, projects, or cost centers. PAY_COSTS captures these distributions, providing the critical bridge between payroll calculation and financial accounting.

Under the Data Vault classification heuristic mined from its foreign key structure, PAY_COSTS is characterized as satellite-leaning. This suggests it behaves primarily as a descriptive satellite attached to parent hub or link entities—most notably PAY_ASSIGNMENT_ACTIONS and PAY_RUN_RESULTS—rather than acting as an independent hub of business keys. Each row describes attributes and measures related to a specific payroll cost event, reinforcing its role as a dependent detail table in the payroll cost model.

Key Information Stored

The table contains 14 documented columns, with COST_ID serving as the surrogate primary key via the PAY_COSTS_PK unique index. COST_ID uniquely identifies each cost record and is the primary business-key candidate. The column BALANCE_OR_COST indicates whether the record represents a balance or a cost entry, while COSTED_VALUE holds the actual monetary amount associated with the cost. DEBIT_OR_CREDIT distinguishes the accounting direction of the entry.

Foreign key columns anchor each record to its sources: ASSIGNMENT_ACTION_ID links to PAY_ASSIGNMENT_ACTIONS, RUN_RESULT_ID links to PAY_RUN_RESULTS, INPUT_VALUE_ID links to PAY_RUN_RESULT_VALUES, and COST_ALLOCATION_KEYFLEX_ID links to PAY_COST_ALLOCATION_KEYFLEX, determining the accounting flexfield distribution. DISTRIBUTED_INPUT_VALUE_ID and DISTRIBUTED_RUN_RESULT_ID support cost distribution scenarios. TRANSFER_TO_GL_FLAG indicates whether the record has been transferred to the General Ledger, while TRANSFERED_TO_PRJ marks transfer to Oracle Projects. SOURCE_ID and INSTANCE_ID provide supplementary lineage and instance tracking.

Common Use Cases and Queries

Payroll cost analysis is the most frequent use case. Cost accountants query PAY_COSTS to reconcile payroll expenditure against GL postings, verify allocation accuracy, and investigate variances. A typical query joins cost records to run results and allocation keyflex data:

• SELECT pc.cost_id, pc.costed_value, pc.debit_or_credit, prr.run_result_id FROM pay_costs pc, pay_run_results prr WHERE pc.run_result_id = prr.run_result_id AND pc.transfer_to_gl_flag = 'Y';
• Identify unposted costs: SELECT * FROM pay_costs WHERE transfer_to_gl_flag = 'N';
• Trace costs by assignment action: SELECT * FROM pay_costs WHERE assignment_action_id = :action_id;
• Project cost transfers: SELECT * FROM pay_costs WHERE transfered_to_prj = 'Y';
• Cost allocation reporting joining PAY_COST_ALLOCATION_KEYFLEX for account segmentation.

These patterns support period-end close, audit trails, and reconciliation between payroll and financial systems.

Related Objects

• PAY_ASSIGNMENT_ACTIONS — joined via PAY_COSTS.ASSIGNMENT_ACTION_ID; the parent action driving the cost.
• PAY_RUN_RESULTS — joined via PAY_COSTS.RUN_RESULT_ID; the run result being costed.
• PAY_RUN_RESULT_VALUES — joined via PAY_COSTS.INPUT_VALUE_ID; supplies the input value context.
• PAY_COST_ALLOCATION_KEYFLEX — joined via PAY_COSTS.COST_ALLOCATION_KEYFLEX_ID; defines the accounting distribution.
• PSP_PAYROLL_LINES — references PAY_COSTS.COST_ID; used by Oracle Payroll subledger accounting.

Together these objects form the linkage chain from payroll calculation through cost allocation to GL and Projects integration.