My Oracle Support Banner

PM : Multiple Message Generation With Different DCN From PMSOUTBR Screen (Doc ID 3038312.1)

Last updated on AUGUST 07, 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
-----------------------------

Multiple message generated with Different DCN when message is generated from PMSOUTBR screen



EXPECTED BEHAVIOR
-----------------------
System should update the message status of the corresponding DCN , instead system is inserting record with new DCN.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Select a txn reference number for which message is in un-generated status
2. Fetch the record in PMSOUTBR screen with reference number
3. One record is available for DCN-ref number combination in un-generated status
4. Click on generate
5. Now another record is available for the same txn reference number ( and different DCN number) in generated-hand off status
6. Click on generate again
7. One record is inserted with different DCN and same txn ref number combination
8. Expectation is that system shall use the same Original DCN number and just update the message status to generated/handed-off
 

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, multiple messages with same transaction ref_no present

Changes

 

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
References


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