Search Results xdp_oe_order_headers




Overview
Explore in AI Chat

Overview

XDP_OE_ORDER_HEADERS is an Oracle E-Business Suite table owned by the XDP schema and belongs to the XDP Provisioning product family. It stores the order header information for orders generated by the Oracle SFM (Service Fulfillment Manager) Order Entry Interface. In practical terms, the table acts as the header-level staging and reference point for provisioning orders that flow into downstream fulfilment processes; each row represents a single order version, identified by the composite business identifier ORDER_NUMBER plus ORDER_VERSION. The Oracle SFM Order Entry Interface writes into this table so that order-level attributes — customer, dates, status, priority, and service-provider context — are captured consistently before line and parameter detail is attached.

In Data Vault modeling terms the ETRM relationship metadata classifies this table as hub-leaning. This is a modeling suggestion rather than a physical constraint: ORDER_NUMBER and ORDER_VERSION behave as a durable business key that lines and parameters reference, which is characteristic of a hub. Practitioners adopting a Data Vault or dimensional model should treat (ORDER_NUMBER, ORDER_VERSION) as the natural key of the hub, with the descriptive columns (dates, status, customer and service-provider attributes) suitable for one or more satellite tables.

Key Information Stored

The table is documented with 30 columns in ETRM 12.2.2. The most significant columns for day-to-day use include:

No single surrogate sequence key is documented; the composite (ORDER_NUMBER, ORDER_VERSION) serves as both primary key and business key. Audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY and LAST_UPDATE_LOGIN are standard EBS WHO-column equivalents.

Common Use Cases and Queries

Typical uses of XDP_OE_ORDER_HEADERS include order-status dashboards, provisioning aging reports and reconciliation between SFM-generated orders and the downstream fulfilment tables.

  • Order status monitoring: select ORDER_NUMBER, ORDER_VERSION, STATUS, PRIORITY and DUE_DATE where STATUS is not closed, ordered by DUE_DATE to surface at-risk orders.
  • Jeopardy reporting: filter JEOPARDY_ENABLED_FLAG = 'Y' and compare CUSTOMER_REQUIRED_DATE against COMPLETION_DATE to identify overdue provisioning.
  • Customer-level history: join on CUSTOMER_ID and ORG_ID to report all orders for a given account, grouping by ORDER_TYPE and ORDER_ACTION.
  • Line detail expansion: join to XDP_OE_ORDER_LINES on ORDER_NUMBER and ORDER_VERSION to produce a full order view.
  • Cross-system reconciliation: match SP_ORDER_NUMBER or SDP_ORDER_ID against the external service-provider or SDP record to confirm the interface completed correctly.

Related Objects

The relationship data documents how the table participates in the provisioning model:

  • XDP_OE_ORDER_LINES — child table; joins on XDP_OE_ORDER_LINES.ORDER_NUMBER = XDP_OE_ORDER_HEADERS.ORDER_NUMBER and ORDER_VERSION = ORDER_VERSION.
  • XDP_OE_ORDER_PARAMETERS — child table carrying order-level parameters; joins on the same ORDER_NUMBER / ORDER_VERSION pair.
  • FND_SECURITY_GROUPS — referenced table; XDP_OE_ORDER_HEADERS.SECURITY_GROUP_ID points to it, enforcing security-group partitioning.

Together these relationships place XDP_OE_ORDER_HEADERS at the centre of the XDP Order Entry Interface data model as the header of a line-and-parameter hierarchy.