cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

YTD data is not calculated correctly

Former Member
0 Likes
755

Hi,

Wondering if anyone has some idea on what the problems are here.

Issue description:

1. In a Periodic model on BPC NW 10.0 800 SP13, YTD value is not calculated correctly as shown below. Somehow month July YTD data take July Periodic data and treating July as the first month and YTD data continued from July onwards again. Revenue is INC accounttype, This seems to only happen to INC/EXP accounttype.


2. Example of Time Dimension is shown below

Any ideas what to verify?

Many thanks

Jingjing

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Likes

Hi..

We faced the same issue. It resolved when we created whole new environment with copying from this environment. As in our case it was giving issue for only few environments.

No Idea about the cause.

Regards,

Priyanka

Former Member
0 Likes

Hi,

Please check your YTD formula using program UJA_MAINTAIN_MEASURE_FORMULA in SE38.

Best Regards,

Deepak

former_member196060
Contributor
0 Likes

Note 2036295 if you are using HANA

Former Member
0 Likes

Hi Hengye,

Not on HANA I am afraid. Trying out note 2131112 at the moment. If it does not work. Might have to create a support ticket with SAP.

Thanks

Jingjing

former_member186338
Active Contributor
0 Likes

I think the issue is related to non standard half year level.

Vadim

former_member186338
Active Contributor
0 Likes

Try (for test) the following levels in TIME hierarchy:

YEAR - Year TOTAL

QUARTER - Half year H1,H2

MONTH - Quarter Q1,Q2,Q3,Q4

DAY - Month JAN-DEC

I have never read notes about supported setup of TIME dimension with Half year hierarchy level.

Vadim

Former Member
0 Likes

I have replicated four levels (Year-Total, Half Year- H1, H2, Quarter-Q1, Q2...Months- Jan etc.) in the environmentshell. I could not reproduce the issue . So wondering if anything else could have impact on this? I also compared time dimension properties with environmentshell dimension. They are identical.

Thanks

Jingjing

former_member186338
Active Contributor
0 Likes

Try to create a new model in you environment with the same dimensions as you have in the model with issue?

Try to create new TIME dimension and a new model based on this new TIME dimension...

Vadim

P.S. In general you have to find the way to reproduce the issue!

former_member186338
Active Contributor
0 Likes

"BPC NW 10.0 800 SP13" - old, and I also think that BW SP is also old!

Please update to the latest BW SP! Use search, it's a well known issue...

Vadim

Former Member
0 Likes

Hi Vadim,

Thanks of your reply.

This issue does not occur in Environmentshell. I have done some research and could not find any evidence of it as a known issue.

I came across a known issue relating to incorrect periodic data in YTD model (note 2136030 and 2131112) This issue is relating to incorrect YTD data in a periodic model. Could this be the same causes??? Is this what you are thinking?

Thanks

Jingjing

former_member186338
Active Contributor
0 Likes

I am unable to tell you the exact note for your issue but upgrading to the latest BW SP will solve your issue with 99% probability

Can you provide complete version info? Including BW SP...

Vadim

former_member186338
Active Contributor
0 Likes

Ups, sorry - I have found half year nodes in your time hierarchy...

Then no warranty that it will work! BPC do not officially support 4 level hierarchy in TIME dimension...

Vadim