Search Results internal_order_id




Overview
Explore in AI Chat

Overview

The view APPS.XDP_READY_ORDER_V is a reporting and integration object within the Oracle E-Business Suite order-to-cash provisioning framework, commonly associated with the Telecommunications and Utilities data model delivered by the ETRM (Enterprise Telecommunications Resource Management) family of products. Its purpose is to expose orders that have been successfully enqueued onto the XDP order processor queue and are therefore considered "ready" for downstream processing, provisioning, or fulfillment. Rather than representing a physical table, the view provides a consolidated, denormalized projection that joins order header information with the queue table state. For a user searching on internal_order_id, this view is significant because it surfaces that identifier directly through a derived column, allowing external callers and internal reporting tools to reconcile the externally visible order number with the internal surrogate key used by the application.

Underlying Base Objects

The view is defined over three documented dependencies. The first is XDP_ORDER_HEADERS (accessed via a synonym in the APPS schema), which supplies the authoritative order header attributes such as external order number, version, due date, and provisioning date. The second is XDP_ORDER_PROCESSOR_QTAB, an Advanced Queue table holding the pending messages addressed to the order processor. The third is the package XDP_SYSCN_UTIL, whose function GET_Q_DATA_NUM is invoked to extract a numeric value from the queue's USER_DATA payload. The join is enforced on two predicates: the header's ORDER_ID must equal the extracted numeric ORDER_ID from the queue payload, and the MSGID of the header must match the MSGID of the queue row. This dual-key join preserves the correspondence between the enqueued message and its originating order record.

Key Columns

The view projects seven columns. EXTERNAL_ORDER_ID maps to OH.EXTERNAL_ORDER_NUMBER and is the business-facing order identifier. EXTERNAL_ORDER_VERSION distinguishes multiple revisions of the same order. INTERNAL_ORDER_ID is computed by XDP_SYSCN_UTIL.GET_Q_DATA_NUM(OPQ.USER_DATA, 'ORDER_ID') and is the internally assigned key, which explains its prominence in user searches. QUEUED_ON derives from the queue's ENQ_TIME and records the moment the order was placed on the processor queue. DUE_DATE and PROVISIONING_DATE come from the order header and indicate scheduling commitments. Finally, PRIORITY reflects the enqueue priority assigned to the message.

Common Use Cases and Queries

Typical usage includes monitoring queue backlog, verifying that an order has reached the ready state, and bridging external and internal identifiers during integration testing. A representative query follows:

  • SELECT INTERNAL_ORDER_ID, EXTERNAL_ORDER_ID, QUEUED_ON, PRIORITY FROM APPS.XDP_READY_ORDER_V WHERE INTERNAL_ORDER_ID = :order_id;
  • SELECT * FROM APPS.XDP_READY_ORDER_V ORDER BY QUEUED_ON DESC;
  • SELECT EXTERNAL_ORDER_ID, DUE_DATE, PROVISIONING_DATE FROM APPS.XDP_READY_ORDER_V WHERE PRIORITY > 5;

Because the view reads live queue data, results change as messages are consumed, so it is best used for near-real-time status inspection rather than historical reconciliation.