IMPORTANT ARTICLES
====================
Purge Obsolete Workflow Runtime Data concurrent request (FNDWFPR) Is Not Purging Data [ID 752383.1]
A closer examination of the Concurrent Program Purge Obsolete Workflow Runtime Data [ID 337923.1]
Quick Reference: How To Purge Obsolete Workflow Runtime Data For Applications [ID 264191.1]
Obsolete Workflow Runtime Data Is Not Purging All Data [ID 270765.1]
What Tables Does the Workflow Purge Obsolete Data Program (FNDWFPR) Touch? [ID 559996.1])
FAQ on Purging Oracle Workflow Data [ID 277124.1
PURGE CONCURRENT PROGRAM
============================
Purge Obsolete Workflow Runtime Data (FNDWFPR)
1. Item Type:
The item type associates with the obsolete runtime data you want to delete. Leave this parameter null to delete obsolete data for all item types.
2. Item Key:
This is a string generated from the application object's primary key. The string uniquely identifies the item within an item type. Leave this parameter null to purge all items for the specified item type.
3. Age:
This is the minimum age of data to purge specified in days if Persistence Type is set to 'Temporary'. The default is set to 0 (zero).
4. Persistence Type:
Persistence type to be purged, either 'Temporary' or 'Permanent'.
Temporary: the Item will be deleted in 'n' days.
Permanent: the Item will be deleted only when forced.
The default is 'Temporary'.
CHECK IF PROGRAM IS RUNNING OR NOT
===================================
SQL> select CONCURRENT_PROGRAM_ID ,CONCURRENT_PROGRAM_NAME,USER_CONCURRENT_PROGRAM_NAME from apps.fnd_concurrent_programs_vl
2 where CONCURRENT_PROGRAM_NAME like 'FNDWFPR%';
CONCURRENT_PROGRAM_ID CONCURRENT_PROGRAM_NAME
--------------------- ------------------------------
USER_CONCURRENT_PROGRAM_NAME
--------------------------------------------------------------------------------
38089 FNDWFPR
Purge Obsolete Workflow Runtime Data
SQL> select REQUEST_ID,REQUEST_DATE from apps.fnd_concurrent_requests where CONCURRENT_PROGRAM_ID=38089;
no rows selected
IMPORTANT QUERIES
===================
> The main tables of concern when dealing with workflows are WF_ITEM_ACTIVITY_STATUS and WF_ITEM_ATTRIBUTE_VALUES.
> The script bde_wf_data.sql . This queries all data that is considered to be eligible for purging. This is a useful and highly recommended script.
select item_type,activity_status,count(*)
from apps.wf_item_activity_statuses
group by item_type,activity_status;
ITEM_TYP ACTIVITY COUNT(*)
-------- -------- ----------
XXPOAPPR COMPLETE 630786
REQAPPRV COMPLETE 15003440
POAPPRV WAITING 152771
POERROR NOTIFIED 151
PORPOCHA ACTIVE 243
POREQCHA ACTIVE 50
WFERROR ERROR 308
POERROR ERROR 90
AZNF004 COMPLETE 2
OAM_BE COMPLETE 15811
POERROR ACTIVE 241
select item_type,count(*)
from apps.wf_item_attribute_values
group by item_type;
SQL> select count(*) from apps.wf_items;
COUNT(*)
----------
1330499
SQL> select count(*) from apps.WF_ITEM_ATTRIBUTE_VALUES;
COUNT(*)
----------
99101567
SQL> select count(*) from apps.WF_ITEM_ACTIVITY_STATUSES;
COUNT(*)
----------
38406566
SQL> select count(*) from apps.WF_NOTIFICATION_ATTRIBUTES;
COUNT(*)
----------
16804958