Results for “sit_effective_end_date”

14 results




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

Overview

HR_ADP_RESIDENT_STATE_TAX_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite (12.1.1 / 12.2.2). It is classified under the PER – Human Resources product module and is described in the ETRM metadata as an ADP payroll interface view. Its purpose is to collect and present resident state tax information — the tax withholding data associated with an employee's state of residence — in a flat, denormalized form suitable for extraction by ADP payroll processing interfaces.

Because the object is a view and not a table, it stores no data itself. Instead it dynamically joins person, assignment, period-of-service, location, and multiple US state and federal tax rule tables, applying HR security and decoding lookup values into ADP-friendly codes. It is typically consumed by concurrent programs, extracts, and outbound interfaces that transmit employee tax setup data to an external ADP payroll provider.

Underlying Base Objects

The view is defined over a substantial set of APPS synonyms and package dependencies. The documented referenced base objects include:

The view text applies an ORDERED and PUSH_SUBQ hint with a comment noting a known CBO bug in Oracle 8.1.6 and recommending re-evaluation of the hints for 9i environments. The join strategy emphasizes filtering rows early and forcing table order for predictable performance.

Key Columns

The columns exposed by the view map directly to the resident state tax attributes needed by ADP. Principal columns include:

These columns are drawn primarily from PAY_US_EMP_STATE_TAX_RULES_F and PAY_US_EMP_FED_TAX_RULES_F, decoded via HR_LOOKUPS and DECODE expressions to match the ADP file layout.

Common Use Cases and Queries

Typical use cases include building the ADP resident state tax extract, validating an employee's resident state withholding before a payroll run, and auditing exemptions or overrides across a business group. Because the view already flattens person, assignment, and tax rule data, it removes the need to replicate these joins in a custom extract.

A representative query filtering by employee number and business group:

  • SELECT employee_number, gre_name, pay_frequency, fit_filing_status_code, fit_exemptions, fit_override_amount, medicare_exempt_flag FROM apps.hr_adp_resident_state_tax_v WHERE business_group_id = :p_bg_id AND employee_number = :p_emp_num;
  • SELECT organization_id, assignment_number, primary_flag, fit_effective_start_date, fit_effective_end_date FROM apps.hr_adp_resident_state_tax_v WHERE person_id = :p_person_id ORDER BY fit_effective_start_date DESC;

Access to the view is mediated by HR_SECURITY, so results are automatically restricted to the operating user's security profile. The view should be treated as read-only reference data for integration purposes.