Search Results pay_nz_soe_run_elements_v




Overview
Explore in AI Chat

Overview

The view PAY_NZ_SOE_RUN_ELEMENTS_V is a New Zealand localisation object delivered in the APPS schema of Oracle E-Business Suite. It belongs to the PAY (Payroll) product family and holds documented VALID status in ETRM for both release 12.1.1 and 12.2.2. The object is a database view rather than a base table, meaning it exposes no independent storage of its own; instead it presents a consolidated, read-only projection of payroll element run data assembled from two subordinate localisation views.

The designation "SOE" (Statement of Earnings) indicates the view's purpose within New Zealand payroll reporting. It serves as a reporting and integration surface through which element-level payroll results, classified and prioritised for processing, can be queried for a given assignment action. Because Oracle delivers this as an APPS-owned view rather than a customer-maintained object, its structure and semantics are governed by the localisation patchset and should be treated as a supported, upgrade-managed interface.

The view functions as a union of two internal views, effectively normalising whatever separation the localisation applies internally into a single logical result set. This makes it convenient for downstream reporting tools, concurrent programs, and extracts that require a uniform list of payroll elements without needing to be aware of the internal split.

Underlying Base Objects

ETRM documents two referenced base objects for this view:

The view text confirms this relationship precisely. It is defined as a UNION ALL of two identically shaped SELECT statements, one from each of the two subordinate views:

SELECT "ELEMENT_REPORTING_NAME", "CLASSIFICATION_NAME", "PAYMENT", "PROCESSING_PRIORITY", "ASSIGNMENT_ACTION_ID", "ASSIGNMENT_ID" FROM PAY_NZ_SOE_RUN_ELEMENTS_V1 UNION ALL SELECT "ELEMENT_REPORTING_NAME", "CLASSIFICATION_NAME", "PAYMENT", "PROCESSING_PRIORITY", "ASSIGNMENT_ACTION_ID", "ASSIGNMENT_ID" FROM PAY_NZ_SOE_RUN_ELEMENTS_V2

Because UNION ALL is used rather than UNION, duplicate rows are not suppressed; the view returns the full concatenation of both sources. Both source views expose the identical six-column projection, so the parent view inherits that exact column list and order. From an APPS data-model perspective, PAY_NZ_SOE_RUN_ELEMENTS_V is therefore two levels removed from physical payroll tables — the V1 and V2 views themselves likely resolve against the core PAY run-result and element tables, but ETRM documents only the direct view dependencies listed above.

Key Columns

The view exposes six columns, all inherited unchanged from the V1 and V2 sources:

  • ELEMENT_REPORTING_NAME — The reporting name of the payroll element, used as the human-readable label on statements and reports.
  • CLASSIFICATION_NAME — The element classification (for example earnings, deduction, or balance-initiating categories), enabling grouping and filtering by payroll treatment.
  • PAYMENT — An indicator of the payment-related attribute of the element run, differentiating monetary from non-monetary or informational elements.
  • PROCESSING_PRIORITY — The priority sequence applied when the element is processed in a payroll run, governing calculation ordering.
  • ASSIGNMENT_ACTION_ID — The identifier of the assignment action, the transactional unit that links an element entry to a specific payroll run and assignment.
  • ASSIGNMENT_ID — The identifier of the assignment (the employee-to-payroll relationship) to which the element run belongs.

The two ID columns form the practical join keys back into core PAY tables, while the name and classification columns support presentation-layer grouping. None of the columns are computed within this view; all transformation, if any, occurs in the V1 and V2 sources.

Common Use Cases and Queries

Typical usage centres on New Zealand Statement of Earnings reporting and reconciliation. A common pattern is to retrieve all element runs for a given assignment action, joining the ID columns to assignment and person data:

SELECT pnre.element_reporting_name, pnre.classification_name, pnre.payment, pnre.processing_priority, pnre.assignment_id FROM apps.pay_nz_soe_run_elements_v pnre WHERE pnre.assignment_action_id = :p_assignment_action_id ORDER BY pnre.processing_priority;

A second scenario lists all elements for an assignment, filtered by classification, to reconcile earnings against deductions. Because order is not guaranteed by the view's UNION ALL definition, queries should always apply an explicit ORDER BY when presentation order matters. A third pattern aggregates element counts or totals per classification for audit and validation of a completed payroll run.

Consumers should note that this view is localisation-specific and read-only; it should be queried, not modified, and any joins should rely on the documented ASSIGNMENT_ACTION_ID and ASSIGNMENT_ID columns for correctness across both union branches.