Search Results process_definition_type

Overview

The CSC_CONDITION_OUTCOMES_V view is an APPS-owned, VALID database object in the Oracle E-Business Suite Customer Care (CSC) module. Its documented purpose is the registration of a PL/SQL process or a workflow with the application for use as an OUTCOME, CONTRACT PROCESS, QA PROCESS, or FUNCTION in a CONDITION LINE. In practical terms, the view serves as a unified catalog of the executable artifacts that the Customer Care condition engine can invoke when evaluating condition lines and associated business rules.

Because it consolidates several heterogeneous process definition types — PL/SQL stored procedures, Oracle Workflow processes, database alerts, and scripts — into a single relational shape, the view plays a central role in reporting, integration, and configuration validation. Downstream reports and interfaces can query one object rather than joining several type-specific sources. The view is especially relevant to users investigating wf_process_name, since the WF_PROCESS_NAME column exposes the workflow process identifier associated with workflow-type (WPS) registrations. This is the column most commonly correlated with the wf_process_name search term and links the condition framework to the Oracle Workflow engine.

Underlying Base Objects

The view is defined over a single documented base object: OKC_PROCESS_DEFS_V, itself a view in the OKC (Contracts Core) schema. The CSC view therefore inherits its data from the contract process definition layer, reflecting the shared infrastructure between Oracle Contracts and Customer Care for process registration. The view text performs a projection of the base columns and derives several calculated columns.

Two DECODE expressions are notable. The EXECUTABLE_NAME column is derived conditionally: for PPS (PL/SQL process) types it returns PROCEDURE_NAME; for WPS (workflow process) types it returns WF_NAME; and for ALERT and SCRIPT types it returns NAME. The PROCESS_DEFINITION_TYPE column translates PDF_TYPE into a human-readable label, mapping PPS to 'PROCEDURE', WPS to 'WORK FLOW', and otherwise passing the raw PDF_TYPE value through. No base tables are directly documented; all derivation occurs above OKC_PROCESS_DEFS_V.

Key Columns

• ID — Primary identifier for the registered process definition.
• PDF_TYPE — The process definition type code (PPS, WPS, ALERT, SCRIPT) driving the conditional derivations.
• NAME — The registered name of the process definition.
• WF_NAME — The workflow name associated with workflow-type registrations.
• WF_PROCESS_NAME — The Oracle Workflow process name; the column targeted by searches for wf_process_name.
• PROCEDURE_NAME and PACKAGE_NAME — The PL/SQL procedure and package invoked for PPS registrations.
• EXECUTABLE_NAME — Derived, type-dependent executable identifier (procedure, workflow, alert, or script).
• PROCESS_DEFINITION_TYPE — Derived, human-readable type ('PROCEDURE', 'WORK FLOW', or raw type).
• USAGE, DESCRIPTION, SHORT_DESCRIPTION, COMMENTS — Descriptive and categorization attributes.
• SFWT_FLAG — Flag column retained from the base definition view.
• BEGIN_DATE and END_DATE — Effective date range for the registration.

Common Use Cases and Queries

Typical scenarios include identifying all workflow-based outcomes attached to condition lines, auditing active versus expired process registrations, and validating that a procedure or workflow referenced by a condition actually exists in the registry. The following query lists workflow processes by name:

SELECT id, name, wf_name, wf_process_name, process_definition_type
FROM csc_condition_outcomes_v
WHERE pdf_type = 'WPS'
AND SYSDATE BETWEEN begin_date AND NVL(end_date, SYSDATE + 1);

To inventory all registered executables regardless of type:

SELECT id, process_definition_type, executable_name, usage, begin_date, end_date
FROM csc_condition_outcomes_v
ORDER BY process_definition_type, executable_name;

These queries support configuration review, migration verification between 12.1.1 and 12.2.2 environments, and troubleshooting of condition lines whose outcome or QA process fails to resolve.