Search Results filing_status_code




Overview
Explore in AI Chat

Overview

The PAY_EMP_LOCAL_TAX_V1 view is a Payroll (PAY) module object owned by the APPS schema and defined as VALID in Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to support the user interface, presenting employee-level local tax withholding information captured against assignment extra information records. Rather than storing data itself, the view flattens and decodes the flexfield-style AEI_INFORMATIONn attributes held in PER_ASSIGNMENT_EXTRA_INFO into named, business-meaningful columns such as STATE_CODE, JURISDICTION_CODE, FILING_STATUS, and LIT_EXEMPT. This makes it a convenient read source for local tax (LIT) configuration, screens, and reporting queries that would otherwise require knowledge of the underlying information type numbering. Because the view joins to lookups and state rules, it returns human-readable values ready for display or downstream integration.

Underlying Base Objects

The documented base objects for this view are FND_NUMBER (package), HR_API (package), HR_LOOKUPS (view), PAY_STATE_RULES (synonym), and PER_ASSIGNMENT_EXTRA_INFO (synonym). The primary driving object is PER_ASSIGNMENT_EXTRA_INFO (aliased PAEI), from which all informational columns are drawn. The view joins PAEI.AEI_INFORMATION1 to PAY_STATE_RULES.STATE_CODE (aliased PSR) to resolve STATE_NAME, and joins PAEI.AEI_INFORMATION3 to HR_LOOKUPS.LOOKUP_CODE where LOOKUP_TYPE = 'US_LIT_FILING_STATUS' to produce FILING_STATUS. The FND_NUMBER package's CANONICAL_TO_NUMBER function converts character-stored numeric attributes into true numeric values. The view is restricted to records where INFORMATION_TYPE = 'LOCALITY'. The HR_API package is referenced in the metadata as a base object associated with the view's processing context.

Key Columns

Common Use Cases and Queries

This view is commonly queried when administrators or interfaces must report which employees are exempt from local income tax, what jurisdiction and filing status applies, and whether override rates or amounts are set. A typical query filtering on the exempt flag is:

  • SELECT ASSIGNMENT_ID, STATE_CODE, STATE_NAME, JURISDICTION_CODE, CITY_NAME, FILING_STATUS, LIT_EXEMPT FROM APPS.PAY_EMP_LOCAL_TAX_V1 WHERE LIT_EXEMPT = 'Y';
  • SELECT ASSIGNMENT_ID, STATE_CODE, JURISDICTION_CODE, LIT_OVERRIDE_RATE, LIT_OVERRIDE_AMOUNT FROM APPS.PAY_EMP_LOCAL_TAX_V1 WHERE LIT_OVERRIDE_RATE IS NOT NULL;
  • SELECT STATE_CODE, JURISDICTION_CODE, COUNT(*) FROM APPS.PAY_EMP_LOCAL_TAX_V1 GROUP BY STATE_CODE, JURISDICTION_CODE;

Because the exempt column is character-based (AEI_INFORMATION7), comparisons should use the string values ('Y'/'N') as stored, and results should be treated as user-interface-oriented rather than a formal API surface.