Search Results pay_jp_bal_matrix_by_act_v




Overview
Explore in AI Chat

Overview

PAY_JP_BAL_MATRIX_BY_ACT_V is a payroll balance view owned by the APPS schema in Oracle E-Business Suite. As documented in the ETRM metadata for release 12.2.2, this object is a VIEW with VALID status, belonging to the PAY - Payroll product family. The documented description states that this is a balance view used exclusively for Japanese localization. It is therefore not a global payroll object and should be treated as a Japan-specific reporting artifact.

The view presents payroll balance information at the level of an assignment action. Its principal role is to expose, in a single denormalized row, the various period-to-date balance accumulations that Japanese payroll legislation and business practice require: monthly, yearly, fiscal-year, and several Japan-specific reset-based accumulations. Rather than forcing report authors to call the balance retrieval API repeatedly, the view pre-computes a matrix of balance values keyed by assignment action and balance type.

Underlying Base Objects

The view is defined with an ORDERED USE_NL hint, indicating a deliberate nested-loop join strategy across a defined set of base objects. The documented referenced objects are:

The join order PPA, PRR, PRRV, FEED, PBTTL reflects the intended execution path: from assignment action through run results and run result values, to the balance feed, and finally to the balance type translation table.

Key Columns

The projection exposes the assignment action identifier along with balance type and UOM attributes. Important columns include:

Common Use Cases and Queries

Typical use cases include Japanese payroll balance reporting, verification of period-based accumulations during payroll runs, and integration of Japan balance data into custom reports or extracts. A representative query follows:

SELECT assignment_action_id, balance_name, balance_uom, currency_code, asg_mtd_jp_bal, asg_ytd_jp_bal, asg_fytd_jp_bal FROM apps.pay_jp_bal_matrix_by_act_v WHERE assignment_action_id = :p_action_id;

Because each row carries every reset variant, the view is well suited to matrix-style reporting where a single record must display all Japanese balance accumulations side by side. Queries should always filter on the assignment action or balance type, given the volume produced by the nested-loop join path.