Setting GTM Party Status to 'RPLS_FAILED' Does Not Change the Associated Restricted Parties Status to 'Verified Match' And Re-screening Does Not Keep the GTM Party Status As 'RPLS_FAILED'
(Doc ID 2728564.1)
Last updated on MARCH 03, 2023
Applies to:
Oracle Global Trade Management Cloud Service - Version 6.3.4 and laterOracle Global Trade Management - Version 6.2.0 and later
Information in this document applies to any platform.
Symptoms
Setting GTM Party status to 'RPLS_FAILED' does not change the associated Restricted Parties status to 'Verified Match' and Re-screening does not keep the GTM Party status as 'RPLS_FAILED'
01. Set GTM Party status to 'RPLS_FAILED'
02. Restricted Party status will not change to 'Verified Match' after setting RPLS Status to Failed.
03. Run Batch Process to screen all the parties in the system after daily DPL content update.
04. GTM Party status changes to 'RPLS_PASSED'
02. Restricted Party status will not change to 'Verified Match' after setting RPLS Status to Failed.
03. Run Batch Process to screen all the parties in the system after daily DPL content update.
04. GTM Party status changes to 'RPLS_PASSED'
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 |