Search Results spouse_type




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_ISDF_SPOUSE_V is a reporting and integration view within the Oracle E-Business Suite Japanese payroll localization. It exposes spouse-related declaration data captured for the Japanese Income Tax and Special Reconstruction Tax Declaration (ISDF) process, which is administered through the Payroll action-information framework. The view presents one row per spouse declaration record linked to a payroll assignment action, allowing payroll administrators, tax reporting extracts, and downstream interfaces to retrieve dependent spouse details in a flattened, query-ready form.

The view is read-only and is intended for inquiry and reporting rather than transaction entry. Its definition filters the underlying DML view strictly to records whose action context type is AAP and whose action information category is JP_ISDF_SPOUSE, ensuring that only spouse declaration entries are surfaced. The user search term widow_type corresponds directly to a column exposed by this view, which records the widow classification used in Japanese tax withholding calculations.

Underlying Base Objects

The ETRM metadata documents two referenced base objects:

  • PAY_JP_ISDF_SPOUSE_DML_V (VIEW) — the immediate source object. All columns are selected from this view, subject to the restricting WHERE clause on action context and category.
  • FND_NUMBER (PACKAGE) — used to convert stored character representations of monetary amounts into numeric values through the FND_NUMBER.CANONICAL_TO_NUMBER function.

Because the view is layered over a DML view, it inherits the action-information data model used by Japanese payroll, where declaration rows are keyed by ACTION_INFORMATION_ID and linked to a specific ASSIGNMENT_ACTION_ID and ASSIGNMENT_ID. The ROW_ID column provides row-level identity for the underlying table, and OBJECT_VERSION_NUMBER supports optimistic locking semantics in the base entity.

Key Columns

  • WIDOW_TYPE — the widow classification for the spouse, a determining factor in Japanese tax exemption and deduction rules.
  • SPOUSE_TYPE — indicates the spouse category (for example, dependent spouse status).
  • SPOUSE_DCT_EXCLUDE — flag indicating whether the spouse is excluded from dependent deduction calculations.
  • EMP_INCOME / SPOUSE_INCOME_ENTRY — income amounts converted to numeric form via FND_NUMBER.CANONICAL_TO_NUMBER.
  • FULL_NAME / FULL_NAME_KANA — spouse name in standard and phonetic kana representation.
  • POSTAL_CODE / ADDRESS — spouse address details.
  • ASSIGNMENT_ID / ASSIGNMENT_ACTION_ID / ACTION_INFORMATION_ID — keys tying the record to the employee assignment and the payroll action that captured it.
  • EFFECTIVE_DATE — the date from which the declaration information applies.
  • STATUS — processing status of the action-information record.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically used to validate spouse declarations, produce tax reporting extracts, and reconcile widow-status classifications against payroll deduction results. A basic query returning widow classifications for a given assignment is:

  • SELECT assignment_id, effective_date, full_name, spouse_type, widow_type, spouse_dct_exclude, spouse_income_entry FROM apps.pay_jp_isdf_spouse_v WHERE assignment_id = :p_assignment_id ORDER BY effective_date DESC;

To isolate records flagged as widows for audit purposes:

  • SELECT assignment_id, full_name, widow_type, effective_date FROM apps.pay_jp_isdf_spouse_v WHERE widow_type IS NOT NULL AND status = 'APPROVED';

Because the view already restricts rows to the JP_ISDF_SPOUSE action category, callers do not need to add category predicates themselves. Joins to PAY_ASSIGNMENT_ACTIONS or employee assignment views on ASSIGNMENT_ACTION_ID and ASSIGNMENT_ID are common when producing formatted declaration reports.