FT-MTUP013 Invalid account error thrown if 52D present in MT103
(Doc ID 2616288.1)
Last updated on DECEMBER 05, 2019
Applies to:Oracle FLEXCUBE Universal Banking - Version 11.2 and later
Information in this document applies to any platform.
During STP when the incoming message contains 52D the outgoing message is not generated and is failing but when the incoming message is having 52a or does not have 52 tag then the out going message is getting generated properly.
FT-MTUP013 - Account is INVALID error is thrown when the message contains 52D.
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