Results for “psb_error_messages”

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

Overview

The PSB_ERROR_MESSAGES table is a core logging and diagnostic object within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores error messages generated by the various batch and concurrent processes that execute across the Public Sector Budgeting application, such as budget upload, position synchronization, and worksheet processing routines. The table is owned by the PSB schema and holds a VALID status in the ETRM registry.

Its principal function is to capture a sequential, auditable trail of diagnostic information emitted whenever a PSB concurrent program encounters a validation failure, data inconsistency, or processing exception. Because PSB processes are frequently invoked as concurrent requests, the table ties error output back to the originating request, enabling administrators and functional users to trace and remediate problems.

From a data-modeling perspective, the ETRM metadata classifies this object as standalone based on its foreign-key structure—no outgoing foreign keys to parent tables are documented. In Data Vault terms this suggests a satellite-like modeling pattern, since the table records descriptive, time-stamped attributes (error descriptions, sequence numbers, source process identifiers) anchored to a request-level key rather than acting as a pure hub or link.

Key Information Stored

The table contains seven documented columns. The most significant are:

• CONCURRENT_REQUEST_ID – The surrogate primary key, defined by the constraint CONCURRENT_REQUEST_ID_PK. It links each error row to the concurrent request that generated it.
• PROCESS_ID – Identifies the specific PSB process or program instance responsible for the message.
• SOURCE_PROCESS – Names the originating process or sub-routine, distinguishing among the many PSB batch routines.
• SEQUENCE_NUMBER – Orders messages emitted during a single run, preserving chronological sequence.
• DESCRIPTION – The human-readable error text, i.e., the actual message content.
• CREATION_DATE – Timestamp of row insertion, useful for run-time correlation and aging analysis.
• CREATED_BY – The application user or process that inserted the record.

The documented primary key is a single-column surrogate on CONCURRENT_REQUEST_ID. No separate business-key unique index is documented in the ETRM metadata; PRO CESS_ID and SOURCE_PROCESS function as interpretive descriptors rather than true business keys.

Common Use Cases and Queries

The table is primarily interrogated during error triage. A typical query retrieves all messages for a failed request:

• SELECT SEQUENCE_NUMBER, SOURCE_PROCESS, DESCRIPTION FROM PSB_ERROR_MESSAGES WHERE CONCURRENT_REQUEST_ID = :request_id ORDER BY SEQUENCE_NUMBER;
• Trend reporting groups failures by SOURCE_PROCESS over a period, filtering on CREATION_DATE.
• Integration monitoring joins the table to FND_CONCURRENT_REQUESTS to surface PSB errors on concurrent manager dashboards.

Reporting use cases include reconciliation of budget upload errors, audit trails for position and worksheet processing, and root-cause analysis of recurring process failures.

Related Objects

Because the metadata classifies PSB_ERROR_MESSAGES as standalone, no FK relationships are enforced. Practically, it is referenced by and correlated with:

• FND_CONCURRENT_REQUESTS – joined on CONCURRENT_REQUEST_ID.
• FND_CONCURRENT_PROGRAMS – via the originating concurrent program.
• PSB budget and position tables that generate the errors.
• FND_LOG_MESSAGES – supplementary diagnostic logging.
• FND_USER – resolving CREATED_BY.

These associations are logical rather than FK-enforced, so joins should be validated against the CONCURRENT_REQUEST_ID linkage.