Search Results asg_jul2jun_jp_bal




Overview
Explore in AI Chat

Overview

APPS.PAY_JP_BAL_MATRIX_BY_DATE_V is a valid Oracle E-Business Suite view owned by the APPS schema, registered in FND Design Data as PAY.PAY_JP_BAL_MATRIX_BY_DATE_V. It presents a date-relative matrix of Japanese payroll balance values for a given assignment, exposing multiple legislative balance accumulations side by side on a single row. The view is marked Oracle Internal Use Only; Oracle Corporation does not support direct access to Oracle Applications data through this object except from standard Oracle Applications programs. It is therefore a supporting internal object for the Oracle Payroll Japanese localization rather than a published, supported application programming interface.

A user searching for asg_jul2jun_jp_bal has reached this view because that token is one of its exposed columns. The matrix layout — one row per assignment and balance type, with several period-based balance columns — is designed to let Oracle Payroll programs compare run, month-to-date, year-to-date, fiscal-year-to-date, inception-to-date, and Japanese-specific alternate period accumulations without repeatedly querying underlying run result tables.

Underlying Base Objects

The documented dependency list shows the view draws on both Oracle HR and Oracle Payroll objects. Contextual session information is obtained from FND_SESSIONS, while HR_GENERAL supplies standard HR utility functions. Payroll structure is sourced from PAY_PAYROLL_ACTIONS and PAY_ASSIGNMENT_ACTIONS, which identify the assignment’s payroll action and payroll run context. Balance definitions and their translated names come from PAY_BALANCE_TYPES, PAY_BALANCE_TYPES_TL, and PAY_BALANCE_FEEDS_F. Actual accumulated values originate from PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES. The Japanese-specific accumulation logic is encapsulated in the PAY_JP_BALANCE_VIEW_PKG package, which supplies the alternate period balances such as ASG_JUL2JUN_JP_BAL and ASG_APR2MAR_JP_BAL. The metadata states that this view is not referenced by any database object, confirming it is a reporting endpoint rather than a building block for other database views.

Key Columns

The view exposes sixteen columns. ASSIGNMENT_ID and BALANCE_TYPE_ID form the natural key, with BALANCE_NAME (VARCHAR2 80) and BALANCE_UOM (VARCHAR2 30) providing the balance’s display name and unit of measure; D_BALANCE_UOM (VARCHAR2 80) supplies a descriptive UOM value, and CURRENCY_CODE indicates the currency where applicable.

The numeric balance columns cover a family of periods:

  • ASG_RUN_BAL — the value from the current payroll run.
  • ASG_PROC_PTD_BAL — processed period-to-date balance.
  • ASG_MTD_JP_BAL — Japanese month-to-date balance.
  • ASG_YTD_JP_BAL — Japanese year-to-date balance.
  • ASG_FYTD_JP_BAL and ASG_FYTD2_JP_BAL — fiscal-year-to-date balances.
  • ASG_ITD_BAL — inception-to-date balance.
  • ASG_AUG2JUL_JP_BAL — balance accumulated over the August-to-July Japanese period.
  • ASG_JUL2JUN_JP_BAL — balance accumulated over the July-to-June period, the column sought by the user.
  • ASG_APR2MAR_JP_BAL — balance accumulated over the April-to-March Japanese fiscal period.

Common Use Cases and Queries

Because the view carries multiple period bases for the same assignment and balance, it is typically used by Japanese localization programs performing statutory reporting, year-end adjustment (年末調整), and reconciliation between run-based and calendar-based accumulations. Because it is unsupported for direct customer access, any use should be treated as diagnostic or read-only. A typical lookup is:

  • Retrieve all balances for one assignment: SELECT balance_name, balance_uom, asg_mtd_jp_bal, asg_ytd_jp_bal, asg_jul2jun_jp_bal FROM apps.pay_jp_bal_matrix_by_date_v WHERE assignment_id = :p_assignment_id;
  • Isolate the July-to-June accumulation: SELECT assignment_id, balance_name, asg_jul2jun_jp_bal FROM apps.pay_jp_bal_matrix_by_date_v WHERE asg_jul2jun_jp_bal IS NOT NULL;
  • Compare Japanese period bases: SELECT assignment_id, balance_name, asg_ytd_jp_bal, asg_apr2mar_jp_bal, asg_aug2jul_jp_bal FROM apps.pay_jp_bal_matrix_by_date_v WHERE balance_type_id = :p_balance_type_id;

All queries should include ASSIGNMENT_ID or BALANCE_TYPE_ID predicates to limit row volume, since the matrix returns one row per assignment and balance type combination.