Search Results pay_jp_def_emp_dml_v




Overview
Explore in AI Chat

Overview

PAY_JP_DEF_EMP_DML_V is an Oracle E-Business Suite database view owned by the APPS schema in the Payroll (PAY) product. As documented in the ETRM metadata, it is used exclusively for the Japanese localization. The view serves as a locale-specific projection of the generic Payroll action information model, exposing person-related declarative attributes — such as name kana, address, marital status, disability, and dependent status indicators — that Japanese statutory reporting requires. Because the object name carries the _DML_V suffix, it is intended to support Data Manipulation Language operations through an interface view, typically used by Oracle Forms or programmatic APIs to insert, update, and query Japanese-specific employee information stored within the generic action information framework.

The view does not create a separate physical entity. Instead, it re-presents a filtered, aliased subset of columns from its underlying storage table, allowing the Japanese localization layer to bind application-defined column names to the generic ACTION_INFORMATION1 through ACTION_INFORMATION23 attributes.

Underlying Base Objects

According to the documented ETRM metadata, PAY_JP_DEF_EMP_DML_V is defined over a single base object: PAY_ACTION_INFORMATION, accessed via a SYNONYM. The view text selects the ROWID pseudocolumn along with action-information identity, versioning, and audit columns, and maps ACTION_CONTEXT_ID to ASSIGNMENT_ACTION_ID.

  • PAY_ACTION_INFORMATION — the transactional table storing generic, context-driven action records. Column names such as ACTION_INFORMATION1..23 are reused across localizations; the Japanese view renames these to meaningful business columns.
  • ACTION_CONTEXT_ID is aliased as ASSIGNMENT_ACTION_ID, tying each record to an assignment action processed during payroll or a related payroll event.
  • ACTION_CONTEXT_TYPE and ACTION_INFORMATION_CATEGORY provide the discriminator that identifies which business transaction (for example, a Japanese employee declaration) the row represents, and the view is normally filtered on these values.

Key Columns

The column list documented in the ETRM metadata exposes both standard audit columns and the Japanese-localized business attributes:

Common Use Cases and Queries

The view is principally consumed by the Japanese localization of Payroll forms and concurrent processes that maintain employee declaration data. Typical access patterns filter on the context type and category to isolate relevant records.

  • Retrieve all declaration records for an assignment: SELECT * FROM apps.pay_jp_def_emp_dml_v WHERE assignment_id = :p_assignment_id AND ACTION_CONTEXT_TYPE = :p_context_type;
  • Extract kana name and address data for statutory output: SELECT last_name_kana, first_name_kana, postal_code, address FROM apps.pay_jp_def_emp_dml_v WHERE action_information_category = :p_category;
  • Identify dependents flagged with disabilities or aged status: SELECT assignment_id, disability_type, aged_type, widow_type FROM apps.pay_jp_def_emp_dml_v WHERE married_flag = 'Y';
  • DML maintenance through the interface, using OBJECT_VERSION_NUMBER for concurrency control.

Because it is a localization-only object, it should not be referenced by global (non-Japanese) customizations.