Last updated on NOVEMBER 18, 2016
Applies to:Oracle Financial Services Funds Transfer Pricing - Version 6.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
When attempting to run an FTP process on FSI_D_BREAK_FUNDING_CHARGES table, the calculation engine is inconsistent when break costs are calculated.
While processing 154 instrument records for a given as_of_date, FTP is not processing all records as expected. It fails to populate break_funding_amt, break_funding_amt_chg, break_funding_rate, break_funding_mv, tran_rate_rem_term or, for some runs, it only populates some of the expected fields and not others.
Instruments are not processed when applying the economic loss adjustment rule to the entire table are somehow successful when specifically targeted in a data filter.
The results are inconsistent with successive runs of the process.
TestCase scenario: There is a Type 2 or Type 3 break record in FSI_D_BREAK_FUNDING_CHARGES
where the changes on the record - (for example
adjustable_type_cd moving from 0 to 50) - results in a change to another
attribute that happens to be the selected processing dimension, the
calculation of break_funding_amt_chg does not happen. Rather the
break_funding_mv is calculated for both prior and current record, but the net
difference of those two values is not populated into the break_funding_amt_chg column.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms