Search Results cs_kb_wf_flow_details




Overview
Explore in AI Chat

Overview

The CS_KB_WF_FLOW_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It functions as the solution flow details table, central to the Knowledge Base (KB) workflow management system. This table stores the individual steps or components that constitute a defined solution workflow. Each workflow (defined in the CS_KB_WF_FLOWS_B table) is comprised of a sequence of detailed steps, which are stored as records in this table. Its primary role is to provide the structural definition for how solution processes are executed, enabling structured troubleshooting, guided resolution, and standardized service delivery.

Key Information Stored

The table's structure is designed to define the sequence and logic of workflow steps. The most critical columns, as indicated by the provided metadata, are:

  • FLOW_DETAILS_ID: The unique primary key identifier for each workflow step record. This column is the target of a foreign key relationship from the CS_KB_SETS_B table.
  • FLOW_ID: A foreign key linking the detail step to its parent workflow definition in the CS_KB_WF_FLOWS_B table. This column is part of a unique key constraint (CS_KB_WF_FLOW_DETAILS_U1).
  • STEP: Defines the order or sequence number of this specific detail within the overall workflow. It works in conjunction with FLOW_ID to ensure step ordering is unique per flow.

While the metadata excerpt does not list all columns, typical columns in such a table would include data to describe the step action (e.g., instruction text, a link to a solution article, a decision point), step type, and conditional logic parameters.

Common Use Cases and Queries

This table is primarily accessed for retrieving and managing the steps of a published solution workflow. A common use case is rendering a guided resolution flow to a service agent within the EBS interface. Reporting use cases include analyzing workflow complexity (step count per flow) or auditing workflow definitions. A fundamental query pattern involves joining to the parent flows table to retrieve a complete workflow definition, ordered by step sequence.

Sample SQL:
SELECT f.FLOW_NAME, fd.STEP, fd.INSTRUCTION_TEXT
FROM CS_KB_WF_FLOWS_B f,
CS_KB_WF_FLOW_DETAILS fd
WHERE f.FLOW_ID = fd.FLOW_ID
AND f.FLOW_ID = :p_flow_id
ORDER BY fd.STEP;

Another critical query involves identifying workflows that reference a specific solution set or article, leveraging the relationship via FLOW_DETAILS_ID.

Related Objects

Based on the documented foreign key relationships, CS_KB_WF_FLOW_DETAILS is integral to two key object relationships:

  • Parent Table (CS_KB_WF_FLOWS_B): The table CS_KB_WF_FLOW_DETAILS references CS_KB_WF_FLOWS_B via the FLOW_ID column. This defines the master-detail relationship where a flow contains many details.
  • Child Table (CS_KB_SETS_B): The table CS_KB_SETS_B references CS_KB_WF_FLOW_DETAILS via the FLOW_DETAILS_ID column. This indicates that specific solution sets or articles are associated with individual steps within a workflow.

These relationships form a chain from the high-level workflow (CS_KB_WF_FLOWS_B) down to its constituent steps (CS_KB_WF_FLOW_DETAILS) and finally to the specific knowledge content (CS_KB_SETS_B) invoked at each step.