In SAS Solution for IFRS17, the sas macro code cap is hardcoded. An issue occurs where SAS Solution for IFRS17 interprets one variable in the sas macro wrong and, as a result, the JVM heap runs out of memory.
Here is an example scenario:
When you execute Partition Discounting Cash Flow cycles, SASServer8_1 runs out of JVM heap.
The following screenshots of the SASServer8_1 Java heap memory dump analysis show that the Partition node cycle consumed 67 GB of the JVM-allocated heap.
There is no workaround for this issue.
The code fix for this issue provides users with flexibility to add a cap to the number of partitions either inside the user interface or within the sas macro parameter.