Hierarchy is not displaying correct in Bex Report

[Former Member]

Hi all,

   I am having an issue with Hierarchies.An  Hierarchy which is correct in RSH1 are displaying incorrect in bex reports.In Bex report hierarchies are still pointing to old values where as in BW system they are up to date. Can some body help me to resolve this issue?

Thanks

Sai Mamidi

[former_member220624 · Accepted solution]

Hi Sai,

Please try re-activating the hierarchies and disable the cache and try to execute the report in RSRT.

Also are the hierarchies time-dependant ?

Regards,

Amit

[cornelia_lezoch]

Hi Jacko,

1) activate the hierarchy.

2) check for time dependencies and compare backend and frontend for the same date.

regards

Cornelia

[Former Member]

Hello All,

   Thank you for the replies. I have tested the 0cust_sales  hierarchy by running in report RSRT and  Bex Analyzer and it is showing wrong values(child is attached to previous parent node) in Bex report. I did activate the hierarchy and yes this is Time dependent hierarchy.

Thanks

J

[former_member220624]

Hi Sai,

In that case do you have any time level restriction in your BEx query.

Do you have valid hierarchies for those time frames?

In BEx setting for hierarchy check if you have enabled current date or is there any other setting which you have used.

If possible share a screenshot of the same.

Regards,

Amit

[Former Member]

Hi Amit,

     I have restricted the query with 0calmonth variable and the hierarchy is enabled to todays date but still query is showing wrong hierarchy values.

Thanks

  J

[former_member220624]

Hi Sai,

This is really strange.

So you do have data for the time frames you give in the prompt.

Let's do one thing. Drill down with 0Cust_sales info object in the Query output and further by calday.

This might take us closer to the root cause.

Also share some screenshots of how is the data output  and the hierarchy from rsh1.

Regards,

Amit

[cornelia_lezoch]

Hi Jacko,

the 0CALMONTH has no influence on the hierarchy.

You need to check what is the value of the key date of the query.

It is given in the query properties.

If there is no setting or variable used, then the key date is the day the query is executed.

regards

Cornelia

[Former Member]

Hi Cornelia/Amit,

     I have selected key date as todays in query hierarchy setting.Please see attached  screen shots of hierarchy and bex query  here. Node Duncan should be shown under IBA as in RSH1 screen short but it is showing under Independent retailer  in Bex report screen shot.

Thanks

J

Filter

Hierarchy Date

Bex Report

RSH1

[former_member220624]

Hi Sai,

Just to find the root cause càn you create a hierarchy variable on cust_sales and check the f4 values in the prompt.

Regards,

Amit

[Former Member]

Hi Amit,

    i am getting old values in the prompt for hierarchy variable.

Thanks

J

[former_member220624]

Can you attach the screenshots here.

1. From the Query designer showing the variable used.

2. prompt value showing the older values.

Also can you activate the master data for customer sales info-objext or run the ACR for same and test.

Thanks,

Amit

[Former Member]

Hi Sai,

First of all, please narrow down if the issue could be reproduced in RSRT- html mode. If yes, try to deactivate cache during runtime to see the result. If still the hierarchy is outdated, try to check the hierarchy itself. For example, check if the updated hierarchy is mapped to the hierarchy I table and K table. I met some similar issues  in the past and solved it by reactivating the hierarchy to get the tables updated.

Regards,
Cecilia

[Former Member]

Hi Cecilia,

    How do i check the updated hierarchy is mapped to the hierarchy I table and K table since i table is having too many SID values for that particular hierarchy node when compared to K table?

Thanks

J

[Former Member]

Hi Jacko,

Just follow the steps:

1. In RSH1, find the relevant hierarchy. Find the "hierarchy ID" from "Header data" button.

2. in table RSRHIEDIR_OLAP, input the above  "hierarchy ID" in field HIEID to get the HIESID.

3. in hierarchcy K table,  input the relevant node name and HIESID. see if it's correctly saved in the table.

Br, Cecilia

[Former Member]

Hi Cecilia,

      Thanks for reply. I have checked the HIESID in K table and RSRHIEDIR_OLAP. They are not matching at all.Is this reason for my issue? If so how do i solve this?When i am activating this hierarchy using program RRHI_HIERARCHY_ACTIVATE i am getting message "there is no modified version for this hierarchy".

Thanks

  J

.

[karthik_vasudevan]

Hi Sai

What is not matching here. Could you please share some screenshots. If the hierarchy is activated, there is nothing to mismatch in normal scenarios.

Better do a hierarchy check in RSRV. If it throws some error, post it here. There is an option to repair as well, but lets decide that if we get the error.

Hope this helps

Regards

Karthik

[Former Member]

Hi Cecilia,,

when i do rsrv test on this 0Cust_sales hierarchy iam getting below error

To rectify this error i have run the correction program RRINCLTAB_REBUILD but  the error still exists.

In KTable of 0cust_sales i am having 2 different HIESID in addition to the one common HIESID seen in RSRHIERDIR_OLAP. Do i need to delete these different HIESID from KTABLE? If so how can i delete from the closed table?

KTABLE

RSRHIERDIR_OLAP

Thanks

J

[karthik_vasudevan]

Hi

If you go the last entries in the table, you would the valid from and valid to date. Even if there are multiple entries, you don't have to worry, I think. If all the validity dates are different, then its proper data which is normal.

After repairing the errors, did you activate the hierarchy and executed the report?

Regards

Karthik

[Former Member]

Hi J,

You don't have to delete the other HIESID entries in K table. They are for other hierarchies.

The RSRV error should not be related as well.

For this, please go ahead to check if the node Duncan and the upper node has the correct relationship in I table. In there, PRED is the upper node SID, SUCC is the node SID for Duncan. From your last screenshot, just enter 20481 in HIESID and W in SVER, and  2997- in SUCC, then find if PRED presents the correct node SID for the expected node IBA.

Regards, Cecilia

[Former Member]

Hi Cecilia,

     Yes they have correct relation ship in I Table.

Thanks

J

[Former Member]

The table looks good so the hierarchy itself should be consistent.
I then have another thought that if the temp tables used in the query execution are wrong~~~

you may get the temp table name from SQL during query execution, and check the nodes relationship in the table directly. Alternatively drop the temp tables by report SAP_DROP_TMPTABLES. Then the temp table will be recreated when you run query again.

Regards,
Cecilia

[karthik_vasudevan]

Hi Sai

Since when you are facing this issue? was there any change in hierarchy recently?

Is the hierarchy in ECC and BI RSH1 matching perfectly?

Please run the query in analyzer and in RSRT to see if its an issue only with portal

ALso let us know the bi version that you are currently using

Regards

Karthik