Results for “wf_process_activities”

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

Overview

WF_PROCESS_ACTIVITIES is a core Oracle Workflow configuration table owned by the APPLSYS schema and registered under the FND — Application Object Library product family. It stores the definition of every individual activity that participates in a workflow process, effectively acting as the runtime and design-time bridge between process definitions and the activity library. Each row represents one activity instance within a specific process, capturing not only the underlying activity it derives from but also the process-specific behaviour, role assignment, and routing characteristics applied when that activity executes inside a given process.

In Oracle EBS 12.1.1 and 12.2.2 the table is central to the Workflow Engine. Process definitions authored in Oracle Workflow Builder are loaded into this table, and the engine consults it whenever an item transitions through a process. Because it is referenced by transition, status, and attribute-value tables, it functions as a modelling hub rather than a transactional satellite. From a Data Vault perspective, the FK topology suggests classifying WF_PROCESS_ACTIVITIES as a hub, since multiple downstream tables (WF_ACTIVITY_TRANSITIONS, WF_ITEM_ACTIVITY_STATUSES, WF_ACTIVITY_ATTR_VALUES) reference it directly as their parent entity.

Key Information Stored

The table contains 17 documented columns. The most significant for query and integration purposes are:

• INSTANCE_ID — Surrogate primary key, enforced by WF_PROCESS_ACTIVITIES_PK (composed with ZD_EDITION_NAME in 12.2.2 for editioning support).
• INSTANCE_LABEL — Human-readable activity label unique within the process; part of the WF_PROCESS_ACTIVITIES_U2 business-key candidate.
• PROCESS_ITEM_TYPE, PROCESS_NAME, PROCESS_VERSION — Identify the owning process definition; also part of the U2 unique index and the FK to WF_ACTIVITIES.
• ACTIVITY_ITEM_TYPE and ACTIVITY_NAME — Point to the underlying reusable activity definition.
• PERFORM_ROLE and PERFORM_ROLE_TYPE — Define who or what performs the activity at runtime.
• START_END — Indicates whether the activity is a start or end node of the process.
• DEFAULT_RESULT — Supplies the default result code when no result is explicitly set.
• ICON_GEOMETRY, USER_COMMENT — Descriptive and diagramming metadata.
• PROTECT_LEVEL and CUSTOM_LEVEL — Control customisation and upgrade protection.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, scoping visibility.

The distinction between the surrogate PK (INSTANCE_ID) and the business-key candidate (INSTANCE_LABEL, PROCESS_ITEM_TYPE, PROCESS_NAME, PROCESS_VERSION, ZD_EDITION_NAME) is important: joins between EBS internals almost always use INSTANCE_ID, while imports and definition queries typically use the natural key.

Common Use Cases and Queries

Typical scenarios include auditing workflow process definitions, diagnosing stuck items, and reporting on routing structures. A common pattern resolves the process-to-activity relationship:

• Listing all activities for a given process version: SELECT INSTANCE_ID, INSTANCE_LABEL, ACTIVITY_NAME, START_END FROM WF_PROCESS_ACTIVITIES WHERE PROCESS_ITEM_TYPE=:p AND PROCESS_NAME=:n AND PROCESS_VERSION=:v;
• Tracing a running item’s activity history by joining INSTANCE_ID to WF_ITEM_ACTIVITY_STATUSES.PROCESS_ACTIVITY.
• Analysing transitions by joining twice to WF_ACTIVITY_TRANSITIONS on FROM_PROCESS_ACTIVITY and TO_PROCESS_ACTIVITY.
• Retrieving activity-level attribute values via WF_ACTIVITY_ATTR_VALUES.PROCESS_ACTIVITY_ID.

Reporting use cases include identifying customised (CUSTOM_LEVEL) activities ahead of patching, verifying which activities are performed by which role, and locating start/end nodes (START_END) when reconstructing a process flow diagram.

Related Objects

• WF_ACTIVITIES — parent activity definition; joined on PROCESS_ITEM_TYPE, PROCESS_NAME, PROCESS_VERSION.
• WF_ACTIVITY_ATTR_VALUES — attribute values per activity instance; FK PROCESS_ACTIVITY_ID.
• WF_ACTIVITY_TRANSITIONS — routing links; FKs FROM_PROCESS_ACTIVITY and TO_PROCESS_ACTIVITY.
• WF_ITEM_ACTIVITY_STATUSES and WF_ITEM_ACTIVITY_STATUSES_H — runtime and historical status; FK PROCESS_ACTIVITY.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.

Together these objects form the structural backbone of Oracle Workflow process execution, with WF_PROCESS_ACTIVITIES acting as the persistent hub linking definitions, transitions, and runtime statuses.