Search Results line_sequence




Overview
Explore in AI Chat

Overview

APPS.PAY_GB_SOE_MESSAGE_V is a reporting view in the Oracle E-Business Suite Payroll (PAY) schema that consolidates payroll message lines with their associated source identifiers. Its name reflects its principal business purpose: supplying the message text used in the United Kingdom "Statement of Earnings" (SOE) and related statutory payroll reporting. The view presents a denormalised, read-only projection of message data so that concurrent programs, Oracle Reports/BI Publisher layouts, and integration routines can retrieve the human-readable text that accompanies a payroll action without navigating the underlying transactional model directly.

The object is defined in the APPS schema and, per the documented metadata for ETRM 12.2.2, is available in both 12.1.1 and 12.2.2. Because it exposes LINE_TEXT, it is frequently the object resolved when a user or developer searches for "line_text" while investigating where payroll message wording is stored and how it is joined to a payroll run or action.

Underlying Base Objects

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

  • PAY_MESSAGE_LINES (SYNONYM) — the repository of individual message text lines, keyed by line sequence and a source identifier.
  • PAY_ACTION_INTERLOCKS (SYNONYM) — the interlock table that records relationships between locking and locked payroll actions.

As shown in the view text, the definition is a UNION of two branches:

  • The first branch selects LINE_SEQUENCE, SOURCE_ID, and LINE_TEXT directly from PAY_MESSAGE_LINES.
  • The second branch selects LINE_SEQUENCE, PAI.LOCKING_ACTION_ID as SOURCE_ID, and LINE_TEXT from PAY_MESSAGE_LINES joined to PAY_ACTION_INTERLOCKS PAI where SOURCE_ID = PAI.LOCKED_ACTION_ID.

The UNION effectively re-attributes message lines whose original source is a locked action to the locking action, so that messages follow the action that superseded or blocked the original run. No aggregate or filter predicates are applied beyond the interlock join.

Key Columns

  • LINE_SEQUENCE — the ordinal position of the message line. Establishes ordering within a source so that multi-line messages are rendered in the correct sequence.
  • SOURCE_ID — the identifier of the originating payroll action. In the first UNION branch this is the source identifier carried on PAY_MESSAGE_LINES; in the second branch it is the LOCKING_ACTION_ID from PAY_ACTION_INTERLOCKS.
  • LINE_TEXT — the actual message text. This is the column most commonly referenced, as it contains the printable wording for statements of earnings and associated payroll diagnostics.

Common Use Cases and Queries

Typical scenarios include retrieving all message lines for a given payroll action in sequence, diagnosing interlock-related messages, and feeding report layouts that require the SOE narrative.

SELECT line_sequence, source_id, line_text
FROM   apps.pay_gb_soe_message_v
WHERE  source_id = :p_action_id
ORDER  BY line_sequence;

Because the view performs the interlock re-attribution, a query filtered by the locking action returns both its own messages and those of the locked action, which is the desired behaviour when presenting a consolidated statement. Where only the raw PAY_MESSAGE_LINES content is required, querying the base table directly avoids the UNION and any duplicate rows the join may introduce. As with all APPS views, access should be granted through the standard payroll responsibility and the view should be treated as read-only.