My Oracle Support Banner

PFT Rule Currency Conversion Occurs Even When Target Currency Dimension is <Same As Source> for Instrument/Transaction Debit Allocation (Doc ID 1513338.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Financial Services Profitability Management - Version 5.6 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) - Version 7.x
Oracle Financial Services Analytical Applications (OFSAA)


On Oracle Financial Services Profitability Management (PFT) 5.6, it appears that the currency conversion of a transaction to instrument allocation is not correctly working.

ISO_CURRENCY_CD of source and target table are the same, i.e. JPY and are non functional currency. Instead of writing the same balance from source to target tables, one way conversion from JPY to functional currency is done.

Source is transaction table, target is instrument table, with Static Driver allocation of *1 for Non AED Currencies ( AED is functional currency ).  Allocation should update the target value to be same as source. Instead, it has updated with converted amount.

The issue can be reproduced at will with the following steps:

1. Create transaction to instrument allocation with rule is a constant rule multiplying the source data with a constant =1 and update the target table .
All the dimensions in the target table are including the currency .
Bank has provided us with a data updated by the rule which has done inverse currency conversion .
Eg ::ACCOUNT_NUMBER - 00101234xxx
Source value - 1,000.06

2. Run the allocation and find the Target value updated - 20,174.70 . Functional currency is AED .




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.