Search Results oracle_session_id

Overview

FND_AMP_REQUESTS_V is a PL/SQL view owned by the APPS schema within the FND — Application Object Library product of Oracle E-Business Suite. The name reflects its origin in the Application Management Pack (AMP), the Oracle Enterprise Manager toolset used to monitor and administer concurrent processing across an EBS environment. Rather than exposing the raw contents of the concurrent requests table, the view denormalizes and translates run-time request data into human-readable form, joining program, responsibility, application, and user names that are otherwise stored only as numeric identifiers in the base transaction table.

Its principal role is to provide a monitoring and reporting surface for administrators who must track the execution lifecycle of concurrent programs. Each row represents a single concurrent request, annotated with its current phase and status expressed in meaningful text, the requested-by user, the owning responsibility, the source application, and the relevant scheduling timestamps. Because phase and status derivation depend on internal business rules controlled by the FND_AMP_PRIVATE package, the view acts as a stable, read-only interface that shields consumers from that logic and from the multi-language translation tables that would otherwise complicate direct queries.

Underlying Base Objects

The view draws on seven documented base objects. FND_CONCURRENT_REQUESTS is the driver table, supplying the request row and its identifiers, phase and status codes, hold flag, timestamps, and argument text. FND_CONCURRENT_PROGRAMS_VL and FND_CONCURRENT_PROGRAMS_TL supply the concurrent program definition and its translated user-facing name. FND_APPLICATION_TL provides the translated application name for the program's owning application. FND_RESPONSIBILITY_TL supplies the translated responsibility name. FND_USER resolves the REQUESTED_BY identifier to a user name. Finally, the FND_AMP_PRIVATE package supplies the GET_PHASE and GET_STATUS functions that convert the raw PHASE_CODE, STATUS_CODE, HOLD_FLAG, and ENABLED_FLAG values into display text.

All joins are performed against translation tables filtered by USERENV('LANG'), so the result set is language-aware and returns names in the session's language. Program and responsibility joins rely on the composite application and program (or responsibility) identifiers, and the translated program name is presented with the request description in parentheses when a description exists.

Key Columns

• REQUEST_ID — The unique concurrent request identifier and the natural primary key for each row.
• PROGRAM — The concurrent program name, optionally combined with the request description as "Description ( Program )".
• PHASE and STATUS — Decoded, human-readable execution phase and status derived by FND_AMP_PRIVATE.GET_PHASE and GET_STATUS.
• PHASE_CODE and STATUS_CODE — The underlying internal codes on which the decoded values are based.
• USER_NAME — Name of the user who submitted the request.
• RESPONSIBILITY_NAME — Responsibility under which the request was submitted.
• APPLICATION — Application owning the concurrent program.
• REQUESTED_START_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE, REQUEST_DATE — Scheduling and completion timestamps used for performance analysis.
• PRIORITY, HOLD_FLAG, QUEUE_METHOD_CODE, CONTROLLING_MANAGER, ORACLE_SESSION_ID, OS_PROCESS_ID — Submission, queuing, and process-identification attributes.
• ARGUMENT_TEXT, COMPLETION_TEXT, PARENT_REQUEST_ID, IS_SUB_REQUEST — Parameters, error output, and request hierarchy details.

Common Use Cases and Queries

Administrators monitor long-running or failed requests, examine request hierarchies, and review submission patterns by user, responsibility, or application. A typical monitoring query filters on the decoded status:

• Locate failures: SELECT request_id, program, status, completion_text FROM fnd_amp_requests_v WHERE phase = 'Completed' AND status = 'Error';
• User activity: SELECT user_name, COUNT(*) FROM fnd_amp_requests_v WHERE request_date >= TRUNC(SYSDATE) GROUP BY user_name;
• Runtime analysis: SELECT program, (actual_completion_date - actual_start_date) * 86400 secs FROM fnd_amp_requests_v WHERE actual_completion_date IS NOT NULL;
• Hierarchy traversal: retrieve PARENT_REQUEST_ID and IS_SUB_REQUEST to map submitted child requests to their parent jobs.

The view is read-only and intended for diagnostic reporting and integration rather than transactional updates, all of which must remain confined to the base concurrent requests tables.