My Oracle Support Banner

Advice Generated In Mstb_dly_msg_out Doesn't Have The Correct Mcs And Node, when viewing account statement in ACDOPTN screen. (Doc ID 2677079.1)

Last updated on JULY 26, 2021

Applies to:

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



When viewing an account statement in ACDOPTN screen, system automatically creates a record in mstb_dly_msg_out.
This message record that is created, considering other mail type of advices, does not have any details in columns MSC and Node.
The message when inserted in the table is automatically sent to status 'G'-Generated, but the EMS then tries to hand-off the message to the path of EMS mail as per MAIL MCS setup.

But this is not done as the MCS for the message is empty, hence the message becomes part of an never ending loop from the EMS and in order to perform the handoff the system increases the message Mod_no, causing issues with the data.

Furthermore, this is causing the bank to stop EMS_OUT job manually as this messages reach the max number in MOD_NO column which is 9999 causing a failure of the job.

The MCS message and Node should be inserted in mstb_dly_msg_out

The issue can be reproduced at will with the following steps:
1. View a account statement in the ACDOPTN screen.
2. Check whether the EMS out job is creating the advices correctly.

The issue has the following business impact:
Due to this issue, EMS out job going on an continuous loop.




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

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