Skip to Content

Planning Calculations P *Q

In the workshop and demo model, an average price is calculated (over 'all products') as gross sales / quantity...

However, in real-life, actual product prices need to be used. In member formulas, you then have to use Exception aggregation to make SAC work on the lowest level. However that is detrimental for performance.. and dependent member formulas in general too. Instead, we could opt to use Data Actions, but then VDT doesn't work. Or 1 model vs multiple model approach pro's and con's... It's always one limitation over the other... a constant balancing act.

Is there a best practice how all SAC planning features can be leveraged, without duplication of objects and without running into obvious limitations on each planning model design decision?

Add a comment
10|10000 characters needed characters exceeded

Related questions

0 Answers

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.