Search Results outfile_name

Overview

OKL_CONC_REQUESTS_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the OKL – Lease and Finance Management product family. It is a user-facing (the "UV" suffix denotes "user view") presentation layer over the standard Oracle Workflow and Concurrent Manager dictionary tables, filtered and enriched for consumption by Lease and Finance Management screens, reports, and integrations. Rather than exposing raw foreign keys and code values, the view resolves lookup codes into human-readable meanings and formats date columns for display.

The view answers the operational question: "What concurrent requests were submitted, by whom, at what priority, and with what outcome?" It is especially relevant when tracing lease accounting programs, such as those that generate accounting entries or period-end processing, that are launched through the concurrent manager. Because it joins to FND_CONCURRENT_REQUESTS, every request visible here is a genuine concurrent request with a REQUEST_ID, phase, and status.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms:

• FND_CONCURRENT_REQUESTS – the driving table (aliased R), supplying request identity, phase, status, priority linkage, dates, and log/out file names.
• FND_CONCURRENT_PROGRAMS (PB) and FND_CONCURRENT_PROGRAMS_TL (PT) – provide the translated concurrent program name, joined on application and program ID and restricted to the session language via USERENV('LANG').
• FND_USER (U) – resolves REQUESTED_BY into the requestor's user name.
• FND_LANGUAGES (FL) and FND_LANGUAGES_TL (FLT) – supply the language description for the request's NLS language.
• OKL_ACCOUNTING_UTIL (package) – the view calls the GET_LOOKUP_MEANING function twice to translate PHASE_CODE and STATUS_CODE into display meanings.

The joins are all inner joins on application ID, program ID, user ID, and language, so a request appears only when its program, requestor, and language records all exist and match.

Key Columns

The view exposes the following principal columns:

• ROW_ID / REQUEST_ID – the row identifier and the unique concurrent request identifier.
• PHASE_CODE / PHASE_MEANING – the request phase (for example, Pending, Running, Completed) and its decoded meaning.
• STATUS_CODE / STATUS_MEANING – the detailed status code and its decoded meaning.
• PRIORITY_REQUEST_ID – the request ID of the parent or higher-priority request to which this request is linked, used to associate child requests (such as a program launched from within another) with the request that triggered them.
• REQUEST_DATE and REQUEST_DATE_DISPLAY – the submission date, both truncated and formatted as DD/MM/YYYY HH:MI:SS AM.
• REQUESTED_BY / REQUESTOR – the submitting user's ID and resolved user name.
• REQUESTED_START_DATE, ACTUAL_START_DATE, ACTUAL_COMPLETION_DATE – scheduled versus actual execution and completion timestamps, each with a corresponding display column.
• COMPLETION_TEXT and ARGUMENT_TEXT – completion messages and the submitted program arguments.
• USER_CONCURRENT_PROGRAM_NAME, LOGFILE_NAME, OUTFILE_NAME, LANGUAGE – program identity, log and output file references, and language description.
• LOG_URL, OUTPUT_URL, DIAGNOSTICS – defined as NULL placeholders for client-side URL construction.

Common Use Cases and Queries

The view is typically queried to audit or monitor Lease and Finance Management concurrent activity, particularly to trace requests by submitter, status, or parent-child priority relationship.

SELECT REQUEST_ID, USER_CONCURRENT_PROGRAM_NAME, PHASE_MEANING,
       STATUS_MEANING, REQUEST_DATE, REQUESTOR
FROM   APPS.OKL_CONC_REQUESTS_UV
WHERE  TRUNC(REQUEST_DATE) >= TRUNC(SYSDATE) - 7
ORDER  BY REQUEST_DATE DESC;

To examine requests associated with a given priority or parent request:

SELECT REQUEST_ID, PRIORITY_REQUEST_ID, USER_CONCURRENT_PROGRAM_NAME,
       STATUS_MEANING, REQUEST_DATE, REQUESTOR
FROM   APPS.OKL_CONC_REQUESTS_UV
WHERE  PRIORITY_REQUEST_ID = :parent_request_id;

Because the view resolves lookup meanings, formats dates, and joins program and user names, it eliminates the repetitive decoding work otherwise required against the underlying FND tables, making it well suited for operational reports and support diagnostics within the OKL module.