Search Results pay_jp_input_value_ids_v




Overview
Explore in AI Chat

Overview

The view PAY_JP_INPUT_VALUE_IDS_V is an APPS-owned database view delivered as part of the Oracle Payroll (PAY) product, specifically supporting the Japanese localization. It is documented as VALID in ETRM for both Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose the surrogate input value identifiers (IV_IDs) for a defined set of Japanese statutory balance input values — the qualification and disqualification dates, associated organization/location references, and reporting output flag used in Health Insurance (HI) and Welfare Pension (WP) processing, as well as Social Insurance (SI) reporting.

Rather than storing data itself, the view resolves the internal primary keys that identify specific balance input values in the payroll balance input value tables. These identifiers are required whenever a report, concurrent program, formula, or integration must read or write the corresponding balance input values for a given business group and legislation. The view therefore functions as a lookup utility that abstracts the underlying Input Value definition lookups behind a single row per business group.

Underlying Base Objects

The documented metadata identifies two referenced base objects:

  • PAY_JP_BALANCE_PKG (PACKAGE) — a Japanese localization payroll package. The view calls the function GET_INPUT_VALUE_ID seven times, once for each balance input value of interest. Each call passes a balance name, an input value name, the business group identifier, and the legislation code, and returns the matching input value ID.
  • PER_BUSINESS_GROUPS (VIEW) — the source of the driving BUSINESS_GROUP_ID and LEGISLATION_CODE values. Every row of this view is joined with the business group view, producing output for each defined business group.

The dependency chain is therefore PER_BUSINESS_GROUPS → PAY_JP_BALANCE_PKG.GET_INPUT_VALUE_ID → the underlying payroll balance input value definition tables. Because the view is defined over a package function that accepts parameters, the resolution of each IV_ID occurs at query time and reflects the input value definitions currently in effect for each business group.

Key Columns

Common Use Cases and Queries

The view is typically used to obtain the correct input value IDs before constructing queries or API calls against the balance input value tables. A common pattern is to retrieve the identifiers for a specific business group and pass them into further processing. For example:

SELECT business_group_id,
       hi_qualified_date_iv_id,
       hi_disqualified_date_iv_id,
       output_flag_iv_id
  FROM apps.pay_jp_input_value_ids_v
 WHERE business_group_id = :p_business_group_id;

Integration and report developers use this view when building Japanese social insurance or labour insurance compliance extracts, ensuring they reference the same input value definitions the localization package expects. It also supports diagnostic queries to confirm that the environment has the expected input values defined for each business group:

SELECT business_group_id,
       wp_qualified_date_iv_id,
       wp_disqualified_date_iv_id,
       wp_organization_iv_id
  FROM apps.pay_jp_input_value_ids_v;

Because the view returns one row per business group and derives all identifiers from the localization package, it should be queried within the APPS schema or an account with the necessary grants, and is best consumed as a lookup rather than as a high-volume reporting source.