Why do we need a time setting module as system module when we already have a dimension of time?
I am a beginner in Anaplan so please pardon if my question is basic.
This lends to one of a key principle of model building calculate once reference many times. The system module allows you to define common attributes that will be refenced in downstream calculation modules.
The best practice for module design explains this in more detail:
https://community.anaplan.com/t5/Knowledge/Best-Practices-for-Module-Design/ta-p/35993
We have time dimension by default, But in order to use the calculations, we need to write some formulas and logic in the line items that are created in Modules. And a popular Anaplan saying, Calculate Once, Refer multiple times. That's why we create a module and as per DISCO, it has to be System module as it's common attribute that we will be using further as filter or in calculations in other modules.
Thank you for your prompt responses. This is very helpful!
We've been building a tool called aplan4sheets and we'd genuinely like input from this community — both on what we've built so far and on what we should prioritize next. The problem we set out to solve: Anaplan's Excel add-in is Windows-centric, and there's no real native way to pivot Anaplan data in Google Sheets. We…
A while back, I shared a pattern for extracting and reporting on Anaplan audit data using a Python project hosted on GitHub. I wrote that during my time on the Operational Excellence Group (OEG) at Anaplan. The Python solution still works, and plenty of teams are running it today. The problem it solves hasn't changed:…
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
