Search Results xdp_dq_exceptions_pk




Overview
Explore in AI Chat

Overview

The XDP_DQ_EXCEPTIONS table is a core infrastructure object within the XDP Provisioning module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It is described in the ETRM metadata as a "common table to store queue exceptions," reflecting its role as the centralized repository for error and exception records generated by the provisioning and fulfillment queue processing engines. When concurrent programs, adapter jobs, or order-processing worklists encounter a failure condition, an exception row is written here and referenced by any dependent entity that needs to record the failure context.

Because it stores descriptive exception detail keyed by a surrogate identifier and does not itself aggregate metrics or model transactions, a heuristic Data Vault classification would suggest modeling this object as a hub, with its dependent references acting as links to the operational entities they qualify. Treat this classification as a modeling suggestion rather than a normative statement of the delivered schema.

Key Information Stored

The table's primary key is XDP_DQ_EXCEPTIONS_PK, defined on the ERROR_REF_ID column, which serves as the surrogate identifier for each exception record and the anchor to which all dependent rows point. Business-context columns include MESSAGE_ID, which correlates the exception to the originating message; WF_ITEM_TYPE and WF_ITEM_KEY, which identify the Oracle Workflow item type and item key associated with the failing process; and CALLER_NAME, which records the program or API that raised the exception. CALLBACK_TEXT holds the callback invocation context, while Q_NAME names the queue in which the exception was detected.

Operational and audit columns include TIME_STAMP for the exception event time, the standard WHO audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, and SECURITY_GROUP_ID, which enforces multi-tenant data access by referencing FND_SECURITY_GROUPS. The documented physical schema comprises fourteen columns in total.

Common Use Cases and Queries

Typical usage centers on exception triage and order fulfillment monitoring. Support and operations teams query this table to locate the root exception behind a stalled order line or failed adapter job, then join forward to the affected entity for resolution. A representative pattern retrieves recent exceptions with their owning order:

  • SELECT e.error_ref_id, e.caller_name, e.q_name, e.time_stamp, oh.order_number FROM xdp_dq_exceptions e JOIN xdp_order_headers oh ON oh.error_ref_id = e.error_ref_id WHERE e.time_stamp >= SYSDATE - 1;
  • Correlating a Workflow failure: join WF_ITEM_TYPE and WF_ITEM_KEY to the Workflow runtime tables to trace the item that generated the exception.
  • Queue-level error trending: aggregate COUNT(*) grouped by Q_NAME or CALLER_NAME to identify unstable queues or adapters.
  • Security-scoped reporting: filter by SECURITY_GROUP_ID to restrict exception visibility to the appropriate operating unit or tenant.
  • Adapter diagnostics: join to XDP_ADAPTER_JOB_QUEUE or XDP_ADAPTER_ADMIN_REQS on ERROR_REF_ID to diagnose adapter-side failures.

Related Objects

The table participates in a one-to-many relationship with multiple provisioning entities through the shared ERROR_REF_ID column. Dependent tables that reference it include:

On the lookup side, the table references FND_SECURITY_GROUPS via SECURITY_GROUP_ID, tying every exception record to the EBS security model. Together these relationships make XDP_DQ_EXCEPTIONS the diagnostic linchpin of the XDP provisioning and fulfillment pipeline.