cancel
Showing results for 
Search instead for 
Did you mean: 

Time dimension doesn't work correctly

Former Member
0 Kudos

Hello, everybody.

We use SAP BPC NW 7.5 SP06.

We have 3 types of period in time dimension.

1. Monthly data

2011.TOTAL

2011.Q1

2011.JAN

2011.FEB

....

2. Quarterly data

Q.2011.YEAR

Q.2011.Q1

Q.2011.Q2

....

3. Yearly data

Y.2011

Y.2012

....

Monthly data works ok.

But we have problem with quarterly data for accounts AST & LEQ.

If EVDRE report contains only Q.2011.Q1 it shows data. But if EVDRE report contains Q.2011.Q1 and Q.2011.YEAR it doesn't show any data for Q.2011.Q1 and Q.2011.YEAR.

We have tried to play with TIMEID property, make different hierarchy for each type of period. But the problem still exists

Help!

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos

I upload my dimension file [here|https://docs.google.com/leaf?id=0B5fonlyQmR0LNzA0YzE3OTgtOGNkNy00N2JhLWE5ZTMtMDMxMGU3YjQwMTFl&hl=en_US].

Former Member
0 Kudos

I have similar issue and we are also in SP6 in 7.5NW.

Can you review the OSS notes as follows

SAP Note 1613715 - No value retrieved on node members with

space in member ID

Note Language: English Version: 4 Validity: Valid Since 29.07.2011

Summary

Symptom

No data would be retrieved on the parent node if the member ID includes

char of space when calculated time hierarchy is enabled.

Other terms

UJA_APPSET_CALC_HIER

Reason and Prerequisites

This is caused by a program error.

Solution

Apply this note or upgrade to BPC75 SP09.

Former Member
0 Kudos

Hi,

I think, it could be due to the 'LEVEL' property. Quarter is generally a calculated level as you have it in your first hierarchy. But for the Q.2010.Q1, you have also defined the level as 'QUARTER'. May be this is causing confusion in calculation.

- just to confirm, you could try only having the PQUARTER information only in the time dimension member sheet and process the dimension. Run the report to see if all okay.

- Else you might need to change the 'level' property to a different valid value and also have a look at your measures definition also.

Thanks,

Sreeni

Former Member
0 Kudos

Our account dimension doesn't contain char of space in ID property.

Value PQUARTER for property LEVEL is invallid. Admin Console caused an error. Only YEAR, QUARTER, MONTH, WEEK, DAY can be used for LEVEL property for Time dimension.

Former Member
0 Kudos

The space can be in any dimension member and the time dimension may malfunction as a result of this. We are also in SP6 in NW7.5

It will be good to raise OSS message and look for SAP solution. Alternative solution is to apply the OSS and see if the issue is resolved. There could be someother OSS note, to fix the issue. I will hunt out.

Edited by: ManiIyer on Aug 10, 2011 7:52 PM

Former Member
0 Kudos

We don't have any special chars (including space) in dimensions IDs.

The exception is dot char in time dimension.

Former Member
0 Kudos

That is the same case with me. That means for no explicit reason this issue happens in SP6

I have send the message to SAP and waiting for the response. Will keep you posted on the outcome

Former Member
0 Kudos

Thanks.

Our time dimension's properties already have this values.

What TIMEID should I set for the same periods?

As far as we have 2 time hierarchy, we have the following members (for example):

2011.Q3 QUARTER 2011 Q3 20110003

2011.JUN ...

....

Q.2011.Q3 QUARTER 2011 Q3 ?????? (what should be set here?)

Former Member
0 Kudos

Hi,

I didnt understand why do you have different members for same periods. Even if you have multiple hierarchies, you can use the same member in them.

By the way, in the report, are you using the first hierarchy or the second one?

I am not sure what's going wrong. It would be difficult to suggest anything without looking at it.

Former Member
0 Kudos

Thank you!

I put on the ISBEGINNING property according to your recomendation, but the problem still exists.

Could your please recommend how to fill LEVEL, PERIOD, TIMEID properties for several time hierarchy.

Former Member
0 Kudos

Hi,

Level can be YEAR, QUARTER, MONTH.

Period can be TOTAL, Q1, Q2, ..., JAN, FEB, ....DEC

For Timeid, you can follow the below:

1. For the months, you can keep the format as YYYYMM00. So, for 2011.JUL, it would be 20110700.

2. For Q1 - YYYY0001, Q2 - YYYY0002, .....Q4 - YYYY0004, TOTAL - YYYY0005

Hope this helps.

Former Member
0 Kudos

It doesn't have ISBEGINNING property.

How should I fill this property?

Former Member
0 Kudos

Hi,

Please add a property ISBEGINNING with length 1. The first members in a hierarchy level should be 1 and rest should be 0.

TOTAL should be 1. Q1 should be 1. JAN should be 1. the rest should be 0.

Hope this helps.

Former Member
0 Kudos

In ApShell time dimension contains only monthly data. It works ok. If I removed monthly or quarterly data the other works fine in my appset. They don't like each other.

Former Member
0 Kudos

Hi,

Strange. Never seen anything like this. I have worked so many instances with different time hierarchies.

How does you ISBEGINNING property look like?

Former Member
0 Kudos

Thank you for reply, but the problem not in the AST/LEQ behaviour.

My quarterly data doesn't have monthly detalization.

Compare 2 EVDRE:

1)

____________ Q.2011.Q1

LeqAcc1 _____ 100

2)

____________ Q.2011.YEAR ___ Q.2011.Q1

LeqAcc1 _____ 0 _______________ 0

Why does 1st report show 100 while the 2d report shows 0 for the same data point?

I think there are 2 posible reasons:

1. SAP BPC NW error.

2. My Time dimension's properties are incorrect.

Former Member
0 Kudos

Hmmm...

Do you see the same behavior in Apshell?

Former Member
0 Kudos

Hi,

The behavior of the AST and LEQ is a bit different from INC or EXP.

If you look at 2011.Q1, the data will be same as 2011.MAR (assuming you are following the calendar year and not fiscal year). So, if you dont have any data in 2011.MAR, then you wont have anything in Q1 either. The same applies to 2011.TOTAL. This will be same as 2011.Q4.

The reason behind this is AST and LEQ are the balance sheet accounts. And these accounts are always considered as the year to date values. So, while calculating Q1, it doesnt add JAN, FEB, MAR. Instead, it takes the year to date value, which basically corresponds to MAR.

Hope this helps.

Jeffrey_Holdema
Active Contributor
0 Kudos

I have moved this thread to the [BPC NW forum|;. Notice the sticky [note|; at the top of the FPM - General (PCM, FC, Other) Forum whereby we announced new dedicated forums for BPC which are the proper place to post your questions regarding BPC in the future.

[Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]

SAP Labs, LLC

BusinessObjects Division

Americas Customer Solutions Adoption (CSA) team