Results for “after_tax_deductions”

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

Overview

The APPS.PAY_AC_EMP_SUM_ACTION_INFO_V view is a payroll reporting object within the Oracle E-Business Suite Payroll (PAY) product. It is defined in the APPS schema with a status of VALID across EBS 12.1.1 and 12.2.2 and is not classified as a multi-org or secure-view synonym, so it is directly accessible to any session with SELECT privileges on the APPS schema. The view materializes the data that drives payroll "action" summary information, presenting aggregated earnings, deduction, tax, and benefit figures for employees in a form suited to payslip display and downstream reporting.

The name of the view reflects its three functional anchors: "AC" for Action, "EMP_SUM" for employee-level summary, and "ACTION_INFO" for the underlying PAY_ACTION_INFORMATION data. Its principal role is to transform the loosely typed, attribute-column structure of action information rows into named, semantically meaningful balance columns. Notably, the user-facing search term row_label maps directly to a column in this view: PAI.ACTION_INFORMATION14 is aliased as ROW_LABEL, allowing consumers to access the descriptive label associated with each summarized action information row.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over the following referenced base objects:

• PAY_ACTION_INFORMATION (SYNONYM) — the primary source table, referenced through the alias PAI. It supplies all ACTION_INFORMATION1 through ACTION_INFORMATION14 attribute columns.
• FND_NUMBER (PACKAGE) — provides the CANONICAL_TO_NUMBER function used to convert the character-stored action information amounts into numeric values for summation.
• PAY_US_EMPLOYEE_PAYSLIP_WEB (PACKAGE) — supplies GET_LEGISLATION_CODE, used to apply Canada-specific logic for after-tax deductions.
• HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) — supporting human-resources utilities referenced in the definition, typically for business group and security context resolution.
• PER_ASSIGNMENTS_F (VIEW) — referenced through the alias PAF, from which BUSINESS_GROUP_ID is derived for the legislation decode.

The view therefore sits one layer above PAY_ACTION_INFORMATION and consolidates its sparse attribute layout into a denormalized, reporting-friendly projection.

Key Columns

• ACTION_CONTEXT_ID — the grouping context for the action information rows.
• ACTION_INFORMATION_CATEGORY — the category classifying each set of action information.
• ROW_LABEL — aliased from ACTION_INFORMATION14; the descriptive row label used in payslip and summary presentations.
• EARNINGS — sum of ACTION_INFORMATION4.
• SUPPLEMENTAL_EARNINGS — sum of ACTION_INFORMATION5.
• IMPUTED_EARNINGS — sum of ACTION_INFORMATION6.
• PRETAX_DEDUCTIONS, INVOLUNTARY_DEDUCTIONS, VOLUNTARY_DEDUCTIONS — sums of ACTION_INFORMATION7, 8, and 9 respectively.
• TAXES, TAXABLE_BENEFITS, NON_PAYROLL_PAYMENTS — sums of ACTION_INFORMATION10, 11, and 13.
• AFTER_TAX_DEDUCTIONS — a DECODE-driven column: for Canadian legislation it sums pre-tax plus involuntary plus voluntary deductions; otherwise it sums involuntary plus voluntary deductions.
• GROSS_EARNINGS — the cumulative total of earnings, supplemental earnings, imputed earnings, taxable benefits, and ACTION_INFORMATION12.

Common Use Cases and Queries

Typical usage includes payslip generation, payroll register reporting, and reconciliation of summarized employee balances. All monetary columns are numerically summed and NVL-protected, making the view safe for direct aggregation in reporting queries.

A representative query selecting the row label alongside core earnings and deduction totals:

• SELECT action_context_id, action_information_category, row_label, earnings, taxes, gross_earnings
• FROM apps.pay_ac_emp_sum_action_info_v
• WHERE action_context_id = :p_action_context_id
• ORDER BY row_label;

Because ROW_LABEL derives from ACTION_INFORMATION14, filtering or ordering on it is the standard means of presenting user-recognizable line descriptions. The view is best consumed read-only for reporting; no DML should be attempted against it.