MS: Outgoing Swift Message Could Not Be Handoff But Fall Into PDE Queue (MSDETPDE)
(Doc ID 2889873.1)
Last updated on AUGUST 16, 2022
Applies to:Oracle FLEXCUBE Universal Banking - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Production Support-SET
Actual Behaviour :
Outgoing Swift Message could not be handoff but fall into PDE queue (MSDETPDE)
find us solution to not send message into PDE queue, this has block Outgoing Swift Message on production to be handoff. Again huge financial impacts for HK where Swift is crucial.
We also need your clarifications on below :
1). What are the validation rules of Flexcube (what are the rules?) to consider a message as duplicated (set PDE_Flag = Y)?
2). Why only on this v.188.8.131.52 this screen is required? In previous version, user confirmed they do not have to manage this PDE queue screen (MSDETPDE)
Outgoing Swift Message could not be hand off but fall into PDE queue (MSDETPDE)
When the message is not a duplicate message, then system should not send message into PDE queue.
Instead message should be handed off successfully wihtout any manual interference.
The issue can be reproduced at will with the following steps:
1. Create a FT/FX contract.
2. Preview the message before auth using maker id and checker id.
3. Close the preview message tab.
4. Check if the preview message is inserted in mstb_dly_msg_out and mstb_msg_pde_log
5. Authorize the contract.
The issue has the following business impact:
Due to this issue, users cannot see the audit log information
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