Search Results action_information23




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_ITAX_OTHER2_V2 is a reporting view in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that exposes a filtered, pre-joined representation of Japanese income tax "Other2" action information records. It is defined over the PAY_ACTION_INFORMATION table and restricts results to rows where ACTION_CONTEXT_TYPE equals 'AAP' and ACTION_INFORMATION_CATEGORY equals 'JP_ITAX_OTHER2'. This view is typically used by payroll localization logic, statutory reporting extracts, and integration interfaces that must consume Japanese income tax secondary information without repeatedly applying the same filtering and concatenation rules.

Because the view is owned by APPS and based on a synonym pointing to the underlying payroll table, it functions as a stable abstraction layer. The view also invokes the FND_NUMBER package to convert ACTION_INFORMATION1 into a numeric value, reflecting the convention that this column stores canonical numeric data for downstream calculations.

Underlying Base Objects

The view is defined over two documented base objects:

  • PAY_ACTION_INFORMATION (SYNONYM) — the primary source table storing generic action information rows for payroll and payroll-related actions. Each row carries an ACTION_INFORMATION_ID, ACTION_CONTEXT_ID, ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, EFFECTIVE_DATE, ASSIGNMENT_ID, and a set of ACTION_INFORMATION1 through ACTION_INFORMATION30 columns.
  • FND_NUMBER (PACKAGE) — used as FND_NUMBER.CANONICAL_TO_NUMBER(ACTION_INFORMATION1), converting the canonical string representation stored in ACTION_INFORMATION1 into a numeric value for reporting and arithmetic use.

The WHERE clause filters the base table to the AAP context type and the JP_ITAX_OTHER2 category, so the view effectively represents a single category of Japanese income tax action information.

Key Columns

The view exposes ROWID along with the standard action information identifiers and descriptive columns. Notable columns include:

Common Use Cases and Queries

The view is commonly used to extract Japanese income tax secondary data for a given assignment or effective period, and to feed statutory or interface files. Because it pre-filters by category and context type, callers avoid repeating those predicates.

Example query by assignment and effective date:

  • SELECT action_information_id, action_context_id, effective_date, assignment_id, action_information_category, fnd_number.canonical_to_number(action_information1) AS numeric_value, action_information21, action_information22 FROM apps.pay_jp_itax_other2_v2 WHERE assignment_id = :p_assignment_id AND effective_date BETWEEN :p_start AND :p_end;

Example query retrieving concatenated pairs:

  • SELECT action_information_id, action_information21 || action_information22 AS combined_21_22 FROM apps.pay_jp_itax_other2_v2 WHERE action_context_id = :p_context_id;

Because the view reads from PAY_ACTION_INFORMATION, users should honor the object version number for concurrent updates and treat the concatenated columns as derived presentation fields rather than stored values.