Search Results pay_jp_soe_assacts_v




Overview

PAY_JP_SOE_ASSACTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Payroll (PAY) product family and is documented as being used exclusively for the Japanese localization. The view consolidates Oracle Payroll assignment action data with their parent payroll action headers and their associated descriptive flexfield-style lookups, and it exposes a derived "messages exist" indicator produced by the payroll localization package. Its purpose is to provide a flattened, query-ready representation of SOE (Statement of Earnings) related assignment actions for Japanese payroll reporting, concurrent processing, and integration with the JP localization flows. Because it is a view and not a base table, it carries no independent data storage; all of its content is derived from the underlying payroll and HR objects at query time. In ETRM 12.2.2 the object is registered as VALID under the APPS schema, and a corresponding 12.1.1 definition (documented as View Text) preserves the same structure.

Underlying Base Objects

The view is defined over a mixture of payroll base tables, translated (TL/VL) views, and HR lookups. The documented referenced objects are:

All set-level joins to consolidation, element, backpay, assignment set, and payroll objects are outer joins, meaning an assignment action row is returned even when those references are absent.

Key Columns

Common Use Cases and Queries

Because it is localisation-specific, the view is most commonly used in Japanese SOE reporting, payroll action monitoring, and troubleshooting of retry-marked actions. A typical query retrieves the decoded status and action type alongside the retry flag:

  • SELECT assignment_action_id, d_action_status, marked_for_retry_flag, payroll_name, effective_date FROM pay_jp_soe_assacts_v WHERE payroll_id = :p_payroll_id;
  • SELECT assignment_id, assignment_action_id, d_action_ty, date_earned, d_action_status FROM pay_jp_soe_assacts_v WHERE assignment_id = :p_assignment_id ORDER BY action_sequence;
  • SELECT payroll_name, d_action_status, COUNT(*) FROM pay_jp_soe_assacts_v GROUP BY payroll_name, d_action_status;

Note that the view does not expose the message-exist flag under a named column alias; consumers who require it should reference the expression through a wrapper query or a synonym definition that assigns an alias. Because HR_LOOKUPS and PAY_ORG_PAYMENT_METHODS_F_TL are language-sensitive, query results vary with the session NLS language, and users should rely on D_ACTION_STATUS / D_ACTION_TY rather than the raw codes when producing human-readable reports.