Submit a special Purge Concurrent Request and/or Manager Data concurrent request with mode count of 5 or 10 for your check event alert and have it run every 5 or 10 minutes. If it runs that often, it will blow up the fnd_concurrent_requests table anyway.
You can workaround using these methods.
1. You can purge only that request using "Purge Concurrent Request and/or Manager Data" (ARGUMENTS as "REQUEST" )
2. Those requests will be visible to only the users submitted. Others won't be able to see normally.
2.1 Can you confirm all users are able see other user's requests ?
In alert before submitting the program call fnd_global.apps_initialize to SYSADMIN. in this can only SYSADMIN can see those program not the end user
It's not a good idea to re-initialize your apps environment within an already running apps environment - could lead to many undesired consequences.
Thanks for replying. These requests ( Check Event Alert) can be accessed only by the user who triggered them. But I want to hide all of these even for the user submitted that request.
I tried with Role Based Access Control - I defined a permission set and a grant where I specified data object as Check Event Alert for a specific user and I presumed it will be visible only by that user.... but still this Check Event Alert is visible in View > Requests for the every user who triggered it.