How to send all the notifications to a single email address ( Workflow mailer EBS R12 )

-

Option 1:


Configure From Front end:

The Override Address is set after the clone is completed as it will be set in OAM. Oracle Workflow sends the Notification Mailer Override Address Verification message when an administrator sets an override address where the notification mailer should send all outgoing e-mail notifications for testing purposes. It can be set as follows:
1. To setup Test Override please do the following:
a. Please log in to OAM.
b. Select Workflow Manager from "Navigate to" LOV and click "GO".
c. Click "Notification Mailers".
d. Click "View Details".
e. Click "Set Override Address".
f. Populate "New Override Address" with a Test address and click "Submit".
g. Populate the verification code that appears in the email notification that was sent to the 'Override Address' and click "APPLY". Example: Verification Code: 896424928
h. Conformation of the change will be provided by the Java Mailer Setup.

2. Test the issue by generating Notification Mail.


 

Option 2:
Configure from Backend:

Please use the following script $FND_TOP/sql/afsvcpup.sql

This will enable to change any and all or your Mailer components.

A. Run the script
B. It will show you the components - pick the comp id for the Workflow Mailer - default is 10006 
C. then it will show you the parameters and their values for the mailer
D. Pick the comp param id for the Override address (it will say Test Address ) - default is 10093

It will show you

You have selected parameter : Test Address
Current value of parameter : NONE

Enter a value for the parameter : <Here you will put the email address you want >


References:
How to set Workflow Mailer Override Address from Backend ? (Doc ID 1533596.1)

How Does One Set Oracle Workflow Override Address After A Clone. (Doc ID 1623032.1) 


Comments

  1. Neha2 September 2019 at 11:09

    I tried to override address in workflow mailer but not getting any verification code.Please suggest what to do?

    ReplyDelete

Post a Comment

Popular posts from this blog

RMAN backup Status (Remaining Time and Percentage)

-
On Running a huge database backup we often need to know the status of backup. 1) How much backup is taken. 2) How much is remain. 3) Estimate time to complete the backup. After lot of search i find out this amazing query below. col dbsize_mbytes for 99,999,990.00 justify right head "DBSIZE_MB" col input_mbytes for 99,999,990.00 justify right head "READ_MB" col output_mbytes for 99,999,990.00 justify right head "WRITTEN_MB" col output_device_type for a10 justify left head "DEVICE" col complete for 990.00 justify right head "COMPLETE %" col compression for 990.00 justify right head "COMPRESS|% ORIG" col est_complete for a20 head "ESTIMATED COMPLETION" col recid for 9999999 head "ID" select recid , output_device_type , dbsize_mbytes , input_bytes/1024/1024 input_mbytes , output_bytes/1024/1
Read more

EBS R12.2 Autoconfig Failed. Resolved

-
Hi, Please do the following and retest the issue: Due to the method required for "cleaning out" / "re-synchronizing" the following tables, it is EXPECTED / REQUIRED that the Applications have been shutdown. The only thing running should be the Database Tier. Note: A full backup should also be taken before any testing begins. Test the following steps in a development instance, and then migrate accordingly once the desired result is confirmed: 1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env: sqlplus applsys/pwd create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files; create table fnd_nodes_bk as select * from fnd_nodes; create table adop_valid_nodes_bk as select * from adop_valid_nodes; 2. Truncate the following tables: truncate table fnd_oam_context_files; truncate table fnd_nodes; truncate table adop_valid_nodes; 3. Run AutoConfig on the DB tier
Read more

Cleaning nodes in EBS databae.

-
Cleaning EBS nodes with EXEC FND_CONC_CLONE.SETUP_CLEAN; . EBSapps.env run   $ sqlplus apps/<PASSWORD> SQL> create table fnd_nodes_22ep14 as select * from fnd_nodes; SQL> exec fnd_conc_clone.setup_clean; PL/SQL procedure successfully completed. SQL> commit; Commit complete. After that run autoconfig in below order to populate the FND TABLES properly. 1) Stop application services ( optional but  recommended )  2) Run autoconfig on dbTier 3) Run autoconfig on appTier
Read more