Search Results pay_gb_soe_message_v




Overview
Explore in AI Chat

Overview

PAY_GB_SOE_MESSAGE_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product family, specifically associated with the GB (United Kingdom) payroll localization. Its documented purpose is to report pay action message lines, providing a consolidated, read-only presentation of message text that has been associated with payroll action processing. In the context of statutory reporting for UK payroll, this view supports the generation of Statements of Earnings (SOE) and related pay action messaging by surfacing the individual message lines that accompany a pay action.

Because it is a view rather than a table, it carries no storage of its own. It exposes a denormalized result set assembled from underlying payroll message and action-interlock data, allowing report generators, concurrent programs, and integration routines to retrieve pay action message lines through a single, stable object name without needing to reproduce the underlying join logic. The view was documented as VALID in ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS synonyms:

  • PAY_MESSAGE_LINES — the primary source of message line text and line sequencing.
  • PAY_ACTION_INTERLOCKS — the source of the locking action identifier used to associate message lines with a locked pay action.

The documented view text is a UNION of two SELECT statements. The first selects LINE_SEQUENCE, SOURCE_ID, and LINE_TEXT directly from PAY_MESSAGE_LINES. The second selects LINE_SEQUENCE, PAI.LOCKING_ACTION_ID aliased as SOURCE_ID, and LINE_TEXT from PAY_MESSAGE_LINES joined with PAY_ACTION_INTERLOCKS PAI where the message line's SOURCE_ID equals PAI.LOCKED_ACTION_ID. This UNION structure means the view returns both the native message lines and the interlock-derived lines, keyed on SOURCE_ID, giving consumers a complete set of pay action message lines for a given source.

Key Columns

  • LINE_SEQUENCE — the ordering value for message lines, allowing callers to present message text in the intended sequence.
  • SOURCE_ID — the key correlating a message line to its originating source. In the first leg of the UNION it is the SOURCE_ID from PAY_MESSAGE_LINES; in the second leg it is derived as PAI.LOCKING_ACTION_ID from PAY_ACTION_INTERLOCKS, matched against the interlock's LOCKED_ACTION_ID.
  • LINE_TEXT — the actual text content of the pay action message line, suitable for direct display or report output.

The user search term "source_id" maps directly to the pivotal column of this view. SOURCE_ID is the join and filtering key that determines which message lines are returned and how they relate to a pay action. Filtering the view by SOURCE_ID is the normal access pattern.

Common Use Cases and Queries

Typical scenarios include building UK SOE reports, retrieving message lines for a specific pay action, and diagnostic queries to confirm which message lines are linked to a locked action through PAY_ACTION_INTERLOCKS. A representative query filtering by the searched column is:

  • SELECT line_sequence, source_id, line_text FROM apps.pay_gb_soe_message_v WHERE source_id = :p_source_id ORDER BY line_sequence;
  • SELECT source_id, COUNT(*) line_count FROM apps.pay_gb_soe_message_v GROUP BY source_id ORDER BY source_id;
  • SELECT line_sequence, line_text FROM apps.pay_gb_soe_message_v WHERE source_id = :p_source_id ORDER BY line_sequence;

Because the view is read-only and defined by a UNION, queries should filter on SOURCE_ID and order by LINE_SEQUENCE to obtain deterministic output. Substituting a specific action identifier for the bind variable yields the message lines associated with that pay action, whether sourced directly from PAY_MESSAGE_LINES or through the locking action relationship in PAY_ACTION_INTERLOCKS.