My Oracle Support Banner

Incoming MT700 message processing fails without updating error code, when field 58 is having Invalid Confirming Bank code BIC. (Doc ID 2557371.1)

Last updated on SEPTEMBER 09, 2019

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------

Processing of any incoming MT700 message is failing in FCUBS application, if it's having Invalid Confirming Bank code BIC in field 58 of the message. But, system fails to populate relevant error code and hence user is not able to validate the failure reason of the problematic swift message.

EXPECTED BEHAVIOR
-----------------------
System should populate error code, if field 58 is not having the branch BIC.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload a 700 with 58A as invalid BIC Code.
2. Launch CSSJOBBR screen
3. Run SWIFT_UPLOAD job
4. Query the MSTB_DLY_MSG_IN table
5. Check whether the message is going to Repair

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot validate the exact reason, why MT700 swift message is not processed in the system.

Changes

 NA

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
Changes
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.