Results for “transfer_date”

50+ results




Overview
Explore in AI Chat

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

Overview

The view PAY_JP_ISDF_ASSACT_DML_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product family. As documented in the ETRM metadata for release 12.1.1 and 12.2.2, the object is a VALID view whose description explicitly limits its use to the Japanese localization only. The name encodes its purpose: it is a DML (Data Manipulation Language) interface over payroll action information, scoped for the Japanese ISDF (a Japanese statutory filing/reporting context) assignment-action processing.

The view presents a row-addressable projection of the PAY_ACTION_INFORMATION table, exposing ROWID alongside the principal identity, context, and action-information columns. Because it includes the ROWID pseudocolumn, this view is designed to support updatable or DML-oriented access patterns — allowing callers to address and manipulate individual action information rows by physical row identifier. In EBS reporting and integration, it functions as a controlled access layer that insulates consumer processes from direct base-table access while preserving the full column set required by the Japanese localization logic.

Underlying Base Objects

The documented referenced base object is PAY_ACTION_INFORMATION, accessed via a synonym. The view is defined as a straightforward SELECT over that base table, with no documented joins. The select list comprises:

Because the view text references only PAY_ACTION_INFORMATION, its behavior mirrors that table for the columns it exposes, adding no filtering predicate at the view level. All Japan-specific semantics are therefore carried by the ACTION_INFORMATION_CATEGORY and ACTION_INFORMATION flexfield-style columns rather than by view-level logic.

Key Columns

  • ROWID / ROW_ID — the physical row address; the presence of ROWID distinguishes this as a DML-capable view.
  • ACTION_INFORMATION_ID — primary surrogate key of the underlying action information record.
  • OBJECT_VERSION_NUMBER — optimistic locking column, incremented on each update; essential when performing DML to avoid lost updates.
  • ACTION_CONTEXT_ID / ACTION_CONTEXT_TYPE — identify the processing context to which the action information belongs.
  • ASSIGNMENT_ID / EFFECTIVE_DATE — the assignment and date the action information applies to.
  • ACTION_INFORMATION_CATEGORY — the category discriminator (e.g., TAX_TYPE in some mappings) that groups the descriptive segments.
  • ACTION_INFORMATION1–9 — the localized descriptive segments holding Japan-specific values such as tax type, transaction status, finalization details, transfer status, and expiry information.
  • WHO columns — LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN for auditing.

The ETRM column listing additionally names TAX_TYPE, TRANSACTION_STATUS, FINALIZED_DATE, FINALIZED_BY, USER_COMMENTS, ADMIN_COMMENTS, TRANSFER_STATUS, TRANSFER_DATE, and EXPIRY_DATE, which map onto the localized action-information segments.

Common Use Cases and Queries

This view is typically used to read and, where the ROWID supports it, update Japanese assignment action information records that drive statutory reporting. Typical queries include:

  • Filtering by category to isolate Japanese tax or transfer records.
  • Joining to PAY_ASSIGNMENT_ACTIONS by ASSIGNMENT_ID for reporting.
  • DML updates guarded by OBJECT_VERSION_NUMBER.

Sample SELECT:

SELECT ACTION_INFORMATION_ID, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_INFORMATION_CATEGORY, ACTION_INFORMATION1, ACTION_INFORMATION2, FINALIZED_DATE FROM APPS.PAY_JP_ISDF_ASSACT_DML_V WHERE ACTION_INFORMATION_CATEGORY = :cat AND EFFECTIVE_DATE BETWEEN :start_date AND :end_date;

Because the object is restricted to the Japanese localization, it should not be treated as a general-purpose payroll interface outside that jurisdiction.