on ‎2019 Mar 31 12:27 PM
Hi Vadim, Hi Community,
We use more than 200 formulas to calculate business key figures. Since we've updated the system, we've noticed that some of them are wrong when used with others on the same sheet. In former times we could solve these kinds of problems by adding/adjusting SOLVE_ORDER.
This is my basic understanding of SOLVE_ORDER: SOLVE_ORDER is especially of interest when you use nested formulas (this is supported with HANA MDX) since you have to make sure that the prior formula has finished work before using the result in the next formula.
now my set up:
- SAP BWonHANA 7.5 SP10, HANA 122
- 1st of all I created a BPC Standard Model based on ENVIRONMENT shell
- I used the delivered model: planning to create an easy sheet
- I activated member formulas on account dimension
- rows: 2 base members (PL010, PL020) from account dimension, 1 node (PL100)
- columns: 12 periods of 2017
- Report: BPC_MIGRATE_TO_HANA -> done
- Environment: ACCELERATOR_ON = X -> ok
- Models: Planning, Consolidation, Ownership, Rates -> ENABLE_HANA_MDX = X -> ok
1st scenario: I entered values for each period on account PL010, and for each 2nd period on account PL020
and I've created 2 member formulas:
- 1st Member Formula: [PL100_MF] shows the result of node [PL100]
- 2nd Member Formula: [PL100_MF_NF] shows the result of Member Formula [PL100_MF]

The result of both member formulas is correct as expected.
In the 2nd scenario, I've added SOLVE_ORDER to both member formulas to create a wrong result on purpose.
SOLVE_ORDER of the 1st member formula PL100_MF is much higher then PL100_MF_NF which should lead to a wrong result.
But the result is still correct?! how is this possible? Where can I find precise rules for SOLVE_ORDER? Or are they not relevant anymore?

The only error I can create is when I set SOLVE_ORDER to lower than 3 which is the standard solve order.
There is one website form Microsoft on the MDX issue but I could find useful information.
https://docs.microsoft.com/en-us/sql/mdx/mdx-function-reference-mdx?view=sql-server-2017
Request clarification before answering.
In general, you don't need solve_order to properly process nested formulas.
Solve_order can be used in some special cases with multiple dimensions involved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To my mind nested formula has higher priority then SOLVE_ORDER!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.