Search Results first_name_kana




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_ISDF_EMP_V is a reporting and integration view in the Oracle E-Business Suite Japanese Payroll (Oracle Payroll for Japan) module. It exposes employee-level "action information" records captured in the Japanese ISDF (Income Statement / data filing) context, specifically those stored against the JP_ISDF_EMP information category. The view is a filtered projection of a DML-capable base view, narrowing the result set to a single action context type and category so that downstream reports, interfaces, and extracts operate on a consistent, pre-qualified population of rows.

In EBS 12.1.1 and 12.2.2 the view resides in the APPS schema and forms part of the payroll action-information framework, in which contextual data is stored against an assignment action and keyed by an action information category. Because it carries the Japanese kana name attributes, the view is primarily used where phonetic (furigana/kana) representation of an employee's name is required, such as statutory filings and Japanese-language payslip or report generation.

Underlying Base Objects

The view is defined over a single documented base object:

PAY_JP_ISDF_EMP_DML_V is a DML-enabled view, meaning it supports insert, update, and delete operations that are propagated to the underlying payroll action-information tables. PAY_JP_ISDF_EMP_V restricts that broader DML view by applying two predicate conditions: ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_ISDF_EMP'. The effect is to present only the ISDF employee records associated with the AAP action context, while hiding all other context/category combinations that the DML view may surface. All columns exposed by PAY_JP_ISDF_EMP_V are inherited directly from PAY_JP_ISDF_EMP_DML_V; the view adds no computed or derived columns of its own.

Key Columns

Common Use Cases and Queries

Typical uses include extracting employee ISDF data for Japanese statutory reporting, validating that kana name fields are populated, and joining to payroll assignment actions for reconciliation. A representative query retrieving kana names is:

  • SELECT employee_number, last_name_kana, first_name_kana, last_name, first_name FROM apps.pay_jp_isdf_emp_v WHERE first_name_kana LIKE 'ア%';
  • SELECT assignment_id, effective_date, employee_number, postal_code, address FROM apps.pay_jp_isdf_emp_v WHERE assignment_id = :p_assignment_id ORDER BY effective_date;
  • SELECT a.assignment_action_id, v.employee_number, v.last_name_kana FROM apps.pay_jp_isdf_emp_v v, apps.pay_assignment_actions a WHERE v.assignment_action_id = a.assignment_action_id AND a.action_status = 'C';

Because the view is read-only in intent for reporting (filtering applied over a DML view), it is best used for extraction and validation; any maintenance of the underlying ISDF employee action information should be performed through the supported payroll action-information APIs or the DML view itself. As always, queries should be schema-qualified and executed under an account with appropriate APPS read privileges.