Results for “pay_jp_def_dep_dml_v”

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

Overview

PAY_JP_DEF_DEP_DML_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product, present in releases 12.1.1 and 12.2.2. Per the ETRM metadata, the object holds a VALID status and is documented explicitly as being used "for Japanese localization only." It is a DML-enabled view, as reflected by its name suffix, exposing a ROWID pseudo-column alongside the persisted columns of its underlying base table. This means the view is not merely a read-only projection; it forms the data-access layer through which form-based maintenance and programmatic DML are performed against Japanese-specific action information records.

In practice the view presents dependent and contact-related action information rows (dependents, their kana and kanji names, addresses, disability details, and estimated annual income) that are stored in the generic PAY_ACTION_INFORMATION structure. For Japanese payroll and statutory reporting, this abstraction allows the localization components to query and maintain dependent data without directly coupling to the wide, key-flexfield-oriented base table.

Underlying Base Objects

The documented referenced base object is PAY_ACTION_INFORMATION, accessed through a SYNONYM. The view text confirms a direct, unfiltered SELECT: it projects ROWID plus the standard columns of PAY_ACTION_INFORMATION (ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER, ACTION_CONTEXT_ID, ACTION_CONTEXT_TYPE, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_INFORMATION_CATEGORY, the 26 ACTION_INFORMATION flexfield segments, and the standard WHO audit columns such as LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY and CREATION_DATE).

Because the view is defined as a simple projection over a single table with no joins or aggregation, Oracle can treat it as inherently updatable. The presence of ROWID and OBJECT_VERSION_NUMBER supports row-level identification and optimistic locking during DML, while the underlying table retains the physical storage and any associated constraints and indexes.

Key Columns

The ETRM column list is broader than the visible view text, reflecting the descriptive names by which the generic ACTION_INFORMATION segments are surfaced for Japanese dependent data. Notable columns include:

• ROW_ID / ACTION_INFORMATION_ID — The row identifier and primary key of the underlying action information record.
• OBJECT_VERSION_NUMBER — Optimistic locking attribute, incremented on each update.
• ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_CONTEXT_ID, ACTION_CONTEXT_TYPE — Contextual keys tying the record to a specific assignment, date, and action context.
• ACTION_INFORMATION_CATEGORY — Classifies the information type, distinguishing dependent records from other action information categories.
• LAST_NAME_KANA / FIRST_NAME_KANA, LAST_NAME / FIRST_NAME — Dependent names in kana and kanji respectively, specific to Japanese localization.
• CONTACT_TYPE, CONTACT_RELATIONSHIP_ID, CONTACT_EXTRA_INFO_ID — Dependent/contact classification and relationship identifiers.
• DATE_OF_BIRTH, DATE_OF_DEATH, ADDRESS — Personal and demographic attributes.
• DEP_TYPE / DEP_TYPE_O, OCCUPATION / OCCUPATION_O, ESTIMATED_ANNUAL_INCOME / ESTIMATED_ANNUAL_INCOME_O, DISABILITY_TYPE / DISABILITY_TYPE_O, DISABILITY_DETAILS / DISABILITY_DETAILS_O — Paired coded and descriptive fields supporting Japanese tax and social-insurance dependent declarations.
• CHANGE_DATE, CHANGE_REASON, STATUS, DATETRACK_UPDATE_MODE, DATETRACK_DELETE_MODE — Datetrack and lifecycle control columns governing effective-dated maintenance.

Common Use Cases and Queries

Typical usage covers Japanese dependent maintenance and statutory reporting: retrieving active dependents for an assignment, extracting kana/kanji names for declaration forms, and maintaining datetracked changes.

List dependent records for an assignment:

SELECT action_information_id, assignment_id, effective_date, contact_type, last_name_kana, first_name_kana, last_name, first_name, date_of_birth
FROM apps.pay_jp_def_dep_dml_v
WHERE assignment_id = :p_assignment_id
AND NVL(status,'A') = 'A'
ORDER BY effective_date;

Retrieve dependent declaration attributes:

SELECT action_information_id, dep_type, occupation, estimated_annual_income, disability_type, disability_details
FROM apps.pay_jp_def_dep_dml_v
WHERE assignment_id = :p_assignment_id
AND action_information_category = :p_category;

Because the view is updatable, localization forms may issue INSERT, UPDATE and DELETE against it directly; the OBJECT_VERSION_NUMBER should be checked on update to preserve concurrency control.