Bug In Currency Correspondent Rule - PMDCYRLE (Doc ID 2956197.1)

Last updated on JUNE 20, 2023

Applies to:

Symptoms

On : 14.5.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Bug in Currency Correspondent Rule - PMDCYRLE

Screen PMDCYRLE has rule for network SWIFT, that derives the Nostro account and BIC Code for a specific currency and source code.
That same rule is being applied for other networks, and it should not, as it is defaulting the wrong currency correspondent for Swift MX networks like SWIFTX, FASTERPAYMENTX and CHAPSX.
 
In screen PSDOCBCT, we can only use MX Networks (FASTERPAYMENTX, CHAPSX, SWIFTX) and the rule specified in PMDCYRLE should not apply as it is for SWIFT network.
This is defaulted on Enrich.
 
For those networks we have set up a different account, that is the ccy correspondent for Faster payments, Natwest, and not Lloyds.
This seems to work correctly in “normal” networks, as the FASTERPAYMENT, defaults OK in Cross border outgoing payments, according to what has been set in Network Preferences screen PMDNCPRF.
 
Also, in screen PMDCYRLE, the MX networks do not show in LOV for the creation of a new rule.

EXPECTED BEHAVIOR
-----------------------
In screen PSDOCBCT, we can only use MX Networks (FASTERPAYMENTX, CHAPSX, SWIFTX) and the rule specified in PMDCYRLE should not apply as it is for SWIFT network.
This is defaulted on Enrich.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Try to create a txn from PSDOCBCT screen for network other than SWIFT and verify if the fields are defaulted

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, system is defaulting the wrong currency correspondent for Swift MX networks

Changes

Cause

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