Search Results pay_jp_isdf_spouse_v




Overview
Explore in AI Chat

Overview

PAY_JP_ISDF_SPOUSE_V is a database view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. As its description states, the object is provided exclusively for the Japanese localization; it does not carry a role in global payroll processing. The view presents spouse-related information captured during the Japanese year-end adjustment (Nenmatsu Chousei) and income reporting workflow, specifically records associated with the Income Summary Data Form (ISDF) spouse declaration process.

Functionally, the view acts as a filtered, canonicalized presentation layer over a DML-enabled view. It restricts rows to a single action context, ACTION_CONTEXT_TYPE = 'AAP', and a single action information category, ACTION_INFORMATION_CATEGORY = 'JP_ISDF_SPOUSE', so that consumers retrieve only spouse declaration records. Because it is a reporting-oriented view rather than a base table, it exposes the collected spouse attributes in a stable shape suitable for inquiry screens, extracts, and interfaces. Two columns additionally pass through the FND_NUMBER.CANONICAL_TO_NUMBER function, converting stored canonical number representations into numeric values for downstream arithmetic or reporting. In Oracle EBS 12.1.1 and 12.2.2 the object remains a VALID dictionary view in the APPS schema.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects:

  • PAY_JP_ISDF_SPOUSE_DML_V (VIEW) — the immediate source of all projected columns. The DML-style view surfaces the stored date-tracked action information rows, and PAY_JP_ISDF_SPOUSE_V narrows those rows to the spouse category and context before exposing them.
  • FND_NUMBER (PACKAGE) — the Oracle Application Object Library numeric utility package, invoked in the select list through FND_NUMBER.CANONICAL_TO_NUMBER to translate the canonical (textual) number representations of income amounts into true numeric values.

The relationship is therefore one of composition: the ISDF spouse view wraps the DML view and applies a package function for numeric normalization. No independent base tables are listed as directly referenced by this view; the storage-level tables are reached indirectly through the DML view.

Key Columns

The projection is organized around identifying a spouse declaration record and the personal, address, and income details it carries.

Common Use Cases and Queries

Typical scenarios include verifying spouse declarations submitted for a payroll assignment action, extracting data for deduction verification, and feeding downstream interfaces. A representative query follows:

SELECT sp.assignment_action_id,
       sp.assignment_id,
       sp.effective_date,
       sp.full_name_kana,
       sp.full_name,
       sp.postal_code,
       sp.address,
       sp.emp_income,
       sp.spouse_type,
       sp.widow_type,
       sp.spouse_dct_exclude,
       sp.spouse_income_entry
  FROM apps.pay_jp_isdf_spouse_v sp
 WHERE sp.assignment_id = :p_assignment_id
   AND sp.status = 'COMPLETED'
 ORDER BY sp.effective_date;

Because the view already restricts rows to the spouse category and AAP context, no additional category filtering is required. Consumers should note that income columns are returned as numeric values, so totals and threshold comparisons can be applied directly. Any DML against the underlying data should be directed to the DML view rather than this read-oriented projection.