PMF flow is not triggered and alerts are not created in TF
(Doc ID 2721843.1)
Last updated on MAY 22, 2023
Applies to:
Oracle Financial Services Transaction Filtering - Version 8.0.6 and laterInformation in this document applies to any platform.
Symptoms
Encountered the below error while posting the swift message and alert is not generated.
[ERROR] 2020-09-10 15:26:27.400 [pool-13-thread-1] aai - com.oracle.ofss.sanctions.postProcess.investigation.client.PmfAutoAssignClient
Exception occured in method AutoAssign Pmf with Message = Failed AutoAssign : HTTP error code : 503
java.lang.RuntimeException: Failed AutoAssign : HTTP error code : 503
Steps to reproduce:
Step 1: Post a swift message through Sanctionspost.jsp
Step 2: Login as TFanalyst and check for the alerts.
Step 3: IF no alerts generated then refresh and check for [ERROR] keyword in rtiserver.log
location : $Deployment_area/applications/TFLT.ear/TFLT.war/logs
Actual result:
Alert is not generated and encountered PMF auto assign error
Expected result:
Alert must be created without PMF auto assign issue.
Changes
NA
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |