Search Results pay_jp_itwb_assact_v




Overview
Explore in AI Chat

Overview

PAY_JP_ITWB_ASSACT_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PAY (Payroll) product family and is documented in the E-Business Suite Technical Reference Manual as being used exclusively for the Japanese localization. The object is delivered with a status of VALID and is classified as a secure, non-mutating read structure; it exposes no DML capability and is intended strictly for query and reporting access.

The view functions as a filtered, type-cast presentation layer over the generic Action Information framework. Its purpose is to surface the subset of assignment action records that carry the Japanese ITWB (income tax witholding and reporting) assignment-action category, translating stored canonical character values into properly typed numeric and date values suitable for application processing, concurrent programs, and localization-specific reports. Because the underlying action-information model is highly generic, this view provides the semantic narrowing required to treat that generic data as a structured Japanese tax record.

Underlying Base Objects

The view is defined over three documented base objects. Its primary data source is the synonym PAY_ACTION_INFORMATION, which stores action information rows keyed by action context and category. The view restricts this table with the predicate ACTION_CONTEXT_TYPE = 'AAP' AND ACTION_INFORMATION_CATEGORY = 'JP_ITWB_ASSACT', selecting only assignment-level action information in the Japanese ITWB category.

Two PL/SQL packages are referenced within the view definition. FND_NUMBER is used via its CANONICAL_TO_NUMBER function to convert character-stored action information values into numeric form, and FND_DATE is used via its CANONICAL_TO_DATE function to convert a character value into a date. Both conversions are wrapped in DECODE expressions so that they apply only when the row's category is JP_ITWB_ASSACT; other rows yield NULL for those derived columns. The view therefore acts as a canonicalization layer, insulating consumers from the raw character storage convention of the Action Information table.

Key Columns

Note that some identifiers shown in the ETRM column listing (such as ASSIGNMENT_ACTION_ID, PAYROLL_ID, JOB_ID, and ORGANIZATION_ID) do not appear in the documented view text and may reflect a variant or expanded listing; the definitive projection is the view text that selects from PAY_ACTION_INFORMATION.

Common Use Cases and Queries

Because the object is Japanese-localization-specific, typical consumers are localization reports, tax-file generation routines, and diagnostic queries validating ITWB data. A representative query retrieves typed tax values for an assignment:

  • SELECT assignment_id, effective_date, action_information2, action_information7 FROM pay_jp_itwb_assact_v WHERE assignment_id = :p_assignment_id;
  • SELECT COUNT(*) FROM pay_jp_itwb_assact_v WHERE effective_date BETWEEN :p_start AND :p_end;
  • SELECT a.assignment_id, a.action_information9 FROM pay_jp_itwb_assact_v a WHERE a.action_information_category = 'JP_ITWB_ASSACT';

These queries demonstrate the view's value: numeric and date columns are already canonicalized, so callers avoid repeating DECODE and conversion logic. Any direct query against PAY_ACTION_INFORMATION for the same purpose should instead use this view to guarantee the correct context and category filters.