Search Results workitem_version

Overview

XDP_ORDER_DETAILS_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite. It belongs to the XDP – Provisioning product family, the module responsible for order orchestration and fulfillment across line items, work items, services, and packages. The view consolidates header-level, line-level, and work-item-level provisioning data into a single queryable structure, so that a one-row-per-work-item result set carries its parent order and line context by default. Because the object is a view rather than a table, it exposes no independent storage and is read-only through normal SQL; DML against it is not supported.

Its principal reporting role is to answer fulfillment questions that span all three levels of a provisioning order without requiring the caller to join XDP_ORDER_HEADERS, XDP_ORDER_LINE_ITEMS, XDP_FULFILL_WORKLIST, and XDP_WORKITEMS manually. The view is VALID in the APPS schema under 12.1.1 and 12.2.2 and appears in ETRM documentation for both releases.

Underlying Base Objects

The view text references four base objects, all reached through APPS synonyms: XDP_ORDER_HEADERS (aliased XOH), XDP_ORDER_LINE_ITEMS (aliased XOLI), XDP_FULFILL_WORKLIST (aliased XFWL), and XDP_WORKITEMS (aliased XWI). The grain is work item instance: ORDER_ID, LINE_ITEM_ID, and WORKITEM_INSTANCE_ID together identify each output row. Joins link order headers to line items on ORDER_ID, line items to fulfillment worklist entries on the line item identifier, and worklist rows to work item definitions on WORKITEM_ID.

Order headers supply external order number, order version, status code, provisioning dates, and hold/cancel/resume audit information. Line items contribute line number, line sequence, sequence in package, item and organization identifiers, and line-level status and date tracking. The fulfillment worklist contributes the work item instance, status code, state, and completion date, while XDP_WORKITEMS contributes the work item name, version, and type code.

Key Columns

• ORDER_ID, ORDER_NUMBER, ORDER_VERSION – provisioning order identity and external reference.
• LINE_ITEM_ID, LINE_NUMBER, LINE_ITEM_NAME, LINE_VERSION – line-level identity.
• LINE_SEQUENCE, SEQ_IN_PACKAGE – the line's ordering position and its position within a package, which is the attribute most often searched under the term "line_sequence".
• WORKITEM_INSTANCE_ID, WORKITEM_ID, WORKITEM_NAME, WORKITEM_VERSION, WI_TYPE_CODE – the fulfillment work item instance and its definition.
• ORDER_STATUS_CODE, LINE_STATUS_CODE, WORKITEM_STATUS_CODE, WORKITEM_STATE – status at each level; ORDER_STATE and LINE_STATE are exposed as NULL placeholders.
• ORGANIZATION_ID, INVENTORY_ITEM_ID – inventory context of the line.
• Provisioning, completion, cancel, hold, and resume dates at order, line, and work-item level, including ACTUAL_PROVISIONING_DATE, ORDER_COMPLETION_DATE, LINE_COMPLETION_DATE, and WORKITEM_COMPLETION_DATE.
• DUE_DATE and CUSTOMER_REQUIRED_DATE at both order and line level.

Common Use Cases and Queries

The view is typically used to report fulfillment progress, to trace which work items remain outstanding for a given order line, and to sequence lines for downstream processing. A common pattern filters line items by LINE_SEQUENCE to reconstruct the intended processing order.

SELECT order_number, line_number, line_sequence,
       seq_in_package, workitem_name, workitem_status_code
FROM   apps.xdp_order_details_v
WHERE  order_number = :p_order_number
ORDER  BY line_sequence, seq_in_package;

Another frequent use is aging or status reporting across open work items:

SELECT order_number, line_number, line_status_code,
       workitem_name, workitem_completion_date
FROM   apps.xdp_order_details_v
WHERE  workitem_status_code NOT IN ('COMPLETED','CANCELED')
ORDER  BY order_due_date, line_sequence;

Because the view flattens three levels, consumers must account for row multiplication: an order with many lines and work items returns one row per work item instance, so aggregate functions or DISTINCT are required when order- or line-level counts are needed.