Results for “actual_provisioning_date”

50+ results




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

Overview

XDP_FULFILL_WORKLIST is a core transactional table in the Oracle EBS Provisioning (XDP) module. It identifies the list of services that must be fulfilled for a given order line, acting as the operational worklist that drives fulfillment orchestration across the provisioning engine. Each row corresponds to a discrete fulfillment workitem instance tied to an order and order line, and it carries the status, state, and lifecycle timestamps that the provisioning framework uses to track progression from creation through completion, hold, cancellation, or resume. The table is owned by the XDP schema and appears as VALID in ETRM 12.2.2, which documents a physical schema of 52 columns.

In Data Vault modeling terms, the FK/PK structure around this table suggests a hub classification. Its WORKITEM_INSTANCE_ID is the subject of numerous inbound foreign keys from satellite-like and link-like tables, positioning it as the central business key anchor for the fulfillment domain. This classification is a heuristic derived from the foreign key topology and should be treated as a modeling suggestion rather than a prescriptive design.

Key Information Stored

The table's surrogate primary key is XDP_FULFILL_WORKLIST_PK on WORKITEM_INSTANCE_ID. A documented unique index, XDP_FULFILL_WORKLIST_U1 on (WORKITEM_INSTANCE_ID, WORKITEM_ID), represents the principal business-key candidate. A second unique constraint, XDP_FULFILL_WORKLIST_UK1, also covers WORKITEM_INSTANCE_ID and WORKITEM_ID. The most operationally significant columns include:

Common Use Cases and Queries

Typical scenarios include monitoring open fulfillment workitems, reporting on order-to-provisioning latency, and diagnosing stuck or failed workitems. A basic status query joins the worklist to its order line items:

  • SELECT w.WORKITEM_INSTANCE_ID, w.ORDER_ID, w.LINE_ITEM_ID, w.STATUS_CODE, w.STATE, w.PROVISIONING_DATE FROM XDP.XDP_FULFILL_WORKLIST w WHERE w.STATUS_CODE = :status;
  • SELECT w.WORKITEM_INSTANCE_ID, w.ERROR_REF_ID FROM XDP.XDP_FULFILL_WORKLIST w WHERE w.ERROR_REF_ID IS NOT NULL;
  • SELECT w.WORKITEM_INSTANCE_ID, w.COMPLETION_DATE - w.PROVISIONING_DATE AS cycle_days FROM XDP.XDP_FULFILL_WORKLIST w WHERE w.COMPLETION_DATE IS NOT NULL;

These patterns support operational dashboards, SLA breach analysis using DUE_DATE and CUSTOMER_REQUIRED_DATE, and exception triage by correlating ERROR_REF_ID with XDP_DQ_EXCEPTIONS.

Related Objects

XDP_FULFILL_WORKLIST is heavily referenced. The most significant related tables, with their join columns, are:

Together these tables form the fulfillment runtime, audit, callback, and timing fabric that surrounds the worklist hub.