My Oracle Support Banner

Inbound MT103 Lands Into Network Resolution Queue Having 57D With Branch Name And Addr (Doc ID 2661991.1)

Last updated on JUNE 22, 2021

Applies to:

Oracle Banking Payments - Version 14.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.3.0.0.0 version, Implementation Support

When attempting to repair the payment from network resolution queue by providing the creditor agent BIC
the following error occurs.

ERROR
-----------------------
The system fails with “Unable to resolve network”.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Inbound MT103 is injected via EMS into OBPM having tag 57D with Branch Name and Address and tag 59 having valid account followed by name and address.
2) The payment is routing to network resolution queue after deriving payment type as outgoing.
3) When user tries to repair the payment from network resolution queue by providing the creditor agent BIC as the branch BIC and system fails with error “Unable to resolve network”.
4) All inbound payments with tag 57D in production are currently routing to network resolution.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot create inbound transaction.

Changes

 

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


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