Search Results action_information11

Overview

APPS.PAY_JP_ITAX_PERSON_V2 is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes element-level "person" income tax information specific to Japanese payroll. It is defined over PAY_ACTION_INFORMATION, the repository that stores user-defined, flexfield-style attributes attached to payroll actions, and it filters that data to the Japanese income tax person context using the predicate action_context_type = 'AAP' and action_information_category = 'JP_ITAX_PERSON'. The view provides a stable, typed interface over the generic ACTION_INFORMATION1..30 columns, converting stored canonical character values into DATE and NUMBER types so downstream reports, interfaces, and extracts can consume Japanese income tax person records without re-implementing conversion logic. The "_V2" suffix distinguishes this version from earlier variants, reflecting a revised column mapping or date/number conversion pattern.

Underlying Base Objects

The view is defined over three documented objects:

• PAY_ACTION_INFORMATION (SYNONYM) — the sole base data source. The view selects ROWID plus the standard action information columns and the thirty generic attribute columns.
• FND_DATE (PACKAGE) — invoked as FND_DATE.CANONICAL_TO_DATE(...) to reinterpret the canonical character storage as DATE values.
• FND_NUMBER (PACKAGE) — invoked as FND_NUMBER.CANONICAL_TO_NUMBER(...) to reinterpret canonical character storage as NUMBER values.

Because the view refers to PAY_ACTION_INFORMATION through the APPS synonym, it remains insulated from the underlying physical table and can be used directly in FastFormula, BI Publisher data models, and custom SQL without grant changes. The WHERE clause restricts rows to the AAP context type and the JP_ITAX_PERSON information category, so only Japanese income tax person records are returned.

Key Columns

The projection carries the structural keys and the converted attributes. Notable columns include:

• ACTION_INFORMATION_ID, ACTION_CONTEXT_ID, ACTION_CONTEXT_TYPE — identity and context linkage; the context type is fixed to 'AAP'.
• ASSIGNMENT_ID, EFFECTIVE_DATE — the assignment and effective dating for the record.
• ACTION_INFORMATION_CATEGORY — fixed to 'JP_ITAX_PERSON' by the view predicate.
• ACTION_INFORMATION1 through ACTION_INFORMATION30 — the generic attribute payload.
• Converted numeric attributes — ACTION_INFORMATION7, 24, and 26 are wrapped with FND_NUMBER.CANONICAL_TO_NUMBER.
• Converted date attributes — ACTION_INFORMATION11, 13, 25, 29, and 30 are wrapped with FND_DATE.CANONICAL_TO_DATE. Notably, ACTION_INFORMATION30 is projected twice, each occurrence converted to a date, so searches for "action_information30" resolve to this view because the column appears twice in the SELECT list.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

This view is typically queried for Japanese payroll income tax person reporting, validation of stored tax attributes, and extraction of effective-dated person tax data for external interfaces. A simple query retrieving converted values follows.

SELECT action_information_id,
       assignment_id,
       effective_date,
       action_information1,
       action_information7 AS num_attr,
       action_information30 AS date_attr
FROM   apps.pay_jp_itax_person_v2
WHERE  assignment_id = :p_assignment_id
ORDER  BY effective_date;

Analysts verifying which attributes are date-typed can inspect the view text or query the converted columns directly. Because ACTION_INFORMATION30 is date-converted and duplicated in the projection, reports referencing that column should alias it explicitly to avoid ambiguity. The view is read-only in practice: it exposes no DML path, and updates must target PAY_ACTION_INFORMATION. For integration, the view is well suited to BI Publisher and OBIEE data models, where the built-in type conversions reduce the need for SQL-level casting.