Level300_Module 303: Step "Adjust Planning Data Model Procedures", Actual Months are wrong

Hi,

I have an issue in this section. I have set the FCST 3+9 as the data entry version. And now I am in the step above.

In the Forecast group I shall add a step after 15 as below

{7F300CE6-344A-4FD7-9B15-666A5F53DD64}.png

I would assume that Actual months and period <>0 should be three as FCST 3+9 is defined, but I always get nine. This is the same issue why I have started 5 times from the scratch but I am not able to find the moment I drift apart.

{917E718B-535D-484D-960E-2D471803D64C}.png

As you can see the months are nine, the quarters are three.

{91026B1B-297D-4A04-BBC5-4DCB0D2D193D}.png

Same issue occur for Planing months for step 18. It should be nine but there are twelve.

{2F3BA5D9-EE27-4F9E-82F8-EF89414FE156}.png

{CB6575BB-B92B-4C4C-80CA-94901224F0C5}.png

As those selections are wrong all further steps are corrupted.

Find more posts tagged with

Data Modeling

Board Academy

Procedures

Time range

Board 14

Accepted answers

Sebastian

ok I got it now, the steps are not linked to the actual "version". I was assuming that steps in procedures refer to the actual selected version. But they do not. FCST 3+9 would be only 3 actual months, but the step lists months until Sep '23 which is the maximum defined period of time (all possible months). Planning months are analog. I assumed values would be "on-the-fly" meaning including the actual selected version. But the calculation happens only after triggering.

Marcus Smith

Hi @Sebastian

Thanks for providing your insights. Yes. No procedure knows where they're going to be executed. So, when they are triggered from a screen, it checks all possibilities and selects only those Months in which the concerned cube has values.

Thanks again!

All comments

Marcus Smith

Hi Sebastian

I've checked and can confirm that the selection step is perfect in the procedure, and the months appearing 9 and 12 are correct.

Can you please let us know at what point of the course, or screen, you find your values wrong? Help us with a screenshot.

Sebastian

So, you will say that 9 months for actual and 12 months for planning months in the FCST 3+9 version are correct? As far as I understood FCST 3 + 9 = 3 actual + 9 planning months.

So when my version is FCST 3+9 and the dynamic selection for months based on the "Set - DF - Actual Months" is 9 in the current year can not be right. It should be 3 as defined in administration screen for that version.

Analog Planning months should be 9 not 12.

{BA00C6D6-58BF-4A77-8861-B35B879D062D}.png

Strange is, if I enter design mode for the Administration screen the view changes to

{110F688B-4145-42C0-999F-1F7E4F7D1D32}.png

and this is also the values which are the results in later procedure steps.

But when data entry is set for FCST 3+9 it is not logical that the result for dynamic selection of months based on "Set - DF - Actual Months" is 9.

{BBA94A64-2D72-4D44-83D1-C67A4ED93433}.png

{13411C59-73F7-43C3-83B1-5D157391C371}.png

Actual months should be Jan to Mar 2023 and no further.

Sebastian

If, like you say, the procedure in Board - Academy is perfect than I would like to hear the explanation for that.

As far as I understand it The initialize Planning Procedure should merge data for the first 3 months of actuals and the planning values from the last 9 months.

But it tries to take actual data for the first 9 months in 2023 while we only have actual data for the first 3 months. —> 6 months missing.

Then 12 Planning months data is merged which will cause duplicates for the first 3 months (maybe double maybe overwritten) . So the "PLN - DF - Sales/Expenses LC" can not be filled correctly.

Sebastian

@Marcus Smith could you explain?

Marcus Smith

Hi @Sebastian,

Can you please let us know on which part of the course you see the mismatch with your data?

Sebastian

Marcus Smith

Hi @Sebastian

Thanks again!