Is it recommended to have multiple models where aim is almost similar throughout for all regions but the way of calculations are different for each cost center.
Hi @snigdhakapila
Well it sort of depends on your client. If they are new to Anaplan Platform, you wouldn't want to complicate things for them by introducing multiple models. Also, data integration would be another issue if you create individual models for each cost center. What if number of cost centers increases. Number of ALM's you'll have to perform will complicate things for you. Maintaining hierarchies common across all models would be another issue and also maintaining Master Data.
I would suggest to create one model and use Line Item Subsets/List Subsets if you feel for some cost centers your calculations can match.
P.S :- I am hoping that you are actually asking about multiple models and not multiple modules.
Thanks,
Megha
Thanks Megha :)
Even I was thinking about creating a Data Hub to maintain Major list and data sets and use one single spokes model for now.
If required we can create other models later, also was not thinking about Cost Center but the Types of Calculations like Revenue, Payroll/workforce etc.(but that is for a later stage)
Thanks a lot!
I am trying to create a Net Debt / EBITDA formula at the bottom of one of our P&L income statements where, i have tried the MOVINGSUM function. However this does not work for summary line items which EBITDA is. What i would like is to be able to sum the previous 12 months EBITDA (Including the current period) numbers in a…
Hi I'm looking to speak to people who have used/are using the Docusign integration in their business. We are exploring the possibility, but we find the current setup quite limiting in terms of how an end user would interact with the integration, but also issues with concurrency and number field formats. Would appreciate…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
