Search Results enqueue_enabled_code

Overview

APPS.OKC_QUE_NAMES_V is a reporting view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes Advanced Queueing metadata for the Oracle Contracts (OKC) product family. Its definition filters the data dictionary view DBA_QUEUES to those rows whose QUEUE_TABLE begins with the literal prefix "OKC". The result is a concise registry of the queues and queue tables provisioned by the Contracts modules — for example the queues used by the Contracts workflow, the contract approval and signature events, and the structured-processing infrastructure that feeds the OKC-related business events.

Unlike a functional application view, OKC_QUE_NAMES_V does not carry contract business data. Instead it is a diagnostic and administrative aid: it tells implementers and DBAs which OKC queue objects exist in the database, what type they are, and whether enqueue and dequeue are currently enabled. Because it is owned by APPS and sourced from DBA_QUEUES, it is frequently used during installation verification, concurrent-manager troubleshooting, and integration testing of inbound or outbound contract events.

Underlying Base Objects

The documented base objects for this view are:

• DBA_QUEUES (referenced as a SYNONYM): the Oracle Streams Advanced Queueing data dictionary view that lists every queue defined in the database along with its owning schema, queue table, queue type, and enabled status for enqueue and dequeue operations. The ETRM metadata confirms the view is defined over this synonym rather than over a local OKC table.
• OKC_UTIL (PACKAGE): the Contracts utility package, whose DECODE_LOOKUP function is invoked in the SELECT list to translate the raw YES/NO flags into the descriptive meanings defined in the OKC_YES_NO lookup. This is the standard EBS mechanism for presenting lookup values in human-readable form.

The WHERE clause queue_table LIKE 'OKC%' is the only restriction applied, so the view returns one row per OKC queue, including any queue whose table name shares the OKC prefix. No join to OKC business tables is performed; the linkage to the Contracts application is entirely by naming convention.

Key Columns

• QID — the numeric identifier of the queue.
• NAME — the queue name as registered in Advanced Queueing.
• QUEUE_TABLE — the underlying queue table (the result of the OKC% filter); this is the column most often queried directly by users searching on "queue_table".
• QUEUE_TYPE — indicates whether the queue is a normal (persistent) or exception queue.
• ENQUEUE_ENABLED / DEQUEUE_ENABLED — raw YES/NO flags from DBA_QUEUES, returned twice: once decoded through OKC_UTIL.DECODE_LOOKUP('OKC_YES_NO', ...) and once as the raw trimmed value.

The duplicated, decoded/undecoded pairs let reports display friendly Yes/No text while still allowing comparisons against the underlying dictionary values.

Common Use Cases and Queries

Typical uses include confirming that OKC queues were created during a Contracts installation or upgrade, auditing whether enqueue/dequeue have been inadvertently disabled, and enumerating queue tables before purging or reconfiguring them.

• List all OKC queues and their enabled states:
  SELECT name, queue_table, queue_type, enqueue_enabled, dequeue_enabled FROM apps.okc_que_names_v;
• Find queues backed by a specific queue table:
  SELECT name, queue_table FROM apps.okc_que_names_v WHERE queue_table = 'OKC_AQ_TABLE';
• Identify disabled queues requiring attention:
  SELECT name, dequeue_enabled FROM apps.okc_que_names_v WHERE dequeue_enabled = 'N';

All queries should be executed in the APPS schema or with the appropriate synonym and privileges.