Results for “error_process”

4 results




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

Overview

WF_ACTIVITIES is the core definition table for the Oracle Workflow engine, residing in the APPLSYS schema and owned by the FND — Application Object Library product. In Oracle EBS 12.1.1 and 12.2.2, it defines a unit of work that contributes to the accomplishment of a process. Every function, notification, event, and sub-process that can participate in a workflow is registered here as an activity, keyed by the item type to which it belongs. Because the Workflow Engine resolves runtime execution by reading activity definitions from this table, WF_ACTIVITIES effectively acts as the activity catalog for all deployed workflow processes in the E-Business Suite.

From a dimensional modeling perspective, the mined FK structure classifies this object as hub-leaning. It is best modeled as a hub, with the composite business key (ITEM_TYPE, NAME, VERSION) identifying each activity, and the attribute-bearing columns treated as a satellite. This classification is a heuristic suggestion derived from the foreign key topology, not a physical design directive.

Key Information Stored

The table contains 26 documented columns. The most significant are:

  • ITEM_TYPE — the workflow item type (process family) that owns the activity; part of the primary key and a foreign key to WF_ITEM_TYPES.
  • NAME — the activity's internal name, unique within an item type and version.
  • VERSION — the activity version, completing the primary key.
  • TYPE — the activity category (for example, function, notification, process, or event).
  • FUNCTION and FUNCTION_TYPE — the PL/SQL or external function invoked when the activity executes, and its execution style.
  • RESULT_TYPE — the datatype of the activity's result, used for branch resolution.
  • RERUN — controls whether the activity may be re-executed on error or loopback.
  • BEGIN_DATE and END_DATE — the effective window during which the activity definition is active.
  • RUNNABLE_FLAG — indicates whether the activity can be launched directly as a top-level process.
  • MESSAGE and ERROR_PROCESS — the notification message template and the error-handling process invoked on failure.
  • SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS scoping the activity to a security context.
  • CUSTOM_LEVEL and PROTECT_LEVEL — customization and protection access levels governing who may alter the definition.

The surrogate primary key is WF_ACTIVITIES_PK. The documented unique index WF_ACTIVITIES_PK (ITEM_TYPE, NAME, VERSION, ZD_EDITION_NAME) is the business-key candidate, with ZD_EDITION_NAME supporting Online Patching editioning in 12.2.x.

Common Use Cases and Queries

Typical usage focuses on auditing activity definitions, diagnosing workflow failures, and reporting on process configuration. A frequent pattern lists all activities for an item type:

SELECT name, version, type, function, result_type, runnable_flag FROM wf_activities WHERE item_type = :item_type ORDER BY name, version;

To identify all runnable top-level processes, filter on RUNNABLE_FLAG = 'Y'. To find activities with customizations, compare CUSTOM_LEVEL against PROTECT_LEVEL. Error diagnostics frequently join to WF_ITEM_ACTIVITY_STATUSES and WF_NOTIFICATIONS to correlate an activity definition with runtime instances. Reporting queries often join to WF_ITEM_TYPES to resolve the display name of the owning process.

Related Objects