Should we absolutely seperate Input & Calculation Modules ?

NouraJ

Hello Anaplan Community,

Following the D.I.S.C.O. Methodology, I understand that it is best practice to separate modules for input and calculation. I'm working on the Level 3 certification and created two modules for account review: one for input and another for calculations, where I referenced the inputs (HOLD / OVERRIDE / override value). However, after completing this, I noticed that my two modules (INP and Calculation) have exactly the same dimensions.

I'm now wondering whether it is still best practice in Anaplan to keep them separate or if it would be better to combine the two modules into one, where users input the data (Hold/Override, override value) and then the final sales target calculations are performed.

Thank you for your help.

Noura

seymatas1

Hi Noura,

You're on the right track with using the DISCO methodology to keep your model organized and easy to understand. It’s a good way to separate your modules. But in real-life models, you'll often need more than just five types of modules because there are so many different kinds of data and calculations modules. For example, in the Level 3 model, we have TAR and QUO modules, which are not mentioned in DISCO.

When dealing with overrides, it’s usually better to keep input and calculation together in one module. This way, when you show it on the UX page, users can see both the input (like hold/override) and the results together.

Trust your gut along with DISCO as you work on Level 3. In real-world models, it’s helpful to name and organize modules based on business needs and use a similar structure across different models to make them easier to understand.

Hope this helps!

Seyma🌷🙂