Skip to Content

PARENTH1 Hierarchy data lost after UJA_REFRESH_DIM_CACHE


I wonder if anyone has also experienced this problem before.

We have a Time-Dependent ACCOUNT Dimension. We have recently (less than one month ago) added PARENTH2 and PARENTH3. We have also recently added Member Formulas to the TIME Dimension

There have been a fair amount of manual input to the ACCOUNT Dimension in the last three months. Mostly to the H1 hierarchies (we don't get Master Data from ECC).

We started getting AmbiguousMemberID errors (last two weeks) when refreshing EPM Reports although none of our Dimensions have ambiguous members across them. Performing an EPM Refresh Dimension Cache seems to work, but the error does re-appear. Not always consistently.

As a result we ran UJA_REFRESH_DIM_CACHE, UJX0_CLEAN_DIM_CACHE and UJX0_CLEAN_TDH_DIM_CACHE to try and solve this.

After running these, all the PARENTH1 hierarchy data from the last three months was lost. This happened in the ACCOUNT, PCENTRE and SUPPACC (user-defined) Dimensions, too.

Anyone else experienced something similar? We can't seem to replicate on DEV / QA at this point.


  1. SAP BPC 10.1 on BW 7.51 SP03 on HANA
  2. Classic Model
  3. We use EPM SP29 or SP30.

Kind Regards


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Jan 04, 2018 at 07:52 AM

    If you have multiple hierarchies in one dimension it's easy to make an error configuring nodes (using common nodes in different hierarchies). Please check!

    In general you can load master data from text file instead of manual changes in web admin.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 04, 2018 at 09:07 AM


    Are you able to isolate the deletion of the hierarchy to the execution of one of the three UJA_REFRESH_DIM_CACHE, UJX0_CLEAN_DIM_CACHE and UJX0_CLEAN_TDH_DIM_CACHE, or did you run all three in sequence and only notice the deletion afterwards?

    It is most likely that this issue occurred after executing the UJA_REFRESH_DIM_CACHE program. While it is fairly common to see this recommended in the forums and even in incidents, I normally don't suggest running this specific program unless there is a clear disconnect between the BW system and BPC AND the BW system is verified as being complete and correct.

    The reason for this is that UJA_REFRESH_DIM_CACHE deletes data from the BPC cache tables and then refreshes this data from the BW tables. Normally, if there is any disconnect between the BPC specific tables and the BW tables we would expect the BPC tables to be the most current, therefore issues can occur when running this program if the BW tables are not correct. See for example note 2011283 regarding a similar issue with UJA_REFRESH_DIM_CACHE deleting member descriptions.

    I think the most likely case here is that the hierarchy was not in sync in BW and executing this program copied the out of date hierarchy back to BPC.

    From memory I believe there are several notes that correct issues of this sort. Without knowing your exact version and SP I cannot comment on if any of these apply to your case.

    If you cannot find any notes regarding this please open an incident with SAP Support and clearly specify the details of how you update the master data in the front end, if you have ever done any direct updates in BW, do you run any Data Manager packages to do so, do you normally transport master data from QA to Prod, etc and we can investigate for you.


    Peter Kreutlein

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Peter and Vadim,

      Many thanks. Both really useful suggestions!

      Vadim Kalinin. We have now got backups (.csv) of all the Dimensions, so I think we need to apply your approach.

      Peter KREUTLEIN. Noted. I actually want to get us to SP05 as soon as possible, but if we can't then I will get the BASIS team to apply the Notes you suggested. Naturally, through the landscape (Dev -> QA -> Prod).

      Much appreciate both your prompt feedback.

      Kind Regards


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.