Search Results county_subj_nwable




Overview
Explore in AI Chat

Overview

The PAY_US_COUNTY_ACTION_INFO_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. Its documented purpose is to retrieve United States county-level tax information from the archiver. In Oracle Payroll, county tax results for a payroll run are written to the action information infrastructure as part of the payroll action processing cycle, and this view provides a pre-joined, presentation-ready projection of those archived results. Because it exposes a stable set of typed columns with meaningful aliases, the view is intended to serve as a query surface for payroll reporting, payroll-to-general-ledger reconciliation, and downstream integration extracts, rather than as a transactional entry point. The view is consistent across EBS 12.1.1 and 12.2.2, since the underlying PAY schemas for US payroll taxation were not structurally re-architected between these releases. When a user searches for the term "county_gross," this view is the primary documented object that surfaces that datum as an aliased column.

Underlying Base Objects

The view is defined over two documented referenced objects. The first is the table PAY_ACTION_INFORMATION (presented to the APPS schema as a synonym), which stores the action context, jurisdiction, assignment, and the generic ACTION_INFORMATIONn columns that carry county tax values. The view restricts this table with the predicate ACTION_INFORMATION_CATEGORY = 'US COUNTY', so only county-level tax rows are returned. The second referenced object is the packaged function library PAY_US_EMPLOYEE_PAYSLIP_WEB, specifically the GET_JURISDICTION_NAME function, which resolves a jurisdiction code into a descriptive name. The view therefore combines a filtered relational source with a lookup function invoked per row, giving consumers both the coded and the human-readable jurisdiction identifiers. Because the source is the archiver-oriented action information store, the view reflects payroll results as archived at the conclusion of processing rather than live, in-flight calculations.

Key Columns

Common Use Cases and Queries

Typical uses include county tax reconciliation for a payroll period, head tax reporting, and non-resident tax analysis by assignment. A representative query retrieving county gross and withheld amounts for an action context is:

  • SELECT action_number, assignment_id, jurisdiction_code, jurisdiction_name, county_gross, county_withheld FROM pay_us_county_action_info_v WHERE action_number = :p_action_number;
  • SELECT jurisdiction_code, SUM(county_gross) county_gross, SUM(county_withheld) county_withheld FROM pay_us_county_action_info_v GROUP BY jurisdiction_code;
  • SELECT assignment_id, head_tax_liability, head_tax_withheld, non_resident_flag FROM pay_us_county_action_info_v WHERE non_resident_flag IS NOT NULL;

Because the derived numeric columns apply TO_NUMBER conversions without explicit error handling, consumers should be aware that non-numeric or null source values may affect results, and aggregation queries should generally be filtered by action context or effective date to bound the data set.