Search Results wf_process_activities_uk2
Overview
The WF_PROCESS_ACTIVITIES table is a core repository within the Oracle E-Business Suite (EBS) Workflow engine, residing in the APPLSYS schema. It serves as the master definition table for all activities that constitute a workflow process. This table stores the static, versioned blueprint of a process, defining each step (activity) within it, such as notifications, functions, or sub-processes. Its role is foundational to the Workflow engine's operation, as it provides the structural metadata against which runtime workflow instances are executed and managed. The data in this table is populated during the upload or creation of workflow process definitions via Oracle Workflow Builder or related APIs.
Key Information Stored
The table's structure is designed to uniquely identify and describe each activity within a specific version of a process. The primary key is the system-generated INSTANCE_ID, which serves as the unique internal identifier for the activity definition. A unique key (WF_PROCESS_ACTIVITIES_UK2) enforces business-level uniqueness based on the combination of INSTANCE_LABEL, PROCESS_ITEM_TYPE, PROCESS_NAME, and PROCESS_VERSION. This ensures that within a given process version, each activity has a distinct label. Other critical columns include the PROCESS_ITEM_TYPE, PROCESS_NAME, and PROCESS_VERSION, which link the activity to its parent process definition in the WF_ACTIVITIES table. The table also stores the ACTIVITY_ITEM_TYPE and ACTIVITY_NAME to identify the specific activity definition being used at that step.
Common Use Cases and Queries
This table is central to administrative queries, process analysis, and troubleshooting within Oracle Workflow. Common use cases include auditing process definitions, identifying all activities within a specific process, and diagnosing issues where runtime item activity statuses (WF_ITEM_ACTIVITY_STATUSES) reference an undefined process activity. A typical query retrieves the full activity list for a process:
- SELECT instance_label, activity_item_type, activity_name FROM apps.wf_process_activities WHERE process_item_type = '<ITEM_TYPE>' AND process_name = '<PROCESS_NAME>' AND process_version = '<VERSION>' ORDER BY instance_id;
Another critical pattern involves joining to WF_ACTIVITY_TRANSITIONS to map the process flow or to WF_ACTIVITY_ATTR_VALUES to review default attribute settings for activities within the process definition.
Related Objects
As indicated by its foreign key relationships, WF_PROCESS_ACTIVITIES is a central hub for several key Workflow tables. It is referenced by WF_ACTIVITY_TRANSITIONS (for defining the from/to paths between activities), WF_ACTIVITY_ATTR_VALUES (for storing default attribute values for the activity within this process), and both WF_ITEM_ACTIVITY_STATUSES and its history table, which track the runtime execution state of these defined activities. Crucially, it has a foreign key dependency on WF_ACTIVITIES, which is the master table for all activity definitions, ensuring referential integrity between a process activity and the global activity template it utilizes.
-
Table: WF_PROCESS_ACTIVITIES
12.1.1
owner:APPLSYS, object_type:TABLE, fnd_design_data:FND.WF_PROCESS_ACTIVITIES, object_name:WF_PROCESS_ACTIVITIES, status:VALID, product: FND - Application Object Library , description: Activity data within a process , implementation_dba_data: APPLSYS.WF_PROCESS_ACTIVITIES ,
-
Table: WF_PROCESS_ACTIVITIES
12.2.2
owner:APPLSYS, object_type:TABLE, fnd_design_data:FND.WF_PROCESS_ACTIVITIES, object_name:WF_PROCESS_ACTIVITIES, status:VALID, product: FND - Application Object Library , description: Activity data within a process , implementation_dba_data: APPLSYS.WF_PROCESS_ACTIVITIES ,
-
eTRM - FND Tables and Views
12.2.2
description: No longer used ,
-
eTRM - FND Tables and Views
12.1.1
description: No longer used ,
-
eTRM - FND Tables and Views
12.2.2
description: No longer used ,
-
eTRM - FND Tables and Views
12.1.1
description: No longer used ,