Blog Archives

How To Purge E-Mail Notifications From The Workflow Queue So The E-Mail Is Not Sent

  1. Verify the current status of each notifications found in the WF_NOTIFICATIONS table that has potential for being sent when the Java Mailer gets started.

SQL> select notification_id, recipient_role, message_type, message_name, status, mail_status
     from wf_notifications
     where status in (‘OPEN’, ‘CANCELED’)
     And Mail_Status In (‘MAIL’, ‘INVALID’)
     order by notification_id;

Normally, only records where status = ‘OPEN’ and mail_status = ‘MAIL’ are notifications that would be sent, but there are programs that also can retry Canceled or Invalid notifications, so we included these as well.
This query should show which notifications are waiting to be e-mailed.

2) Use BEGIN_DATE in the where clause to help narrow down the emails not to get sent by the Mailer from a specific date range.

For example :

SQL> select notification_id, begin_date, recipient_role, message_type, message_name, status, mail_status
     from wf_notifications
     Where Status In (‘OPEN’, ‘CANCELED’)
     And Mail_Status In (‘MAIL’, ‘INVALID’)
     and begin_date < sysdate-30              — List only emails older than 30 days ago
     order by notification_id;

 3) To update a notification so that it will not get e-mailed, simply set the MAIL_STATUS = ‘SENT’, and rebuild the Mailer queue using wfntfqup.sql
The mailer will think the e-mail has already been sent and it will not send it again.
Note : Users can still reply to all these notifications from the worklist page in the applications.


SQL> update WF_NOTIFICATIONS set mail_status = ‘SENT’ where mail_status in (‘MAIL’,’INVALID’)
     and Status In (‘OPEN’, ‘CANCELED’);

(Remember to include any other filters you want like begin_date < sysdate-30)

This will update all notifications waiting to be sent by the mailer to SENT, and therefore will not get emailed when the Mailer is restarted.

4) Run the script $FND_TOP/patch/115/sql/wfntfqup.sql to purge the WF_NOTIFICATION_OUT queue and rebuild it with data currently in the WF_NOTIFICATIONS table. This is what purges all notifications waiting in the queue to be sent.  It will then populate the queue with the current data in the wf_notifications table.
Since you have changed the mail_status = ‘SENT” it will not enqueue these messages again.. Only the ones where mail_status = ‘MAIL’ and status = ‘OPEN’ will be placed in the WF_NOTIFICATION_OUT queue and sent by the mailer. (or CANCELED and INVALID if certain concurrent reports are run)


$ sqlplus apps/apps@db @$FND_TOP/patch/115/sql/wfntfqup.sql apps apps applsys

5) Now start the Workflow Java Mailer.

Reference : MOS Doc ID 372933.1


Oracle Apps Purge Log/Out Commands

Following command will help you in regular purging of log and out files in Oracle EBS R12

1. Report cache logs: Retention period 5days
/usr/bin/find $LOG_HOME/ora/10.1.2/reports/cache/ -mtime +5 -exec rm  {} \;

2. Apache logs: Retention period 7days
/usr/bin/find $LOG_HOME/ora/10.1.3/Apache/ -mtime +7 -exec rm  {} \;

3. Concurrent manager log files : Retention period 30days
/usr/bin/find $LOG_HOME/appl/conc/log/ -mtime +30 -exec rm  {} \;

4. Concurrent manager out files : Retention period 30days
/usr/bin/find $LOG_HOME/appl/conc/out/ -mtime +30 -exec rm  {} \;

5. Appltmp logs: Retention period 30days
/usr/bin/find $APPLTMP/ -mtime +30 -exec rm  {} \;

6. Opmn logs: Retention period 7days
/usr/bin/find $LOG_HOME/ora/10.1.3/opmn/ -mtime +7 -exec rm  {} \;


You can also run the below concurrent request from Sysadmin responsibility:

Purge Concurrent Request and/or Manager Data Program