Search Results processing_priority




Overview
Explore in AI Chat

Overview

APPS.PAY_NZ_SOE_RUN_ELEMENTS_V is a reporting view in the Oracle E-Business Suite Payroll module that consolidates payroll run element information specifically for New Zealand Start of Year / End of Year (SOE) statutory reporting. The view presents a unified result set of payroll element details associated with assignment actions generated during a payroll run, exposing the reporting name of each element, its classification, payment characteristics, processing priority, and the assignment identifiers that tie the records back to individual employees. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only, denormalized interface used by SOE extract processes, concurrent programs, and custom reporting, shielding consumers from the partitioning logic implemented in the underlying definitions. Because the view is owned by APPS and defined over two sibling views combined with a UNION ALL, it provides a stable, query-friendly surface for integration and reporting without requiring direct knowledge of how the source data is split.

Underlying Base Objects

The documented metadata identifies two referenced base objects: PAY_NZ_SOE_RUN_ELEMENTS_V1 (VIEW) and PAY_NZ_SOE_RUN_ELEMENTS_V2 (VIEW). The view text is a UNION ALL that selects an identical column list from each source:

The UNION ALL operator preserves all rows from both branches, including duplicates, which is the appropriate choice for a reporting view where each assignment action must be reported independently. This two-branch construction is characteristic of NZ payroll views that separate data by business grouping, legislative category, or source table partition, then reunite the segments into a single consumable layer. Neither branch filters or aggregates the data beyond what is internally defined, so the parent view behaves as a straightforward union of its constituents.

Key Columns

  • ELEMENT_REPORTING_NAME — The reporting label of the payroll element, used to identify the earning or deduction on statutory returns and reports.
  • CLASSIFICATION_NAME — The element classification, which governs how the element is treated in payroll calculations and reporting taxonomies.
  • PAYMENT — Indicates the payment attribute of the element, distinguishing monetary disbursements from non-payment entries.
  • PROCESSING_PRIORITY — The priority sequence that controls the order in which elements are processed within the payroll run. This column is the most frequently searched attribute for this view, as it directly determines calculation sequencing and dependency resolution. Lower or higher numeric values dictate whether an element is evaluated before or after related elements in the run.
  • ASSIGNMENT_ACTION_ID — The unique identifier of the assignment action record, linking the element entry to a specific processing instance.
  • ASSIGNMENT_ID — The identifier of the employee assignment, enabling joins to assignment and person tables for employee-level reporting.

Common Use Cases and Queries

This view is typically queried to audit element ordering, reconcile SOE payroll extracts, and join payroll element data to employee assignments. A representative query filtering by processing priority is:

  • SELECT element_reporting_name, classification_name, payment, processing_priority, assignment_action_id, assignment_id FROM apps.pay_nz_soe_run_elements_v WHERE processing_priority = :priority ORDER BY processing_priority, element_reporting_name;
  • SELECT v.element_reporting_name, v.processing_priority, a.assignment_id FROM apps.pay_nz_soe_run_elements_v v JOIN apps.pay_assignment_actions a ON a.assignment_action_id = v.assignment_action_id WHERE v.assignment_id = :assignment_id;

Typical scenarios include verifying that SOE-relevant elements fire in the expected sequence, extracting element-level detail for year-end filings, and diagnosing calculation discrepancies caused by incorrect priority values. Because the view is a UNION ALL with no filtering predicates, consumers should apply their own WHERE clauses to restrict to the relevant payroll run, assignment action, or priority band. All queries should be issued against the APPS synonym, and performance is generally governed by the definitions of the two underlying views rather than the union itself.