Break Identification Testing Yields Inconsistent Results for Breaks, Minimums, and Break Types
(Doc ID 2454546.1)
Last updated on OCTOBER 03, 2019
Applies to:Oracle Financial Services Funds Transfer Pricing - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
In Oracle Financial Services Funds Transfer Pricing (FTP) 8.0.x, for a Break Identification Process, the process is outputting inconsistent and wrong results. For example, you observe one or more of the following:
- Some fully and partially broken accounts are not identified by the break process
- The process ignores the "Minimum Break Amount" specified in the parameters screen for Partial breaks
- The process always outputs Full, Partial, and restructure breaks regardless of which Break Type option is selected in the parameters screen
As a result, you think Break Identification is not working correctly.
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