Skip to main content

Resend Failed/Sent Notifications Again in Oracle Apps R12

Resend Failed/Sent Notifications Again in Oracle Apps R12

In this post, I am sharing how to resend the notification mail to users if it fails or user have not received.

1) Check if the Notification mailer/Agent listener is running
 
    select (case when (select count(1)
                         from apps.fnd_concurrent_queues
                        where concurrent_queue_name = 'WFMLRSVC') > 0
                 then 'Notification Mailer Running' 
                 else 'Notification Mailer Not Running'
                end) "Status"
       from dual

2) Run the below query to get the exact number based on dates

       select *
        from wf_notifications
      where 1=1
         and trunc(begin_date) <= trunc(sysdate-4)
         and mail_status = 'FAILED'
         and status = 'OPEN'
         order by trunc(begin_date) 
Get details based on the recipient roles

  select * from wf_notifications where recipient_role='HIMANSHU';

3) Run the concurrent program 'Resend Failed/Error Workflow Notifications' from 'System  Administrator' responsibility.
     > All parameters are optional, please select the parameter values accordingly so that only required notifications get re-processed.

     Mail Status: Error/Failed
     Message Type: Workflow Item Types
     Recipient Role: List of workflow roles
     Notifications sent on or after: Date
     Notifications sent on or before: Date

4) For resending the Sent notifications, please 'Rewind'

    >> Goto Workflow > Status Monitor
        >> Search with 'Type Internal Name' and 'Item Key'
             >> You can get it from wf_notifications table

        >> Click on 'Activity History' > Select the Activity with 'Notified' Status and 'Rewind'
            >> Again select the same activity and 'Apply'
             >> You will get a message for Rewind.

    Check the wf_notifications table for the same 'message_type' and 'item_type', there should be two entries with the previous one 'Closed'.

5) If notification is getting failed, again and again, check the user preferences for that recipient.

      Select *
        from fnd_user_preferences
       where user_name = <> ;

You can also debug the notification with the notification id

Run the @$FND_TOP/sql/wfmlrdbg.sql  
 > Parameter: Enter Value for 1: <Notification_ID >

It will generate the debug file in the same directory.



If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...