Well, that's what SUM( ) sometimes says. It doesn't perform its duty correctly when you use multiple auxiliary key-figures in macro steps and then you use the SUM( ) on these auxiliary key-figures.
This was identified with some unexpected results in one the BiG macros we had, and was given to SAP (almost an year back). SAP, after its kind attention toward the problem has come up with a minor development and the associated NOTE can be seen at 1895631.
But beware: this note only has solved the problem we had gone with. And when we confirmed on the success of the fix with the reported case: the note was released to all the customers. But I cannot guarantee on this yet, I was not in the project and I heard some other problems later, so: implement it at your own risk :razz:
Note:
- Auxiliary tables are global tables, they store the values of auxiliary key-figures not specific to a planning object - so, be ready for any misunderstandings in the macro calculations when you use auxiliary key-figures :wink:
- Best fix to solve the misunderstandings of 1) is to initialize the auxiliary values (you can do this in macro settings [double-click on the macro and don't check "Do not Initialize Auxiliary Table"]) ℹ
- SAP Managed Tags:
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
