Search Results psp_report_errors_u1

Overview

PSP.PSP_REPORT_ERRORS is a transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 PSP (Payroll/Effort Reporting) schema. It records error, warning, and informational messages generated at every level of the effort reporting process, whereas the companion table PSP_EFFORT_REPORT confines its diagnostics to the person level. Because errors may be raised against a payroll action, a request, a source record, or a parent source, this table serves as the central diagnostic log for the entire effort report creation cycle, capturing the context needed for both user-facing notification and downstream retry logic.

The table is physically stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its indexes reside in APPS_TS_TX_IDX. Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is that of a standalone structure. A modeling exercise might characterise it as a satellite positioned around the payroll action and reporting request business processes, since it carries descriptive diagnostic attributes rather than defining a shared business key or a many-to-many relationship between hubs.

Key Information Stored

The primary key, PSP_REPORT_ERRORS_PK, is composed of ERROR_SEQUENCE_ID and REQUEST_ID. The unique index PSP_REPORT_ERRORS_U1 covers ERROR_SEQUENCE_ID alone, making it the business-key candidate for uniquely identifying a message instance. The most operationally significant columns are:

• ERROR_SEQUENCE_ID (VARCHAR2 240) — surrogate/business identifier for the error record.
• REQUEST_ID (NUMBER) — concurrent request that produced the message; part of the primary key and indexed by PSP_REPORT_ERRORS_N1.
• MESSAGE_LEVEL — classification of the entry, typically E for Error or W for Warning.
• ERROR_MESSAGE (VARCHAR2 2000) — the human-readable text displayed to users.
• SOURCE_ID, SOURCE_NAME, PARENT_SOURCE_ID, PARENT_SOURCE_NAME — identify the offending element and its parent context.
• PAYROLL_ACTION_ID — foreign key to PAY_PAYROLL_ACTIONS, tying the error to a specific payroll action.
• RETRY_REQUEST_ID and PDF_REQUEST_ID — link diagnostics to subsequent retry and PDF-generation processes.
• VALUE1–VALUE10 (NUMBER) and INFORMATION1–INFORMATION10 (VARCHAR2 1000) — generic slots holding additional numeric and textual context specific to each error type.

Common Use Cases and Queries

Support teams query this table to diagnose failed effort report runs, and application logic uses it to drive retry and PDF regeneration. Typical patterns include retrieving all errors for a concurrent request:

• SELECT ERROR_SEQUENCE_ID, MESSAGE_LEVEL, ERROR_MESSAGE, SOURCE_NAME FROM PSP_REPORT_ERRORS WHERE REQUEST_ID = :request_id ORDER BY ERROR_SEQUENCE_ID;
• Filtering only errors for a payroll action: ... WHERE PAYROLL_ACTION_ID = :payroll_action_id AND MESSAGE_LEVEL = 'E';
• Joining to PAY_PAYROLL_ACTIONS to present action-level context alongside the messages.
• Reporting counts of errors versus warnings per request to identify systemic versus isolated failures.

Related Objects

• PSP.PSP_EFFORT_REPORT — companion effort reporting table; person-level errors differ from the broader levels captured here.
• PAY_PAYROLL_ACTIONS — referenced by PAYROLL_ACTION_ID; provides payroll action context.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to resolve request status and submitter.
• PSP_REPORT_ERRORS_U1 — unique index on ERROR_SEQUENCE_ID enforcing business key uniqueness.
• PSP_REPORT_ERRORS_N1, _N2, _N3 — non-unique indexes supporting lookups by request, payroll action, and source.