Results for “sla_mode”

18 results




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

Overview

APPS.PAY_ASSIGNMENT_ACTIONS_V is a reporting and integration view that presents the relationship between payroll actions and the assignment-level action records they generate. In Oracle EBS 12.1.1 and 12.2.2, it consolidates data from payroll actions, assignment actions, assignments, and people so that payroll administrators, concurrent programs, forms, and downstream interfaces can query a flattened, human-readable representation of payroll processing activity. The view is defined as a UNION ALL of two SELECT statements, allowing it to expose both standard payroll action rows and additional rows that would otherwise be excluded by the base filter logic.

The view is particularly relevant to the search term "messages_exist". This column is derived by calling PAY_ASSIGNMENT_ACTIONS_PKG.MESSAGE_LINE_EXISTS(AAC.ASSIGNMENT_ACTION_ID), which returns an indicator of whether an assignment action has associated message lines. This is operationally significant because assignment actions with messages typically require review, correction, or reprocessing before payroll can be completed. The presence of MESSAGES_EXIST allows users to filter for actions that need attention.

Underlying Base Objects

The view is owned by APPS and is defined over a combination of synonyms, views, and packages documented in ETRM 12.2.2. The principal data-bearing objects are the synonyms PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS, which supply the assignment action and payroll action rows. These are joined to PER_ASSIGNMENTS_F2 and PER_PEOPLE_F (with synonyms PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F) to resolve assignment number, person name, and effective dating.

HR_LOOKUPS provides decode values for ACTION_TYPE, and several packages are referenced: HR_GENERAL for DECODE_LOOKUP resolution, HR_PAYROLLS for DISPLAY_PERIOD_NAME, PAY_ASSIGNMENT_ACTIONS_PKG for GET_ACTION_STATUS and MESSAGE_LINE_EXISTS, and HR_PERSON_NAME, HR_API, and HR_SECURITY for supporting person and security logic. PAY_BATCH_LINES is also referenced. The view joins on assignment ID, payroll action ID, and effective date ranges, and it explicitly excludes action types 'Z', 'X', and 'BEE'.

Key Columns

Common Use Cases and Queries

A primary use case is identifying payroll assignment actions that have generated messages and therefore require investigation. The MESSAGES_EXIST column supports this directly:

  • SELECT assignment_action_id, payroll_action_id, full_name, period_name, action_status FROM apps.pay_assignment_actions_v WHERE messages_exist IS NOT NULL;
  • SELECT action_type, type, COUNT(*) FROM apps.pay_assignment_actions_v GROUP BY action_type, type;
  • SELECT period_name, action_status, COUNT(*) FROM apps.pay_assignment_actions_v WHERE effective_date BETWEEN :start_date AND :end_date GROUP BY period_name, action_status;

The view is also used to reconcile payroll action activity by period, to drive status dashboards, and to feed integrations that need decoded action types and statuses rather than raw codes. Because it is a view, it inherits the security and performance characteristics of its base objects; queries should be filtered by business group and effective dates where possible.