Results for “d_action_status”

38 results




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

Overview

PAY_JP_SOE_RETRO_ASSACTS_V is an APPS-owned database view within the Oracle Payroll (PAY) product, delivered as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. It exists specifically to support the Japanese Statement of Earnings (SOE) functionality surfaced through the PAYJPSOE.fmb Oracle Forms module. In that context, the view presents the subset of assignment action records that represent retroactive processing entries, so that the SOE form can display, validate, and report on retroactive assignment actions for a given assignment set.

The view is not a standalone reporting object; it is a filtered projection of the broader assignment-action view PAY_JP_SOE_ASSACTS_V. Its defining filter restricts the result set to rows where ACTION_TYPE equals 'G', which is the action type associated with retroactive entries. Its inclusion of the D_ACTION_TYPE column is directly relevant when users search for "d_action_type," as that column carries the translated or display form of the base ACTION_TYPE value that the SOE form presents to the user.

Underlying Base Objects

The view's definition references the following documented base objects:

  • PAY_JP_SOE_ASSACTS_V (VIEW) — the immediate source of all selected columns; PAY_JP_SOE_RETRO_ASSACTS_V is a WHERE-filtered projection of this view.
  • PAY_JP_SOE_PKG (PACKAGE) — invoked through the function RETRO_ENTRIES_PROCESSED_FLAG in the final SELECT expression.
  • HR_API, HR_GENERAL, HR_SECURITY (PACKAGES) — documented dependencies inherited through the underlying view's reference chain, typically supplying security and utility functions underlying assignment-level data access.

Because the underlying object is itself a view, no base tables are referenced directly. The retroactive flag is computed per row, not stored, using SUBSTRB(PAY_JP_SOE_PKG.RETRO_ENTRIES_PROCESSED_FLAG(ASSACT.ASSIGNMENT_ACTION_ID), 1, 1) to yield a single-character indicator.

Key Columns

Common Use Cases and Queries

Typical uses include auditing retroactive payroll actions before SOE generation, confirming that backpay sets carry a processed retro flag, and troubleshooting why a given assignment action is excluded from retro reporting. A representative query follows:

SELECT assignment_action_id,
       d_action_type,
       d_action_status,
       date_earned,
       backpay_set_name,
       retro_entries_processed_flag
  FROM apps.pay_jp_soe_retro_assacts_v
 WHERE assignment_id = :p_assignment_id
 ORDER BY effective_date, action_sequence;

To isolate actions pending retro processing:

SELECT assignment_action_id, d_action_type, request_id
  FROM apps.pay_jp_soe_retro_assacts_v
 WHERE retro_entries_processed_flag = 'N';

Because the view is filtered to ACTION_TYPE = 'G', queries joining it to PAY_JP_SOE_ASSACTS_V or to payroll action tables should expect only retroactive rows, and any comparison of counts between the two views will reflect that narrowing.