5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

TEST workflow mailer after clone Fnd_User , per_all_people_f and

wf_local_roles

Set serveroutput on

UPDATE fnd_svc_comp_param_vals fscpv

SET fscpv.parameter_value = 'dummyemail@test.com'
WHERE fscpv.parameter_id
IN (SELECT fscpt.parameter_id
FROM fnd_svc_comp_params_tl fscpt
WHERE fscpt.display_name = 'Test Address')
/
Commit
/

UPDATE per_all_people_f
SET email_address = 'dummy@test.com'
WHERE email_address IS NOT NULL;

UPDATE fnd_user
SET email_address = 'dummy@test.com'
WHERE user_name NOT IN
('ANONYMOUS',
'AUTOINSTALL',
'INITIAL SETUP',
'FEEDER SYSTEM',
'CONCURRENT MANAGER',
'STANDALONE BATCH PROCESS')
AND email_address IS NOT NULL;
/
Commit:
/

UPDATE jtf_rs_resource_extns
SET source_email = 'dummy@test.com'
WHERE source_email IS NOT NULL;

update wf_local_roles
set notification_preference='QUERY'
where orig_system in ('FND_USR','PER')
and name NOT IN ('Xuser1','Xuse2')

update fnd_user_preferences
set preference_value='QUERY'
where preference_name='MAILTYPE' and module_name='WF'
and user_name not in ('-WF_DEFAULT-',
'Xuser1','Xuser2')

update wf_local_roles
set notification_preference='QUERY'

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 1/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

where orig_system in ('FND_USR','PER');

update fnd_user_preferences
set preference_value='MAILHTML'
where preference_name='MAILTYPE' and module_name='WF'
and user_name <> '-WF_DEFAULT-';

UPDATE wf_local_roles
SET email_address = 'dummy@test.com'
WHERE email_address IS NOT NULL
AND (ORIG_SYSTEM = 'PER' OR ORIG_SYSTEM = 'PER_ROLE');

/
Commit:
/

update WF_NOTIFICATIONS set mail_status = 'SENT' where mail_status in('MAIL',null);

update wf_notifications
set mail_status = 'SENT'
where end_date is not null
and status = 'CLOSED'
and MAIL_STATUS = 'MAIL';

Posted 31st January 2017 by Unknown

3 View comments

Blogger 16 November 2017 at 12:00

BlueHost is the best hosting company for any hosting plans you might need.
Reply

TxSolve Solutions for Oracle Consultants 19 May 2018 at 10:10

PLSQL code profiler is an Android App, Useful Code Review solution for Oracle consultants. please it
checkout in google play store :

https://play.google.com/store/apps/details?id=appinventor.ai_pshreedhar.PLSQL_Review1

and also check out the solution demo in Youtube

https://youtu.be/Wckm1_s9Y0M?list=PLqfoPI5nmJaNJNleopCOYh3rqX-8zraqU
Reply

Jennifer N 12 February 2019 at 16:02

Thanks and Regards. Oracle Apps R12 Training Videos at affordable cost. please
check oracleappstechnical.com
Reply

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 2/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Workflow Notification Mailer and scripts

WORKFLOW
Purge WF_NOTIFICATION_OUT queue
cd $FND_TOP/patch/115/sql
sqlplus apps/ @wfntfqup.sql APPS (appspwd) APPLSYS
e.g sqlplus apps/apps @wfntfqup.sql APPS apps APPLSYS

This purges the WF_NOTIFICATION_OUT queue and rebuilds 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.
Only notifications with mail_status = 'MAIL' and status = 'OPEN' will be re-enqueued in the
WF_NOTIFICATION_OUT queue and sent by the mailer.

Workflow TEST Address Update

sqlplus apps/ @$FND_TOP/sql/afsvcpup.sql

Enter Component Id: 10006

Enter the Comp Param Id to update : 10093

Enter a value for the parameter : WFdevUsers@abc.com

Setup Test address/override address for WF

Below is the script to update the override address from backend. You do not need the verification code to
set the override address using the below script

update fnd_svc_comp_param_vals
set parameter_value = '&EnterEmailID'
where parameter_id =
( select parameter_id
from fnd_svc_comp_params_tl
where display_name = 'Test Address'
);

Workflow From Address Update :

sqlplus apps/ @$FND_TOP/sql/afsvcpup.sql

Enter Component Id: 10006

Enter the Comp Param Id to update : 10065

Enter a value for the parameter : Lenovo DEV Workflow Mailer"

set overriding address:

update FND_SVC_COMP_PARAM_VALS
set parameter_value = 'Configuration.Workflows@abc.com'
where PARAMETER_ID = 10057;

Scipt to see workflow configuration

SQL> select p.parameter_id,p.parameter_name,v.parameter_value value
from fnd_svc_comp_param_vals_v v,
fnd_svc_comp_params_b p,
fnd_svc_components c
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in
('OUTBOUND_SERVER', 'INBOUND_SERVER',
'ACCOUNT', 'FROM', 'NODENAME', 'REPLYTO','DISCARD' ,'PROCESS','INBOX')
order by p.parameter_name;

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 3/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

SQL to monitor (check status) of Workflow Notification Mailer (Java)

SELECT COMPONENT_STATUS from APPS.FND_SVC_COMPONENTS where

COMPONENT_ID=10006;

sqlplus -s system/${PASSWD}@${ORACLE_SID} << SQLEND >${script}/apps/wf_status.out

set linesize 90
col COMPONENT_NAME format a50
col COMPONENT_status format a20
spool ${script}/apps/wf_status.lst
select COMPONENT_ID,COMPONENT_NAME,COMPONENT_STATUS from apps.fnd_svc_components
where COMPONENT_ID not in (10000,10001,10020,10021,10022) and COMPONENT_STATUS <>
'RUNNING';

select mail_status, count(*) from apps.wf_notifications

where status = 'OPEN'
and mail_status in ('MAIL','ERROR')
group by mail_status;
spool off"

To see error message for a workflow notification

SQL> select ERROR_MESSAGE from wf_item_activity_statuses_v WHERE NOTIFICATION_ID =
7377659;

Here are steps/events for Oracle Workflow Notification Outbound Processing(eMail from Oracle
Applications Workflow to Users)

1.When workflow Engine determines that a notification message must be sent, it raises an event in BES
(Business Event System) oracle.apps.wf.notifications.send
Event is raised with Notification ID (NID) as event key
2. There is seeded subscription to this Event
3. Event is placed on WF_DEFERRED agent
4.Event is dequeued from WF_DEFERRED and subscription is processed
5. Subscription places event message to WF_NOTIFICATION_OUT agent.
6.Notification Mailer dequeues message from WF_NOTIFICATION_OUT agent and
6.1convert XML representation of notification into MIME encoded message (Multi-purpose Internet Mail
Extensions) and
6.2 Send message by SMTP (Simple Mail Transfer Protocol) to intended user (If Test Address/Override
Address is set then email is sent to Test Address

E-Mail Notification is sent if all below conditions are true

a) Notification status is OPEN or CANCELED and
b) Notification mail_status is MAIL or INVALID and
c) Recipient Role has a valid e-mail address and Notification Preference is in the format MAIL%
d) Workflow Deferred Agent Listener is running
e) Workflow Notification Mailer is running

To check a) & b) run below query

SELECT status, mail_status FROM wf_notifications WHERE notification_id = ‘&NID’;

mail_status >> SENT means mail has gone out of mailer to user

To check c) run below query

SELECT email_address, nvl(WF_PREF.get_pref(name, ‘MAILTYPE’),notification_preference)
FROM wf_roles
WHERE name = upper(’&recipient_role’);

To check d) & e) Use OAM (Oracle Application Manager)

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 4/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Workflow version embedded in 11i

************************
Run following SQL from apps user ;
SQL>select TEXT from WF_RESOURCES where NAME='WF_VERSION';

You should see output like

TEXT
-----------------------
2.6.0
Which means you are on Workflow Version 2.6.0

You can also use script wfver.sql in FND_TOP/sql to find version of workflow in Apps.

To Configure Workflow Notification Mailer need below information

PARAMETER_NAME VALUE
------------------------------ ------------------------------
Inbound Server Name wfmailer.abc.com
Username wftst
Password oracle
Outbound Server Name wfmailer.abc.com
Reply-to Address wftst@abc.com

Taking a backup of the workflow configuration

cd $HOME/
sqlplus “/ as sysdba”
spool wf_mailer.log
set lines 130
set pages 200
col value format a30
select p.parameter_id,p.parameter_name,v.parameter_value value
from apps.fnd_svc_comp_param_vals_v v,
apps.fnd_svc_comp_params_b p,
apps.fnd_svc_components c
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in
('OUTBOUND_SERVER', 'INBOUND_SERVER',
'ACCOUNT', 'FROM', 'NODENAME', 'REPLYTO','DISCARD' ,'PROCESS','INBOX')
order by p.parameter_name;

To schdule Gather schema stats and purge workflow runtime data

Login into application as sysadmin and schedule below Requests.

Gather Schema Statistics (ALL , 20% , degree 6 ) to run every SUN and WED
Workflow Background Process to run every 10 mts and Apply the interval as :From the completion of the
prior run
Purge Obsolete Workflow Runtime data - Every week
Workflow Control Queue Cleanup - Every 12 hours

To update WF notification status

IMPORTANT STEP ! Connect to SQL*PLUS as APPS user and do the following steps
update applsys.wf_notifications
set status ='CLOSED', mail_status ='SENT', end_date ='01-JAN-01'
where mail_status='MAIL';
update wf_notifications set status=’CLOSED’;
commit;"
Select distinct status from wf_notification" this should return only one value CLOSED.
or simple do
update wf_notifications set status = 'CLOSED', mail_status = 'SENT';
madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 5/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

commit;

Update workflow a/c pwd from backend

set define off
update APPLSYS.FND_SVC_COMP_PARAM_VALS set PARAMETER_VALUE=
'_@#0@##^90@#!4^86#!$^68$#9$4#@@$6!!!9#0@`$B9+}*0&9&@0&8#|'
where
PARAMETER_ID=
( select parameter_id from APPLSYS.FND_SVC_COMP_PARAMS_B where parameter_name =
'INBOUND_PASSWORD');

To check WF mail status

select count(*), mail_status
from wf_notifications
where begin_date > sysdate - 1
group by mail_status;

There are 141 messages with status `MAIL¿, this status should remain very short and then progress to
status `SENT¿.
: OAM Login > Site Map > Workflow > Service Components.
These same detail are also given in the output from script $FND_TOP/sql/wfver.sql

To check the WF status from backend

check the status of Agent Listeners:

set pagesize 400

set linesize 120
set pagesize 50
column COMPONENT_NAME format a45
column STARTUP_MODE format a15
column COMPONENT_STATUS format a15
select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS
from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc
where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;

Typical output from this

COMPONENT_NAME STARTUP_MODE COMPONENT_STATU

--------------------------------------------- --------------- ---------------
WF_JMS_IN Listener(M4U) AUTOMATIC RUNNING
Workflow Deferred Agent Listener AUTOMATIC RUNNING
Workflow Deferred Notification Agent Listener AUTOMATIC RUNNING
Workflow Error Agent Listener AUTOMATIC RUNNING
Workflow Inbound Notifications Agent Listener AUTOMATIC RUNNING
Workflow Java Deferred Agent Listener AUTOMATIC RUNNING
Workflow Java Error Agent Listener AUTOMATIC RUNNING
Workflow Notification Mailer AUTOMATIC RUNNING
ECX Inbound Agent Listener MANUAL STOPPED
ECX Transaction Agent Listener MANUAL STOPPED
Web Services IN Agent MANUAL STOPPED
Web Services OUT Agent MANUAL STOPPED
Workflow Inbound JMS Agent Listener MANUAL STOPPED

13 rows selected.

Steps to start/stop notification mailer

1.a Check workflow mailer service current status

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 6/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

sqlplus apps/

select running_processes
from fnd_concurrent_queues
where concurrent_queue_name = 'WFMLRSVC';

Number of running processes should be greater than 0

1.b Find current mailer status

sqlplus apps/

select component_status
from fnd_svc_components
where component_id =
(select component_id
from fnd_svc_components
where component_name = 'Workflow Notification Mailer');

Possible values:
RUNNING
STARTING
STOPPED_ERROR
DEACTIVATED_USER
DEACTIVATED_SYSTEM

2. Stop notification mailer

sqlplus apps/

declare
p_retcode number;
p_errbuf varchar2(100);
m_mailerid fnd_svc_components.component_id%TYPE;
begin
-- Find mailer Id
-----------------
select component_id
into m_mailerid
from fnd_svc_components
where component_name = 'Workflow Notification Mailer';
--------------
-- Stop Mailer
--------------
fnd_svc_component.stop_component(m_mailerid, p_retcode, p_errbuf);
commit;
end;
/

3. Start notification mailer

sqlplus apps/

declare
p_retcode number;
p_errbuf varchar2(100);
m_mailerid fnd_svc_components.component_id%TYPE;
begin
-- Find mailer Id
-----------------
select component_id
into m_mailerid
from fnd_svc_components
where component_name = 'Workflow Notification Mailer';
--------------
-- Start Mailer
--------------
madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 7/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

fnd_svc_component.start_component(m_mailerid, p_retcode, p_errbuf);

commit;
end;
/

TO configure workflow
Workflow Mailer Notification settings.
Log on to OAM
Click on Workflow Administrator -> Business Event Local System
Change VIS.ABC.COM to PROD.ABC.COM

Click on Workflow Manager ->Notification Mailer -> Workflow Notification Mailer -> Edit
Edit outbound Email Account (SMTP) -> Server Name =Concurrent Tier
IMAP Server -> Server Name = xxx.xxx.x.xx
Username/password: wfvis/xxxxx :
Reply-To Address: wfvis@abc.com

Click on Advance -> Next->Next

Under General Tab
Mailer Node =WFVIS
Under IMAP: Enter server IP address, username and password of wfvis
Under Outbound Email Account
Outbound Server Name= concurrent tier
Click Next –>Next….Save and Apply

Workflow Version with Apps

Connect to Database as apps user
SQL> select TEXT Version from WF_RESOURCES where NAME = ‘WF_VERSION’;
Output like 2.6.0 means workflow version 2.6.0

Workflow logfile location

$APPLCSF/$APPLLOG with filename like FNDCPGSC[pid].txt

After executing autoconfig make sure Workflow System Administrator is NOT set to SYSADMIN .
Please set this to ""Workflow Administrator Web (New)""
Following script will take care of this .

sqlplus apps/""pwd""
SQL> update wf_resources set text = 'FND_RESP|FND|FNDWF_ADMIN_WEB_NEW|STANDARD' where
name = 'WF_ADMIN_ROLE';

1 row updated.

SQL> commit;

Commit complete.

or xml changes can be done link this.

$ grep -i s_wf_admin_role PROD_mdsxaorit.xml
username
oa_var=""s_wf_admin_role"">FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD

To set the Workflow Administrator from Sys Admin to Workflow Administrator

Navigate to Responsibility -- Workflow Administarator
then Administrator Workflow -- Administration

On top we will find Workflow Configuration :

Workflow System Administrator :: This value we need to change to Workflow Administrator

Or we can update from backend

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 8/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Update wf_resources set text='FND_RESP|FND|FNDWF_ADMIN|STANDARD' where name =

'WF_ADMIN_ROLE';

Or can be set in xml,

grep -i s_wf_admin_role TRAIN2_vcosxaor09.xml username
oa_var=""s_wf_admin_role"">FND_RESP|FND|FNDWF_ADMIN|STANDARD

modify this profile option to have the value of an actual App Server
WF: Workflow Mailer Framework Web Agent : http://hostname.domainname:8000

Make sure following parameters are set for Workflow :

As system administrator –
Oracle Applications Manager
Workflow Manager

Inbound Server Name wfmailer.domain.com

Outbound Server Name wfmailer.domain.com
From The lenovo PROD Workflow Mailer
Reply-to Address wfvis@domain.com

Workflow smtp port 25 and imap port 143

[root@hostname]# telnet wfmailer 143

additonal notes

Steps to start/stop notification mailer

1. Check workflow mailer service current status

sqlplus apps/<apps password>

select running_processes
from apps.fnd_concurrent_queues
where concurrent_queue_name = 'WFMLRSVC';

Number of running processes should be greater than 0

2. Find current mailer status

sqlplus apps/<apps password>

select component_status
from apps.fnd_svc_components
where component_id =
(select component_id
from apps.fnd_svc_components
where component_name = 'Workflow Notification Mailer');

Possible values:
RUNNING
STARTING
STOPPED_ERROR
DEACTIVATED_USER
DEACTIVATED_SYSTEM

2. Stop notification mailer

sqlplus apps/<apps password>
declare
p_retcode number;
p_errbuf varchar2(100);
m_mailerid fnd_svc_components.component_id%TYPE;
begin
-- Find mailer Id
madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 9/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

-----------------
select component_id
into m_mailerid
from fnd_svc_components
where component_name = 'Workflow Notification Mailer';
--------------
-- Stop Mailer
--------------
fnd_svc_component.stop_component(m_mailerid, p_retcode, p_errbuf);
commit;
end;
/

3. Start notification mailer

sqlplus apps/<apps password>

declare
p_retcode number;
p_errbuf varchar2(100);
m_mailerid fnd_svc_components.component_id%TYPE;
begin
-- Find mailer Id
-----------------
select component_id
into m_mailerid
from fnd_svc_components
where component_name = 'Workflow Notification Mailer';
--------------
-- Start Mailer
--------------
fnd_svc_component.start_component(m_mailerid, p_retcode, p_errbuf);
commit;
end;
/

A workflow notification send event (notification email) can fail at several different points, so monitoring it
using one method usually is not going to give you a complete picture.Additionally, you have to keep in
mind that the process is dynamic, meaning that as transactions are created into the queues they are also
mailed out; so a
count of data is at best only a snapshot of a particular moment in time.
1. Here is a more robust script for monitoring the wf_notifications table:
select message_type, mail_status, count(*) from wf_notifications
where status = 'OPEN'
GROUP BY MESSAGE_TYPE, MAIL_STATUS
messages in 'FAILED' status can be resent using the concurrent request 'resend failed workflow
notificaitons'
messages which are OPEN but where mail_status is null have a missing email address for the recipient,
but the notification preference is 'send me mail'
2. Some messages like alerts don't get a record in wf_notifications table so you have to watch the
WF_NOTIFICATION_OUT queue.

select corr_id, retry_count, msg_state, count(*)

from applsys.aq$wf_notification_out
group by corr_id, msg_state, retry_count
order by count(*) desc;
Messages with a high retry count have been cycling through the queue and are not passed to smtp
service.Messages which are 'expired' can be rebuilt using the wfntfqup.sql

1.Please provide the below query output in excel sheet.

select * from fnd_nodes;
2.Please provide the screen shot of below profile option value.
WF: Workflow Mailer Framework Web Agent
madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 10/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

1. The uploaded file “ATGSuppJavaMailerSetup12_9392180_diag.txt” shows that the correct parameter

was not used when attempting to run. For instance “‘R-ex-hub01.internal.kfshrc.edu.sa’” was used for
“Inbound mail server (INBOUND_SERVER)” and on the other hand the file “wfmlrdbg23569786.html”
shows the INBOUND_SERVER is “appforms3.kfshrc.edu.sa”. For that reason the test failed and “Server
{R-ex-hub01.internal.kfshrc.edu.sa} at port {143} is not reachable” was generated.
Please do the following this.
a. Please un the following SQL to collect necessary info before executing
“ATGSuppJavaMailerSetup12.sh”. The SQL will collect all the info required to run the script except IMAP
account password.
select p.parameter_id,
p.parameter_name,
v.parameter_value value
from fnd_svc_comp_param_vals_v v,
fnd_svc_comp_params_b p,
fnd_svc_components c
where c.component_type = ‘WF_MAILER’
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in (‘OUTBOUND_SERVER’, ‘INBOUND_SERVER’,
‘ACCOUNT’, ‘FROM’, ‘NODENAME’, ‘REPLYTO’,'DISCARD’ ,’PROCESS’,'INBOX’)
b. Then run “ATGSuppJavaMailerSetup12.sh” per the steps from 748421.1.
3. Please upload the new output to help us collect the data to help us troubleshoot the issue.
4. Please also upload the Autoconfig log files
a. Database Tier Autoconfig log :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/NetServiceHandler.log
b. Application Tier Autoconfig log -
$INST_TOP/apps/$CONTEXT_NAME/admin/log/<MMDDHHMM>/adconfig.log
5. Restart the Workflow Mailer and Agent Listener services
a. From Self Service > Select “Workflow Manager” under “Oracle Applications Manager” > Click
“Notification Mailers” > Service Components (Service Components: <SID>) >
b. Click “Workflow Mailer Service” under “Container” Column.
e. From “Service Instances for Generic Service Component Container:<SID>”page, click “Pull Down”
button from the Start All/ Stop All.
f . Select Stop All > Go.
g. We conformed that for the Services to read Actual 0 Target 0 and Deactivated.
h. Restart the mailer services using the “Start All” button.
I. We run the following SQL to make sure service are stopped.
SELECT component_name, component_status, component_status_info
FROM fnd_svc_components_v
WHERE component_name like ‘Workflow%’;
6.However all the services are sill down (Stopped).
STATEMENT level logging is already enabled.
7.About to upload the log files from $APPLCSF/$APPLLOG/FNDCPGSC*.txt i.e. the log file for the Active
process for Workflow Mailer Service and Agent Listener services.
To retrieve the last 2 log files for Workflow Mailer and Agent Listener services, run the following command:
ls -lt $APPLCSF/$APPLLOG/FNDCPGSC*.txt
8. The issue started yesterday after running Autoconfig to correct Discoverer issue per Oracle Support.
I might request Autoconfig logs after reviewing the mailer log..
1. Please run the script $FND_TOP/sql/afsvcpup.sql, and edit Notification Mailer , and change the
parameter Framework URL Timeout from 30 to 120.
2. Use the same script to change mailer’s parameter Log Level to 1.
3. Set the profile option WF: Workflow Mailer Framework Web Agent to a physical web tier, using the
syntax http://WEBHOST:port
4. Bounce the mailer.
5. Please follow the navigation below:
a. Workflow Administrator web Applications Responsibility
b. Workflow Manager
c. Click on the Notification Mailers icon
d. Click on Workflow Notification Mailers link
e. Click on Test Mailer button
Enter the user name of the user with the problem, and verify if a test mail is received.
Then, please provide the output of the script wfmlrdbg.sql using the steps from note 1364300.1 for the id’s
returned from the following two queries:
madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 11/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

select max(notification_id)
from wf_notifications
where message_type=’WFTESTS’
and message_name =’OAFWK_MSG’
. Then, provide the mailer log returned by the following query:
SELECT fcp.logfile_name
FROM fnd_concurrent_queues fcq, fnd_concurrent_processes fcp, fnd_lookups flkup
WHERE concurrent_queue_name in (‘WFMLRSVC’)
AND fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND fcq.application_id = fcp.queue_application_id
AND flkup.lookup_code=fcp.process_status_code
AND lookup_type =’CP_PROCESS_STATUS_CODE’
AND meaning=’Active’
Please run the diagnostics from Note 748421.1 Oracle Workflow ATG Support: R12 Java Mailer Setup
Diagnostic Test and upload its archive file.
How does workflow Notification Mailer IMAP (Inbound Processing) Works:
This is the inbound flow:
1. Approver sends email response which is directed to the value defined in Replyto address.
a. This address has been setup by the customer’s mail administrator to route incoming mail to the IMAP
Inbox folder.
2. The Workflow Inbound Agent Listener picks up the message. Only messages which are in ‘unread’ state
are evaluated; the rest of the messages in the inbox are ignored.
3. The message is scanned to see if it matches entries in the TAG file . Mail tags are defined in the OAM
mailer configuration pages and these list strings of text and actions to take if those strings are
encountered. An example of this are ‘Out of Office’ replies. If the string of the message matches a mail tag
and the action is ‘Ignore’ then nothing else will happen.
4. The message is then scanned for the presence of a Notification Id (NID). This NID is matched against
valid NID for the mailer node.
5. If valid NID is not detected, (and there is no matching TAG file entry) then the message is placed into the
DISCARD folder.
6. If a valid NID is detected the listener raises a subscription to the WF_NOTIFICATION_IN queue and
places the mail message in the Processed folder.
7. From this point on the message is handled by the product workflow (like PO APPROVAL) . An event
created by that group will monitor the WF_NOTIFICATION_IN queue and will trigger the rest of the
approval workflow.
Here are steps/events for Oracle Workflow Notification Outbound Processing(eMail from Oracle
Applications Workflow to Users)
1.When workflow Engine determines that a notification message must be sent, it raises an event in BES
(Business Event System) oracle.apps.wf.notifications.send
Event is raised with Notification ID (NID) as event key
2. There is seeded subscription to this Event
3. Event is placed on WF_DEFERRED agent
4.Event is dequeued from WF_DEFERRED and subscription is processed
5. Subscription places event message to WF_NOTIFICATION_OUT agent.
6.Notification Mailer dequeues message from WF_NOTIFICATION_OUT agent and
6.1convert XML representation of notification into MIME encoded message (Multi-purpose Internet Mail
Extensions) and
6.2 Send message by SMTP (Simple Mail Transfer Protocol) to intended user (IfTest Address/Override
Address is set then email is sent to Test Address

E-Mail Notification is sent if all below conditions are truea) Notification status is OPEN or CANCELED and
b) Notification mail_status is MAIL or INVALID and
c) Recipient Role has a valid e-mail address and Notification Preference is in the format MAIL%
d) Workflow Deferred Agent Listener is running
e) Workflow Notification Mailer is running
To check a) & b) run below query
SELECT status, mail_status FROM wf_notifications WHERE notification_id = ‘&NID’;
mail_status >> SENT means mail has gone out of mailer to user
To check c) run below query
SELECT email_address, nvl(WF_PREF.get_pref(name, ‘MAILTYPE’),notification_preference)
FROM wf_roles
WHERE name = upper(‘&recipient_role’);
To check d) & e) Use OAM (Oracle Application Manager)
How to purge e-mail notifications from the Workflow queue
madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 12/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Some times Due to large number of e-mail notifications to accumulated in the queue Workflow mailer will
not start,To fix this issue we need purge the notifications from the Workflow queue.

The below outlines the steps, Please take proper backup before performing the below.
1) You need to update the notifications you do not want sent, in the WF_NOTIFICATIONS table.
2) Check the WF_NOTIFICATIONS table as below. Records where status = ‘OPEN’ and mail_status =
‘MAIL’ are notifications that will have an e-mail notification sent.
SQL> select notification_id,status,mail_status,begin_date from WF_NOTIFICATIONS where status =
‘OPEN’ and mail_status = ‘MAIL’;
3) This should show you which notifications are waiting to be e-mailed.
4) To update a notification so that it will not get e-mailed. Set the MAIL_STATUS = ‘SENT’. The mailer will
think the e-mail has already been sent and it will not send it again.
SQL> update WF_NOTIFICATIONS set mail_status = ‘SENT’ where mail_status = ‘MAIL’;
-> This will update all notifications waiting to be sent by the mailer.
5) Then run the script 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.Only the ones where mail_status = ‘MAIL’ and status = ‘OPEN’ will be placed in the
WF_NOTIFICATION_OUT queue and sent by the mailer.
SQL>sqlplus apps/apps_pwd @$FND_TOP/patch/115/sql/wfntfqup APPS APPS_PWD APPLSYS
6) Now you can start your WF Containers and then Mailer
Posted 6th April 2016 by Unknown

View comments

XXX is not a valid responsibility for the current user. Please

contact your System Administrator.
Error: " XXX Not a valid responsibility for the current user. Please contact your
System Administrator."

1) Login with System Administrator Responsibility

2) Navigate to Profile > System, click on User and enter the user name
3) Search for profile 'Applications Start Page'. Delete the value set at user level and save
4) Go to Functional Administrator -> Clear Cache
5) Try logging into the account and try again

---

Oracle EBS: Repairing the "XXX is not a valid responsibility for the current user"
error in Oracle
How to "fix" a problem that can occur in Oracle when you have granted a user access to a new web-based
responsibility but the middle-tier application servers have not picked up this change.

Below are detailed instructions on how to clear the cache on the middle-tier application server(s). As it
says in the warning when you try and do it there will be a performance hit while it re-reads all the data from
the database - use on Production Systems at you own risk!!

At the moment I'm currently configuring Oracle Internet Expenses (11, not 12) and several times we've
granted a user the "Internet Expenses" responsibility, they've logged into Oracle, selected Internet
Expenses and then received an error along the lines of "Internet Expenses is not a valid responsibility for
the current user. Please contact your System Administrator". For example when trying to access "Function
Administrator" privilege you get the message:

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 13/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Figure 1: Sample error for "Functional Administrator" Responsibility

You only get this issue with Web-based responsibilities. If I'd assigned "Payables Manager" then it works
without any issues, the reason for this error is that in order to improve performance Oracle caches some
information on the web server. In order to "fix" this problem we need to clear the cache by following these
steps;

Step 1: Log in and select the "Functional Administrator" responsibility

Now this is where we get a delicious taste of irony; this responsibility is web-based so if you are trying to fix
a problem that's occurring now and you don't already have this responsibility then I'm afraid you're too late.
You'll have to bounce the Apache server (something that will require a DBA). In short; you need to have
granted yourself this responsibility BEFORE you run into problems!

Figure 2: "Functional Administrator" Welcome Screen

Step 2: Select "Core Services" (the tab at the top right)

Figure 3: "Function Administrator" > "Core Services"

Step 3: Select "Caching Framework" (second option from the right on blue bar)

Figure 4: "Core Services" > "Caching Framework"

Step 4: Select "Global Configuration" (bottom option on the left)

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 14/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Figure 5: "Caching Framework" > "Global Configuration"

This page shows you the currently configured Caching Statistics and Policy. The bit we're interested in
though is the "Clear All Cache" button the right-hand side.

Step 5: Click "Clear All Cache"

Figure 6: Clear Cache Warning Message

Read the message, it's there for a reason!

Step 6: Click "Yes"

Figure 7: Confirmation Message

And we're done, the user should now be able to log in with the new responsibility.

R12 --XXX is not a valid responsibility for the current user. Please contact your System Administrator.

How to Resolved XXX is not a valid responsibility for the current user. Please contact your System
Administrator.

Some time it happens that we assign a new web based responsibility like isupplier or iprocurement but
when opening it display following screenshot.

This is happening because middle tiers has yet to pick the change in assigned responsibility. To resolve
this issue we need to clear the middle tier cache.

Navigate to Functional administrator>Core Service >Caching Framework > Global Configuration

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 15/16
5/20/2019 Bounce Apache server in R12 | ORACLE APPS DBA

Click on Clear All Cache

A warning message will displayed. Click Yes

Confirmation will be displayed. Now if you navigate to iProcurement responsibility.

It
will open without error

madhanappsdba.blogspot.com/2015/10/inactive-no-this-is-what-you-see-this.html 16/16