My Oracle Support Banner

MT999 Generated Instead of MT754 & MT756 against Negotiating bank with RMA on save in message preview (Doc ID 3069393.1)

Last updated on JANUARY 29, 2025

Applies to:

Oracle Banking Trade Finance - 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
---------------
MT999 generated instead of MT754&MT756 against negotiating bank with RMA on SAVE in Message Preview
'ADV_PMT_ACPT' Message preview is coming as 999 instead of 754 when using RMA bank in Negotiating bank. After authorization it is coming as 754 as expected.
Issue- On Message Preview, ADV_PMT_ACPT is generated as 999 instead of 754 and Message receiver is showing 'BANK-A-XXX'.
Note- After authorization 'ADV_PMT_ACPT' is coming as 754 with correct Message receiver as 'BANK-B-XXX'.

EXPECTED BEHAVIOR
-----------------------
Expected- MT754 should generate since Negotiating bank is RMA bank with valid BIC in Address1 under Parties tab.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Bill booked in Initial stage
2) Parties tab--> Negotiating Bank is Non RMA Bank, Swift Address 'BANK-A-XXX' provided for the same under Medium
3) Unlock Bill and modify the Stage to Final
4) Parties tab--> Update RMA Bank customer with valid Address1 'BANK-B-XXX' in Negotiating Bank & Remove Swift address under Medium.
5) Save the bill

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, On Message Preview, ADV_PMT_ACPT is generated as 999 instead of 754 and Message receiver is showing 'BANK-A-XXX'.

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
References


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