Results for “process_name”

50+ results




Overview
Explore in AI Chat

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

Overview

The WF_RUNNABLE_PROCESSES_V view is an Oracle E-Business Suite database object owned by the APPS schema and categorized under the FND – Application Object Library product. It exposes the complete set of workflow process definitions that have been flagged as runnable, meaning each row represents a process that the Oracle Workflow engine is permitted to execute at runtime. Because Oracle Workflow underpins approval routing, notifications, and business event handling across 12.1.1 and 12.2.2, this view serves as the authoritative reference for identifying which processes can be launched programmatically through Workflow APIs such as WF_ENGINE.CreateProcess and WF_ENGINE.StartProcess.

Rather than querying the underlying activity definition tables directly, developers and functional analysts use this view to obtain a clean, filtered list of active process definitions. It abstracts the complexity of date-effective and multilingual storage in the base tables, returning only those processes whose effective date range includes the current system date.

Underlying Base Objects

The view is defined over a single documented base object: WF_ACTIVITIES_VL, itself a view in the APPS schema. WF_ACTIVITIES_VL is the translated (VL, or "view with language") representation of workflow activity definitions, combining the language-independent activity data with language-specific display names. The WF_RUNNABLE_PROCESSES_V definition applies three filters against this source:

  • RUNNABLE_FLAG = 'Y' — restricts output to activities explicitly marked runnable.
  • TYPE = 'PROCESS' — excludes other activity types such as functions, notifications, and events, returning only process definitions.
  • SYSDATE BETWEEN BEGIN_DATE AND NVL(END_DATE, SYSDATE) — enforces date-effective validity, treating a null end date as open-ended.

Key Columns

The view projects three columns from the base object:

  • ITEM_TYPE — the internal name of the workflow item type that owns the process. This identifies the business object or functional area (for example, an order or requisition item type) to which the process belongs.
  • PROCESS_NAME — the internal, language-independent name of the runnable process. This is the identifier passed to Workflow engine APIs when launching the process.
  • DISPLAY_NAME — the translated, user-facing label for the process, suitable for presentation in concurrent program parameters, custom forms, or reporting output.

The combination of ITEM_TYPE and PROCESS_NAME forms the logical key used to reference a process in integration code.

Common Use Cases and Queries

Typical uses include validating a process name before invoking Workflow APIs, populating a list of values for a custom concurrent program, and auditing which processes are currently runnable for a given item type. A representative query listing all runnable processes for a specific item type is:

  • SELECT item_type, process_name, display_name FROM wf_runnable_processes_v WHERE item_type = :p_item_type ORDER BY process_name;
  • SELECT item_type, COUNT(*) FROM wf_runnable_processes_v GROUP BY item_type ORDER BY item_type;

Because the view depends on SYSDATE, results reflect only processes valid as of the query execution date, which is important when troubleshooting date-effective changes to workflow definitions.