Search Results messages_exist_flag




Overview
Explore in AI Chat

Overview

PAY_JP_SOE_PREPAY_ASSACTS_V is a reporting view owned by the APPS schema within the Payroll (PAY) product family of Oracle E-Business Suite, validated for releases 12.1.1 and 12.2.2. The view is documented in the E-Business Suite Technical Reference Manual (ETRM) as being used for Japanese localization only. Its purpose is to expose a filtered subset of assignment action records that are relevant to the Japanese Statement of Earnings (SOE) prepayment process, specifically those whose action type is either "P" (prepayment) or "U". The view is built on top of the PAY_JP_SOE_ASSACTS_V view and enriches that data with two derived lock-status values retrieved through the PAY_JP_SOE_PKG package.

The presence of the MESSAGES_EXIST_FLAG column, which was the term the searcher used, is significant. This flag indicates whether messages (warnings or errors) exist for a given assignment action. It is commonly used by SOE prepayment validation and reporting logic to determine whether a record requires attention before it is processed or reported.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, this view is defined over the following referenced objects:

  • PAY_JP_SOE_ASSACTS_V (VIEW) — the primary source of assignment action rows. The view text selects from this view aliased as ASSACT and restricts it with ACTION_TYPE IN ('P','U').
  • PAY_JP_SOE_PKG (PACKAGE) — the source of the GET_LOCK_STATUS_VAL function, invoked twice as scalar subqueries against DUAL to produce M_LOCK_STATUS and M_ACTION_STATUS.
  • HR_API, HR_GENERAL, and HR_SECURITY (PACKAGES) — supporting HR foundation packages referenced in the dependency chain, typically used for security and utility access.
  • DUAL (SYNONYM) — the single-row pseudo table used by the scalar subqueries that call the lock-status function.

The view text contains an explicit inline warning stating that the PAY_JP_SOE_PKG.GET_LOCK_STATUS_VAL function must never be called directly, because doing so will cause severe loss of performance. This is why the function calls are wrapped inside the view, allowing consuming code to reference the pre-computed columns instead.

Key Columns

The view exposes 24 columns. The most operationally important are summarized below.

Common Use Cases and Queries

This view is typically used by Japanese localization reporting, SOE prepayment reconciliation, and interface programs that must inspect prepayment or update actions together with their lock and message states. A representative query filtering on the searched flag is shown below.

SELECT assignment_id, assignment_action_id, action_status, action_type, messages_exist_flag, m_action_status, m_lock_status FROM apps.pay_jp_soe_prepay_assacts_v WHERE messages_exist_flag = 'Y';

Additional patterns include joining to payroll or assignment tables via ASSIGNMENT_ID to enrich the report, and selecting only rows for a specific payroll:

SELECT assignment_action_id, payroll_name, action_status, d_action_status, messages_exist_flag FROM apps.pay_jp_soe_prepay_assacts_v WHERE payroll_id = :p_payroll_id AND action_type = 'P';

Because the view already performs the lock-status function calls internally, consumers should query M_LOCK_STATUS and M_ACTION_STATUS columns rather than invoking PAY_JP_SOE_PKG.GET_LOCK_STATUS_VAL directly, in accordance with the performance warning embedded in the view definition.