Search Results pay_message_lines_pk

Overview

PAY_MESSAGE_LINES is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM repository, the table stores error messages generated from running a process. It functions as the diagnostic message repository for payroll run and related batch processes, capturing per-line output that is surfaced to users through concurrent program logs and the message viewing forms. Each row represents a single message line associated with a payroll process execution.

The documented physical schema for 12.2.2 lists six columns: LINE_SEQUENCE, PAYROLL_ID, MESSAGE_LEVEL, SOURCE_ID, SOURCE_TYPE, and LINE_TEXT. The primary key, PAY_MESSAGE_LINES_PK, is defined on LINE_SEQUENCE. The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table has no formally documented foreign key dependencies to parent business entities in the ETRM metadata. From a modeling perspective, this suggests treating PAY_MESSAGE_LINES as a small, self-contained reference or logging structure whose relationships to payroll processes are conveyed through the SOURCE_ID and SOURCE_TYPE columns rather than enforced referential constraints. Note, however, that the PK column itself is a surrogate line identifier rather than a natural business key, so any integration or warehouse design should treat it accordingly.

Key Information Stored

The most significant columns documented for this table are:

• LINE_SEQUENCE — the primary key column and the sole unique index (PAY_MESSAGE_LINES_PK) documented. It sequences the individual message lines generated by a process.
• PAYROLL_ID — identifies the payroll context associated with the message, linking the diagnostic output to a specific payroll run or payroll definition.
• MESSAGE_LEVEL — records the severity or classification of the message, distinguishing informational output from errors and warnings.
• SOURCE_ID — the identifier of the entity that produced the message, used together with SOURCE_TYPE to locate the originating record.
• SOURCE_TYPE — the category of the source entity, allowing the same SOURCE_ID to be interpreted against different object types.
• LINE_TEXT — the actual message text displayed to the user or written to the process log.

The documented metadata does not expose additional columns, and the table is described as standalone, so no foreign key targets are asserted. The combination of SOURCE_TYPE and SOURCE_ID is the practical business-key candidate for locating messages associated with a particular originating record, even though only LINE_SEQUENCE is documented as a unique index.

Common Use Cases and Queries

The primary use case is troubleshooting payroll processes. Support and payroll administrators query PAY_MESSAGE_LINES to retrieve the error text emitted during a payroll run, filtering by payroll and severity level. A typical pattern is:

• Retrieve all messages for a given payroll: SELECT line_sequence, message_level, line_text FROM pay_message_lines WHERE payroll_id = :payroll_id ORDER BY line_sequence;
• Filter to errors only: add AND message_level = 'E' to isolate failure conditions.
• Trace a message back to its source record using source_type and source_id.
• Reporting: message volume and severity counts per payroll run, used to monitor process health and recurring error patterns.

Because the table is documented as standalone, joins to parent payroll tables must be performed through the PAYROLL_ID and SOURCE_ID/SOURCE_TYPE columns rather than through declared foreign keys.

Related Objects

The ETRM metadata documents no foreign keys, so relationships below are based on the documented columns and standard Payroll module context:

• PAY_PAYROLL_ACTIONS — the payroll action/run header associated via PAYROLL_ID.
• PAY_ASSIGNMENT_ACTIONS — assignment-level action rows potentially referenced through SOURCE_TYPE and SOURCE_ID.
• PAY_RUN_RESULTS — run result rows whose processing may generate messages.
• FND_CONCURRENT_REQUESTS — the concurrent request that executed the payroll process and triggered message output.
• PAY_MESSAGE_LINES_PK — the primary key constraint enforcing uniqueness on LINE_SEQUENCE.

No other dependent views, APIs, or foreign keys are documented in the ETRM metadata for this object.