Apply-To Rate Component does not Work with two Digit Decimals when FCPO is Checked
(Doc ID 2355824.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On Oracle Revenue Management and Billing (ORMB) v188.8.131.52.0, Apply-To rate component does not work with two decimals when FCPO is checked.
We have a rate component with value type percentage and precision as 2 decimals that gets input from a previous rate component and is supposed to calculate -1% of the input.
It correctly calculates 1% but fails to apply the negative sign. It only works if we uncheck FCPO flag or increase precision to 8-9 decimals.
When FCPO is checked, the result is not correct.
Below is the scenario explained and expected result:
799951.2 *-0.01=$-7999.51( FCPO is checked and decimal is 0.01)
However the system is behaving as follows:
799951.2 *-0.01=$7999.51(FCPO is checked and decimal is 0.01), this is not correct as it is missing the negative sign.
799951.2 *-0.01=$-7999.51(FCPO is unchecked and decimal is 0.01), This is correct, but it needs FCPO remain unchecked.
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