Hi!
1. If your Prod Year is custom list, then create a module with custom list dimension and a year formatted line item. Fill it with FY23 in this case.
Then in target, use formula: Source Module.Data[LOOKUP: New Module.Mapping]
2. If your Prod Year is native time, then value will automatically aggregate in Target module and sum/lookup is not required.
Cheers!!
Himanshu's answer is spot on!
I would just like to add that Anaplan Time behaves in this way because each member of the time dimension is treated as discrete member - This is how the PREVIOUS, LAG etc. formulas work only with Anaplan Time. Members of a normal dimension are contiguous and can be summed against.
Anaplan Modelers: Has Anyone Recreated a Showcase Model for Learning Purposes? One of the most valuable learning resources I've come across is Anaplan's Modeling Showcase. It features sophisticated, real-world model examples that offer an incredible opportunity to learn how experienced model builders structure their…
Hi everyone 👋 If you build or maintain Anaplan models, you've probably hit the same walls I kept hitting. Some basic questions about a model's structure have no single screen to answer them. You end up clicking through modules and pages one by one, or writing API scripts just to get a list. These were the gaps that…
Hi Everyone, We have a requirement in Anaplan Consolidation & Reporting (Fluence) where the Entity Structure needs to change effective January 2026. The key requirement is that the existing entity structure should continue to be applicable for all reporting and consolidation periods through December 2025, while the new…
