Search Results over_and_short_amount




Overview

APPS.PAY_JP_WL_BON_PAY_INFO_V is a reporting view in the Oracle E-Business Suite (EBS) Applications (APPS) schema that exposes Japanese statutory bonus payment information captured during payroll processing. It is a Japanese localization object, designated in FND Design Data as PAY.PAY_JP_WL_BON_PAY_INFO_V, and holds a status of VALID. The "WL" and "BON" components of the name indicate that the view surfaces "Work List" and "Bonus" data, meaning it consolidates the bonus payment details that payroll administrators review, validate, and process during a bonus payroll run.

The view functions as a denormalized, read-only presentation layer over the payroll action information stored in the underlying infrastructure. Its principal role is to make Japanese bonus payment computations—including social insurance deductions, dependent counts, tax rates, and both national and local tax withholding—available for reporting, payroll verification, and downstream integration. Because it consolidates these values into a single row per bonus payment action, it is well suited to ad hoc reporting tools, concurrent program extracts, and interfaces that must transmit bonus and withholding information to external systems such as statutory filing or accounting platforms.

The view is defined over base objects that include the FND_DATE package, the FND_NUMBER package, and the PAY_ACTION_INFORMATION synonym. Its columns are populated through the action information mechanism, in which payroll action parameters are stored and then decoded. Users searching for LOCAL_TAX_AMOUNT will find that this view exposes that column directly.

Underlying Base Objects

Per ETRM 12.2.2 metadata, the referenced base objects are:

  • PAY_ACTION_INFORMATION (SYNONYM) — The core source of the view's data. This table stores key-value action information records tied to assignment actions. The view decodes these records into the structured columns listed in its definition.
  • FND_DATE (PACKAGE) — Used to convert stored date values into proper date datatypes for date-typed columns such as BONUS_PAYMENT_DATE and EFFECTIVE_DATE.
  • FND_NUMBER (PACKAGE) — Used to convert stored character representations of numeric values into the NUMBER datatype for the many amount and count columns.

The view is joined logically to payroll action structures via ASSIGNMENT_ACTION_ID and ASSIGNMENT_ID, linking each payment record to a specific assignment action and employee assignment. ACTION_INFORMATION_ID identifies the originating action information row, while ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY classify the record within the Japanese bonus processing context.

Key Columns

Principal columns exposed by the view include:

Common Use Cases and Queries

Typical applications include bonus withholding verification, statutory reporting of social insurance and local tax, payroll audit reconciliation, and data extracts feeding external accounting or tax filing systems. A common query retrieves the local tax withholding for a given employee or bonus period:

  • Review bonus payments by person and date: SELECT person_id, bonus_payment_date, total_payment_amount, total_deduction_amount, net_balance_amount, local_tax_amount FROM apps.pay_jp_wl_bon_pay_info_v WHERE person_id = :p_person_id AND bonus_payment_date BETWEEN :p_start AND :p_end;
  • Analyze local tax against computed and collected tax: SELECT bonus_payment_date, computed_tax_amount, collected_tax_amount, ci_amount, local_tax_amount FROM apps.pay_jp_wl_bon_pay_info_v WHERE assignment_id = :p_assignment_id ORDER BY bonus_payment_date;
  • Aggregate social insurance and tax components for a payroll period: SELECT SUM(si_deduction_amount), SUM(hi_deduction_amount), SUM(total_si_amount), SUM(local_tax_amount) FROM apps.pay_jp_wl_bon_pay_info_v WHERE bonus_payment_date BETWEEN :p_start AND :p_end;

Because all monetary values are numeric, aggregations are performed directly without further conversion. Reports should always qualify the view with the APPS schema (or an appropriate synonym) and restrict by date and person/assignment to avoid full-table scans on the underlying action information data.