Search Results psb_error_messages_n2

Overview

PSB.PSB_ERROR_MESSAGES is an Oracle E-Business Suite interface table residing in the PSB schema and stored in the APPS_TS_INTERFACE tablespace. Its purpose is to capture error messages generated during concurrent processes, specifically those related to constraints checking and Human Resource Management Systems data extract. In the context of Oracle EBS 12.1.1 and 12.2.2, this table functions as a diagnostic and audit repository that records the reason a given concurrent request failed, allowing administrators and support personnel to review the exact error text produced by a specific process run.

The table is registered in FND Design Data as PSB.PSB_ERROR_MESSAGES and holds a VALID status. Its dependency profile indicates that it does not reference any database object and is referenced only through the APPS synonym PSB_ERROR_MESSAGES. From a heuristic Data Vault modeling perspective, the object is classified as standalone; while the metadata does not explicitly assign a hub, link, or satellite designation, its structure — a surrogate primary key on CONCURRENT_REQUEST_ID combined with descriptive attributes such as DESCRIPTION, PROCESS_ID, and SOURCE_PROCESS — suggests a satellite-like pattern keyed to a concurrent request hub, with the source process attribute acting as a descriptive qualifier rather than a true business key.

Key Information Stored

The table contains seven documented columns that together describe the error context, ordering, and audit trail for each message. The most important columns are:

• CONCURRENT_REQUEST_ID (NUMBER): The concurrent request unique identifier for the request that created the error message. This column is the documented primary key (CONCURRENT_REQUEST_ID_PK) and serves as the surrogate primary key for the row.
• PROCESS_ID (NUMBER): Unique identifier for the process for which errors are being logged. It participates in the nonunique index PSB_ERROR_MESSAGES_N1 and functions as a business-key candidate for grouping related messages.
• SOURCE_PROCESS (VARCHAR2, 30): The source process type generating the error. Documented valid values are WORKSHEET_CREATION, DATA_EXTRACT, VALIDATE_BUDGET_HIERARCHY, and BUDGET_REVISION. This column is the term the user searched for and is a key discriminator for filtering messages by originating process.
• SEQUENCE_NUMBER (NUMBER): The sequence in which messages are inserted for a concurrent request, used to order messages within the Error Report.
• DESCRIPTION (VARCHAR2, 2000): The full error description text.
• CREATION_DATE (DATE): Standard Who column recording when the message row was created.
• CREATED_BY (NUMBER): Standard Who column recording the user or process that inserted the row.

Two nonunique indexes exist in the APPS_TS_INTERFACE tablespace: PSB_ERROR_MESSAGES_N1 covers PROCESS_ID, SOURCE_PROCESS, and CONCURRENT_REQUEST_ID, while PSB_ERROR_MESSAGES_N2 covers CONCURRENT_REQUEST_ID.

Common Use Cases and Queries

Typical scenarios include troubleshooting failed concurrent requests, auditing constraints checking runs, and validating data extract outcomes for HRMS integrations. A common query filters by source process to isolate messages of a particular type:

• SELECT CONCURRENT_REQUEST_ID, PROCESS_ID, SOURCE_PROCESS, SEQUENCE_NUMBER, DESCRIPTION FROM PSB.PSB_ERROR_MESSAGES WHERE SOURCE_PROCESS = 'DATA_EXTRACT' ORDER BY SEQUENCE_NUMBER;
• SELECT DESCRIPTION FROM PSB.PSB_ERROR_MESSAGES WHERE CONCURRENT_REQUEST_ID = :request_id ORDER BY SEQUENCE_NUMBER;
• SELECT SOURCE_PROCESS, COUNT(*) FROM PSB.PSB_ERROR_MESSAGES GROUP BY SOURCE_PROCESS;

Reporting use cases include reconciling error volumes by process type and reconstructing the ordered error narrative for a specific request run.

Related Objects

The metadata documents that PSB_ERROR_MESSAGES does not reference any database object and is referenced by the APPS synonym PSB_ERROR_MESSAGES. Because the table's relationships are defined through its columns rather than declared foreign keys, the most significant related objects are those joined via its key and business-key columns:

• FND_CONCURRENT_REQUESTS: joined on CONCURRENT_REQUEST_ID to link messages to the originating concurrent request.
• APPS.PSB_ERROR_MESSAGES: the synonym through which the table is accessed.
• PSB process control or process definition tables: joined on PROCESS_ID to resolve the process for which errors are logged.
• HRMS data extract and constraints checking concurrent programs: the sources of SOURCE_PROCESS values such as DATA_EXTRACT and WORKSHEET_CREATION.

These relationships are inferred from documented columns and the standalone design of the object; no explicit foreign keys are recorded in the ETRM metadata.