My Oracle Support Banner

DUPLICATE FT ARE GETTING CREATED BECAUSE OF MESSAGES IN REPAIR STATUS (Doc ID 2697261.1)

Last updated on APRIL 26, 2021

Applies to:

Oracle FLEXCUBE Universal Banking - Version 14.0.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.0.0.0.0 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
As per current code ,repair message picked by incoming job and gets
processed. Checker authorizes repaired message and process_stat goes as
unprocessed.And this message gets picked up again and fails with FT-MTUP102 .
 


EXPECTED BEHAVIOR
-----------------------
Duplicate contracts should not be created

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1)In prod there are  around 20 messages in repair and 3-4 unprocessed messages in each run.
2)Repair/Edit a message from incoming browser screen(MSSINBRW).(Do not save. Wait until step3 is done)
3)Start incoming job from CSSJOBBR.
4)Click on save. The repaired message goes as unauth in mstb_dly_msg_in
5)The repaired message gets picked by incoming job and gets processed and generated reference number gets updated in mstb_dly_msg_in.Message still in unauth stage.
6)Checker authorizes repaired message and process_stat goes as U(unprocessed).
7)The message gets picked up again and fails with FT-MTUP102.(Duplicate reference number)


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, duplicate FT contract created which is creating huge financial impact

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


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