Results for “pay_cost_account_type”

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

Overview

APPS.PAY_PAYMENT_COSTS_V is a reporting and integration view in the Oracle E-Business Suite Payroll module that consolidates payment cost accounting information generated during the payroll prepayment process. The view provides a denormalized, human-readable representation of the rows stored in the PAY_PAYMENT_COSTS table (aliased internally as PCOS, which corresponds to the "PCOS" search term frequently used by developers and support analysts). Its principal role is to expose costed payment amounts alongside their associated payment methods, GL account combinations, payroll actions, and assignment context, enabling both reporting and downstream financial integration.

The view is particularly significant because it resolves several foreign-key relationships and applies lookup decoding at query time, sparing report writers and integration developers from repetitive joins and manual decoding logic. It is commonly referenced in custom reports, Oracle Payables/General Ledger reconciliation extracts, and cost analysis inquiries.

Underlying Base Objects

The view is defined over several base objects owned by APPS, accessed through synonyms. The documented referenced objects are:

• PAY_PAYMENT_COSTS (PCOS) — the driving table holding individual payment cost records, including accounting date, cost type, debit/credit indicator, value, currency, and source information.
• PAY_PRE_PAYMENTS (PPP) — links each cost record to its originating prepayment, joined on PRE_PAYMENT_ID.
• PAY_ORG_PAYMENT_METHODS_F (OPM) — supplies the payment method name; the join additionally constrains the payroll action effective date to fall between the payment method's effective start and end dates.
• PAY_ASSIGNMENT_ACTIONS (PAA) — connects the cost record to the assignment action, joined on ASSIGNMENT_ACTION_ID.
• PAY_PAYROLL_ACTIONS (PAC) — provides payroll action context, joined via PAYROLL_ACTION_ID.
• GL_CODE_COMBINATIONS (GCC) — supplies the chart of accounts identifier for the account combination referenced by ACCOUNT_ID.
• HR_GENERAL and HR_CHKFMT (packages) — invoked as PL/SQL functions to decode lookups and format currency values.

Key Columns

• PAYMENT_METHOD_NAME — derived from the organization payment method, identifying how the payment was disbursed.
• ACCOUNTING_DATE — the date the cost is recognized for accounting purposes.
• COST_TYPE — decoded via HR_GENERAL.DECODE_LOOKUP('PAY_COST_ACCOUNT_TYPE', ...), classifying the nature of the payment cost.
• DEBIT_OR_CREDIT — decoded via HR_GENERAL.DECODE_LOOKUP('DEBIT_CREDIT', ...), indicating the accounting side.
• COSTED_VALUE — the monetary amount, format-masked through HR_CHKFMT.CHANGEFORMAT using the record's currency code.
• SOURCE_TYPE / SOURCE_ACTION_ID — identify the originating source of the cost and the associated action.
• GL_ACCOUNT_CCID / FLEX_NUM — the GL code combination identifier and its chart of accounts identifier.
• ASSIGNMENT_ID / ASSIGNMENT_ACTION_ID — assignment-level context for the cost.
• PRE_PAYMENT_ID / PAYMENT_COST_ID — primary linkage keys to the prepayment and the underlying cost row.

Common Use Cases and Queries

Typical uses include reconciling payroll payment costs to General Ledger, analyzing costs by payment method or cost type, and extracting payment cost data for third-party financial systems. A representative query retrieves costed values for a given accounting period:

• SELECT payment_method_name, accounting_date, cost_type, debit_or_credit, costed_value FROM apps.pay_payment_costs_v WHERE accounting_date BETWEEN :p_start AND :p_end;
• SELECT cost_type, SUM(costed_value) FROM apps.pay_payment_costs_v GROUP BY cost_type;
• SELECT a.* FROM apps.pay_payment_costs_v a WHERE a.assignment_id = :p_assignment_id;

Because COSTED_VALUE is returned as a formatted string, numeric aggregation should be performed against the underlying PAY_PAYMENT_COSTS.VALUE column where precise arithmetic is required. Filtering by FLEX_NUM supports multi-chart-of-accounts environments, while SOURCE_TYPE and SOURCE_ACTION_ID enable traceability back to originating payroll processes.