Results for “xdp_order_headers”

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

Overview

XDP_ORDER_HEADERS is the master transactional table within the Provisioning (XDP) module of Oracle E-Business Suite, holding the header-level record for every provisioning order processed by the application. The object resides in the XDP schema and is fully validated in both EBS 12.1.1 and 12.2.2. It captures the full identity, lifecycle, and workflow context of an order, from receipt through provisioning, completion, hold, resume, or cancellation. As the anchor of the XDP order model, it is referenced by nearly every subordinate provisioning entity, including bundles, line items, parameters, relationships, and messaging infrastructure used by the XNP integration layer.

From a dimensional modeling perspective, the FK structure suggests classifying XDP_ORDER_HEADERS as a hub. It carries the durable business key (EXTERNAL_ORDER_NUMBER, EXTERNAL_ORDER_VERSION, ORDER_REF_NAME) and serves as the central point to which multiple satellite-like detail tables attach. This classification is heuristic and should be treated as a design suggestion rather than a mandated model.

Key Information Stored

The table is defined with 67 columns in the documented 12.2.2 schema. The most significant columns include:

• ORDER_ID — surrogate primary key (XDP_ORDER_HEADERS_PK) and the value propagated to all child tables.
• EXTERNAL_ORDER_NUMBER / EXTERNAL_ORDER_VERSION / ORDER_REF_NAME — the business key enforced by unique index XDP_ORDER_HEADERS_U1/U2, allowing the same external order number to exist across versions and reference contexts.
• STATUS_CODE / STATE — the provisioning order's current state within its workflow lifecycle.
• DATE_RECEIVED, PROVISIONING_DATE, ACTUAL_PROVISIONING_DATE, COMPLETION_DATE — key milestone timestamps.
• CANCEL_PROVISIONING_DATE / CANCELED_BY, HOLD_PROVISIONING_DATE / HELD_BY, RESUME_PROVISIONING_DATE / RESUMED_BY — audit columns tracking the cancellation, hold, and resume actions.
• DUE_DATE / CUSTOMER_REQUIRED_DATE — commitment and SLA timing fields.
• WF_ITEM_TYPE / WF_ITEM_KEY — linkage to the Oracle Workflow instance driving order processing.
• CUST_ACCOUNT_ID / CUSTOMER_ID / CUSTOMER_NAME / ORG_ID / SERVICE_PROVIDER_ID — customer, operating unit, and service provider context.
• ORDER_ACTION / ORDER_SOURCE / ORDER_TYPE / PRIORITY / ORDER_COMMENT — order classification and business intent.
• ERROR_REF_ID — pointer to XDP_DQ_EXCEPTIONS when the order fails data-quality validation.
• ATTRIBUTE1–ATTRIBUTE20 / ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting and operational scenarios include order status dashboards, SLA compliance, hold/cancel analysis, and workflow reconciliation. Common patterns:

• Identifying in-flight orders by status and age:
  SELECT order_id, external_order_number, status_code, date_received FROM xdp_order_headers WHERE status_code = :status AND provisioning_date IS NULL;
• Tracking order progression by milestone:
  SELECT order_id, provisioning_date, actual_provisioning_date, completion_date FROM xdp_order_headers WHERE date_received BETWEEN :from AND :to;
• Analyzing held or canceled orders:
  SELECT order_id, held_by, hold_provisioning_date, canceled_by, cancel_provisioning_date FROM xdp_order_headers WHERE canceled_by IS NOT NULL;
• Joining to customer context:
  SELECT h.order_id, h.customer_name, c.account_number FROM xdp_order_headers h, hz_cust_accounts c WHERE h.cust_account_id = c.cust_account_id;
• Correlating orders with workflow state via WF_ITEM_TYPE and WF_ITEM_KEY.

Related Objects

The table participates in an extensive FK web. The most significant related objects and their join columns are:

• HZ_CUST_ACCOUNTS — joined on CUST_ACCOUNT_ID (this table references it).
• XDP_DQ_EXCEPTIONS — joined on ERROR_REF_ID (this table references it).
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID.
• XDP_ORDER_LINE_ITEMS — child, joined on ORDER_ID.
• XDP_ORDER_BUNDLES — child, joined on ORDER_ID.
• XDP_ORDER_PARAMETERS — child, joined on ORDER_ID.
• XDP_ORDER_RELATIONSHIPS — child, linked via ORDER_ID and RELATED_ORDER_ID (self-referencing order-to-order linkage).
• XNP_MSGS / XNP_CALLBACK_EVENTS — messaging and callback records joined on ORDER_ID.
• XNP_SV_ORDER_MAPPINGS / XNP_SYNC_REGISTRATION / XNP_TIMER_REGISTRY — XNP integration tables joined on ORDER_ID.

These relationships confirm that XDP_ORDER_HEADERS acts as the central hub of the provisioning order model, and any extraction or reporting should preserve its join to HZ_CUST_ACCOUNTS and its child detail tables.