My Oracle Support Banner

Incorrect SWIFT Message Blocks All Further Edits Through MSSINBRW (Doc ID 2802542.1)

Last updated on AUGUST 27, 2021

Applies to:

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


On : version, Implementation Support

When an incorrect SWIFT message with 35+ characters in field 70 is uploaded into the system, it blocks users from not just editing that specific message to reduce the length to 35 but also blocks editing of any other messages received before or after this message, which may be in Repair status and do not have more than 35 characters in any field, and which are valid SWIFT messages, but where user may want to change the account/IBAN due to any problem or have any other field which needs a business correction, or simply to Edit and Save to retry the processing for the message.

System should not block edit feature completely for all messages. Currently after uploading a message with more than 35 characters, Edit option is not possible anymore and shows ST-SAVE-028 error for all messages.

The issue can be reproduced at will with the following steps:
1. Upload a wrong SWIFT message with 36 characters in field 70
2. After upload, it is expected to fail in MSSINBRW with MS-01010 error.
3. Once message goes to Repair, try to edit this message and remove extra characters by using "Edit" option in MSSINBRW screen
4. System shows ST-SAVE-028 error.
5. Now try to edit any other message by using "Edit" option in MSSINBRW screen
6. System shows ST-SAVE-028 error for all other messages.

Due to this issue, user is unable to edit the subsequent messages which are in repair status.




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.