My Oracle Support Banner

Able To Input FX In FXDTRONL With Different Counterparty To Netting Customer (Doc ID 2867486.1)

Last updated on MAY 09, 2022

Applies to:

Oracle Banking Treasury Management - Version 14.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.5.0.0.0 version, Production Support

ACTUAL BEHAVIOR
---------------
Able to input FX in FXDTRONL with different Counterparty to Netting Customer

Ior those FX contracts enabled for FX netting, when the netting customer is different from the counterparty, system does not validate the following:

whether the ‘netting customer’ has a SSI maintained for underlying currencies of the FX contract
Whether the ‘netting customer’ is part of the netting arrangement with the counterparty and maintained in STDTRCIF
Issue identified: When a netting customer is chosen which doesnot have an SSI maintained, then as part of Auto netting done during EOD batch process, it fails and stops the EOD process.

EXPECTED BEHAVIOR
-----------------------
System should perform the customer number validation while saving the FX deal.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Input an FX contract and mention the counterparty as party A, for which Netting agreement (with netting type ‘Auto’) is maintained but there is NO SSI maintained for one of the underlying deal currency (e.g. EUR). During save, system will validate this and throw error.
2. Change the counterparty to Party B which has a valid SSI maintained for EUR and other leg (e.g. GBP). However, the netting customer which was originally defaulted to party A is not changed by the system when Party B is chosen as the counterparty (Note: Party A and Party B doesnot have any netting relationship and their respective CIF Id’s are maintained as netting customer in STDTRCIF)
3. System doesnot do any validation and allows to save the record.
4. On the value date, system tries to do Auto netting as part of EOD and checks the SSI for party A (which was wrongly maintained as netting customer) and since it doesnot find the SSI, EOD fails.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, EOD is getting aborted

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
References


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