Search Results action_information_category




Overview

APPS.PAY_JP_ITWB_ASSACT_V is a reporting and integration view within the Oracle E-Business Suite Payroll (PAY) schema, purpose-built for Japanese payroll processing. The view name reflects its functional scope: Japanese (JP) Income Tax Withholding Bank (ITWB) assignment action data (ASSACT). It exposes a curated, type-normalized projection of the generic Oracle Payroll action information repository, restricted exclusively to records where the action context type is 'AAP' (assignment-level action) and the action information category is 'JP_ITWB_ASSACT'.

Rather than presenting the raw, heterogeneous column set stored in PAY_ACTION_INFORMATION — where attributes are held as loosely typed VARCHAR2 columns named ACTION_INFORMATION1 through ACTION_INFORMATIONn — this view applies DECODE logic and FND conversion functions so that consumers receive semantically correct numeric and date values. This design is characteristic of Oracle Payroll flexible-attribute (flexfield) storage, where one physical table serves many unrelated business contexts. The view therefore acts as a strongly typed façade over an entity-attribute-value style structure, insulating report writers, interfaces, and localization deliverables from the underlying storage conventions.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is owned by APPS and is defined over three referenced objects:

  • PAY_ACTION_INFORMATION (SYNONYM) — the single source table supplying all rows and columns. The view is a filtered, transformed projection of this table and introduces no joins to other business tables.
  • FND_NUMBER (PACKAGE) — invoked via FND_NUMBER.CANONICAL_TO_NUMBER to convert the canonical (NLS-independent) character representation of numeric attributes into true NUMBER values.
  • FND_DATE (PACKAGE) — invoked via FND_DATE.CANONICAL_TO_DATE to convert the canonical character representation of date attributes into true DATE values.

Because the view is defined over the synonym, it inherits the same runtime privileges and localization behavior as the base PAY_ACTION_INFORMATION table. Reporting against the view does not alter or duplicate data; it is a purely logical construct.

Key Columns

Common Use Cases and Queries

Typical uses include Japanese withholding-tax reconciliation reports, payroll data extracts, and assignment-level integration feeds. Because the view already filters and types the data, queries are concise. A canonical retrieval for a given assignment is:

  • SELECT action_information_id, assignment_id, effective_date, action_information1, action_information2, action_information7 FROM apps.pay_jp_itwb_assact_v WHERE assignment_id = :p_assignment_id AND effective_date = :p_effective_date;
  • Joining to PER_ALL_ASSIGNMENTS_F or PER_PEOPLE_F for names, joining on ASSIGNMENT_ID for reporting.
  • Aggregating numeric withholding attributes across a payroll period for tax filing extracts.

Consumers should note that the numeric and date columns return native NUMBER and DATE types, not characters, which simplifies arithmetic and comparisons but requires callers to handle nulls where the category conversion does not apply.