FTP Questions on Using Breakage Charged FSI_D_BREAK_FUNDING_CHARGES Process

(Doc ID 2361667.1)

Last updated on MARCH 05, 2018

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version 8.0.4 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Funds Transfer Pricing (FTP)

Goal

Based on <Document 2142478.1> which states some "Pre-requisites for calculating Breakage Charges", the following additional question arise:

Question 1:
Based on point in doc: 1. Break event records should be populated in the FSI_D_BREAK_FUNDING_CHARGES table.
This can be done directly through a manual data loading process or can be automated using an FTP Break Identification Process. (see Chapter Break Identification Process, page 29-1)

When an automated FTP Break Identification Process is created on "fsi_d_term_deposits" table for example, after running the process are the break identified records copied into "FSI_D_BREAK_FUNDING_CHARGES" by deleting the actual record in "fsi_d_term_deposits". Does the same record appear in to tables?

Question 2:
Based on point in doc: 3. 3. A Standard Transfer Pricing (TP) Process should be defined with the following: (see Chapter Transfer Pricing Process, page 28-1)

  1. The Break Funding Charges table selected on the Product Selection block
  2. Adjustments must be selected on the Calculation Elements block
  3. An Adjustment Rule containing the required Breakage Charge assumptions must be selected

Questions:
1. Is a TP rule not required to create a TP process?
2. How will TP rate be calculated for these records in FSI_D_BREAK_FUNDING_CHARGES table, if no TP rule is configured.

Question 3: How to populate data from FSI_D_BREAK_FUNDING_CHARGES table into FCT_FTP_COMMON_ACCOUNT_SUMMARY, is there any  Table to Table (T2T) or other Data Transformation process?

Question 4: How to load data into "FCT_COMMON_ACCOUNT_SUMMARY" from "FSI_D_BREAK_FUNDING_CHARGES" for FULL BREAK records, so as to avoid the FK_336_1 error.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms