My Oracle Support Banner

SWIFT migration tools in Transaction filtering (Doc ID 2688195.1)

Last updated on JULY 08, 2020

Applies to:

Oracle Financial Services Transaction Filtering - Version 8.0.6 and later
Information in this document applies to any platform.

Goal

Actual behavior : 

While migrating the configuration of the non-OOB SWIFT types from one instance to another, the migration tool will not consider or analyze the difference between the source and the target instances.

For examples:
1. user tried to upload the new JSON format in the target instance,
the system will create the new N_SANCTION_SWIFT_MSG_ID for the new message
type or the new version of the existing message type. But the migration tool
will not know that new N_SANCTION_SWIFT_MSG_ID between the Source and the
Target instance could be meant to different message types. Therefore after the Migration, some existing SWIFT message types were gone
or been replaced by another message type.

2. Same logic as above, once the user updates or create the SWIFT
configuration on the target instance, there might create new N_MATCH_TABLEID,
N_EXPR_ID, N_MSG_TAGS_CONF_ID...etc. The Migration tool is also not able to
compare the difference between the source and target instance. Therefore after the Migration, some existing configuration of the
SWIFT message types were gone or been replaced by another configuration.

Expected behavior : 

The swift migration utility should consider the difference between the source and the target instances.

 

Solution

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