Search Results pay_jp_isdf_emp_v




Overview
Explore in AI Chat

Overview

The view PAY_JP_ISDF_EMP_V is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PAY - Payroll product family. Its documented status is VALID in ETRM 12.2.2, and the same definition is applicable to the 12.1.1 code line. As stated directly in the Oracle documentation, this view "is used for Japanese localization only." It therefore does not participate in global payroll processing logic; its scope is confined to the Japanese statutory reporting requirements collectively known as ISDF (Individual Statement of Earnings and Deductions / 給与所得の源泉徴収票-related output).

Functionally, the view presents employee-level action information that has been classified within the payroll action framework. It exposes a curated slice of the action-information model where ACTION_CONTEXT_TYPE = 'AAP' (Assignment Action Processing) and ACTION_INFORMATION_CATEGORY = 'JP_ISDF_EMP'. This identifies records holding the Japanese employee attributes required for ISDF output — including Japanese phonetic name fields (LAST_NAME_KANA, FIRST_NAME_KANA), the standard romanized name fields, and postal address data. The view is consequently a reporting and integration façade rather than a transactional entry point.

Underlying Base Objects

The documented referenced base object is a single view: PAY_JP_ISDF_EMP_DML_V. The dependency is a straightforward projection: PAY_JP_ISDF_EMP_V selects all columns from PAY_JP_ISDF_EMP_DML_V and applies two filter predicates. No joins are introduced at this level, and no base tables are referenced directly. The DML view name suffix indicates that the underlying object supports insert/update/delete operations (via INSTEAD-OF triggers), while PAY_JP_ISDF_EMP_V itself functions as the read/query layer restricted to the ISDF employee category.

Sitting beneath PAY_JP_ISDF_EMP_DML_V, the action-information framework is rooted in the core payroll action information tables (PAY_ACTION_INFORMATION and its assignment-action context), which store attribute-value pairs keyed by ASSIGNMENT_ACTION_ID and ACTION_INFORMATION_CATEGORY. The view inherits its referential behavior from that model, including the surrogate key ACTION_INFORMATION_ID and the OBJECT_VERSION_NUMBER used for optimistic locking.

Key Columns

  • ROW_ID — ROWID-based identifier used for DML addressing through the underlying DML view.
  • ACTION_INFORMATION_ID — Primary surrogate key of the action information record.
  • OBJECT_VERSION_NUMBER — Optimistic-locking version stamp; incremented on each update.
  • ASSIGNMENT_ACTION_ID — Foreign key to the assignment action under which the information was captured.
  • ACTION_CONTEXT_TYPE — Always 'AAP' in this view; the action processing context.
  • ACTION_INFORMATION_CATEGORY — Always 'JP_ISDF_EMP'; the Japanese ISDF employee category.
  • ASSIGNMENT_ID — The assignment to which the ISDF employee data belongs.
  • EFFECTIVE_DATE — Date from which the record is effective.
  • EMPLOYEE_NUMBER — The employee number as displayed on ISDF output.
  • LAST_NAME_KANA / FIRST_NAME_KANA — Phonetic (furigana) forms of the family and given names.
  • LAST_NAME / FIRST_NAME — Standard character forms of the family and given names.
  • POSTAL_CODE / ADDRESS — Employee postal code and address.
  • Audit columns: LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical consumers include the Japanese ISDF report programs, payroll localization extensions, and audit extracts. Because the category filter is embedded, callers need only constrain by assignment, action, or effective date range. A representative query is:

SELECT EMPLOYEE_NUMBER, LAST_NAME, FIRST_NAME,
       LAST_NAME_KANA, FIRST_NAME_KANA, POSTAL_CODE, ADDRESS
FROM   APPS.PAY_JP_ISDF_EMP_V
WHERE  ASSIGNMENT_ID = :p_assignment_id
AND    EFFECTIVE_DATE = :p_effective_date;

For broader reporting, joining to PAY_ASSIGNMENT_ACTIONS on ASSIGNMENT_ACTION_ID links the ISDF attributes to the originating payroll action, while joining to PER_ALL_PEOPLE_F via ASSIGNMENT_ID supports person-attribute reporting. When integrating with downstream Japanese statutory filing systems, the phonetic name columns are the critical fields, since ISDF output requires furigana rendering independent of the stored kanji forms. All access should be granted through the APPS schema respecting standard Oracle EBS security conventions.