Search Results xdp_worklist_details




Overview
Explore in AI Chat

Overview

The XDP_WORKLIST_DETAILS table is a core data object within the Oracle E-Business Suite Provisioning (XDP) module, specifically for versions 12.1.1 and 12.2.2. It functions as the detailed parameter storage for the fulfillment worklist, which is a central component of the order-to-fulfillment process. This table stores the specific runtime values for parameters associated with individual work items (tasks) that are assigned to agents or systems for execution. Its primary role is to persist the detailed input and output data required for the execution and tracking of each step in a service provisioning workflow, linking high-level worklist entries to their granular execution data.

Key Information Stored

While the full column list is not detailed in the provided metadata, the primary and foreign key relationships define its critical structure. The table is uniquely identified by a composite primary key consisting of WORKITEM_INSTANCE_ID and PARAMETER_NAME. This structure indicates that for each instance of a work item (a specific execution of a task), the table can store multiple named parameters. Key columns include WORKITEM_INSTANCE_ID, which links to the parent worklist entry in XDP_FULFILL_WORKLIST; WORKITEM_ID and PARAMETER_NAME, which together link to the parameter's definition in XDP_WI_PARAMETERS; and columns like TXN_ATTRIB_DETAIL_ID and ATTRIB_SOURCE_ID, which create relationships to the Service Inventory (CSI) module's extended attributes tables (CSI_T_EXTEND_ATTRIBS, CSI_I_EXTENDED_ATTRIBS, CSI_IEA_VALUES). These latter relationships allow the worklist details to be enriched with and linked to specific asset or service instance attributes.

Common Use Cases and Queries

This table is primarily accessed for operational reporting, troubleshooting fulfillment workflows, and data audits. A common use case is generating a detailed report of all parameter values for a specific work item instance or for all work items related to a particular service order. Technical consultants may query it to diagnose why a provisioning step failed by examining the input values passed to it. A typical SQL pattern involves joining to the parent worklist table to provide context.

  • Sample Query: Retrieving all details for a work item instance.
    SELECT wld.* FROM xdp_worklist_details wld WHERE wld.workitem_instance_id = <INSTANCE_ID> ORDER BY wld.parameter_name;
  • Sample Query: Joining to the worklist and parameter definition for a comprehensive view.
    SELECT wl.workitem_instance_id, wl.workitem_id, wld.parameter_name, wld.parameter_value, wip.parameter_data_type FROM xdp_fulfill_worklist wl JOIN xdp_worklist_details wld ON wl.workitem_instance_id = wld.workitem_instance_id JOIN xdp_wi_parameters wip ON wld.workitem_id = wip.workitem_id AND wld.parameter_name = wip.parameter_name WHERE wl.order_number = '<ORDER_NUMBER>';

Related Objects

The XDP_WORKLIST_DETAILS table sits at a critical integration point within the XDP schema and connects to the Service Inventory module. Its documented foreign key relationships are as follows:

  • XDP_FULFILL_WORKLIST: Links via WORKITEM_INSTANCE_ID. This is the primary parent table, providing the worklist header context for the detail records.
  • XDP_WI_PARAMETERS: Links via the composite foreign key (WORKITEM_ID, PARAMETER_NAME). This references the master definition of valid parameters for a given work item type.
  • CSI_T_EXTEND_ATTRIBS (CSI_T_EXTEND_ATTRIBS): Links via TXN_ATTRIB_DETAIL_ID. This connects worklist details to transaction-level extended attributes.
  • CSI_I_EXTENDED_ATTRIBS (CSI_I_EXTENDED_ATTRIBS): Links via ATTRIB_SOURCE_ID. This connects worklist details to instance-level extended attribute definitions.
  • CSI_IEA_VALUES: Links via ATTRIB_SOURCE_ID. This connects worklist details to the actual values stored for instance-level extended attributes.