Results for “queue_name”

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

Overview

OKC_QUE_SUBSCRIBERS_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC (Contracts Core) product family. The view exposes subscriber registration metadata for the Advanced Queuing (AQ) infrastructure that underpins the Contracts event model. Specifically, it presents the list of queue subscribers associated with the AQ queue table OKC_AQ_EV_TAB, which the Contracts application uses to publish and propagate business events such as contract approval, amendment, termination, and renewal.

In EBS 12.1.1 and 12.2.2, the view has a documented status of VALID. It behaves as a thin projection over an Oracle-managed AQ dictionary table rather than a Contracts business entity view. Its role is therefore diagnostic and administrative: it allows DBAs, integration developers, and support engineers to inspect which subscribers (internal or external) are registered against the Contracts event queue without querying the underlying AQ$ dictionary tables directly. Because AQ subscriber definitions govern who receives contract events, this view is relevant to workflow, BPEL, and third-party integration troubleshooting.

Underlying Base Objects

The documented view text is:

• SELECT NAME, QUEUE, ADDRESS, PROTOCOL FROM AQ$OKC_AQ_EV_TAB_S

The single referenced base object is the synonym AQ$OKC_AQ_EV_TAB_S. In Oracle Advanced Queuing, the AQ$ prefix denotes system-generated dictionary views created for a queue table. The suffix _S designates the subscriber dictionary view for the queue table, as opposed to the _Q (queue) or _T (queue table) variants. Consequently, AQ$OKC_AQ_EV_TAB_S is not a Contracts application table; it is generated and maintained by the AQ subsystem when the OKC_AQ_EV_TAB_S queue table is created and whenever subscribers are added or removed.

Because OKC_QUE_SUBSCRIBERS_V selects only four columns from this dictionary object, it is a read-only convenience view. It carries no Application Object Library (AOL) validation triggers, no WHO columns, and no Multi-Org (org_id) filter. It should not be treated as a transactional view; its contents change only when queue subscription configuration changes.

Key Columns

• NAME (SUBSCRIBER_NAME) — The name of the registered subscriber. This is the logical identifier used by AQ to distinguish one consumer of the queue from another.
• QUEUE (QUEUE_NAME) — The name of the queue to which the subscriber is attached. For OKC, this resolves to the Contracts event queue associated with the OKC_AQ_EV_TAB_S queue table.
• ADDRESS — The address to which enqueued messages are delivered for the subscriber. Depending on the subscription type, this may be a queue name, a PL/SQL callback identifier, or an HTTP endpoint.
• PROTOCOL — The delivery protocol number defined by AQ (for example, for PL/SQL callbacks or HTTP/web-service delivery). It determines how the message is transmitted to the ADDRESS.

Together these columns fully describe a subscriber registration, which is why the view requires no joins to be useful.

Common Use Cases and Queries

Typical scenarios include confirming that a custom or seeded subscriber exists after an OKC patch or upgrade, verifying delivery endpoints following a clone, and auditing which components consume contract events. A basic listing:

• SELECT name, queue, address, protocol FROM apps.okc_que_subscribers_v;

To locate a specific subscriber by name or address (for example, when the user search term "okc_aq_ev_tab_s" leads to the parent queue table):

• SELECT name, address, protocol FROM apps.okc_que_subscribers_v WHERE name = :p_subscriber;
• SELECT name, queue, address FROM apps.okc_que_subscribers_v WHERE UPPER(address) LIKE '%OKC_AQ_EV%';

Because the view is AQ metadata, results are best interpreted alongside AQ administration views such as USER_QUEUES and USER_QUEUE_SUBSCRIBERS when validating end-to-end Contracts event delivery.