Search Results pay_jp_def_dep_os_dml_v




Overview
Explore in AI Chat

Overview

PAY_JP_DEF_DEP_OS_DML_V is an Oracle E-Business Suite database view owned by the APPS schema and defined within the PAY (Payroll) product family. As stated in the documented metadata, this view is used exclusively for Japanese localization. Its name reflects its purpose: "JP" denotes Japan, "DEF_DEP" refers to dependent definitions, "OS" typically signifies "Old Style" or out-of-system dependent records, and "DML" indicates that the object is designed to support Data Manipulation Language operations within the Japanese payroll localization.

In Oracle EBS 12.1.1 and 12.2.2, Japanese payroll requires specialized handling of dependent information and payer details that differ from standard global payroll processing. This view exposes a flattened access path to the PAY_ACTION_INFORMATION table, presenting both standard action information columns and Japanese-specific dependent attributes. The view is treated as a reporting and integration layer, allowing localization-specific forms, concurrent programs, and third-party interfaces to read and write dependent information without directly referencing the underlying base table. Because it includes ROWID and the full DML-compatible column set, it can be used within forms and APIs that require updatable query structures.

Underlying Base Objects

The view is defined over a single documented base object: PAY_ACTION_INFORMATION, accessed through a SYNONYM. PAY_ACTION_INFORMATION is a core Payroll table that stores generic action information records, using a category and a set of numbered attributes (ACTION_INFORMATION1 through ACTION_INFORMATION18) to store context-specific data. The view text selects ROWID along with ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER, ACTION_CONTEXT_ID, ACTION_CONTEXT_TYPE, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_INFORMATION_CATEGORY, the eighteen generic ACTION_INFORMATION attributes, and standard WHO audit columns (LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE) directly from PAY_ACTION_INFORMATION.

The documented column list is broader than the view text attribute set, indicating that the metadata describes a localized logical model where the generic ACTION_INFORMATION attributes map to Japanese dependent and payer fields such as LAST_NAME_KANA, FIRST_NAME_KANA, DATE_OF_BIRTH, DATE_OF_DEATH, OCCUPATION, and the out-of-system salary payer name and address fields. The view therefore acts as a semantic bridge between the generic action information storage model and the Japanese dependent definition requirements.

Key Columns

  • ACTION_INFORMATION_ID — Primary identifier for the action information record.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent DML operations.
  • ACTION_CONTEXT_TYPE / ACTION_CONTEXT_ID — Define the context under which the action information applies.
  • ASSIGNMENT_ID / ASSIGNMENT_ACTION_ID — Link the record to a specific assignment and payroll action run.
  • EFFECTIVE_DATE — The date from which the dependent information is effective.
  • ACTION_INFORMATION_CATEGORY — Classifies the type of action information stored.
  • LAST_NAME_KANA / FIRST_NAME_KANA — Japanese phonetic (kana) representations of the dependent's name.
  • LAST_NAME / FIRST_NAME — Standard kanji or character name fields.
  • DATE_OF_BIRTH / DATE_OF_DEATH — Life event dates relevant to dependent eligibility.
  • OCCUPATION / OCCUPATION_O — Occupation and its alternate or original representation.
  • OS_SALARY_PAYER_NAME, OS_SALARY_PAYER_ADDRESS and their "_O" variants — Out-of-system salary payer details used in Japanese tax and dependent reporting.
  • CONTACT_EXTRA_INFO_ID / CONTACT_RELATIONSHIP_ID — Link dependent contact records to their relationship definitions.
  • WHO columns — Audit trail for creation and last update.

Common Use Cases and Queries

This view is typically queried by Japanese localization reports, dependent registration forms, and interfaces that submit or retrieve out-of-system dependent payer information. A typical retrieval of active dependent information for an assignment follows:

SELECT action_information_id, assignment_id, effective_date, last_name_kana, first_name_kana, last_name, first_name, date_of_birth, os_salary_payer_name, os_salary_payer_address FROM apps.pay_jp_def_dep_os_dml_v WHERE assignment_id = :p_assignment_id AND effective_date <= SYSDATE ORDER BY effective_date DESC;

Because the view exposes ROWID and OBJECT_VERSION_NUMBER, it may also be used in correction or migration scripts that reconcile dependent and payer data between legacy Japanese payroll systems and Oracle EBS. Queries filtering on ACTION_INFORMATION_CATEGORY are common when isolating dependent definition records from other action information types. All access should respect the Japanese localization configuration and the standard EBS row-level security and audit conventions.