My Oracle Support Banner

On Authorizing A Transaction From PSDOCBBT, The Message Type And Swift Message Type Updated Wrongly (Doc ID 3018152.1)

Last updated on APRIL 24, 2024

Applies to:

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

Symptoms

On : 14.5.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
On Authorizing a transaction from PSDOCBBT, the message type and swift message type updated wrongly

Issue: On Authorizing a transaction from PSDOCBBT, the message type and swift message type updated wrongly

Problem Description: On authorizing a transaction from PSDOCBBT screen, 2 records are getting populated in PMTB_MSG_DLY_MSG_OUT table with message type BANK_TRANSFER and DEBIT_ADVICE. But message type is wrongly populated as BANK_TRANSFER and swift message type as 202 instead of DEBIT_ADVICE.
 
EXPECTED BEHAVIOR
-----------------------
On Authorizing a transaction from PSDOCBBT, the message type and swift message type update correctly

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On Authorizing a transaction from PSDOCBBT screen
2. 2 records are getting populated in PMTB_MSG_DLY_MSG_OUT table with message type BANK_TRANSFER and DEBIT_ADVIC
3. But message type is wrongly populated as BANK_TRANSFER and swift message type as 202 instead of DEBIT_ADVICE.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Transaction from PSDOCBBT, the message type and swift message type updated wrongly.

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
References


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