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...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...