Search Results pay_jp_itax_person_v




Overview
Explore in AI Chat

Overview

PAY_JP_ITAX_PERSON_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product family, classified as VALID in the ETRM repository. Its stated purpose is to support the Japanese localization only; it is not a global payroll object. In EBS 12.1.1 and 12.2.2 the view serves as a reporting and integration surface for Japanese individual income tax (ITAX) person-level data, presenting a focused projection of the underlying action-information store rather than a normalized master entity.

The view filters records from PAY_ACTION_INFORMATION to a single semantic slice: rows whose ACTION_INFORMATION_CATEGORY equals 'JP_ITAX_PERSON' and whose ACTION_CONTEXT_TYPE equals 'AAP'. This makes it the canonical read interface for Japanese withholding-tax person records used in localization reporting, tax filing extracts, and downstream interfaces.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: PAY_ACTION_INFORMATION, accessed through a synonym in the APPS schema. The view is a straightforward SELECT over that table, exposing ROWID plus the standard action-information audit columns, the 30 generic ACTION_INFORMATION1..30 flex slots, and LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, and CREATION_DATE.

Because the view is defined directly over PAY_ACTION_INFORMATION with fixed predicates, it inherits the table's DML restrictions and does not add joins to person, assignment, or address tables. Localization-specific attributes such as names in kana/kanji, birth dates in multiple era formats, and tax-organization identifiers are surfaced as columns but are physically stored in the generic action-information flexfield segments.

Key Columns

Common Use Cases and Queries

Typical consumers include Japanese withholding-tax extracts, localization validation reports, and interfaces to external tax submission systems. A frequent pattern is to retrieve currently open ITAX person records for a payroll or organization:

  • Selecting active records: WHERE OPEN_DATE IS NOT NULL AND (CLOSE_DATE IS NULL OR CLOSE_DATE > SYSDATE).
  • Filtering by employee or assignment to reconcile with person master data.
  • Reporting birth dates using era-specific columns for statutory forms.

Example:

SELECT employee_number, last_name_kanji, first_name_kanji, open_date, close_date, district_code FROM apps.pay_jp_itax_person_v WHERE action_context_type = 'AAP' AND action_information_category = 'JP_ITAX_PERSON' AND (close_date IS NULL OR close_date > SYSDATE) ORDER BY employee_number;

Because the view is read-only in practice and localization-specific, queries should always constrain by the category and context predicates even though the view already applies them, and should be mindful that the flexfield-derived columns are sparsely populated depending on the ITAX record state.