My Oracle Support Banner

MT320 Nack'ed For Back Dated Deal (Doc ID 2776094.1)

Last updated on MAY 21, 2021

Applies to:

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

Symptoms

On : 14.1.0.0.0 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
MT320 Nack'ed for Back Dated MM Deal

Outgoing MT320, confirmation message for newly booked MM deals have been rejected with below reason.

D56 C3-A
In sequence B, field 32H is not allowed and field 30X is mandatory, if field 22B (in sequence A) contains CONF.

EXPECTED BEHAVIOR
-----------------------
System is expected to populate 30X(Next Interest Due Date) in the MT320 message.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a back dated MM deal with maturity date as application date.
2. Review the outgoing MT320 generated.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, MT320 got NACK'ed in production.

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


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