Results for “xdp_order_line_items”

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

Overview

XDP.XDP_ORDER_LINE_ITEMS is the core transactional table for order line items within the Oracle E-Business Suite Provisioning module (product code XDP). In the EBS service fulfillment and provisioning flow, an order header represents a customer request, and this table decomposes that request into discrete, provisionable line items. Each row captures a single configurable or simple item being ordered, its lifecycle state, scheduling dates, workflow linkage, and inventory context. The table is central to driving downstream provisioning activities such as service activation, work item generation, and fulfillment tracking.

Based on the foreign key topology documented in the ETRM metadata, this object exhibits hub characteristics in a Data Vault modeling sense: it holds a stable business key (ORDER_ID, LINE_NUMBER) and serves as the integration point for multiple dependent satellites and link tables such as XDP_FULFILL_WORKLIST, XDP_LINE_RELATIONSHIPS, and XDP_ORDER_LINEITEM_DETS. This classification is a heuristic suggestion derived from the FK structure, not a functional declaration.

Key Information Stored

The table contains 70 documented columns. The most operationally significant are:

• LINE_ITEM_ID — Surrogate primary key, enforced by index XDP_ORDER_LINE_ITEMS_PK and unique index XDP_ORDER_LINE_ITEMS_U1. This is the foreign key target for most child tables.
• ORDER_ID and LINE_NUMBER — Constitute the business-key candidate (unique index XDP_ORDER_LINE_ITEMS_U2). Together they identify a line item unambiguously within its order. ORDER_ID references both XDP_ORDER_HEADERS and XDP_ORDER_BUNDLES.
• STATUS_CODE and STATE — Track provisioning lifecycle transitions (e.g., held, canceled, completed).
• PROVISIONING_REQUIRED_FLAG, IS_PACKAGE_FLAG, IS_VIRTUAL_LINE_FLAG — Determine whether and how the line participates in provisioning logic.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — Link the line to MTL_SYSTEM_ITEMS_B, identifying the item and owning inventory organization.
• WORKITEM_ID — Associates the line with a XDP_WORKITEMS record for workflow execution.
• IB_SOURCE_ID and IB_SOURCE — Tie the line to installed base records in CSI_ITEM_INSTANCES and CSI_T_TXN_LINE_DETAILS. This is the join path relevant to the user search on csi_t_txn_line_details.
• SITE_USE_ID — References HZ_CUST_SITE_USES_ALL, identifying the customer site where service is provisioned.
• PROVISIONING_DATE, DUE_DATE, COMPLETION_DATE, and related hold/cancel/resume dates with actor columns — Provide scheduling and SLA tracking.
• WF_ITEM_TYPE and WF_ITEM_KEY — Point to the Oracle Workflow process instance governing the line.
• ERROR_REF_ID — References XDP_DQ_EXCEPTIONS for data quality or provisioning errors.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS for multi-tenant data segregation.
• ATTRIBUTE1 through ATTRIBUTE20 — Descriptive flexfield storage for client-specific extensions.

Common Use Cases and Queries

Typical usage centers on tracking line-level provisioning progress, diagnosing failures, and reconciling installed base changes to orders.

• Line status reporting: Join to XDP_ORDER_HEADERS to report all lines in a given state for a customer order, filtering on STATUS_CODE and DUE_DATE.
• Installed base reconciliation: Join IB_SOURCE_ID to CSI_T_TXN_LINE_DETAILS and CSI_ITEM_INSTANCES to confirm that each provisioned line produced an active instance. This directly addresses searches referencing csi_t_txn_line_details.
• Error triage: Query lines where ERROR_REF_ID is not null and join to XDP_DQ_EXCEPTIONS.
• Fulfillment worklist: Join via LINE_ITEM_ID or the composite (ORDER_ID, LINE_NUMBER) to XDP_FULFILL_WORKLIST.
• Line relationships: Use XDP_LINE_RELATIONSHIPS to identify parent/child or related line item structures through LINE_ITEM_ID and RELATED_LINE_ITEM_ID.
• Item/location analysis: Aggregate by INVENTORY_ITEM_ID and ORGANIZATION_ID joined to MTL_SYSTEM_ITEMS_B to measure provisioning volumes.

Related Objects

The most significant related objects, with their documented join columns, include:

• XDP_ORDER_HEADERS — Joined on ORDER_ID; provides order-level context.
• XDP_ORDER_BUNDLES — Joined on ORDER_ID; groups lines into bundles.
• CSI_ITEM_INSTANCES and CSI_T_TXN_LINE_DETAILS — Joined on IB_SOURCE_ID; installed base and transaction detail linkage.
• MTL_SYSTEM_ITEMS_B — Joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; item master definition.
• HZ_CUST_SITE_USES_ALL — Joined on SITE_USE_ID; customer site identification.
• XDP_WORKITEMS — Joined on WORKITEM_ID; workflow work item execution.
• XDP_FULFILL_WORKLIST — References this table via LINE_ITEM_ID and (ORDER_ID, LINE_NUMBER); drives fulfillment processing.
• XDP_LINE_RELATIONSHIPS — References LINE_ITEM_ID and RELATED_LINE_ITEM_ID; models inter-line dependencies.
• XDP_ORDER_LINEITEM_DETS — References LINE_ITEM_ID; stores supplementary line detail.
• XDP_DQ_EXCEPTIONS and FND_SECURITY_GROUPS — Referenced via ERROR_REF_ID and SECURITY_GROUP_ID respectively.

Documentation confirms physical schema ownership by XDP with 70 columns in release 12.2.2, and the same structural characteristics apply within the 12.1.1 footprint of the Provisioning module.