Control/Compliance Screening Does Not Change the (TL_CONTROL_SCREENING) Status to (TL_CONTROL_SCREENING_ON HOLD) From the First Run
(Doc ID 2631107.1)
Last updated on MAY 06, 2022
Applies to:
Oracle Trade Compliance Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
Control/Compliance Screening does not change the (TL_CONTROL_SCREENING) status to (TL_CONTROL_SCREENING_ON HOLD) from the first run.
EXAMPLE:
-----------
01. Compliance Rule: CR-01 (License + Item Remark: COLOR = RED)
02. Compliance Rule: CR-02 (License Exception + Item Remark: COLOR = RED)
03. Compliance Rule: CR-03 (License + Item Remark: BOND TYPE = B)
04. Compliance Rule Set: CR-01-02
05. Compliance Rule Set: CR-03
06. Compliance Rule Set Group: CR-01-02-03
07. Transaction: TT_01 (Item Remark: COLOR = RED)
08. Execute Compliance using Compliance Rule Set Group: CR-01-02-03
TL_CONTROL_SCREENING TL_CONTROL_SCREENING_PASSED
09. Update the Item Remark (Item Remark: BOND TYPE = B)
10. Execute Compliance using Compliance Rule Set Group: CR-01-02-03
TL_CONTROL_SCREENING TL_CONTROL_SCREENING_PASSED
11. Again Execute Compliance using Compliance Rule Set Group: CR-01-02-03
TL_CONTROL_SCREENING TL_CONTROL_SCREENING_ON HOLD
ISSUE:
The status should go to (TL_CONTROL_SCREENING_ON HOLD) in step#10 which is not happening.
But it goes to the expected status (TL_CONTROL_SCREENING_ON HOLD) after executing the action again in step#11
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 |
| References |