My Oracle Support Banner

Sanction Seizure On Recall Is Marking Original Transaction Status As "Recall Seized" (Doc ID 2688430.1)

Last updated on DECEMBER 18, 2020

Applies to:

Oracle Banking Payments - Version 14.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
-------------
We previously raised.
Inbound SCT (SEPA Credit Transfer) Status is updated as Recall Seized
When Recall transaction is marked as BLOCK OFAC, the original transaction status is marked as Recall Seized

EXPECTED BEHAVIOR
-----------------------
When Recall transaction is marked as BLOCK OFAC, the original transaction status should not move to Recall Received. It should remain as processed

STEPS
-----------------------
1. The issue can be reproduced at will with the following steps:
2. Upload pacs008 for SCT incoming such that it will get stuck in Sanction Queue
3. Provide Force Pass from Sanction Queue for original transaction
4. Verify the SCT incoming transaction is processed
5. Upload Recall for SCT incoming
6. Provide Block OFAC for the Recall transaction from Sanction Queue
7. Validate the Original transaction status is Processed

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Transaction cannot be processed.

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
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.