Results for “itax_yea_category”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_JP_PRE_ITAX_V1 is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the PAY (Payroll) product family. It exists specifically to support Japanese statutory payroll reporting, serving as the underlying data source for the concurrent programs PAYJPITT (Income Tax), PAYJPITW, and PAYJPPRS, as well as for associated value sets used within those report parameters. The view consolidates pre-tax declaration data captured against completed payroll and assignment actions, exposing organization-level, salary-category, and income-tax-category attributes required by Japanese tax reporting regulations.

The view operates over action information records associated with the JP_PRE_TAX_1 information category — the Japanese pre-tax declaration DFF context — and restricts output to assignment actions in a completed ('C') status linked to payroll actions of type 'R', 'Q', 'B', or 'I' (Regular, QuickPay, Bonus, and Immediate). Because it is derived entirely from transactional payroll action data rather than configuration tables, the view is refreshed implicitly as payroll runs are completed and their action information is populated.

Underlying Base Objects

The view is defined over four documented base objects:

• PAY_PAYROLL_ACTIONS — supplies PAYROLL_ACTION_ID, BUSINESS_GROUP_ID, ACTION_TYPE, and EFFECTIVE_DATE; drives the restriction on action types.
• PAY_ASSIGNMENT_ACTIONS — the primary linkage between assignments and payroll actions; filters ACTION_STATUS = 'C' and provides ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID, and ACTION_SEQUENCE.
• PAY_ACTION_INFORMATION — the descriptive flexfield store, filtered on ACTION_INFORMATION_CATEGORY = 'JP_PRE_TAX_1' and ACTION_CONTEXT_TYPE = 'AAP', providing the tax organization, salary category, and income tax category attributes.
• FND_NUMBER (Package) — used via CANONICAL_TO_NUMBER to convert the character-form ACTION_INFORMATION1 value into a numeric assignment action identifier for joining to PAY_ASSIGNMENT_ACTIONS.

PAY_ACTION_INTERLOCKS is also documented as a referenced object, typically involved in interlock processing logic associated with action sequencing. The join chain requires matching BUSINESS_GROUP_ID, PAYROLL_ACTION_ID, and effective-date contexts between the three payroll tables.

Key Columns

• BUSINESS_GROUP_ID — the enterprise business group, essential for multi-organization segregation.
• ITAX_ORGANIZATION_ID — derived from ACTION_INFORMATION21; identifies the tax-reporting organization.
• EFFECTIVE_DATE / DATE_EARNED — the payroll action effective date and the date the earnings were earned; used for reporting period determination.
• ASSIGNMENT_ID / ASSIGNMENT_ACTION_ID / ACTION_SEQUENCE — identifiers linking the record to the person's assignment and the specific action instance.
• SALARY_CATEGORY — from ACTION_INFORMATION13; restricts to values such as SALARY, BONUS, SP_BONUS, TERM, YEA, or RE_YEA.
• ITAX_CATEGORY — from ACTION_INFORMATION22; values include M_KOU, M_OTSU, D_KOU, D_OTSU, and D_HEI, reflecting Japanese income tax withholding categories.
• ITAX_YEA_CATEGORY — from ACTION_INFORMATION23; classifies year-end adjustment (YEA) treatment.

Common Use Cases and Queries

The primary use case is feeding statutory Japanese income tax reports. The view's built-in NOT EXISTS filter prevents a year-end adjustment assignment action from appearing alongside ordinary payroll actions for the same assignment and tax organization within the same calendar year, ensuring clean report output.

A typical query retrieves tax declaration rows for a period and organization:

• SELECT assignment_id, itax_organization_id, salary_category, itax_category, itax_yea_category, effective_date FROM pay_jp_pre_itax_v1 WHERE business_group_id = :p_bg_id AND itax_organization_id = :p_org_id AND effective_date BETWEEN :p_start AND :p_end;

Analysts also use it to reconcile which assignments contributed to a tax filing, or to validate that YEA and RE_YEA rows were captured correctly. Because it exposes only completed actions with valid JP_PRE_TAX_1 DFF data, it is a reliable validation source before and after running PAYJPITT, PAYJPITW, and PAYJPPRS.