Strange parts of my construction at Level 300
- The numbers on the screen I constructed are incorrect. The values of PY Actual and CY on the Sales Planning Screen are the same. Which part of the structure or operation do you think is causing this?
- The dynamic year selection for SET Lock Planning and SET Unlock Planning, which are DM Procedures, is not working properly. When selecting Data Entry member from Version Status, All Year is selected, even though only 2023 should be selected.
- Also, the Lock Data view on the Administration Screen looks strange. Although the configuration should be the same as the model.
I hope you can give me a solution or hint for any or all of the above errors.
Answers
-
Dear @i
When numbers are incorrect this is most possibly due to wrong selections or calculations.
Your screen shows that all years are selected (8/8)—what would you expect "actual" and "previous" to be?
It seems to me that all points in your list are related to the administration. The dynamic select uses the cube "SET - DE - Planning Year" which should be populated like this
If that's the case, the dynamic select should look like this on the screen (your screenshot)
…and like this in the procedures that calculate the lock/unlock
Regarding your third point—"strange looking" is something that I can't interpret. It would be nice if you could provide a screenshot of that.
Best,
Helmut0 -
Dear @i
apart from the first screenshot the others were not visible at first, sorry.
To enter locks into the cube you'd need to set the "Show all" on the rows like here
Since the cube is cleared in the procedure and you need to populate it manually, even rows with no values need to be displayed and that can only be achieved with "Show all".
Best,
Helmut0 -
Dear Heimann
I think "Actual Previous Year" means the actual sales figures for the year before the selected year. (When 23 is selected, it is the actual sales figures for 22). If so, it makes sense that PY Actual is not displayed correctly when all cities are selected. However, CY and PY Actual are equal even when I select only 23 in my building.
According to the Functional Test, when Sweden is selected as the country and 23 is selected as the year, it should be displayed as follows.
The dynamic selection uses SET DE Planning Months instead of SET DE Planning Year. It have been renamed.
In the two procedures Lock Planning and Unlock Planning, 23 is selected as the year dynamic selection at first, but when Data Entry is selected in Version Status, why is All year dynamically selected? Where do I set SET DE Planning Months so that only 23 is dynamically selected?
Regarding Lock Data View in the Administration Screen, Show All is already checked when I first asked. I don't understand why it doesn't look similar to the sample image.
My building
Sample
0 -
0
-
Dear @i
regarding the question with the CY/PY comparison: could you please doublecheck that the layout is built according to this:
Regarding the Administration screen: I assume the filter is responsible for you not seeing any data. Could you please doublecheck that the cube "SET - DE - Planning months" is populated?
That might be the reason for the procedures not working properly, as well.
Best,
Helmut0 -
Dear @i
The cube SET - DE - Planning Months on which the dynamic selection is based, is dimensioned by Month and Version, Month is a child to Year and Version is a child to Version Status. If Version Status="Data Entry" is selected, this obviously will select the Version(s) currently related to "Data Entry". In the picture below that would be "FCST 3+9"
Secondly, it will select all related months; according to the Planning Months Settings that should be Apr.23..Dec.23
This month-selection is then used in the dynamic selection for the year, resulting in "2023".
If, after the selection of "Data Entry", all years are selected, that means the cube SET - DE - Planning Months isn't populated correctly.
Best,
Helmut0