My Oracle Support Banner

OBPM |MX Message <InstrId> Is Captured As Source Ref Number Instead Of Txn Ref No (Doc ID 3060871.1)

Last updated on DECEMBER 10, 2024

Applies to:

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

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
 
Outgoing FCAT payments - MX message captured as Source Reference Number instead of transaction reference number. Actually, the transaction should release the outgoing message with transaction reference number.

We have also checked in PMDSORCE maintenance, the preferred reference number is kept as Transaction Reference only.



EXPECTED BEHAVIOR
-----------------------
the transaction should release the outgoing message with transaction reference number.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Login to OBDX using maker
2.Initiate international transfer
3.Submit the txn for approval
4.Login using checker
5.Approve the txn using checker.Txn get submitted successfully to OBPM.

 

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.