Search Results wf_name




Overview
Explore in AI Chat

Overview

APPS.CSC_CONDITION_OUTCOMES_V is a reporting and integration view that exposes process definition metadata used by Oracle E-Business Suite's condition and outcome framework. The view presents a unified, decoded representation of the process definitions that can be executed when a business condition is satisfied — whether those definitions are stored procedures, workflow processes, alerts, or scripts. Because it consolidates several distinct executable types into a single, consistently shaped row set, the view serves as a common reference point for Oracle Contracts and related modules that need to resolve the runnable action associated with a given process definition.

The view is owned by the APPS schema and is defined entirely over another view, OKC_PROCESS_DEFS_V, rather than over base tables directly. This layering means CSC_CONDITION_OUTCOMES_V inherits its filtering, joining, and decoding logic from its parent while adding its own decode expressions to normalize the different executable categories. In the Oracle EBS 12.1.1 and 12.2.2 releases, the object is documented as part of the ETRM (Enterprise Transaction and Reference Model) metadata set and is marked Oracle Proprietary, Confidential Information.

Underlying Base Objects

The single documented referenced base object is OKC_PROCESS_DEFS_V (a VIEW). All columns surfaced by CSC_CONDITION_OUTCOMES_V are sourced from that parent view; CSC_CONDITION_OUTCOMES_V adds no joins to independent tables of its own. Its principal contribution is the two DECODE expressions that transform the PDF_TYPE discriminator into human-readable values and into a single EXECUTABLE_NAME accessor. Because the dependency chain terminates at OKC_PROCESS_DEFS_V, any change to the parent view's column list or predicate logic propagates directly to this view.

Key Columns

  • ID — Primary identifier of the process definition row.
  • PDF_TYPE — Discriminator indicating the process definition type: 'PPS' (stored procedure), 'WPS' (workflow process), 'ALERT', or 'SCRIPT'.
  • NAME — Name of the process definition; used directly as the executable name for ALERT and SCRIPT types.
  • EXECUTABLE_NAME — Derived column that resolves to PROCEDURE_NAME for PPS, WF_NAME for WPS, and NAME for ALERT or SCRIPT.
  • PROCESS_DEFINITION_TYPE — Derived column that returns 'PROCEDURE', 'WORK FLOW', or the raw PDF_TYPE value.
  • WF_NAME — Name of the workflow process, populated for 'WPS' definitions. This is the column most relevant to the "wf_name" search.
  • WF_PROCESS_NAME — Additional workflow process identifier associated with the definition.
  • PROCEDURE_NAME and PACKAGE_NAME — PL/SQL procedure and package identifiers for 'PPS' definitions.
  • DESCRIPTION, SHORT_DESCRIPTION, COMMENTS, USAGE, SFWT_FLAG — Descriptive and control attributes.
  • BEGIN_DATE and END_DATE — Effective date range for the process definition.

Common Use Cases and Queries

Typical use cases include enumerating the workflow processes available for condition outcomes, resolving the executable action for a definition, and validating effective-dated definitions. A query to retrieve workflow-based outcomes by name is:

SELECT ID, NAME, WF_NAME, WF_PROCESS_NAME, PROCESS_DEFINITION_TYPE
FROM   APPS.CSC_CONDITION_OUTCOMES_V
WHERE  PDF_TYPE = 'WPS'
AND    WF_NAME IS NOT NULL;

To resolve a unified executable name across all definition types:

SELECT ID, NAME, PDF_TYPE, EXECUTABLE_NAME, PROCESS_DEFINITION_TYPE
FROM   APPS.CSC_CONDITION_OUTCOMES_V
WHERE  SYSDATE BETWEEN BEGIN_DATE AND NVL(END_DATE, SYSDATE);

The view is also used to differentiate workflow-based outcomes from procedure-based ones when integrating condition processing with Oracle Workflow. Because filtering by WF_NAME depends on the parent view, queries should treat CSC_CONDITION_OUTCOMES_V as the supported interface rather than referencing OKC_PROCESS_DEFS_V directly.