What are the best practices in matter of entity dimension design?
Yet I was thinking of creating one hierarchy with all the base members of the application in order to increase consolidation speed for the other hierarchies. Is this correct?
Thanks a lot for your help,
There is no best practice since each client has different requirements.
However, creating a flat hierarchy with all the base entities is usual because a) you increase the spread of calculating the group results (less entities) and b) you are sure that you see the correct contribution of each base entity to the group. But again there are other similar approaches that are usually will fit client's requirements.
There are various ways you can improve hte performance of the consolidation.
1. Start from Rules > Check if they are running for all value dimensions > change that to run for Entity currency and entity currency Adjs
2. Extract data and see if you have zeroes in you app > Clear zeroes by adding a logic to you rule file.
3. Check if all scenarios use all Business logics > If Actuals use certain and BDGT use certain. Divide the same based on scenarios and control accordingly
4. Turn Off Data Audit if you are not using. Clear log files always.
5, Lastly see if Metadata was not setup correctly and make design changes if necessary.
There are various ways, you can approach. Hope this helps.
There are always ways to improve your consolidation. If you are not familiar with the task, it is more useful to seek advice from a consultant.
I believe that the first step is to add timers in the rules and figure out which part of the rules require more time. After the that you will start working on individual items based on your client requirements. There are cases in which 1minute more in consolidation can create such value for the user which will be acceptable.