Results for “order_num”

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

Overview

CS_KB_WF_FLOW_DETAILS is a Service (CS) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the CS schema and currently reported with a status of VALID. The table stores solution flow details — the ordered, step-by-step definition of the actions that make up a knowledge base solution flow used within Oracle Service's knowledge management and workflow functionality. Where the companion header table defines a flow as a unit, this table holds the constituent steps that drive that flow's execution and presentation.

From a data modeling perspective, the ETRM metadata applies a heuristic Data Vault classification of satellite-leaning. Practically, this indicates that CS_KB_WF_FLOW_DETAILS behaves as a descriptive satellite dependent on a parent flow entity, rather than as an independent hub or an associative link. Each row carries attributes (step ordering, action, effective dates) that describe the state or configuration of its owning flow at a point in time, which is the characteristic shape of a satellite. This classification should be treated as a modeling suggestion, not an authoritative constraint.

Key Information Stored

The table is documented with 14 columns in the 12.2.2 physical schema. The most significant are:

• FLOW_DETAILS_ID — the surrogate primary key, defined by the constraint CS_KB_WF_FLOW_DETAILS_PK. Uniquely identifies each flow step record.
• FLOW_ID — foreign key to CS_KB_WF_FLOWS_B, identifying the parent solution flow that this detail row belongs to. Along with STEP, this is a strong business-key candidate, reflected by the unique index CS_KB_WF_FLOW_DETAILS_U1 on FLOW_ID and STEP.
• STEP — the step identifier or ordinal within the parent flow; combined with FLOW_ID it establishes uniqueness of the sequence element.
• ORDER_NUM — the display or execution sequence of the detail step.
• ACTION — the action or operation performed at this step in the flow.
• GROUP_ID — grouping attribute used to organize related flow detail steps.
• BEGIN_DATE / END_DATE — the effective-dating window controlling when the step is active.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data access and security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO audit columns tracking row creation and modification.

Common Use Cases and Queries

Typical uses include reconstructing a solution flow's step sequence for a knowledge base article, auditing which flows are currently effective, and reporting flow configuration by action or group. Because the table is effective-dated, queries commonly filter on the current date. A representative join retrieves flow steps for a given parent flow:

• SELECT d.FLOW_DETAILS_ID, d.FLOW_ID, d.STEP, d.ORDER_NUM, d.ACTION FROM CS.CS_KB_WF_FLOW_DETAILS d WHERE d.FLOW_ID = :flow_id ORDER BY d.ORDER_NUM;
• Join to the header table to obtain flow context: SELECT f.*, d.STEP, d.ACTION FROM CS_KB_WF_FLOW_DETAILS d, CS_KB_WF_FLOWS_B f WHERE d.FLOW_ID = f.FLOW_ID;
• Effective-dated filtering: WHERE TRUNC(SYSDATE) BETWEEN d.BEGIN_DATE AND NVL(d.END_DATE, SYSDATE);

Concurrent program or workflow diagnostics frequently use the same predicates, since the table drives which actions execute for a flow.

Related Objects

• CS_KB_WF_FLOWS_B — the parent flow header; joined on CS_KB_WF_FLOW_DETAILS.FLOW_ID = CS_KB_WF_FLOWS_B.FLOW_ID.
• CS_KB_SETS_B — references this table via CS_KB_SETS_B.FLOW_DETAILS_ID, linking solution sets to specific flow details.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security and data-access resolution.
• CS_KB_WF_FLOW_DETAILS_PK / _U1 — the primary and unique constraints that enforce row identity and the FLOW_ID+STEP business key.