Search Results pay_jp_payjpdmw_values_v




Overview
Explore in AI Chat

Overview

The view APPS.PAY_JP_PAYJPDMW_VALUES_V is a balance view belonging to the Payroll (PAY) product family in Oracle E-Business Suite, and it is documented as being reserved for the Japanese localization. Its status is VALID in the APPS schema. Rather than storing data, the view resolves balance values at runtime by invoking PL/SQL functions, most notably PAY_JP_BALANCE_VIEW_PKG.GET_VALUE and PAY_BALANCE_PKG.GET_VALUE. This design places the view in the reporting and integration layer: it gives consumers a queryable, row-shaped representation of payroll balances for a selected assignment without requiring them to call balance APIs directly.

The view behaves as a general balance provider for the Japanese legislation. It presents each defined balance together with its dimension attributes and a computed value, so that downstream Japanese payroll reports, extracts, and integration interfaces can read balances such as period-to-date and year-to-date figures through ordinary SQL.

Underlying Base Objects

The documented base objects are extensive and reflect the view's dependency on payroll run results, balance definitions, and date context. They include PER_ALL_ASSIGNMENTS_F, which supplies the assignment and its effective dating, and PAY_DEFINED_BALANCES, which supplies the balance definition, dimension, and legislation filtering. PAY_BALANCE_DIMENSIONS_VL contributes the dimension name, level, period type, start date code, and database item suffix that drive how each balance is calculated.

Session and date context come from FND_SESSIONS, joined through USERENV('SESSIONID') to obtain the effective date. Balance values and source rows are drawn from PAY_BALANCE_FEEDS_F, PAY_BALANCE_PKG, PAY_JP_BALANCE_VIEW_PKG, PAY_RUN_RESULTS, PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_ACTION_CONTEXTS, and PAY_INPUT_VALUES_F. Supporting objects include PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_TYPES_F_TL for element naming, FF_CONTEXTS for context values, PER_TIME_PERIODS for period definitions, and utility packages PAY_CORE_UTILS and FND_NUMBER.

Key Columns

  • ASSIGNMENT_ID — the assignment for which the balance value is resolved.
  • BALANCE_TYPE_ID — identifier of the balance type associated with the defined balance.
  • DEFINED_BALANCE_ID — the specific defined balance being evaluated.
  • DATABASE_ITEM_SUFFIX — suffix used to construct the balance database item name.
  • VALUE — the calculated balance amount, produced by the balance view package or the core balance package.
  • ELEMENT_NAME — element name, populated for element-level dimension rows and NULL for assignment-level rows.
  • EFFECTIVE_DATE — the effective date of the balance row, consistent with the session context.
  • SOURCE_ID — the originating source row, such as the element entry identifier.
  • DISPLAY_ORDER — ordering indicator used to control presentation, with assignment-level rows distinct from element-level rows.

Common Use Cases and Queries

The principal use case is Japanese payroll balance reporting, where a report must display the current value of one or more defined balances for a set of assignments. Because the view filters on the session effective date and the Japanese legislation, it is typically queried after the application session context has been established. A representative query is:

SELECT assignment_id, defined_balance_id, database_item_suffix, value
FROM apps.pay_jp_payjpdmw_values_v
WHERE assignment_id = :p_assignment_id
ORDER BY display_order;

A second common pattern retrieves element-level breakdowns, filtering on rows where ELEMENT_NAME IS NOT NULL to isolate period-to-date or year-to-date element balances. A third pattern joins the view back to PAY_DEFINED_BALANCES and PAY_BALANCE_DIMENSIONS_VL to label each value with its balance name. Because the view calls PL/SQL functions per row, queries should always be constrained by assignment and balance criteria to avoid excessive function execution across large assignment populations.