cancel
Showing results for 
Search instead for 
Did you mean: 

Query warning msg:Hierarchy in version was not found for key date 20061020.

Former Member
0 Kudos

One of our query includes two hierarchy variables in the row design which are called V Company Code and V Plant respectively for company code hierarchy and plant hierarchy. In the filter, we restrict the PO Requisition type = EMERG. When we run this report, get the following warning msg:

"Hierarchy V EMERG in version was not found for key date 20061020.

Message no. BRAIN685"

What causes the reason for the above error msg? How to resolve it?

Thanks in advance!

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

hi Edwin,

Our system is BW 3.5. The solution in this OSS Note says:

BW 3.50

Import Support Package 12 for 3.5 (BW3.50 Patch 12 or SAPKW35012) into your BW system.

But our BASIS has used Package 14 level already which should be more advanced than Package 12, right? Still don't know why.

Thanks

0 Kudos

hi Kevin,

not sure relevant Note 834855 - Error message BRAIN 365: Hierarchy with key date 99991231

hope this helps.

Summary

Symptom

An error message appears for a query:

The hierarchy <name> in Version <version> was not found for key date 99991231 (BRAIN 685).

Other terms

Query, hierarchy, authorization, hierarchy node, NODE_FROM_AUTHORITY_FILL_2

Reason and Prerequisites

This problem is caused by a program error.

The error occurs in the following situation:

1. The query contains a hierarchy whose name is time-dependent.

2. This hierarchy is determined by a key date that is variable.

3. The query also contains a node variable that can be input, whose default values are the authorized values. The nodes should come from the above hierarchy.

Since the key date for determining the authorized nodes is not yet established, the date in the program is 31.12.9999 and the system tries to use the authorized nodes from this hierarchy. However, the error message appears if there is no hierarchy for the key date.

Solution

In this case, the solution now involves the current day being taken to determine the hierarchy. After the "correct" key date has been determined, this is the date that will continue to be used.

BW 3.0B

Import Support Package 27 or 3.0B (BW3.0B Patch 27 or SAPKW30B27) into your BW system. The Support Package will become available oncenote 723258 with the short text, "SAPBWNews BW3.0B Support Package 27", which describes this Support Package in more detail, is released for customers.

BW 3.10 Content

Import Support Package 21 for 3.10 (BW3.10 Patch 21 or SAPKW31021 ) into your BW system. The Support Package will become available once <Z1>note 723263 with the short text, "SAPBWNews BW3.1 Content SP 21", which describes this Support Package in more detail, is released for customers.

BW 3.50

Import Support Package 12 for 3.5 (BW3.50 Patch 12 or SAPKW35012) into your BW system. The Support Package will become available oncenote 763340 with the short text, " SAPBWNews BW SP12 NetWeaver'04 Stack 12", which describes this Support Package in more detail, is released for customers.

In urgent cases, you can use the correction instructions.

To provide information in advance, the notes mentioned may already be made available before the Support Packages are released. However, the short text in this case will still contain the words "Preliminary version".