Results for “source_type_meaning”

50+ results




Overview
Explore in AI Chat

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

Overview

PAY_PAYWSQEE_MESSAGES is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the PAY (Payroll) product and is documented as being "used to support user interface." In practice, the view consolidates payroll batch message lines—warnings, errors, and informational messages produced during batch element entry and payroll batch processing—into a single, presentation-ready result set. It plays a supporting role in the Batch Element Entry (BEE) and payroll batch UI flows, and it is equally useful for reporting, reconciliation, and integration where batch-level diagnostics must be surfaced outside the standard forms.

The user search term "source_type_meaning" corresponds directly to a column on this view: SOURCE_TYPE_MEANING. Because the raw SOURCE_TYPE and CONTROL_TYPE codes are internal lookup values, the view resolves them to human-readable meanings, which makes it particularly attractive for reporting and troubleshooting queries.

Unlike transactional base tables, this object is a read-only view. It does not store data; it derives all content at query time, and its validity depends on the underlying synonyms and lookups remaining available in the APPS schema.

Underlying Base Objects

Per the documented view text, PAY_PAYWSQEE_MESSAGES is defined over several base objects, joined through a UNION ALL of message contexts:

The union structure means each row represents one message line, with context-specific columns populated for the batch-header, batch-line, or control-total segment from which the message originated.

Key Columns

  • LINE_SEQUENCE / PAYROLL_ID — the ordering and payroll assignment of the message line.
  • MESSAGE_LEVEL — the raw severity code; MESSAGE_LEVEL meaning is resolved via HR_LOOKUPS (LOOKUP_TYPE = 'MESSAGE_LEVEL').
  • SOURCE_ID / SOURCE_TYPE — the originating record identifier and its type; SOURCE_TYPE distinguishes header ('H'), line ('L'), and other contexts.
  • SOURCE_TYPE_MEANING — the decoded meaning of SOURCE_TYPE via HR_LOOKUPS (LOOKUP_TYPE = 'MESSAGE_SOURCE_TYPE'). This column is the subject of the user's search and is what makes the view self-describing.
  • LINE_TEXT — the actual message text shown to the user.
  • BATCH_ID / IDENTIFIER — the batch identifier; IDENTIFIER carries the batch name for header messages or the batch sequence for line messages.
  • CONTROL_TYPE_MEANING — decoded control-total type via HR_LOOKUPS (LOOKUP_TYPE = 'CONTROL_TYPE'); NULL for non-control messages.
  • ASSIGNMENT_NUMBER / ELEMENT_NAME — contextual assignment and element names, populated only for batch-line messages.

Common Use Cases and Queries

Typical uses include diagnosing why a batch failed, auditing message severity across payroll runs, and feeding batch diagnostics into custom reports or downstream integrations. A representative query retrieving error-level messages with their decoded source type and batch context:

  • SELECT batch_id, identifier, message_level, source_type_meaning, line_text FROM apps.pay_paywsqee_messages WHERE payroll_id = :p_payroll_id ORDER BY line_sequence;
  • SELECT source_type, source_type_meaning, COUNT(*) FROM apps.pay_paywsqee_messages GROUP BY source_type, source_type_meaning;
  • SELECT batch_id, element_name, assignment_number, line_text FROM apps.pay_paywsqee_messages WHERE source_type = 'L' AND message_level = 'E';

Because the view decodes lookup meanings inline, it removes the need for callers to join HR_LOOKUPS themselves, making it the preferred source for user-facing batch message reporting in Oracle EBS 12.1.1 and 12.2.2.