Search Results jp_isdf_entry

Overview

APPS.PAY_JP_ISDF_ENTRY_V is a reporting and integration view in Oracle E-Business Suite Payroll (Oracle HRMS / Payroll) for the Japanese localization. The suffix "ISDF" refers to the Japanese Insurance and Social Deduction Framework data that the payroll engine collects for statutory insurance premiums and related deductions applicable to Japanese payroll processing. The view presents a flattened, number-normalized projection of insurance premium entry information keyed by assignment action, so that downstream processes, reports, and interfaces can consume premium values without having to interpret the underlying descriptive flexfield storage directly.

The view is defined over PAY_JP_ISDF_ENTRY_DML_V and is filtered to a single action context: records where ACTION_CONTEXT_TYPE = 'AAP' (Assignment Action Processing) and ACTION_INFORMATION_CATEGORY = 'JP_ISDF_ENTRY'. This restriction means the view exposes only the ISDF entry rows associated with the assignment action processing context, presenting the data in the shape expected by payroll action-information consumers.

Underlying Base Objects

The documented base objects referenced by the view are:

• PAY_JP_ISDF_ENTRY_DML_V (VIEW) — The primary source of the row data. This DML-capable view is the transactional surface for the ISDF entry information; PAY_JP_ISDF_ENTRY_V selects from it, applying the ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY predicates.
• FND_NUMBER (PACKAGE) — The Oracle Application Object Library numeric utility package, used here via FND_NUMBER.CANONICAL_TO_NUMBER to convert the canonical (character) representation of numeric flexfield segment values into true NUMBER values. All ID and premium columns are wrapped in this function.

Both objects are owned by APPS, consistent with the EBS convention that seeded payroll views are deployed under the APPS schema. Because the view reads from a DML view rather than directly from base tables, the ISDF entry data is presented through the same abstraction layer used for data manipulation, ensuring that the reported values match what the payroll engine persists.

Key Columns

The view exposes a combination of administrative, key, and premium columns:

• ROW_ID, OBJECT_VERSION_NUMBER, LAST_UPDATE_* / CREATED_BY / CREATION_DATE — Standard EBS WHO columns and row identity attributes used for concurrency and auditing.
• ACTION_INFORMATION_ID, ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID — Identifiers linking the entry to an assignment action and to the assignment (employee) it belongs to.
• EFFECTIVE_DATE, ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, STATUS — Context and lifecycle attributes; the view is restricted to ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_ISDF_ENTRY'.
• Datetrack mode columns — INS_DATETRACK_UPDATE_MODE and IS_DATETRACK_UPDATE_MODE indicate the date-tracked update mode applied to insurance (INS) and income-tax/social (IS) entries.
• Element entry identifiers — INS_ELEMENT_ENTRY_ID, INS_EE_OBJECT_VERSION_NUMBER, IS_ELEMENT_ENTRY_ID, IS_EE_OBJECT_VERSION_NUMBER, all canonical-to-number converted, referencing the payroll element entries that carry the wages and deductions.
• Insurance premium columns — Life general and pension premiums (LIFE_GEN_INS_PREM, LIFE_PENS_INS_PREM), non-life long/short term premiums (NONLIFE_LONG_INS_PREM, NONLIFE_SHORT_INS_PREM), earthquake insurance (EARTHQUAKE_INS_PREM), social insurance (SOCIAL_INS_PREM), mutual aid (MUTUAL_AID_PREM), national pension (NATIONAL_PENS_INS_PREM), and spouse income (SPOUSE_INCOME). The suffix "_O" columns (for example LIFE_GEN_INS_PREM_O) hold the corresponding override or original values.

Common Use Cases and Queries

Typical usage involves reporting Japanese insurance deduction amounts for an assignment action, reconciling element entries against ISDF entries, and feeding interfaces that require numeric premium values.

• List ISDF entries for a given payroll run or assignment action by filtering on ASSIGNMENT_ACTION_ID.
• Retrieve all premium components and their overrides for an assignment across a date range using EFFECTIVE_DATE.
• Join to PAY_ASSIGNMENT_ACTIONS and PER_ALL_ASSIGNMENTS_F to resolve employee and payroll context.

Sample query:

SELECT assignment_action_id,
       assignment_id,
       effective_date,
       social_ins_prem,
       national_pens_ins_prem,
       spouse_income
  FROM apps.pay_jp_isdf_entry_v
 WHERE assignment_action_id = :p_assignment_action_id;

Because the view pre-applies the 'AAP' context and 'JP_ISDF_ENTRY' category filters, callers do not need to add those predicates themselves; they should filter on assignment, date, or action identifiers as required.