Level 3 Certification, create new modules or use previous modules ?

Noura99
Noura99
in Modeling

Hello Anaplan Community,

I'm working on the Anaplan Level 3 certification, and I'm currently at the Assigning Accounts & Sales Reps process. I'm facing some confusion regarding modules while trying to keep the D.I.S.C.O methodology in mind.

  • Can we display SYS modules on the UX? For example, can we add a line item for input in this module and display it, or would it be better to create an entirely new module dedicated to that single input line item (e.g., for sales reps) and then reference other line items from the SYS module?
  • Alternatively, I could use the existing TAR02 Account Review module to add a line item for sales reps assignment since all the line items I need already exist in this module. However, there is a yearly time scale that I don’t necessarily need.

I’m confused because I understand that the D.I.S.C.O methodology emphasizes separating outputs from calculations, etc.

  • I also have another question based on my build experience. I was told that we should never display calculation modules on the UX, but for this certification, I’ve displayed the TAR modules on the UX. I think they are equivalent to calculation modules in the D.I.S.C.O methodology. Am I correct, or do I need to duplicate modules and create new ones named OUTPUT just to reference all the calculations and then display them?

Sorry for the long explanations, but I’m really confused about this. Any help would be highly appreciated.

Thank you,

Noura

Answers

  • Dikshant
    Dikshant

    Keep the Account to Sales Rep mapping in the TAR02 module because this mapping changes every year. A lot of people wonder about DISCO and how to use it effectively. Think of it this way: you could place this particular line item in a System module as well. Since you’ll be loading this mapping from a file rather than entering it manually.Moreover you can set up your own classification based on different use cases. Anaplan uses TAR for classifying all Target modules, so you can create a classification that fits your needs. That’s what DISCO is really about—customizing it to work best for you.

Categories