Avoiding circular references with calculations on Previous List Item (Numbered List)
Hello community members!
I am facing an issue which i cannot seem to find a solution to, but that someone might be able to help! This particular exercise started as a way to deal with massive amounts of sparsity in a model used by my employer. The business has a dimension (monthly vintages) representing monthly loan originations. The current approach was to use this as a dimension, alongside Time and a few others, which results in huge amounts of sparsity, as for example, a future loan originated in say Jan 21, still gets provisioned for all items on the time scale the module utilises, even if by definition there is no valid calculation to take place.
I have thought of a way to deal with this using what i would be doing in "excel logic". Basically i figured out a way to calculate the valid intersections of vintages and time, and created a numbered list with the relevant number of intersections.
The problem starts once i try to calculate line items that depend on a previous list member. Anaplan is not able to tell that there is no circularity in the logic (even though the same calculation works just fine when performed in a module with the time dimension). I think this is the same problem discussed here (https://community.anaplan.com/t5/Anaplan-Platform-Discussions/PREVIOUSITEM-PREVIOUS-on-a-list/td-p/24575), but i was unable to apply any of the solutions there (maybe i am just missing something?).
The line items and logic is as follows:
Good Book - Opening Receivables: Prior List member's closing receivables
New Advances: Linked to input modules
Good Book Payments: Based on an input % of (opening receivables + new advances)
Good book Interest charge: Based on an input % of (opening receivables + new advances)
Flow to Bad Book: Based on an input % of the prior List Member's Good Book's Closing Receivables
Good Book Closing Receivables: Summation of the items above.
I can provide blue print and grid views if required. Would very much appreciate any tips or possible solutions to try out.