FTP 8.0.6.6: Incorrent Breakage Data Populated When Data Filter With Relation Is Used in Break Identification Process
(Doc ID 2820701.1)
Last updated on APRIL 24, 2023
Applies to:
Oracle Financial Services Funds Transfer Pricing - Version 8.0.6.6.0 to 8.1.2 [Release 8 to 8.1]Information in this document applies to any platform.
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Symptoms
On FTP 8.0.6.6.0 version, below issues were identified with breakage data:
1. Accounts with ALM_PROFITABILITY_FLG=1 are being updated with breakage data although user has applied filter to include only ALM_PROFITABILITY_FLG = 2 data. Engine behavior seems wrong.
2. January data is updated with February data only for BREAKAGE_TYPE_CD and BREAKAGE_AMOUNT columns. This is wrong and user understanding is this gets updated by Out Of The Box (OOTB) function BREAK_DETECTION.
Example:
From Jan 21 result, the breakage_type_cd of Jan 21 data was "2" with a particular balance of breakage_amount.
After running Break detection for Feb 21 data, the breakage_type_cd and the balance of breakage_amount of Jan21 data was replaced by those from Feb 21 data.
ID_NUMBER BREAKAGE_TYPE_CD BREAKAGE_AMOUNT BREAK_FUNDING_AMT_CHG
Before Feb21 100001 2 -46.08 1.05
Before Feb21 100002 2 -0.01 0.07
Before Feb21 100003 2 311.72 -4.9
Before Feb21 100004 2 1.3 -0.28
After run Feb21 100001 1 251104.82 1.05
After run Feb21 100002 2 -0.01 0.07
After run Feb21 100003 2 311.72 -4.9
After run Feb21 100004 2 1.3 -0.28
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 |
| Cause |
| Solution |
| References |