Search Results psb_error_requests_v




Overview
Explore in AI Chat

Overview

PSB_ERROR_REQUESTS_V is an APPS-owned, VALID database view in Oracle E-Business Suite (12.1.1 and 12.2.2) belonging to the PSB – Public Sector Budgeting product. Its purpose is to present a consolidated, human-readable list of concurrent requests and processing activities that have generated errors during budget preparation. Public Sector Budgeting depends on multiple concurrent processes — data extraction, budget hierarchy validation, worksheet creation, budget journal creation, and interface/transfer jobs — and when any of these fail or raise exceptions, error rows are written into the underlying error message table. The view enriches those raw error rows by joining them to lookup meanings, resolving the source process into a descriptive label, and substituting the actual process name (for example the budget group name, data extract name, or worksheet name) depending on the originating process. The result is a reporting-friendly record keyed by concurrent request that administrators and budget analysts can query to identify what failed, in which process, and against which named budget object.

The object is classified as a view rather than a table because it holds no persistent data; it is a query layer over error and definition tables owned by the PSB schema, exposed under APPS for consistent access and security. It typically appears in diagnostics, error-tracking reports, and troubleshooting queries rather than in transactional application logic.

Underlying Base Objects

The view text references the following base objects:

These definition tables are combined through UNION ALL into an inline view (COMBO_T) that is joined back to the error rows using correlated OR predicates on PROCESS_ID and a discriminator tag, so that each error is matched only to the correct type of source object. ETRM documents no explicitly named referenced base objects, but the view text confirms the dependencies above.

Key Columns

Common Use Cases and Queries

Typical scenarios include diagnosing why a budget submission failed, monitoring errors by concurrent request, and auditing which budget groups or worksheets repeatedly raise exceptions.

List all errors for a given request:

  • SELECT concurrent_request_id, process_id, source_process_meaning, process_name FROM apps.psb_error_requests_v WHERE concurrent_request_id = :request_id;

Count errors grouped by source process:

  • SELECT source_process_meaning, COUNT(*) FROM apps.psb_error_requests_v GROUP BY source_process_meaning ORDER BY 2 DESC;

Find all errors tied to a specific named worksheet or budget group:

  • SELECT concurrent_request_id, process_id, process_name FROM apps.psb_error_requests_v WHERE process_name = :name;

Because the view deduplicates on request, process, and source process, users should join to PSB_ERROR_MESSAGES directly when the full error text of each individual message is required.