Search Results okc_que_names_v




Overview
Explore in AI Chat

Overview

OKC_QUE_NAMES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKC (Contracts Core) product family. The view exposes configuration metadata about Oracle Advanced Queuing (AQ) objects whose queue tables are named with the OKC prefix, providing a contracts-centric window into the underlying DBA_QUEUES data dictionary view. It functions as a filtered, presentation-layer abstraction over DBA_QUEUES, restricting results to queues that support Contracts Core workflows such as concurrent request queueing, workflow messaging, and asynchronous contract processing.

Because it centralizes queue configuration details and translates low-level yes/no flag codes into user-readable values, OKC_QUE_NAMES_V is primarily used for diagnostics, administrative verification, and integration monitoring. It answers operational questions such as which OKC queues are enabled for enqueue and dequeue, which queue tables they reside on, and how those queues are typed. This makes it valuable in both 12.1.1 and 12.2.2 environments where contracts processing depends on the availability and correct configuration of AQ infrastructure.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over two base objects:

  • DBA_QUEUES (SYNONYM) — The Oracle data dictionary view describing all queues in the database. It supplies QID, NAME, QUEUE_TABLE, QUEUE_TYPE, ENQUEUE_ENABLED, and DEQUEUE_ENABLED. The view applies the filter WHERE QUEUE_TABLE LIKE 'OKC%' to isolate OKC-related queues.
  • OKC_UTIL (PACKAGE) — The Contracts Core utility package. Its DECODE_LOOKUP function is invoked to translate the raw enqueue/dequeue enablement codes into descriptive values, using the lookup type OKC_YES_NO.

The view additionally applies RTRIM and LTRIM to the enablement flags, normalizing any padded values before decoding. Because it derives from DBA_QUEUES, the view effectively reflects any queue whose backing table carries the OKC prefix.

Key Columns

  • QUEUE_ID — Surfaces QID, the numeric identifier of the queue.
  • QUEUE_NAME — Surfaces NAME, the queue name as defined in Oracle AQ.
  • QUEUE_TABLE — The queue table name; always matches OKC% by virtue of the view's filter.
  • QUEUE_TYPE — The AQ queue type, typically indicating normal or exception queue behavior.
  • ENQUEUE_ENABLED — The decoded, human-readable value indicating whether enqueue operations are permitted, based on OKC_YES_NO.
  • ENQUEUE_ENABLED_CODE — The raw, trimmed enablement flag from DBA_QUEUES.
  • DEQUEUE_ENABLED — The decoded value indicating whether dequeue operations are permitted.
  • DEQUEUE_ENABLED_CODE — The raw, trimmed dequeue enablement flag.

The paired decoded/code columns allow both administrative readability and direct comparison against dictionary values.

Common Use Cases and Queries

Typical scenarios include verifying that contract-related queues are enabled, auditing queue configuration after patching, and troubleshooting stalled contract processing caused by a disabled queue. A basic listing of OKC queues and their operational status:

SELECT QUEUE_NAME, QUEUE_TABLE, QUEUE_TYPE, ENQUEUE_ENABLED, DEQUEUE_ENABLED FROM APPS.OKC_QUE_NAMES_V ORDER BY QUEUE_NAME;

To identify queues where dequeue has been disabled — a frequent cause of processing backlogs:

SELECT QUEUE_NAME, QUEUE_TABLE FROM APPS.OKC_QUE_NAMES_V WHERE DEQUEUE_ENABLED_CODE = 'N';

To review queue types across all OKC queue tables:

SELECT QUEUE_TABLE, QUEUE_TYPE, COUNT(*) FROM APPS.OKC_QUE_NAMES_V GROUP BY QUEUE_TABLE, QUEUE_TYPE;

These queries provide administrators a concise, decoded inventory of the Contracts Core queue landscape without querying DBA_QUEUES directly.