Results for “pay_jp_def_assact_dml_v”

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

Overview

PAY_JP_DEF_ASSACT_DML_V is an Oracle E-Business Suite view owned by the APPS schema within the PAY (Payroll) product family. It is documented in the E-Business Suite Technical Reference Manual (ETRM) as a Japanese localization-only object, meaning its presence and behavior are relevant exclusively to legislations and business flows configured for Japan. The view is classified as VALID in the documented releases (12.1.1 and 12.2.2) and is registered as a VIEW object type.

Functionally, the view exposes rows from the action information infrastructure used by Oracle Payroll to store supplementary, categorized data attached to payroll actions. Because the name carries the "DML" suffix, the object is intended to support data manipulation semantics (query, insert, update, and delete against the underlying base) rather than read-only reporting, making it a candidate for use in localized integration or maintenance routines. It is not a general-purpose payroll reporting view; its role is narrow and dictated by the Japanese localization requirements it was created to satisfy.

Underlying Base Objects

The documented metadata identifies a single base object: PAY_ACTION_INFORMATION, accessed through a SYNONYM. The view text confirms the relationship, projecting a defined column list directly from PAY_ACTION_INFORMATION without joins to other tables. This one-to-one relationship means that every row in the view corresponds to a row in the base table as filtered or shaped by the view definition, and that any modification performed through the view is applied to PAY_ACTION_INFORMATION.

The view additionally exposes the ROWID pseudo-column of the base table, which is characteristic of views designed to support DML operations and to allow callers to identify physical rows unambiguously. The base table PAY_ACTION_INFORMATION is the payroll repository for categorized action information records, keyed by ACTION_INFORMATION_ID and associated with assignments and action contexts.

Key Columns

• ROWID — Pseudo-column identifying the physical row in PAY_ACTION_INFORMATION; required for DML targeting.
• ACTION_INFORMATION_ID — Primary identifier of the action information record.
• OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
• ACTION_CONTEXT_ID / ACTION_CONTEXT_TYPE — Identify the context within which the action information applies.
• ASSIGNMENT_ID — The assignment to which the action information relates.
• EFFECTIVE_DATE — Date from which the information is effective.
• ACTION_INFORMATION_CATEGORY — Classifies the record, governing interpretation of the ACTION_INFORMATION1 through ACTION_INFORMATION8 flexfield-style attribute columns.
• ACTION_INFORMATION1..8 — Generic descriptive attributes whose meaning is determined by the category.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, and CREATION_DATE provide standard who-column auditing.

The ETRM column listing additionally references names such as ASSIGNMENT_ACTION_ID, TAX_TYPE, TRANSACTION_STATUS, FINALIZED_DATE, FINALIZED_BY, EXPIRY_DATE, and comment fields; these reflect the Japanese localization's extended semantic layer over the generic action information structure.

Common Use Cases and Queries

Typical usage is confined to Japanese payroll localization maintenance and diagnostics. A basic retrieval for a given assignment might be written as:

SELECT action_information_id, assignment_id, effective_date, action_information_category, action_information1 FROM apps.pay_jp_def_assact_dml_v WHERE assignment_id = :p_assignment_id;

Because the view supports DML, it is also used in corrective scripts that update localized action information attributes, always keyed by ACTION_INFORMATION_ID and validated against OBJECT_VERSION_NUMBER to prevent lost updates. Audit-oriented queries join the audit columns to identify records created or changed by specific users within a date range. Given the object's localization-specific and DML-enabled nature, it should be invoked with the same care as direct base-table maintenance.