Troubleshoot Workflow Errors 

Troubleshoot Workflow Errors



Error:

-

ORA

-

20002: 3207: User 'SYSADMIN' does not have access to notification

 1621941 . ORA

-

06512: at "APPS.WF_ADVANCED_WORKLIST", line 82 ORA

-

06512: at line 1

There are two methods to resolve this perticular issue.

First M

ethod:

1. Login to E

-

Business as the user who will modify the Workflow System

Administrator and navigate as follows:

Workflow Administrator Web Applications > Administration

Then select either the SYSADMIN user or the Workflow Administrator Web

Applicatio

ns responsibility as the Workflow System Administrator.

Please Note: We can get the responsibility/role from backend by issuing the below

sql statement WF_ADMIN_ROLE.

select text from wf_resources where name='WF_ADMIN_ROLE';

If output of above query is n

ot ‘SYSADMIN’ or ‘Workflow Administrator Web

Applications’ responsibility then we will get the issue. Therefore update the table as

per the requirement,as shown below.

update wf_resources set text='*' where name='WF_ADMIN_ROLE';

commit:

2. Now send one m

ore notification and verify that that the issue has been

resolved.

Second Method:

1. Login to E

-

Business as the user who can modify the Workflow System

Administrator and navigate:

Workflow Administrator Web Applications > Administration

Then select use

r or responsibility as the Workflow System Administrator.

Author

–

A.Kishore/Sachin

http://appsdba.info

2

2.

Change the Workflow Mailer Framework User parameter from

FND_USER.USER_ID = 0 to the USER_ID of the Workflow System Administrator

user or to a user that is assigned as Workflow System Administr

ator.



Obtain the FND_USER.USER_ID:

select user_id, user_name from fnd_user where

user_name=upper('');



Run $FND_TOP/sql/afsvcpup.sql to change the Framework User

parameter under the Workflow Notification Mailer Component ID

to the selected user_id.



Sh

utdown and restart the Workflow Mailer Service.

3. Now send one more notification and verify that the issue has been resolved.



Notification Mailer Fails to Send Email Notifications after cloning.

After cloning, mails are not floating through workflow m

ailer, even all agent listener

and notification mailer are up and running.

Some times we may get the following error after cloning,we check mailer log file

FNDCPGSCXXXXX.txt at $APPLCSF/$APPLLOG.

Below error was their in logs:

-

'Problem obtaining the HTML

content oracle.apps.fnd.wf.common.HTTPClientException: Unable to

invoke method HTTPClient.HTTPConnection.Get caused by: java.net.ConnectException: Connection

refused'

Solution:

-

Solution is to purge the wf_notification_out outbound message queue and

repo

pulates from the WF_NOTIFICATION table.Please follow the below steps to fix

the issue.

1. Stop the Workflow mailer.

2. Purge the wf_notification_out queue and recreate it out of the wf_notifications

table by executing:

cd $FND_TOP/patch/115/sql

sqlplus A

PPS/ @wfntfqup.sql APPS APPLSYS

3. Start the mailer

4. Verify the issue by re

-

submitting the same workflow again