Results for “pay_jp_wic_assacts_v2”

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

Overview

PAY_JP_WIC_ASSACTS_V2 is an Oracle E-Business Suite database view owned by the APPS schema and defined in the PAY (Payroll) product. As the object description states, it is used for Japanese localization only. The view presents assignment action and assignment set information relevant to Japanese statutory withholding, year-end adjustment, and related tax reporting requirements. In EBS 12.1.1 and 12.2.2 it is treated as a VALID database object and functions as a reporting and integration surface rather than a transaction entry point. Because no forms-driven DML is expected against a view of this type, its primary consumers are payroll extracts, localization reports, and downstream interfaces that must resolve Japanese tax attributes for an assignment action.

PAY_JP_WIC_ASSACTS_V2 is a refinement of PAY_JP_WIC_ASSACTS_V1. Where V1 supplies the raw assignment-action set, V2 applies additional conditional logic so that year-end adjustment (YEA) flags, period-of-service starts, and termination data follow the rules required by Japanese payroll processing.

Underlying Base Objects

The documented base objects referenced by this view are:

• PAY_JP_WIC_ASSACTS_V1 (VIEW) — the sole FROM-clause source; all column values originate here.
• FND_DATE (PACKAGE) — referenced for date handling.
• FND_NUMBER (PACKAGE) — referenced for numeric handling.

The body of the view selects exclusively from PAY_JP_WIC_ASSACTS_V1 (aliased WIC) and re-expresses several columns through CASE expressions. The most significant transformation concerns the YEA category. When ITAX_YEA_CATEGORY is populated, a correlated subquery counts rows in PAY_JP_WIC_ASSACTS_V1 (aliased WIC2) for the same ASSIGNMENT_ID with a greater ACTION_SEQUENCE whose EFFECTIVE_DATE falls before the start of the following year (ADD_MONTHS(TRUNC(WIC.EFFECTIVE_DATE,'YYYY'),12)). If any such future assignment actions exist, the expression returns '-1'; otherwise the original ITAX_YEA_CATEGORY is returned. This encodes the documented rule that a YEA followed by later assignment actions is not treated as a YEA but as a normal payment, so the previous-jobs and adjustment amounts do not contribute to the total.

Key Columns

V2 exposes the full V1 column set, including ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, ACTION_SEQUENCE, PAYROLL_ACTION_ID, BUSINESS_GROUP_ID, PAYROLL_ID, EFFECTIVE_DATE, DATE_EARNED, ITAX_ORGANIZATION_ID, SALARY_CATEGORY, ITAX_CATEGORY, PERSON_ID, and PERIOD_OF_SERVICE_ID. Several columns are specially derived in V2:

• ITAX_YEA_CATEGORY — returned as '-1' when later assignment actions exist after the YEA and before year end, otherwise the stored value, or NULL when no YEA category exists.
• DATE_START — populated only when DATE_START falls on or after the start of the effective year, otherwise NULL.
• LEAVING_REASON and ACTUAL_TERMINATION_DATE — populated only when EFFECTIVE_DATE is on or after the start of the year in which the actual termination date falls.

Tax amounts carried through are TAXABLE_AMT, SI_PREM, MUTUAL_AID, ITAX, ITAX_ADJUSTMENT, and DISASTER_TAX_REDUCTION. EMPLOYMENT_CATEGORY, LEGISLATIVE_PARAMETERS, and ITAX_ORGANIZATION_ID supply further classification for Japanese statutory processing.

Common Use Cases and Queries

Typical consumers retrieve assignment-action sets for a business group or payroll run and then evaluate YEA eligibility, period-of-service dates, and termination context for Japanese withholding and year-end adjustment reports.

Example: list YEA-eligible assignment actions for a person.

SELECT assignment_action_id, action_sequence, effective_date, itax_yea_category, taxable_amt, itax, itax_adjustment FROM apps.pay_jp_wic_assacts_v2 WHERE person_id = :p_person_id AND itax_yea_category IS NOT NULL ORDER BY action_sequence;

Example: reconcile Japanese tax amounts for a payroll action.

SELECT assignment_id, effective_date, taxable_amt, si_prem, mutual_aid, itax, disaster_tax_reduction FROM apps.pay_jp_wic_assacts_v2 WHERE payroll_action_id = :p_payroll_action_id;

Because the view contains the YEA-invalidation logic, reports that rely on ITAX_YEA_CATEGORY should query V2 rather than V1 to obtain the corrected treatment of assignment actions followed by later actions within the same year.