Hierarchy Key Date

[Former Member]

I've noticed something strange in our system.

We have queries defined using a time-dependent hierarchy for which we specified a key date different from the query date.

Now I cannot change it because the selection options for key date are greyed-out. Even creating a query from scratch with the hierarchy results in greyed-out key-date options on the hierarchy. It defaults to the key-date of the query. Can this be a change in behaviour after upgrade to 3.5?

Regards,

Eric

[Former Member]

Hi Erics,

Please try to evaluate if the OSS Note # 801980 "Time-dependent display hierarchies with query key date" is applicable.

Best regards,

Eugene

[former_member635540]

Hi Eugene

However I don't think the key date of query is what I need for key date of time-dependent hierarchy.

we need to know why the input of key date for time-dependent heirarchy in query desinger is disabled.

eric

[Former Member]

Hi,

I’ve made an additional search for OSS notes. Found a lot, concerned mainly on incorrect hierarchy or query key date.

Found also very strange note, # 674220 “Date entry not valid for time-dependent hierarchy structure”:

<b>Symptom

For characteristics with time-dependent hierarchy structures, the

hierarchy validity date is always the key date of the query

Other terms

Query, time-dependent hierarchy structures

Reason and Prerequisites

Programm Error

Solution

The date radio group buttons available for Key date

has no meaning, when hierarchy structure is time-dependent. The validity

date for hierarchy will always be taken as the key date of the query.

in this case. Hence, kindly ignore any other date entered in this field.

A corrective action will be taken in the future release to stop

entering any other date.</b>

It might be understood that hierarchy key date should always be as a query key date. Though the note was applicable to earlier releases but it could be read as that in future releases this option for hierarchy key date is going to be disabled.

I’ve searched BW for 3.5 SP notes. Found nothing about this option to be disabled. Moreover, in my system this option is enabled. So, if there is a bug, I couldn’t find anything usefull.

Documentation says that this option is to be enabled for time-dependent hierarchies only. So, if your situation is not caused by a bug, then something might be wrong with your hierarchies. Please look directly in SE16 at your H, I, J & K hierarchies tables, try to find something unusual. Maybe DATEFROM or DATETO values are missing in H table. Maybe the hierarchy is not active or corrupt. Or something.

Should you have found nothing, the last resort is to raise OSS note to SAP.

Best regards,

Eugene

Message was edited by: Eugene Khusainov

[former_member635540]

Hi Eric

Yes, We meet the exactly same problem as you do, our version is also BW3.5, is any one able to help us out?

or Eric, have you solved this problem by yourself?

Thanks and best regards,

eric