Search Results housing_loan_deduction

Overview

APPS.PAY_JP_WL_YEA_INFO_V is a reporting view in the Oracle EBS Payroll (PAY) schema that exposes Japanese Year-End Adjustment (YEA) information. It is registered under FND Design Data as PAY.PAY_JP_WL_YEA_INFO_V and carries a VALID status in the APPS schema. The view surfaces the detailed tax, social insurance, and income figures that Oracle Payroll calculates for each employee during the Japanese year-end adjustment process, giving downstream users a single denormalized structure for reporting, reconciliation, and integration rather than requiring direct joins across the underlying payroll action-information storage.

Because the view is defined over payroll action-information data, its rows are keyed by the assignment action and the associated action context, and they are tied to a specific effective date. This makes it usable for point-in-time reporting on YEA results as well as for feeding external tax filing or interface processes. In Oracle EBS 12.1.1 and 12.2.2 the object behaves consistently as a read-only reporting layer; it is not intended as an update surface.

Underlying Base Objects

The documented metadata identifies two referenced base objects:

• PAY_ACTION_INFORMATION (SYNONYM) — the payroll action-information entity that stores the YEA result values generated by the Japanese payroll processes. The view reads from this synonym, which resolves to the underlying PAY action-information table in the APPS schema.
• FND_NUMBER (PACKAGE) — the Oracle Application Object Library numeric utility package. Its inclusion indicates the view uses FND_NUMBER conversion functions to translate stored character representations of numeric values into proper NUMBER datatypes for the columns exposed.

This design mirrors the standard action-information pattern in Oracle Payroll, where detailed results are persisted as key/value pairs against an assignment action and then exposed through views that decode and coerce them into typed columns.

Key Columns

The view exposes identifying keys plus a comprehensive set of YEA financial measures:

• ROW_ID, ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER — technical identifiers for the row and the underlying action-information record.
• ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, PERSON_ID — the assignment and person context for the adjustment.
• ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, EFFECTIVE_DATE — classification and effective dating of the action information.
• SAL_AMT and BON_AMT — salary amount and bonus amount. BON_AMT is the column most frequently searched, representing the bonus component of the employee's income subject to the year-end adjustment.
• TAXABLE_INCOME, SAL_TAX, BON_TAX, NET_INCOME, CALCULATED_TAX, YEA_ANNUAL_TAX, OVER_AND_SHORT_TAX — income, tax, and annual true-up figures.
• SI_DEDUCTION, SI_PREM, LI_PREM, EI_PREM, PP_PREM, NPI_PREMIUM, LONG_TERM_AI_PREM, MUTUAL_AID_PREM — social insurance and premium deductions.
• DEP_EXEMPTION, DEP_SPOUSE_EXEMPTION, DEPENDENT_EXEMPTION, BASIS_EXEMPTION, DEP_DISABLED_EXEMPTION, TOTAL_SE_DE_BE_DISE — dependent and basis exemption amounts.
• SPOUSE_SP_EXEMPT, SPOUSE_INCOME, HOUSING_LOAN_DEDUCTION, TOTAL_INCOME_DEDUCTION, NET_ASS_SAL_INCOME_MONEY — spouse, housing loan, and net income measures.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Typical usage centers on retrieving YEA results per person or assignment, verifying bonus and salary amounts, and reconciling calculated tax against deductions. A representative query for the BON_AMT search term is:

• SELECT person_id, assignment_id, effective_date, sal_amt, bon_amt, taxable_income, yea_annual_tax FROM apps.pay_jp_wl_yea_info_v WHERE person_id = :p_person_id;
• Summarizing bonuses by effective date: SELECT effective_date, SUM(bon_amt) FROM apps.pay_jp_wl_yea_info_v GROUP BY effective_date;
• Reconciling tax: SELECT assignment_action_id, calculated_tax, sal_tax, bon_tax, over_and_short_tax FROM apps.pay_jp_wl_yea_info_v;

These queries support year-end reporting, audit verification, and downstream tax interfaces.