Results for “paybv_message_line”

15 results




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

Overview

PAYBV_MESSAGE_LINE is an Oracle E-Business Suite view owned by the APPS schema and classified as a VALID database object within the PAY (Payroll) product family. Its documented purpose is to serve as a Discoverer base view for the underlying PAY_MESSAGE_LINES entity. In the Oracle EBS reporting architecture, "BV" views such as this one are not intended for direct transactional processing; rather, they are published as the presentation layer that Oracle Business Intelligence Discoverer (and, by extension, other ad hoc reporting tools) uses to expose payroll data in a business-friendly form. The view is defined with the READ ONLY clause, reinforcing its role as a query-only reporting artifact that protects the integrity of the base payroll tables.

Because the view is a simple, non-materialized projection over its base object, it always returns current data at query time. It is available in both Oracle EBS 12.1.1 and 12.2.2, where the underlying metadata remains consistent.

Underlying Base Objects

The ETRM metadata documents two referenced objects for this view:

  • PAY_MESSAGE_LINES (SYNONYM) — the primary base object. The view text selects from PAY_MESSAGE_LINES PML, aliasing the table for column qualification.
  • HR_BIS (PACKAGE) — referenced through the call HR_BIS.BIS_DECODE_LOOKUP, a decode utility that translates internal lookup codes into their displayable meanings.

The view definition joins these elements by passing the stored code columns MESSAGE_LEVEL and SOURCE_TYPE through BIS_DECODE_LOOKUP, while the remaining columns are projected directly from PAY_MESSAGE_LINES. The WITH READ ONLY clause prevents any DML against the view.

Key Columns

The view exposes the following columns, as documented:

  • LINE_SEQUENCE — the ordering sequence of individual message lines, drawn directly from PML.LINE_SEQUENCE.
  • LINE_TEXT — the actual textual content of the message line.
  • MESSAGE_LEVEL / MESSAGE_LEVEL_CODE — MESSAGE_LEVEL is the decoded, user-readable value produced by BIS_DECODE_LOOKUP('MESSAGE_LEVEL', ...); MESSAGE_LEVEL_CODE preserves the raw stored code.
  • SOURCE_TYPE / SOURCE_TYPE_CODE — SOURCE_TYPE is the decoded label from BIS_DECODE_LOOKUP('MESSAGE_SOURCE_TYPE', PML.SOURCE_TYPE); SOURCE_TYPE_CODE retains the raw code.
  • SOURCE_ID — the identifier of the originating source record associated with the message.
  • PAYROLL_ID — the payroll to which the message line belongs.

The deliberate pairing of decoded and coded columns allows report authors to display friendly labels while still filtering or grouping on stable codes.

Common Use Cases and Queries

Typical usage centers on payroll message reporting: auditing validation and log messages produced during payroll runs, tracing messages back to a payroll or source record, and building Discoverer workbooks. A representative query retrieves messages for a specific payroll:

  • SELECT line_sequence, message_level, line_text, source_type, source_id, payroll_id FROM apps.paybv_message_line WHERE payroll_id = :p_payroll_id ORDER BY line_sequence;
  • SELECT message_level, COUNT(*) FROM apps.paybv_message_line GROUP BY message_level;

Because the view is read only and directly backed by PAY_MESSAGE_LINES, it is well suited to ad hoc investigation and to serving as the data source for published payroll reports, while transactional maintenance of message lines must be performed against the base table rather than the view.