Results for “legislative_parameters”

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

Overview

PAY_JP_SOE_COST_ASSACTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as a Japanese localization object within the PAY (Payroll) product family, and its role is to expose assignment action records that have been classified as cost actions. The view is a filtered, denormalized projection over the underlying assignment action set, restricted to rows whose ACTION_TYPE equals 'C' (cost).

The view serves as a reporting and integration surface for the Japanese Statement of Earnings (SOE) cost processing flow. Rather than requiring consumers to call the Japanese payroll package directly, the view performs the localization-specific derivations for lock status inside its SELECT list and exposes the results as ordinary columns. This makes the view suitable for concurrent program data sources, BI Publisher reports, and downstream interfaces that need to read assignment action data without embedding PL/SQL calls.

Underlying Base Objects

The documented referenced base objects for this view are HR_API (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), PAY_JP_SOE_ASSACTS_V (VIEW), PAY_JP_SOE_PKG (PACKAGE), and DUAL (SYNONYM). The single FROM-clause object is the view PAY_JP_SOE_ASSACTS_V, aliased ASSACT, which supplies all passthrough columns. The HR packages are referenced indirectly because PAY_JP_SOE_ASSACTS_V inherits the standard Oracle HRMS security and utility semantics used across assignment action reporting views, including business group and security profile handling.

The two derived columns are produced by scalar subqueries against DUAL, each invoking PAY_JP_SOE_PKG.GET_LOCK_STATUS_VAL. The same localization package is therefore the operative dependency for the view's computed output. Because the view reads from another view rather than directly from a base table, there is no direct base-table join to PAY_ASSIGNMENT_ACTIONS in the view text; the assignment action data reaches it through PAY_JP_SOE_ASSACTS_V.

Key Columns

• ASSIGNMENT_ID / ASSIGNMENT_ACTION_ID — Identifiers for the assignment and its action row; the action ID is the argument passed to the lock status function.
• OBJECT_VERSION_NUMBER — Optimistic locking column carried from the source view.
• ACTION_STATUS / D_ACTION_STATUS — Status code and its displayed (translated) value.
• ACTION_TYPE / D_ACTION_TYPE — Action type code and display value; the view is filtered to ACTION_TYPE = 'C'.
• MARKED_FOR_RETRY_FLAG, ACTION_SEQUENCE, REQUEST_ID — Processing control attributes indicating retry state, ordering, and the concurrent request that produced the row.
• PAYROLL_ACTION_ID, PAYROLL_ID, PAYROLL_NAME — Payroll action and payroll context.
• START_DATE, EFFECTIVE_DATE, DATE_EARNED — Date attributes of the assignment action, including the earned date relevant to cost allocation.
• CONSOLIDATION_SET_ID / CONSOLIDATION_SET_NAME — Consolidation set linkage used in payroll costing and reporting.
• LEGISLATIVE_PARAMETERS, MESSAGES_EXIST_FLAG — Payroll legislative parameters and a flag indicating generated messages.
• T_LOCK_STATUS — Derived lock status returned by PAY_JP_SOE_PKG.GET_LOCK_STATUS_VAL for parameter 'LOCK_STATUS'. This column is the primary target of the search term "lock_status."
• T_ACTION_STATUS — Derived action status returned by the same function for parameter 'ACTION_STATUS', providing the localized status used in SOE cost reporting.

Common Use Cases and Queries

The principal use case is identifying Japanese SOE cost assignment actions by their lock status, typically to determine whether records can be modified or must be excluded from a costing run. A representative query filters on the derived lock status column:

• SELECT assignment_action_id, assignment_id, t_lock_status, t_action_status, payroll_name, date_earned FROM apps.pay_jp_soe_cost_assacts_v WHERE t_lock_status IS NOT NULL;
• SELECT assignment_action_id, t_lock_status, action_sequence FROM apps.pay_jp_soe_cost_assacts_v WHERE request_id = :p_request_id ORDER BY action_sequence;
• SELECT payroll_id, payroll_name, COUNT(*) FROM apps.pay_jp_soe_cost_assacts_v GROUP BY payroll_id, payroll_name;

Because the view is locale-specific and valid only in the APPS schema, queries should be issued with the APPS schema prefix or through a synonym, and access should respect HR security profiles inherited from the underlying assignment action view.