[SICSR-17117] Missing FC1/2 after running Occ Year Allocation order
Product Line:	P&C
Component/s:	Accounting Functional Currency
Affects Version/s:	SICS 4.8.5 SSP2 REN1
Fix Version/s:	SICS SQL SICS 4.9.5 SICS 4.8.5 SSP2 REN6
Customer:	Renaissance Re
External Issue ID:	SO-281

Problem:
Missing FC1/2 after running Occurrence Year Allocation of Losses order

Solution:
When running the Occurrence Year Allocation of Losses order, and the system is splitting the loss amounts among Occurrence Years according to the Booking Year split of the Premium, we must make sure the system uses more than 6 decimals, suggestion is 24 decimals, in all calculations.

Workaround:
None

Root Cause:
The calculation that takes place when the individual loss details are split by occurrence year based on the premium split by booking year is done in this way:
loss amount/total premium for all booking years*premium for each booking year
This is used both when the original loss amount and when FC1/FC2 amounts for the loss is calculated and split.
So if the loss amount in ratio to the total premium for all booking years is very small, so that the amount in the first half of the calculation becomes less than 0,0000001, this amount is rounded to 0,000000 (zero), since the amounts stored in the calculation uses only 6 decimals.

Extent of Impact:
Wrong or missing functional currency amounts

Impact on Existing Data

Recovery Method for Existing Data Affected
Before the above solution will have any affect, a clean up of the database is necessary. Therefore, a script to reverse the details created by the Occurrence Year Allocation of Losses order, with wrong functional currency amounts, should be run. When all details are reversed, and the above correction is implemented, then new Occurrence Year Allocation of Losses orders can be run and correct FC amounts will be calculated.