Changing GTM Party Status to "RPLS_FAILED" NOT Changing Denied Party Status to "Verified Match"
(Doc ID 2978652.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Global Trade Management Cloud Service - Version 19.3 and laterOracle Global Trade Management - Version 6.3.7 and later
Information in this document applies to any platform.
Symptoms
Changing GTM Party's Restricted Party status to RPLS_FAILED NOT changing Denied Party Screening status to 'Verified Match'.
Expected Behavior is when GTM Party's Restricted Party status to RPLS_FAILED, system should change the Denied Party Screening status to 'Verified Match'.
Steps to Reproduce
--------------------------
The issue can be reproduced at will with the following steps:
1. Find a Party PARTY-001
a. Make sure it's RPLS Status is REQUIRES_REVIEW
b. And Denied Party Screening Status is Potential Match
2. Select the party record > Actions -> Utilities -> Change Restricted Party Status -> Status value selected as "RPLS_FAILED" -> Ok
Outcome
1. This changed the Party's RPLS Status into RPLS_FAILED
2. Denied Party Screening Status is not changed, it is still as Potential Match.
--------------------------
The issue can be reproduced at will with the following steps:
1. Find a Party PARTY-001
a. Make sure it's RPLS Status is REQUIRES_REVIEW
b. And Denied Party Screening Status is Potential Match
2. Select the party record > Actions -> Utilities -> Change Restricted Party Status -> Status value selected as "RPLS_FAILED" -> Ok
Outcome
1. This changed the Party's RPLS Status into RPLS_FAILED
2. Denied Party Screening Status is not changed, it is still as Potential Match.
Changes
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 |