Search Results head_tax_liability




Overview
Explore in AI Chat

Overview

APPS.PAYBV_US_COUNTY_ARCHIVE is a read-only Oracle EBS view that exposes archived United States county-level payroll tax information maintained by the Oracle Payroll/Balance Validation (PAYBV) subsystem. It is defined over the PAY_ACTION_INFORMATION table, filtering to records whose ACTION_INFORMATION_CATEGORY equals 'US COUNTY'. Each row represents a discrete county tax transaction or balance snapshot associated with a payroll action, keyed by an action_context_id, a tax_unit_id, an assignment, and an effective date.

The view is intended primarily for reporting, reconciliation, and payroll-to-GL or third-party tax filing integrations. Because it decodes the generic ACTION_INFORMATION1 through ACTION_INFORMATION7 columns into semantically meaningful county tax figures, it provides a consumable interface for analytics and extracts without requiring downstream tools to interpret the raw action-information layout.

Underlying Base Objects

The view text references three documented dependencies:

  • PAY_ACTION_INFORMATION (referenced via a synonym) — the driving base table. Every column in the view derives from it, with the exception of the two lookup columns produced by packaged functions. The WHERE action_information_category = 'US COUNTY' predicate isolates county tax rows.
  • PAY_AC_UTIL (package) — supplies GET_STATE_ABBREV, used to derive the STATE column from the jurisdiction code.
  • PAY_US_EMPLOYEE_PAYSLIP_WEB (package) — supplies GET_JURISDICTION_NAME, used to resolve a human-readable jurisdiction name from the jurisdiction code.

Because it depends on a mutable base table and on packaged function calls, the view is subject to the performance and read-consistency characteristics of PAY_ACTION_INFORMATION. The view is created WITH READ ONLY, so it cannot be used as a DML target.

Key Columns

Common Use Cases and Queries

Typical uses include reconciliation of county withholding against payroll results, extraction of county tax detail for filing, and analysis of head tax liability by jurisdiction, employee, or period.

Example: retrieve head tax liability for an employee over a date range.

SELECT action_number,
       tax_unit_id,
       effective_date,
       assignment_id,
       jurisdiction_name,
       state,
       head_tax_liability,
       head_tax_withheld
FROM   apps.paybv_us_county_archive
WHERE  assignment_id = :p_assignment_id
AND    effective_date BETWEEN :p_start AND :p_end
ORDER BY effective_date;

Example: aggregate county subject and gross by state and jurisdiction.

SELECT state,
       jurisdiction_name,
       SUM(county_gross)          AS total_gross,
       SUM(county_subject)        AS total_subject,
       SUM(county_withheld)       AS total_withheld,
       SUM(head_tax_liability)    AS total_head_liability
FROM   apps.paybv_us_county_archive
WHERE  effective_date >= :p_period_start
GROUP BY state, jurisdiction_name
ORDER BY state, jurisdiction_name;

Example: isolate non-resident county tax activity.

SELECT action_number, assignment_id, jurisdiction_name, county_withheld, head_tax_liability
FROM   apps.paybv_us_county_archive
WHERE  non_resident_flag IS NOT NULL
AND    effective_date BETWEEN :p_start AND :p_end;

All queries should limit effective_date ranges to constrain the underlying scan of PAY_ACTION_INFORMATION and to minimize repeated invocation of the packaged lookup functions.