Results for “submission_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_QUE_LSNR_V is a reporting view owned by the APPS schema within the OKC – Contracts Core product of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. The view provides a filtered, presentation-ready listing of concurrent requests submitted by the Oracle Contracts concurrent programs OKCRAQO and OKCRAQE. These programs correspond to the Contracts Core "listener" queue processes, which poll and process inbound contract-related transactions as part of the Contract Approval and fulfillment queue mechanism.

The view is designed to expose the operational status of these listener requests in a user-readable form. Rather than requiring a report developer to decode FND lookup codes or join multiple Foundation tables, the view resolves phase and status codes into their display meanings and concatenates the request description with the concurrent program name to produce a meaningful listener label. The view is commonly consumed by Oracle Contracts setup pages, diagnostics, and custom operational dashboards that monitor whether the listener processes are running, stalled, or completed in error.

Underlying Base Objects

The view is defined over four FND base objects, all referenced through APPS synonyms, plus one PL/SQL package:

• FND_CONCURRENT_REQUESTS — supplies the requested-by user, phase code, status code, request date, completion text, and the program identifiers used for joining.
• FND_CONCURRENT_PROGRAMS — provides the base concurrent program name (CONCURRENT_PROGRAM_NAME) matched against 'OKCRAQO' and 'OKCRAQE', and joins on application and program identifiers.
• FND_CONCURRENT_PROGRAMS_TL — the translated table, supplying USER_CONCURRENT_PROGRAM_NAME filtered to the current session language via USERENV('LANG').
• FND_USER — resolves the user identifier into the user name displayed in the USER_NAME column.
• OKC_UTIL — the Contracts Core utility package, invoked as OKC_UTIL.DECODE_LOOKUP for the CP_PHASE_CODE and CP_STATUS_CODE lookup types.

The filter clause restricts output to requests whose phase is not complete, or which are complete with an error status (PHASE_CODE = 'C' AND STATUS_CODE = 'E'), so running and failed listener requests are surfaced while successful completions are suppressed.

Key Columns

• REQUEST_ID — the concurrent request identifier from FND_CONCURRENT_REQUESTS.
• LISTENER — a derived label combining the request description (when present) with the user-facing concurrent program name.
• CONCURRENT_PROGRAM — the internal concurrent program name, OKCRAQO or OKCRAQE.
• PHASE / PHASE_CODE — the decoded phase meaning and its underlying lookup code.
• STATUS / STATUS_CODE — the decoded status meaning and its underlying lookup code.
• APPLICATION_ID — the responsibility application identifier.
• SUBMISSION_DATE — the request submission date.
• USER_NAME — the requesting FND user.
• COMPLETION_TEXT — the completion message returned by the request.

Common Use Cases and Queries

Typical usage includes monitoring listener health, diagnosing stalled queue processing, and generating operational evidence during support escalations. A representative query is:

• SELECT listener, phase, status, user_name, submission_date, completion_text FROM okc_que_lsnr_v ORDER BY submission_date DESC;
• SELECT request_id, concurrent_program FROM okc_que_lsnr_v WHERE status_code = 'E';