Results for “xdp_pend_order_v”

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

Overview

XDP_PEND_ORDER_V is a reporting view within the Oracle E-Business Suite XDP (Provisioning) module. Its stated purpose, per the ETRM repository, is to show all orders currently resident in the Pending Order Queue. The view therefore functions as a real-time window into the provisioning backlog, exposing orders that have been enqueued for processing but have not yet been dequeued and completed by the provisioning engine.

Because the underlying queue storage is an advanced-queue table whose payload columns are opaque, XDP_PEND_ORDER_V exists to present a flattened, query-friendly projection of that data. Instead of parsing raw queue payloads, report authors and integrators can join the view against standard lookup and order header information using ordinary SQL. The ETRM metadata explicitly documents the column EXTERNAL_ORDER_ID, which is the alias applied to XDP_ORDER_HEADERS.EXTERNAL_ORDER_NUMBER and is the most common search term associated with this object.

Underlying Base Objects

The view is defined over three documented sources:

• XDP_ORDER_HEADERS (OH) — the master provisioning order header, supplying external order number, version, due date, provisioning date, message ID, and process state.
• XDP_PENDING_ORDER_QTAB (PEOQ) — the advanced-queue staging table holding pending orders, supplying the queue payload (USER_DATA), enqueue time, priority, and message ID.
• FND_LOOKUPS (LK) — the standard lookup table, used specifically to translate OH.STATE into a human-readable meaning via the lookup type 'XDP_PROCESS_STATE'.

Joins are formed on OH.ORDER_ID equal to XDP_SYSCN_UTIL.GET_Q_DATA_NUM(PEOQ.USER_DATA,'ORDER_ID') and on matching OH.MSGID and PEOQ.MSGID. The internal order identifier is not stored as a discrete column in the queue but is extracted at runtime by the XDP_SYSCN_UTIL.GET_Q_DATA_NUM packaged function. The ETRM record notes that the view is not implemented in the source database from which the metadata was harvested and documents no additional referenced base objects, so environments may differ in availability.

Key Columns

• EXTERNAL_ORDER_ID — the externally assigned order number, aliased from XDP_ORDER_HEADERS.EXTERNAL_ORDER_NUMBER. This is the primary correlation key for external systems.
• EXTERNAL_ORDER_VERSION — the version of the external order, supporting revision tracking across submissions.
• INTERNAL_ORDER_ID — the EBS-internal order identifier derived from the queue payload.
• STATE — the decoded provisioning process state from FND_LOOKUPS where LOOKUP_TYPE = 'XDP_PROCESS_STATE'.
• QUEUED_ON — the enqueue timestamp indicating when the order entered the pending queue, useful for aging analysis.
• DUE_DATE — the order's contractual or requested completion date.
• PROVISIONING_DATE — the date on which provisioning activity is targeted.
• PRIORITY — the queue priority assigned to the pending order, determining dequeue sequence.

Common Use Cases and Queries

Typical uses include backlog monitoring, order aging, and reconciliation between external order identifiers and internal EBS order records. A representative query retrieves pending orders by external identifier:

• SELECT external_order_id, external_order_version, internal_order_id, state, queued_on, due_date, priority FROM xdp_pend_order_v WHERE external_order_id = :p_external_order_id;
• SELECT state, COUNT(*) FROM xdp_pend_order_v GROUP BY state; — distribution of pending orders by process state.
• SELECT external_order_id, queued_on, SYSDATE - queued_on age_days FROM xdp_pend_order_v ORDER BY queued_on; — queue aging report.

All queries should be scoped to the appropriate operating unit or responsibility context where data security applies.