Search Results xdp_oe_order_lines




Overview
Explore in AI Chat

Overview

XDP_OE_ORDER_LINES is a provisioning-module table owned by the XDP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all order line information for orders generated by the Oracle SFM (Service Fulfillment Manager) Order Entry interface. In the provisioning lifecycle, this table acts as the line-level staging and tracking repository between an incoming service order and the downstream provisioning detail records, capturing what line items must be fulfilled, whether provisioning is required, and the scheduling and completion attributes associated with each line.

In Data Vault terms, the documented foreign-key structure suggests a satellite-leaning classification. The table carries a composite business key of ORDER_NUMBER, ORDER_VERSION, and LINE_NUMBER, and it holds descriptive and status attributes that describe order lines over time. It references the parent order through XDP_OE_ORDER_HEADERS and is itself referenced by XDP_OE_ORDER_LINE_DETS. This structure is consistent with a satellite attached to an order hub/link, with XDP_OE_ORDER_LINE_DETS functioning as a dependent child set.

Key Information Stored

The table contains 27 documented columns. The most operationally significant are listed below.

No separate surrogate single-column primary key is documented; the primary key is the composite business key, so ORDER_NUMBER, ORDER_VERSION, and LINE_NUMBER serve both as the uniqueness constraint and the join key to related tables.

Common Use Cases and Queries

Typical usage centers on provisioning status reporting, order line tracking, and scheduling analysis. A common query retrieves all lines for a given order:

  • SELECT ORDER_NUMBER, ORDER_VERSION, LINE_NUMBER, LINE_ITEM_NAME, STATUS FROM XDP_OE_ORDER_LINES WHERE ORDER_NUMBER = :order_number;
  • Lines pending provisioning: filter WHERE PROVISIONING_REQUIRED_FLAG = 'Y' AND COMPLETION_DATE IS NULL.
  • Overdue analysis: compare DUE_DATE or CUSTOMER_REQUIRED_DATE against the current date to surface lines in jeopardy, optionally joined with JEOPARDY_ENABLED_FLAG.
  • Bundled line sequencing: order by BUNDLE_ID, BUNDLE_SEQUENCE, PROVISIONING_SEQUENCE to reconstruct execution order.

Reporting extracts frequently join to XDP_OE_ORDER_HEADERS for customer and order context, and to XDP_OE_ORDER_LINE_DETS for granular provisioning detail. Security-aware queries should filter on SECURITY_GROUP_ID where responsibility-based data access applies.

Related Objects

  • XDP_OE_ORDER_HEADERS — parent order table; join on XDP_OE_ORDER_LINES.ORDER_NUMBER and ORDER_VERSION to XDP_OE_ORDER_HEADERS.
  • XDP_OE_ORDER_LINE_DETS — child detail table; join on ORDER_NUMBER, ORDER_VERSION, and LINE_NUMBER.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for data security.
  • Oracle SFM Order Entry interface — the process that populates this table.
  • Provisioning execution logic — reads STATUS, PROVISIONING_REQUIRED_FLAG, and sequencing columns to drive downstream fulfillment.