Search Results flex_num




Overview

The view APPS.PAY_PAYMENT_COSTS_V belongs to the Oracle Payroll (PAY) product and is supplied in the APPS schema with a status of VALID in both Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, presentation-ready projection of payment cost information captured during payroll processing. Rather than exposing the raw cost rows held in PAY_PAYMENT_COSTS, the view resolves internal identifiers into descriptive values — a lookup-driven cost type, a debit/credit indicator, an organization payment method name, and a formatted costed amount — and joins in the chart of accounts context for the accounting flexfield. The view is read-only and intended for reporting and integration consumption, particularly where cost distribution data must be reconciled against the General Ledger. It is a key object for the reported search term cost_type, which is surfaced as a decoded column rather than as the underlying ACCOUNT_TYPE code.

Underlying Base Objects

The view is defined over seven referenced objects, all resolved through APPS synonyms:

  • PAY_PAYMENT_COSTS (alias PCOS) — the driving cost table supplying accounting date, account type, debit/credit flag, value, currency, source type, source action ID, and account ID.
  • PAY_PRE_PAYMENTS (alias PPP) — links a cost row to its pre-payment and organization payment method.
  • PAY_ORG_PAYMENT_METHODS_F (alias OPM) — supplies the payment method name and the effective date range used to bracket the payroll action.
  • PAY_ASSIGNMENT_ACTIONS (alias PAA) — maps the cost row to an assignment action and hence to a payroll action.
  • PAY_PAYROLL_ACTIONS (alias PAC) — supplies the effective date tested against the payment method's effective range.
  • GL_CODE_COMBINATIONS (alias GCC) — resolves the account ID to a code combination and its chart of accounts ID.
  • HR_GENERAL and HR_CHKFMT — PL/SQL packages providing the lookup decoder and the currency formatting function, respectively.

Joins are equi-joins on the respective primary keys, with one range predicate: PAC.EFFECTIVE_DATE BETWEEN OPM.EFFECTIVE_START_DATE AND OPM.EFFECTIVE_END_DATE.

Key Columns

Common Use Cases and Queries

Typical uses include payroll cost distribution reporting, reconciliation of payroll costs to GL postings, and extracting payment cost detail for interfaces. Because COST_TYPE is already decoded, queries do not need to join lookup tables.

  • Filter by cost type for a period: SELECT payment_method_name, accounting_date, cost_type, debit_or_credit, costed_value FROM apps.pay_payment_costs_v WHERE cost_type = '...' AND accounting_date BETWEEN :from_date AND :to_date;
  • Aggregate costs by method and type: SELECT payment_method_name, cost_type, debit_or_credit, SUM(...) FROM apps.pay_payment_costs_v GROUP BY payment_method_name, cost_type, debit_or_credit;
  • Reconcile to GL: select gl_account_ccid, flex_num, and source_action_id to trace a cost row back to its GL code combination and source action.