Search Results last_name_kanji




Overview
Explore in AI Chat

Overview

APPS.PER_JP_SI_DEPENDENT_TRANSFER_V is a Japanese localizations view in Oracle E-Business Suite, provided by the Oracle Human Resources (PER) product family and registered under FND Design Data as PER.PER_JP_SI_DEPENDENT_TRANSFER_V. It exposes dependent transfer information for Japanese social insurance (SI) processing, covering qualified and disqualified dependents for health insurance and type 3 insured persons under the national pension scheme. The view combines person identification data with dependent relationship, transfer status, transfer date, and qualification or disqualification reason details.

The view is documented as Internal and carries an explicit Oracle Internal Use Only warning: Oracle does not support access to applications data using this object except from standard Oracle Applications programs. It is therefore best regarded as a reporting and integration interface used by Oracle's Japanese SI programs and by sanctioned extensions, rather than as a supported public API. Its most visible columns include FIRST_NAME_KANJI and LAST_NAME_KANJI, which hold the dependent's personal name in kanji characters, a standard requirement for Japanese statutory reporting.

Underlying Base Objects

The view is defined over several documented base objects. Person and assignment data are sourced from PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F, providing PERSON_ID, BUSINESS_GROUP_ID, EMPLOYEE_NUMBER, ASSIGNMENT_ID, and the kanji name columns. Dependent relationships are drawn from PER_CONTACT_RELATIONSHIPS, while additional dependent attributes such as dependent type and qualification details are held in PER_CONTACT_EXTRA_INFO_F. The CONTACT_PERSON_ID column returns the dependent as a person record in PER_ALL_PEOPLE_F.

The definition also references the FND_DATE package, which is used to apply Oracle Applications date semantics to the TRANSFER_DATE column, and DUAL as the standard single-row source used in the view's SQL. Because the view reads from the effective-dated person and assignment tables, query results reflect the date-tracked state of the underlying records.

Key Columns

  • BUSINESS_GROUP_ID — Business group identifier scoping the person and assignment records.
  • PERSON_ID — Foreign key to PER_ALL_PEOPLE_F for the employee or person of interest.
  • EMPLOYEE_NUMBER — Employee number of the person.
  • LAST_NAME_KANJI and FIRST_NAME_KANJI — Last and first names in kanji, each VARCHAR2(150). FIRST_NAME_KANJI is the column most frequently targeted in Japanese name reporting.
  • ASSIGNMENT_ID — Foreign key to PER_ALL_ASSIGNMENTS_F.
  • CONTACT_PERSON_ID — Foreign key to PER_ALL_PEOPLE_F identifying the dependent contact.
  • DEPENDENT_TYPE — 'S' for a spouse dependent of health insurance, 'D' for a non-spouse dependent of health insurance, and '3' for a type 3 insured person of the national pension.
  • TRANSFER_TYPE — 'I' for include and 'E' for exclude.
  • TRANSFER_DATE — The qualified date, or the day before the disqualified date.
  • TRANSFER_REASON_CODE — Qualified or disqualified reason code for spouse dependents and type 3 insured persons; null for non-spouse dependents.
  • TRANSFER_REASON_DESCRIPTION — Free-text qualified or disqualified reason, and the sole reason field for non-spouse dependents.
  • TYPE3_DISQUALIFIED_NOTICE — Indicates whether a type 3 disqualified notification is required; applicable only to type 3 insured persons and null for health insurance dependents.

Common Use Cases and Queries

Typical uses include generating Japanese social insurance dependent acquisition and loss reports, validating that kanji names are populated for dependents, and extracting transfer events for interface files submitted to health insurance and pension authorities. A basic retrieval of a dependent's kanji name is shown below.

SELECT person_id,
       employee_number,
       last_name_kanji,
       first_name_kanji
  FROM apps.per_jp_si_dependent_transfer_v
 WHERE first_name_kanji IS NOT NULL
 ORDER BY employee_number;

Filtering by transfer event and dependent category supports periodic statutory reporting:

SELECT employee_number,
       first_name_kanji,
       last_name_kanji,
       dependent_type,
       transfer_type,
       transfer_date,
       transfer_reason_code
  FROM apps.per_jp_si_dependent_transfer_v
 WHERE transfer_date BETWEEN :from_date AND :to_date
   AND dependent_type IN ('S','3')
 ORDER BY transfer_date, employee_number;

Because the object is marked Internal, implementations should route reporting through the view only where standard Oracle Japanese localization programs do so, and avoid building unsupported dependencies upon its structure.