MDX LAG in Member Formula

[former_member214044]

Hi.

Using BPC NW 10.1 Standard on NW with HANA. A Periodic application used for planning.

ENABLE_HANA_MDX is not turned on.

In our Test BW environment. The following Member Formula:

([TIME].CURRENTMEMBER.LAG(1),[M_COSI])

M_COSI is an Account member.

Returns the following output:

I suspect that for formula in 2016.004 is looking back at 2016.Q1 for some reason. It does not behave like this in our Development environment.

Our time dimension looks pretty ordinary:

I am completely stuck. What am I missing?

Thank you for any help.

Mike

[former_member214044]

It is a lot better but i called out fixed too early. There is distinctly different behaviour now depending on wether ENABLE_HANA_MDX is on or off.

When OFF - it looks like it treats LAG as LEAD and then has a problem with the first month in each Quarter.

When ON it is almost perfect, but then has this strange issue around 2019.003, 2019.004, 2019.007. The amounts in periods 3 and 4 are overstated and the amount in period 7 is understated by exactly the amount overstated in periods 3 and 4 - eg it comes back to balance???

The following is dummy data, but explains our symptoms.

We have tried refreshing different slices of data and it looks like those periods in 2019 are always wrong and the pattern is the same.

Checking the Time Dimension for that area:

Nothing stands out to me here - The 'Calendar' total has been removed.

In addition we have run UJHANA_REFRESH_VIR_CUBE on the source Model.

Thanks again for any help

[former_member186338]

Have you deleted Calendar member?

Please perform tests on the fresh copy of environmentshell.