Hi @mikeng , Have faced similar problems in past. The roll up of data happens independently of the selective access currently. Had devised a solution using a combination of selective access module kept as system module and using the same for calculation of cost at an aggregate level (especially when users don't have aggregate level access). Here is how I have approached this: Lists: Created two lists - Cost Heads & Cost Details. Cost Heads as the parent of Cost Details. Input Module: One simple module to have the source data of costs. This can be calculated in your case. Selective Access Module: Here comes the tricky part. Idea is to populate this basis the selective access settings in the Users tab. You can create the export from the user tab (make sure to save the export definition). This exported file will be brought back into Anaplan in the system module and used for calculation. Once the exported file is available, this needs to be imported into Anaplan and calculations need to happen. Below are the structure of the module and the import definition. Import Definition: Aggregate Calculation: The final bit is to calculate the aggregate cost number based on the selective access settings. This is a simpler calculation. Module structure and data as below: You need to use users list in the calculations as selective access is at a user level. Please let me know if this is something that can be used. Thanks Anik
... View more
@mikeng The reason you can't use SUM is because your target module doesn't have a common dimension to a list formatted line item in your reference module. The best practice method for what you are trying to do is to use DISCO. In this case we need a system module which is a single module with one dimension, in your case the transaction module or reference module. Calculate once, refer often. Here's an example. I use countries and product but you could use as many dimensions as you want. The transaction module (reference module) only has the values we need and is keyed on a unique value that identifies the row. If you have a time dimension you should dimensionalize that and it should not be part of your key. Then we build a system module using the keys of the transaction module. Now we can use a SUM function in our output module. Notice how the output module has the same dimension as the list formatted line item in our system module. And we get the sales to sum on the country dimension!
... View more