Search Results fnd_conc_req_summary_v

Overview

FND_CONC_REQ_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, part of the FND – Application Object Library product. It presents a denormalized, human-readable summary of concurrent requests by joining the core transactional request table (FND_CONCURRENT_REQUESTS) to supporting lookup and translation tables for programs, users, and printer styles. Its purpose is to spare report developers and integrators from repeatedly reconstructing the multi-table joins required to render a meaningful concurrent request listing. Instead of raw internal identifiers, the view surfaces resolved values such as the requestor user name, the user-facing concurrent program name, and the effective printer style.

The view carries the ETRM status VALID and is flagged "Retrofitted," indicating it is part of the standard FND object set maintained across releases including 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own and always reflects the current state of its underlying base tables at query time. This makes it suitable for ad hoc operational reporting, custom concurrent programs, and integration extracts that need to enumerate and describe concurrent requests by their status, phase, and priority.

Underlying Base Objects

The documented base objects referenced by this view are all accessed through APPS synonyms:

• FND_CONCURRENT_REQUESTS — the driving table, aliased R, which supplies the request-level attributes.
• FND_CONCURRENT_PROGRAMS — aliased PB, joined on PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID, supplying program execution metadata.
• FND_CONCURRENT_PROGRAMS_TL — aliased PT, the translated program name table, joined on the same keys and constrained to the session language via USERENV('LANG').
• FND_USER — aliased U, joined on REQUESTED_BY = USER_ID to resolve the requestor.
• FND_PRINTER_STYLES_TL — aliased S, an outer join on PRINT_STYLE and session language, supplying the user printer style name.

The view is therefore a read-only projection over the concurrent request and program configuration model, with language-sensitive outer joins ensuring rows are not lost when a printer style is undefined.

Key Columns

• REQUEST_ID — unique identifier of the concurrent request; the primary join key for downstream queries.
• PRIORITY_REQUEST_ID — identifies the request against which priority ordering is evaluated, relevant when requests are chained or subordinated.
• PRIORITY — the numeric priority assigned to the request.
• PHASE_CODE and STATUS_CODE — the lifecycle phase (for example Pending, Running, Completed) and detailed status.
• REQUEST_DATE, REQUESTED_START_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE — scheduling and execution timestamps.
• REQUESTED_BY and REQUESTOR — the requesting user identifier and resolved user name.
• PROGRAM, PROGRAM_SHORT_NAME, USER_CONCURRENT_PROGRAM_NAME — readable program identification.
• HOLD_FLAG, HAS_SUB_REQUEST, IS_SUB_REQUEST, PARENT_REQUEST_ID — request hierarchy and control flags.
• PRINTER, USER_PRINT_STYLE, COMPLETION_TEXT — output configuration and result messaging.

Common Use Cases and Queries

A frequent requirement is locating a request by its priority grouping or by PRIORITY_REQUEST_ID, which is the term the user searched. The following query lists outstanding requests with their resolved program and requestor names:

• SELECT request_id, priority_request_id, priority, phase_code, status_code, program, requestor, request_date FROM fnd_conc_req_summary_v WHERE priority_request_id = :p_priority_request_id ORDER BY priority, request_date;
• SELECT request_id, program, requestor, actual_start_date, actual_completion_date FROM fnd_conc_req_summary_v WHERE phase_code = 'C' AND status_code = 'E' AND actual_completion_date >= SYSDATE - 1;
• SELECT request_id, program, user_print_style, printer FROM fnd_conc_req_summary_v WHERE hold_flag = 'Y';

These patterns support operational monitoring, error triage, and prioritization reporting. Because the view resolves names and language-specific program titles automatically, it is well suited to custom reports and integration extracts that must present concurrent request data without additional application-layer lookups.