My Oracle Support Banner

Fields MSG_TYPE , SWIFT_MSG_TYPE are blank for RTGS, SWIFTMX Transactions after mini ps 37407998, 37562718 (Doc ID 3078556.1)

Last updated on APRIL 02, 2025

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
Regression after deploying mini patch set 37407998, 37562718, as bank observed that msg_type, swift_msg_type not populated in pmtb_msg_dly_msg_out table for RTGS, SWIFTMX transactions

EXPECTED BEHAVIOR
-----------------------
After deploying mini patch set 37407998, 37562718, msg_type, swift_msg_type fields in pmtb_msg_dly_msg_out table should get populated for RTGS, SWIFTMX transactions

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In UAT of latest production image
2. Deploy mini patch set 37407998, 37562718
3. Perform RTGS, SWIFT MX transactions and check fields msg_type, swift_msg_type fields in pmtb_msg_dly_msg_out table are blank

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see the value in fields msg_type, swift_msg_type in pmtb_msg_dly_msg_out table for RTGS, SWIFTMX transaction.

Changes

 Application fix will set the value for Msg type, Swift msg type fields in table pmtb_msg_dly_msg_out

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


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