Search Results pay_jp_itax_person_v2




Overview
Explore in AI Chat

Overview

PAY_JP_ITAX_PERSON_V2 is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product module. It is scoped exclusively to the Japanese localization and presents person-level income tax (ITAX) information held in the generic action information repository. The view does not store data itself; it is a filtered, typed projection over the consolidated PAY_ACTION_INFORMATION table, restricted to the action context type AAP and the action information category JP_ITAX_PERSON. Its status is VALID in both EBS 12.1.1 and 12.2.2, and it is documented in ETRM with the description "This view is used for Japanese localization only."

Because Japanese statutory reporting requires the conversion of canonical (stored-as-text) values into properly typed numbers and dates, the view embeds calls to the FND_NUMBER and FND_NUMBER/FND_DATE canonical conversion functions directly in its SELECT list. This makes the view a convenient read layer for reporting, extracts, and integration interfaces that must consume Japanese income tax person data without re-implementing the canonical-to-native data type conversions.

Underlying Base Objects

The documented referenced base objects are:

  • PAY_ACTION_INFORMATION (SYNONYM) — the single underlying data source. In the APPS schema this is a synonym resolving to the PAY action information table that holds all action-context records.
  • FND_DATE (PACKAGE) — supplies canonical-to-date conversion used for the DATE_START, JP_DATE_START, DATE_OF_BIRTH, and related columns.
  • FND_NUMBER (PACKAGE) — supplies canonical-to-number conversion used for numeric action information elements.

The view's defining predicate is ACTION_CONTEXT_TYPE = 'AAP' AND ACTION_INFORMATION_CATEGORY = 'JP_ITAX_PERSON'. All exposed fields derive from columns on PAY_ACTION_INFORMATION, with the numeric and date variants produced through the package calls named above. The view text also projects the standard audit columns (LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE) and ROWID for row identification.

Key Columns

  • ROW_ID / ACTION_INFORMATION_ID — unique row identifier for the action information record.
  • ACTION_CONTEXT_ID / ACTION_CONTEXT_TYPE — the context linkage; the type is fixed to AAP for this view.
  • ACTION_INFORMATION_CATEGORY — fixed to JP_ITAX_PERSON, confirming the Japanese income tax person scope.
  • EFFECTIVE_DATE, JP_DATE_START, DATE_START — effective and start dating for the tax record, with canonical date conversion applied to the date-typed variants.
  • EMPLOYEE_NUMBER, LAST_NAME_KANA, FIRST_NAME_KANA, LAST_NAME_KANJI, FIRST_NAME_KANJI — person identity fields; kana and kanji representations support Japanese tax documentation conventions.
  • SEX, DATE_OF_BIRTH — demographic attributes, with era-specific birth date columns (MEIJI, TAISHOU, SHOUWA) supplied for Japanese calendar reporting.
  • ADDRESS_ID, ADDRESS_KANA, ADDRESS_KANJI, COUNTRY — address attributes for tax filing purposes.
  • LEAVING_REASON — reason an individual has left, relevant to termination-year income tax processing.

Common Use Cases and Queries

Typical scenarios include generating Japanese income tax extracts, reconciling person tax data for year-end adjustment, and feeding downstream interfaces that require typed numeric and date values.

SELECT action_information_id,
       employee_number,
       last_name_kanji,
       first_name_kanji,
       date_of_birth,
       date_start
FROM   apps.pay_jp_itax_person_v2
WHERE  effective_date BETWEEN :p_start AND :p_end
ORDER  BY employee_number;

Because the view already resolves canonical storage into native data types, callers can filter directly on DATE_START or DATE_OF_BIRTH and perform arithmetic on the numeric columns without invoking FND_NUMBER or FND_DATE themselves. For auditing a specific individual, join on ACTION_CONTEXT_ID or ASSIGNMENT_ID. All access should be granted through the APPS synonym, and queries should observe standard EBS multi-org and security conventions where applicable.