Search Results xdp_ready_order_v




Overview
Explore in AI Chat

Overview

The XDP_READY_ORDER_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Provisioning module (XDP). Its documented purpose is to expose all orders currently present in the Order Ready Queue, providing a consolidated, query-friendly representation of work items that have been staged for downstream provisioning processing. In EBS 12.1.1 and 12.2.2 the view carries a VALID status and is shipped as part of the standard XDP product installation.

Rather than requiring integrators to interrogate the advanced-queue storage structures directly, the view flattens the queue payload and joins it to the order header, delivering a stable set of named columns. This makes it suitable for operational reporting, monitoring of queue depth, SLA tracking against due dates, and external system integration where a subscriber needs to identify which orders are awaiting provisioning. The inclusion of the EXTERNAL_ORDER_VERSION column is particularly relevant for external systems that stage order revisions and need to correlate a queued item with a specific version of the upstream order.

Underlying Base Objects

The metadata documents three referenced base objects:

  • XDP_ORDER_HEADERS (accessed via synonym) — the order header table supplying external order identity, version, and key dates.
  • XDP_ORDER_PROCESSOR_QTAB (accessed via synonym) — the order processor queue table holding the enqueued work items, their priority, enqueue time, and user data payload.
  • XDP_SYSCN_UTIL (package) — a utility package whose GET_Q_DATA_NUM function extracts a numeric value (notably ORDER_ID) from the queue's USER_DATA payload.

The join is performed on two predicates: the header's ORDER_ID must equal the numeric ORDER_ID decoded from the queue user data, and the header's MSGID must match the queue table's MSGID. This dual join ensures that the correct order header row is associated with its corresponding queued message.

Key Columns

  • EXTERNAL_ORDER_ID — derived from XDP_ORDER_HEADERS.EXTERNAL_ORDER_NUMBER; the identifier used by the external ordering system.
  • EXTERNAL_ORDER_VERSION — derived from XDP_ORDER_HEADERS.EXTERNAL_ORDER_VERSION; the version of the external order, allowing consumers to distinguish revisions of the same order.
  • INTERNAL_ORDER_ID — the numeric order identifier decoded from the queue payload via XDP_SYSCN_UTIL.GET_Q_DATA_NUM.
  • QUEUED_ON — the enqueue timestamp (OPQ.ENQ_TIME) indicating when the item entered the ready queue.
  • DUE_DATE — the order due date from the header, useful for prioritization and overdue analysis.
  • PROVISIONING_DATE — the header's provisioning date.
  • PRIORITY — the queue priority assigned to the work item.

Common Use Cases and Queries

Typical scenarios include monitoring ready-queue volume, reconciling queued orders against external order versions, and feeding integration processes that poll for new work.

List all ready orders ordered by queue time:

  • SELECT external_order_id, external_order_version, internal_order_id, queued_on, due_date, priority FROM apps.xdp_ready_order_v ORDER BY queued_on;

Locate a specific external order and version:

  • SELECT external_order_id, external_order_version, queued_on, priority FROM apps.xdp_ready_order_v WHERE external_order_id = :p_order_id AND external_order_version = :p_version;

Identify overdue or high-priority queued items:

  • SELECT external_order_id, external_order_version, due_date, priority FROM apps.xdp_ready_order_v WHERE due_date < SYSDATE OR priority = 1 ORDER BY due_date;

Determine current queue depth:

  • SELECT COUNT(*) FROM apps.xdp_ready_order_v;