My Oracle Support Banner

Conditional Assumptions Not Using the Assigned TP Method Selection Defined in the Transfer Pricing Rule (Doc ID 2366970.1)

Last updated on MARCH 17, 2019

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version 8.0.1 and later
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)


As per Calculation Engine logic, conditional assumptions are not using the assigned TP method selection in Transfer Pricing Rule:

For one particular example, a Transfer Pricing rule had been configured on FSI_D_LOAN_CONTRACTS with two conditional assumptions, used for selecting either of the two different corresponding TP methods or the default one:


As per FSI_O_FTP_AUDIT_TRAIL table data, FTP engine is processing different number of records under each condition as below:


As per instrument data in FSI_D_LOAN_CONTRACTS table (49601 records in total), below number of records satisfy each condition:

Ideally, FTP engine should assign the TP method to a record based on the satisfied conditions.  Based on obtained results, this has been found to work differently. What is the explanation for this?


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

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