Search Results re_yea




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_WIC_ASSACTS_V1 is a Japanese payroll localization view shipped with Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents a consolidated, reporting-oriented projection of assignment-level payroll action data drawn from the payroll action, assignment action, and action information tables. The view is designed to expose Japanese statutory withholding and year-end adjustment (WIC / gensen choshu) attributes — such as pre-tax amounts, salary and bonus classification, deduction codes, and canonical numeric/date conversions — for a defined set of completed payroll actions.

In EBS reporting and integration contexts, this view functions as a denormalized staging layer. Instead of requiring callers to join the three underlying entities and decode PAY_ACTION_INFORMATION columns by category, consumers can query a single object that has already filtered to relevant action types, status, and Japanese-specific information categories. This makes it suitable for regulatory extracts, year-end adjustment (RE_YEA / YEA) reporting, and custom interfaces between payroll and external tax or interface processes. The inclusion of a USE_NL hint and explicit index directives in the view text indicates it was tuned for assignment-driven access paths.

Underlying Base Objects

The view is defined over the following documented base objects, all owned or referenced by APPS and accessed through synonyms:

  • PAY_PAYROLL_ACTIONS — the header-level payroll run action; aliased PPA and the driving table in the join.
  • PAY_ASSIGNMENT_ACTIONS — the per-assignment action rows; aliased PAA and joined on payroll_action_id with action_status = 'C'.
  • PAY_ACTION_INFORMATION — the descriptive-flexfield-style action information store; aliased PAI, filtered to action_information_category = 'JP_PRE_TAX_1' and action_context_type = 'AAP'.
  • PAY_ACTION_INTERLOCKS — referenced as part of the action interlocking model.
  • FND_DATE (package) — provides canonical_to_date conversion of the stored canonical date strings.
  • FND_NUMBER (package) — provides canonical_to_number conversion of stored canonical numeric strings.

Relationships are established by joining paa.payroll_action_id = ppa.payroll_action_id and linking pai.action_information1 = to_char(paa.assignment_action_id) with pai.assignment_id = paa.assignment_id. Only actions of type R, Q, B, or I are included.

Key Columns

  • assignment_action_id, assignment_id, action_sequence — identify the assignment action instance.
  • payroll_action_id, business_group_id, payroll_id — identify the payroll run context.
  • effective_date, date_earned — the action effective and earnings dates.
  • action_information13 — the payment/earning classification, restricted in scope to values such as SALARY, BONUS, SP_BONUS, YEA, and RE_YEA. The presence of RE_YEA here directly connects this view to the "re_yea" search term.
  • action_information22 — deduction classification (M_KOU, D_KOU, M_OTSU, D_OTSU, D_HEI).
  • action_information21, 4, 15, 24, 25, 29 and additive expressions over columns 2/3 and 6/9/12/14/20 — canonical-converted monetary amounts.
  • action_information16, 18 — canonical-converted dates. action_information17, 30 — text attributes. legislative_parameters — payroll legislative context.

Common Use Cases and Queries

Typical uses include extracting Japanese pre-tax withholding data for a payroll period, identifying year-end adjustment (YEA/RE_YEA) records, and reconciling salary versus bonus classifications. A representative query:

  • SELECT assignment_id, payroll_id, action_information13, action_information22 FROM apps.pay_jp_wic_assacts_v1 WHERE action_information13 = 'RE_YEA';
  • SELECT assignment_action_id, effective_date, date_earned FROM apps.pay_jp_wic_assacts_v1 WHERE business_group_id = :p_bg AND effective_date BETWEEN :p_from AND :p_to;

Because the view already applies the action-type, status, and category filters, callers should not re-apply those predicates unless narrowing further.