Search Results xdp_adapter_job_queue_v




Overview
Explore in AI Chat

Overview

The XDP_ADAPTER_JOB_QUEUE_V view is a read-optimized presentation layer over the internal queue table XDP_ADAPTER_JOB_QUEUE in the Oracle E-Business Suite Provisioning module (XDP). Its purpose is to expose the most recent adapter-job queue entry for each unique fulfillment request context, rather than the full history of queue records. This view plays a critical infrastructure role in the Fulfillment Action (FA) workflow processing model. When the FA workflow attempts to execute a Fulfillment Procedure (FP) against a Fulfillment Element (FE), it must first allocate a free adapter to service that request. The XDP_ADAPTER_JOB_QUEUE_V view surfaces the current queue state that supports this adapter allocation and job dispatch logic.

The view is owned by the APPS schema and is documented as VALID in the ETRM metadata for both EBS 12.1.1 and 12.2.2. It is classified as an internal queue table and should not be treated as a business-facing reporting object.

Underlying Base Objects

The view is defined exclusively over the base table XDP_ADAPTER_JOB_QUEUE (exposed via a synonym in the APPS schema). No joins to master or transactional tables are present in the view definition. Instead, the view applies a correlated subquery filter:

  • FROM XDP_ADAPTER_JOB_QUEUE AJQ1 — the outer query aliases the base table as AJQ1.
  • WHERE QUEUED_ON = (SELECT MAX(AJQ2.QUEUED_ON) FROM XDP_ADAPTER_JOB_QUEUE AJQ2 WHERE AJQ2.ORDER_ID = AJQ1.ORDER_ID AND AJQ2.FE_ID = AJQ1.FE_ID AND AJQ2.WORKITEM_INSTANCE_ID = AJQ1.WORKITEM_INSTANCE_ID) — the inner query selects the latest enqueue timestamp per logical fulfillment unit.

The effect is that one row is returned for each distinct combination of ORDER_ID, FE_ID, and WORKITEM_INSTANCE_ID, corresponding to the most recently queued adapter job. Because the view references only one base table, the join relation is a self-referential de-duplication rather than a multi-table expansion.

Key Columns

  • JOB_ID — Identifier of the queued adapter job record; distinguishes individual queue entries.
  • FE_ID — Fulfillment Element identifier; identifies the fulfillment element against which the Fulfillment Procedure will run.
  • ORDER_ID — Identifier of the provisioning order that owns the fulfillment context.
  • WORKITEM_INSTANCE_ID — Instance identifier of the workflow work item that initiated the request; together with ORDER_ID and FE_ID, it forms the grouping key for the MAX subquery.
  • FA_INSTANCE_ID — Instance identifier of the Fulfillment Action workflow attempting to allocate an adapter.
  • QUEUED_ON — Timestamp at which the job was enqueued; drives the latest-row filter as well as natural ordering.

Common Use Cases and Queries

This view is principally used for diagnostics and monitoring of adapter allocation during fulfillment orchestration.

  • Identify the most recent queued adapter job per order and fulfillment element:
SELECT job_id, order_id, fe_id, workitem_instance_id,
       fa_instance_id, queued_on
FROM   apps.xdp_adapter_job_queue_v
WHERE  order_id = :p_order_id;
  • Inspect the current adapter queue depth for a given Fulfillment Action instance:
SELECT fa_instance_id, COUNT(*)
FROM   apps.xdp_adapter_job_queue_v
GROUP  BY fa_instance_id;
  • Investigate stalled fulfillment work items by joining the view to order/workitem context to confirm whether a queue entry was ever recorded.

Because the view collapses historical entries and is not indexed as a reporting structure, queries should always be restricted by ORDER_ID, FE_ID, or FA_INSTANCE_ID to avoid full scans of the underlying queue table. For historical queue analysis, the base table XDP_ADAPTER_JOB_QUEUE should be queried directly.