Search Results v_action_status

Overview

The PAY_JP_SOE_RUN_ASSACTS_V view is an Oracle E-Business Suite database object owned by the APPS schema and defined with VALID status in the ETRM repository. It belongs to the PAY – Payroll product family and is documented as being used for Japanese localization only. In practice, the view is a reporting and integration façade over assignment action data collected during a Japanese "SOE" (Statement of Earnings) payroll run. It exposes the assignment action records associated with a payroll action, together with derived status indicators that are specific to the Japanese SOE locking mechanism.

The view is significant because the Japanese localization introduces an additional locking workflow on top of the standard Oracle Payroll assignment action model. Standard assignment actions carry an ACTION_STATUS code and its decoded description; the Japanese version augments these with lock-oriented status values computed through a dedicated package. The view therefore acts as a single query surface through which Oracle Forms, concurrent programs, and custom reports can retrieve both base assignment action attributes and the localized lock status without calling the underlying package functions directly.

Because it is a view and not a table, no DML is possible against it, and its contents are always current with respect to the underlying Japanese SOE assignment action view.

Underlying Base Objects

The documented base objects referenced by PAY_JP_SOE_RUN_ASSACTS_V are:

• PAY_JP_SOE_ASSACTS_V – the Japanese SOE assignment actions view, which supplies the base assignment action columns (assignment id, action status, action type, payroll, consolidation set, element set, assignment set, and related attributes).
• PAY_JP_SOE_PKG – the Japanese SOE package whose functions, notably GET_LOCK_ACTION_NUM and GET_LOCK_STATUS_VAL, produce the lock and correlated status values exposed as derived columns.
• HR_API, HR_GENERAL, and HR_SECURITY – HRMS packages generally required by the Japanese SOE views and their security/validation logic.
• DUAL – a synonym used as the source for the scalar subqueries that invoke the lock status functions.

The view's SELECT text confirms this structure: it wraps PAY_JP_SOE_ASSACTS_V as an inline view and projects additional scalar subqueries against DUAL that call PAY_JP_SOE_PKG.GET_LOCK_STATUS_VAL and GET_LOCK_ACTION_NUM. This layering means the base view supplies raw assignment action rows, while the outer view enriches them with localized lock metadata and correlated action identifiers.

Key Columns

The most frequently referenced columns include:

• ACTION_STATUS and D_ACTION_STATUS – the base assignment action status code and its decoded description; these are the columns most commonly searched for.
• MARKED_FOR_RETRY_FLAG – indicates whether the assignment action has been marked for retry.
• ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID, PAYROLL_ACTION_ID, PAYROLL_ID, PAYROLL_NAME – core identity and payroll context for the action.
• ACTION_TYPE and D_ACTION_TYPE – the action type code and its description.
• P_ASSIGNMENT_ACTION_ID and P_ACTION_STATUS – the parent or primary assignment action identifier and status derived via the lock package.
• M_LOCK_STATUS and M_ACTION_STATUS – derived lock and action status values produced by PAY_JP_SOE_PKG.GET_LOCK_STATUS_VAL.
• C_, T_, and V_ prefixed assignment action id and action status pairs – correlated variants used by the Japanese SOE lock workflow.
• LEGISLATIVE_PARAMETERS and MESSAGES_EXIST_FLAG – legislative context and error/warning indicators.

The view text carries an explicit warning that the lock status functions must never be called directly, as doing so causes severe performance loss; querying the view is the sanctioned access path.

Common Use Cases and Queries

Typical uses include diagnosing the status of Japanese SOE payroll runs, identifying assignment actions awaiting processing or in a locked state, and feeding downstream reconciliation reports. A representative query for locating actions by status is:

• SELECT assignment_action_id, assignment_id, action_status, d_action_status, m_lock_status FROM apps.pay_jp_soe_run_assacts_v WHERE action_status = :status;
• SELECT a.assignment_action_id, a.payroll_name, a.action_status, a.marked_for_retry_flag FROM apps.pay_jp_soe_run_assacts_v a WHERE a.payroll_action_id = :payroll_action_id ORDER BY a.action_sequence;

Because the columns are exposed as a flat view, these queries can be joined directly to other assignment, payroll, or person views using ASSIGNMENT_ID or ASSIGNMENT_ACTION_ID as the key.