Search Results logical_ios

Overview

FND_CONC_REQUESTS_FORM_V is a view owned by the APPS schema in Oracle E-Business Suite (12.1.1 and 12.2.2), residing in the FND — Application Object Library product. It presents a form-oriented, denormalized projection of concurrent request data, combining the core transactional columns of FND_CONCURRENT_REQUESTS with descriptive, lookup-decoded attributes drawn from program definitions, applications, languages, users, release classes, and printers. Its primary purpose is to feed the Concurrent Requests form and related user-interface queries within the System Administrator responsibility, exposing each request's phase, status, timing, output/print configuration, arguments, and execution statistics in a single row. Because it surfaces columns such as LOGFILE_NAME and LOGFILE_NODE_NAME, it is also central to log and output file retrieval for reports, integrations, and support diagnostics — the search term "logfile_node_name" maps directly to the LOGFILE_NODE_NAME column this view exposes.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following objects (all referenced as synonyms unless noted): FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_PROGRAMS_TL, FND_APPLICATION and FND_APPLICATION_TL, FND_CONC_RELEASE_CLASSES and FND_CONC_RELEASE_CLASSES_TL, FND_LANGUAGES and FND_LANGUAGES_TL, FND_LOOKUP_VALUES, FND_PRINTER_STYLES_TL, FND_USER, HR_ALL_ORGANIZATION_UNITS_TL, FND_CONFLICTS_DOMAIN, and the package FND_CONC_REQUEST_PKG. The central base table is FND_CONCURRENT_REQUESTS, which supplies the request identifiers, phase and status codes, timing fields, file names, and argument slots. The TL (translation) tables join the translatable name and description attributes for programs, applications, release classes, languages, and printers, while FND_LOOKUP_VALUES decodes codes such as phase, status, and output type into displayable values. This join-heavy definition explains why the view returns user-facing labels alongside raw codes and why it underlies the Concurrent Requests form.

Key Columns

• REQUEST_ID — Primary identifier of the concurrent request; the join key to child and sub-request rows via PARENT_REQUEST_ID and PRIORITY_REQUEST_ID.
• PHASE_CODE / STATUS_CODE / COMPLETION_TEXT — Execution lifecycle indicators used for progress tracking and completion reporting.
• LOGNAME — LOGFILE_NAME — Path to the request log file.
• LOGFILE_NODE_NAME — The application tier node on which the log file resides; essential for distributed/multi-node environments when retrieving logs.
• OUTFILE_NAME / OUTFILE_NODE_NAME — Corresponding output file path and node.
• ORACLE_ID / OS_PROCESS_ID / ORACLE_PROCESS_ID — Database and OS process identifiers for the executing request, useful in performance and hang analysis.
• CONCURRENT_PROGRAM_ID / PROGRAM_APPLICATION_ID — Program definition references, joined to program and application tables for names.
• REQUESTED_BY / RESPONSIBILITY_ID — The requesting user and responsibility, linking to FND_USER and responsibility context.
• REQUEST_DATE / ACTUAL_START_DATE / ACTUAL_COMPLETION_DATE — Scheduling and runtime timing columns.
• ARGUMENT1 … ARGUMENT25 / ARGUMENT_TEXT — Parameter values passed to the program.

Common Use Cases and Queries

The view supports operational reporting, log retrieval, and monitoring of concurrent processing. Because it is defined in the APPS schema, standard queries must qualify it as APPS.FND_CONC_REQUESTS_FORM_V or run within the APPS context. Typical scenarios include locating recent failures, tracing long-running requests, and retrieving the log/output node for a completed job.

• Find requests awaiting or running: SELECT request_id, phase_code, status_code, request_date, requested_by FROM fnd_conc_requests_form_v WHERE phase_code IN ('P','R') ORDER BY request_date DESC;
• Locate the log file and node for a request (logfile_node_name use case): SELECT request_id, logfile_name, logfile_node_name, outfile_name, outfile_node_name FROM fnd_conc_requests_form_v WHERE request_id = :req_id;
• Report recent completions with runtime statistics: SELECT request_id, actual_start_date, actual_completion_date, cpu_seconds, completion_text FROM fnd_conc_requests_form_v ORDER BY actual_completion_date DESC;
• Inspect arguments and program context: SELECT request_id, concurrent_program_id, program_application_id, argument1, argument2 FROM fnd_conc_requests_form_v WHERE request_id = :req_id;

These queries align with the view's form-focused design, providing administrators and integration developers with a single, readable source for concurrent request details, including the logfile_node_name attribute central to log file location in Oracle EBS 12.1.1 and 12.2.2 deployments.