Search Results pay_state_rules




Overview
Explore in AI Chat

Overview

The HR_ADP_STATE_TAX_CODES_V view is a dictionary object owned by the APPS schema within Oracle E-Business Suite, belonging to the PER (Human Resources) product family. It is documented in ETRM as an ADP payroll interface view, indicating that its primary purpose is to supply ADP with the state tax code reference data required for third-party payroll processing. The view presents a simple, denormalized three-column projection that pairs a state code with the lookup code and its meaning, allowing ADP-facing integrations and reports to resolve state-level tax rules without querying the underlying HR lookup and payroll rule tables directly.

Because the object is a view rather than a table, it carries no independent storage and is always current with the base data. Its status is VALID across the documented releases (12.1.1 and 12.2.2), confirming that the definition has remained stable. In practice it serves as a lightweight reference surface: consumers select a small, predictable set of columns suitable for flat-file extraction, interface staging, and ad hoc reporting on state tax code mappings.

Underlying Base Objects

ETRM documents three referenced base objects for this view: HR_LOOKUPS (a view), PAY_STATE_RULES (a synonym targeting the underlying payroll table), and HR_API (a package). The view text is a straightforward inner join between the lookup and state-rule sources:

  • HR_LOOKUPS — supplies the lookup code and meaning of the tax code value, filtered by the lookup type held on the state rule row.
  • PAY_STATE_RULES — the payroll state rules source, which supplies the state code and the foreign-system lookup type (FS_LOOKUP_TYPE) used to join to HR_LOOKUPS.
  • HR_API — the HR package referenced in the dependency tree, typically through the validation and lookup-access logic that underpins HR_LOOKUPS.

The join predicate ties HRL.LOOKUP_TYPE = PSR.FS_LOOKUP_TYPE, meaning the view returns the lookup values that a given state rule designates as foreign-system tax codes. Only rows where a state rule has a matching lookup type and lookup code are exposed.

Key Columns

  • STATE_CODE — sourced from PAY_STATE_RULES; identifies the state (or tax jurisdiction) to which the tax code applies.
  • LOOKUP_CODE — sourced from HR_LOOKUPS; the coded value used by the ADP interface to represent the tax code.
  • MEANING — sourced from HR_LOOKUPS; the human-readable description of the lookup code.

These three columns constitute the complete projection. There is no effective-date or enabled-flag column exposed, so consumers should treat the view as a current-state reference rather than a date-effective history.

Common Use Cases and Queries

Typical uses include generating ADP state tax code extract files, validating inbound tax code values against configured state rules, and building lookup screens for payroll administrators.

  • List all tax codes for a single state: 
    SELECT state_code, lookup_code, meaning
FROM   apps.hr_adp_state_tax_codes_v
WHERE  state_code = 'CA';
  • Produce a full mapping extract ordered for the ADP interface: 
    SELECT state_code, lookup_code, meaning
FROM   apps.hr_adp_state_tax_codes_v
ORDER  BY state_code, lookup_code;
  • Validate a value received from ADP: 
    SELECT COUNT(*)
FROM   apps.hr_adp_state_tax_codes_v
WHERE  state_code = :p_state
AND    lookup_code = :p_code;

Because the view joins through PAY_STATE_RULES, results reflect only those states for which state rules and matching lookup types are configured. If a jurisdiction is absent from the output, the deficiency generally lies in missing or misconfigured state rule data rather than in the view definition itself.