BPC Embedded: Static (Non-Rolling) Planning Cycle - 2 Years - Exits or A Better Option?

[former_member192555]

Case

I am trying to define a column structure where I have a combination of Category/Version and Time infoobjects. The query

Selection:

• Fiscal Period (1st planning period in the planning cycle in the first year)
• Category (Forecast1, Forecast2, etc)

Example:

By selecting Forecast and Period 2018.005, we should set the range 2018.001-2018.004 to Actual category/version and 2018-005-2019.012 to Forecast.

Exits Solution

I was able to achieve it by defining 11 exit variables for each period 2018.001-2018.011 and using the restricted key-figures functionality. The second year is always Forecast so no need for additional variables.

I don't like this approach as it calls 11 times the exit BADI. I believe it has a bad impact on the performance which has an explanation.

I tried to use just one exit variable and then overwriting the rest manual non-input type variables with a default value, but I wasn't able to Modify/Overwrite i_t_var_range as it is not allowed.

Question

Is there a better and more efficient way to create/develop that scenario? At least from the performance perspective?

[former_member192555]

@John Hawk,

In that scenario, I don't know how I will switch category relevant to each period? I would have 1 RKF with 24 time members compared to 24 RKFs. Working with just one RFK won't allow me to switch category?

@All

There was an improvement by enabling the parallel execution of the query.

[john_hawk]

Hi Emil,

Consider using a variable on the fiscal period as a filter. Let the Fiscal period then simply be displayed as a column header.

Apply the category as restriction in restricted key figures.

John Hawk