Search Results spr_term_valid

Overview

APPS.PAY_JP_TAX_SWOT_V is an Oracle E-Business Suite internal database view owned by the APPS schema, registered under FND Design Data as PAY.PAY_JP_TAX_SWOT_V and flagged VALID. It belongs to the Japanese payroll localization layer of Oracle HRMS/Payroll and is designated Oracle Internal Use Only: Oracle does not support direct customer access to the underlying application data except through standard Oracle Applications programs. The view is a derived reporting object rather than a base table, and it is not referenced by any other database object in the shipped metadata, confirming it is consumed only by application code or ad hoc reporting.

The name components reflect its purpose: the "SWOT" designation in Japanese statutory year-end reporting relates to the Salary Withholding Tax report (Shotoku Zei), and the view supplies the payroll and assignment context needed to build that filing. It exposes both payroll aggregate identifiers and person-level termination qualification data. The column SPR_TERM_VALID, which users frequently search for as spr_term_valid, is the termination validity indicator surfaced by this view.

Underlying Base Objects

The view is defined over the following documented objects:

• PAY_JP_WIC_PKG (PACKAGE) — the core Japanese withholding-tax package; supplies the business logic, tax category derivation, and termination calculations reflected in the output columns.
• PAY_JP_WIC_ASSACTS_V (VIEW) — the assignment action source, providing payroll-period assignment activity that drives period-of-service and effective-date values.
• PER_ADDRESSES (SYNONYM) — used to resolve town or city attributes associated with the person or tax organization.
• FND_DATE (PACKAGE) — standard date conversion/validation utility used in the view's expression logic.
• FND_NUMBER (PACKAGE) — standard numeric conversion utility, applied to the SPR_TERM_VALID derivation.

Because the definition references PL/SQL packages as well as a view and a synonym, the view is effectively a logic wrapper: the packages perform the Japanese tax and termination calculations, and the view exposes the resulting attributes in a queryable relational form.

Key Columns

• BUSINESS_GROUP_ID (NUMBER, 15) — legal employer / business group context, the mandatory partitioning key for HRMS data.
• YEAR, TAX_ORGANIZATION_ID, TAX_CATEGORY, TAX_YEA_CATEGORY — the Japanese tax year and withholding-tax classification used for statutory reporting.
• EFFECTIVE_DATE, DATE_EARNED — the effective and earned dates that place each row within a payroll period and calendar year.
• ASSIGNMENT_ACTION_ID, PERSON_ID, PERIOD_OF_SERVICE_ID — links to the assignment action, person, and period-of-service entities that generated the row.
• TOWN_OR_CITY (VARCHAR2, 30) — municipality text, relevant to local inhabitant tax and address-based filing.
• ACTUAL_TERMINATION_DATE (DATE) — the actual date of leaving, as distinct from intended termination.
• SPR_TERM_VALID (NUMBER) — the termination validity flag. Its numeric value, derived through FND_NUMBER and the WIC package logic, indicates whether the termination qualifies for the reporting period; it is the column most commonly referenced in searches such as spr_term_valid.

Common Use Cases and Queries

The view supports year-end withholding-tax validation and reconciliation, typically to confirm that terminated employees are correctly included or excluded, and to reconcile tax categories against period-of-service records.

SELECT person_id
     , year
     , tax_organization_id
     , tax_category
     , actual_termination_date
     , spr_term_valid
  FROM apps.pay_jp_tax_swot_v
 WHERE business_group_id = :p_bg_id
   AND year = :p_year
   AND spr_term_valid = 1;

A second pattern joins the view to PER_ALL_PEOPLE_F on PERSON_ID to obtain employee names and numbers for a Japanese statutory file. Because Oracle marks the view as internal, production integrations should consume it only through standard Oracle Applications programs; direct SQL should be restricted to diagnostic and read-only analysis performed by authorized technical staff, and any custom dependency carries the risk of change across 12.1.1 and 12.2.2 patch levels.