Results for “cp_phase_code”

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

Overview

APPS.OKC_QUE_LSNR_V is a reporting view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and associated with the Oracle Knowledge Content (OKC) module — a component of the Procurement Contracts and Contract Terms library stack. The view presents a filtered, human-readable listing of concurrent requests submitted by the two OKC contract listener programs: OKCRAQO and OKCRAQE. Rather than exposing raw concurrent request rows, the view decodes internal lookup codes into descriptive text and joins program, user, and language information so that administrators and developers can monitor listener activity without writing joins against the underlying FND tables themselves.

The view is especially relevant because it resolves the CP_PHASE_CODE lookup through OKC_UTIL.DECODE_LOOKUP, which is the specific token the user searched for. This makes OKC_QUE_LSNR_V a convenient entry point for investigating the phase lifecycle of contract queue listener requests — for example, whether they are pending, running, completed normally, or completed with an error.

Underlying Base Objects

Per documented ETRM 12.2.2 metadata, the view is defined over four base objects plus one PL/SQL package:

• FND_CONCURRENT_PROGRAMS (SYNONYM) — supplies the executable/concurrent program definition, aliased as PB; joined on APPLICATION_ID and CONCURRENT_PROGRAM_ID.
• FND_CONCURRENT_PROGRAMS_TL (SYNONYM) — the translated program names, aliased as PT; joined by the same keys plus the session language (USERENV('LANG')).
• FND_CONCURRENT_REQUESTS (SYNONYM) — the request rows themselves, aliased as R; the driving table for REQUEST_ID, PHASE_CODE, and STATUS_CODE.
• FND_USER (SYNONYM) — supplies USER_NAME of the requester, aliased as U, joined on U.USER_ID = R.REQUESTED_BY.
• OKC_UTIL (PACKAGE) — not a table but a PL/SQL package supplying DECODE_LOOKUP, used to translate CP_PHASE_CODE and CP_STATUS_CODE values into display text.

The view is therefore a thin, decoded projection over the standard concurrent manager tables, restricted to listener programs and language.

Key Columns

• REQUEST_ID — the concurrent request identifier, uniquely locating each listener run.
• LISTENER — a decoded description combining R.DESCRIPTION with the program's user-defined name (or the program name alone if no description exists).
• CONCURRENT_PROGRAM — the internal program short name; constrained to OKCRAQO or OKCRAQE.
• PHASE / PHASE_CODE — the decoded and raw concurrent request phase. PHASE is produced via okc_util.decode_lookup('CP_PHASE_CODE', R.PHASE_CODE).
• STATUS / STATUS_CODE — the decoded and raw status, using the CP_STATUS_CODE lookup.
• APPLICATION_ID — the responsibility application ID (R.RESPONSIBILITY_APPLICATION_ID).
• SUBMISSION_DATE — the request submission timestamp.
• USER_NAME — the FND user who submitted the request.
• COMPLETION_TEXT — the completion message returned by the listener program.

Common Use Cases and Queries

Typical use cases include monitoring contract listener health, diagnosing stalled or erroring listeners, and tracing submissions by a specific user. The most direct query is:

SELECT listener, concurrent_program, phase, status, submission_date, user_name
FROM   apps.okc_que_lsnr_v
WHERE  phase_code = 'R';

To isolate failures, filter on completed-with-error requests:

SELECT request_id, listener, phase, status, completion_text
FROM   apps.okc_que_lsnr_v
WHERE  phase_code = 'C' AND status_code = 'E';

Because the view decodes CP_PHASE_CODE internally, external queries need only compare raw codes; the PHASE column already renders the descriptive equivalent. This makes OKC_QUE_LSNR_V a compact, self-contained instrument for contract listener operations and a useful reference when troubleshooting the OKC concurrent queue.