Search Results is_datetrack_update_mode




Overview
Explore in AI Chat

Overview

The APPS.PAY_JP_ISDF_ENTRY_V view is a Japanese localization object within the Oracle E-Business Suite Payroll (PAY) module. Its documented purpose in ETRM is narrow: "This view is used for Japanese localization only." The acronym ISDF refers to the Japanese Income and Social Insurance Deduction Form (a statutory tax and insurance reporting artifact), and this view exposes the element-entry data required to populate it. The view is a filtered projection over a DML-capable view, restricted to a single action context and information category so that consumers see only ISDF-relevant rows.

The view is primarily a reporting and integration surface. It does not perform payroll calculation; the underlying element entries are produced by the Japanese payroll processes. This view presents those entries in a canonical, typed form suitable for concurrent programs, BI Publisher data templates, and interfaces that generate the Japanese statutory form. It is owned by the APPS schema and is reported VALID on both 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects:

  • PAY_JP_ISDF_ENTRY_DML_V (VIEW) — the source of all columns, including the ROW_ID and object-version columns needed to support updates through the DML layer.
  • FND_NUMBER (PACKAGE) — invoked via FND_NUMBER.CANONICAL_TO_NUMBER to convert canonical-form numeric values into database NUMBER values for the insurance premium and income columns.

The text also references PAY_JP_ISDF_ENTRY_DML_V as contained within the FROM clause, with a WHERE predicate restricting output to ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_ISDF_ENTRY'. Because the base object is a DML view, the exposed rows correspond to assignment-action information records written by the Japanese payroll action-processing path.

Key Columns

The view carries both identifying/audit columns and approximately two dozen numeric premium and income columns. The principal columns the user searched for — the mutual aid premium — appear as MUTUAL_AID_PREM and its object-version companion MUTUAL_AID_PREM_O, both wrapped in FND_NUMBER.CANONICAL_TO_NUMBER. Related insurance columns include SOCIAL_INS_PREM, NATIONAL_PENS_INS_PREM, EARTHQUAKE_INS_PREM, NONLIFE_SHORT_INS_PREM, NONLIFE_LONG_INS_PREM, LIFE_GEN_INS_PREM, and LIFE_PENS_INS_PREM, each with a corresponding _O object-version column.

Common Use Cases and Queries

Typical scenarios include reconciling mutual aid and social insurance premiums from element entries, feeding the Japanese ISDF statutory report, and validating that the premium values stored on the action information record match the element entries for a given assignment and period.

Sample query retrieving mutual aid premiums for a specific assignment:

SELECT assignment_id, effective_date,
       mutual_aid_prem, mutual_aid_prem_o,
       social_ins_prem, national_pens_ins_prem
FROM   apps.pay_jp_isdf_entry_v
WHERE  assignment_id = :p_assignment_id
AND    effective_date BETWEEN :p_start AND :p_end
ORDER  BY effective_date;

Sample query summarizing insurance premiums by action:

SELECT assignment_action_id,
       SUM(mutual_aid_prem)        AS total_mutual_aid,
       SUM(social_ins_prem)        AS total_social_ins,
       SUM(national_pens_ins_prem) AS total_national_pens
FROM   apps.pay_jp_isdf_entry_v
WHERE  status = 'PROCESSED'
GROUP  BY assignment_action_id;

Because the view is restricted to the 'AAP' / 'JP_ISDF_ENTRY' context, consumers do not need to reapply those predicates, though adding effective-date or assignment filters is recommended for performance.