Results for “pay_jp_def_dep_oe_dml_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_JP_DEF_DEP_OE_DML_V is a database view owned by the APPS schema in Oracle E-Business Suite, documented as VALID in both the 12.1.1 and 12.2.2 releases. It belongs to the PAY (Payroll) product family and, per the ETRM metadata, is used for Japanese localization only. The view is not designed for general payroll processing; rather, it is a localized construct that exposes Japanese-specific dependent and family contact information (dependents, relationship, name kana, address, and related attributes) for data manipulation and query purposes.

The suffix "DML_V" indicates that this is a data manipulation view designed to support insert, update, and delete operations, not merely read-only reporting. In the Oracle EBS Japanese localization, such views are typically used by forms and business flows that must maintain dependent/other-eligible (OE) information for payroll and benefits processing in Japan.

Underlying Base Objects

The documented base object referenced by this view is PAY_ACTION_INFORMATION, which appears in the metadata as a SYNONYM. The view text confirms this mapping: it selects a broad set of columns from PAY_ACTION_INFORMATION, including ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_INFORMATION_CATEGORY, ACTION_INFORMATION1 through ACTION_INFORMATION23, plus the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ROWID.

The ROWID exposure is a key indicator that the view supports DML operations against the underlying table. PAY_ACTION_INFORMATION is the repository for date-tracked, category-based action records attached to assignments; the Japanese localization stores dependent and contact information within the ACTION_INFORMATION1..23 flex columns.

Key Columns

The documentation lists a number of columns whose names reflect the Japanese localization semantics, including:

• ACTION_INFORMATION_ID — primary identifier for the action information row.
• ASSIGNMENT_ID — the assignment to which the dependent/contact record belongs.
• EFFECTIVE_DATE — date from which the record is effective, supporting date-tracked updates.
• ACTION_INFORMATION_CATEGORY — category used to classify the record.
• LAST_NAME_KANA / FIRST_NAME_KANA — phonetic (kana) representations of names, required for Japanese processing.
• LAST_NAME / FIRST_NAME — dependent or contact names in standard form.
• CONTACT_TYPE, DATE_OF_BIRTH, DATE_OF_DEATH, ADDRESS — dependent/contact demographic data.
• CHANGE_DATE, CHANGE_REASON — audit information for changes to the record.
• OCCUPATION, OCCUPATION_O — occupation details, with an "O" variant typically indicating an override or alternative value.
• OE_CONTACT_RELATIONSHIP_ID and OE_CONTACT_RELATIONSHIP_ID_O — relationship identifiers for the "other eligible" (OE) contact, again with an override variant.
• OE_FULL_NAME, OE_CONTACT_TYPE, OE_ADDRESS — other-eligible contact details.
• DATETRACK_UPDATE_MODE and DATETRACK_DELETE_MODE — control flags indicating whether updates/deletes should be date-tracked.
• OBJECT_VERSION_NUMBER / CEI_OBJECT_VERSION_NUMBER — versioning columns for optimistic locking.

Common Use Cases and Queries

Because the view exposes ROWID and DML-relevant columns, it is typically used by Japanese localization forms or concurrent processing that maintain dependent and other-eligible contact records against PAY_ACTION_INFORMATION. A common read scenario is retrieving current dependent information for an assignment on or after a given effective date:

SELECT assignment_id, effective_date, last_name, first_name, last_name_kana, first_name_kana, contact_type, date_of_birth FROM pay_jp_def_dep_oe_dml_v WHERE assignment_id = :p_assignment_id AND effective_date <= SYSDATE ORDER BY effective_date DESC;

For DML-driven localization flows, the view supports updates to name kana, address, occupation, or OE contact relationship values, controlled by the DATETRACK_UPDATE_MODE and DATETRACK_DELETE_MODE flags, together with the object version numbers for concurrency control. Developers should note that this view is intended strictly for Japanese localization and should not be used for general payroll queries; for standard reporting, the underlying PAY_ACTION_INFORMATION table or its standard DML views are preferred. As with any APPS-owned view, direct changes should be avoided outside of supported localization functionality.