Skip to Content

Error when using Base Level Time members with YTD Measure

Hi All,

I've been searching around and found several threads and notes that slightly match my issue, but not found anything that seems to match exactly.

We've recently upgraded our SP levels from CPMBPC 801 SP 3 to 801 SP 10 on BW 7.31 using BPC 10.0 NW and since our Production system was patched have found that when executing any EPM Reports in Excel using the PERIODIC Measure, the Time Dimension can be used at Base Level and all Parents with no issue. If we try the same thing with the YTD measure it gives an error (see below). However, the error is restricted to the Production system only and only on one Environment. When using YTD on another Environment the Base Level members can be included without error.

code: UJO_READ_EXCEPTION_018

severity: error

description: MDX statement error: Value 2017.01 0HIER_NODE for characteristic /CPMB/EMD9S9O unknown

I'm not sure if it's related at all, but I found that for this Environment only and only in Production that there is an extra entry in the UJ0_PARAM_APP table for the Models within this Environment called "ACCOUNT_TYPE_ALIGNED". I'm not sure why this is in this table or when it got there, but it is a difference between this and other (working) Environments and systems. Some of the Models are marked "X" and some blank, but the error appears to be in all of the Models of this Environment (NB: QTD is effected in some but not others). Is this likely to be the root of the problem? Should I delete these from the UJ0_PARAM_APP table and if so can I do this without other consequences?

I've also seen some discussions suggesting that changing the UJO_PARAM table entry for "ENGINE_TYPE" to "CL_UJO_QUERY_BASE" may work. The current value that I have for this in Dev, QA and Production is "CL_UJO_QUERY_MDXPTD2" and as I've said already the Dev and QA systems are working fine, as are the other Production Environments - it's only the one Environment in our Production system that has the problem. As such, I don't think this the right solution, but willing to be convinced otherwise.

NB: Our Models use Storage Type PER (PERIODIC).

Many thanks in advance.

John

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Dec 16, 2015 at 01:09 PM

    Just to clarify (as I don't think I was 100% clear) I can execute a query using any of the PERIODIC, QTD or YTD Measures using TIME Dimension Parent Members, but as soon as I try and use a Base Level Member it shows the error mentioned above.

    PERIODIC works perfectly and has no problems, QTD shows errors in some but not all Models and YTD always seems to have errors in all of the Models of this one Environment.

    I've checked for differences in the MDX formulae for PERIODIC, QTD and YTD of one of these Models against a correctly working Model in another Environment, but the same system and there was no difference.

    The only difference I've found to date is the inclusion of "ACCOUNT_TYPE_ALIGNED" in table UJ0_PARAM_APP. I'm tempted to remove this to see if it makes a difference, but I'm not sure if removing it will create other issues?

    Regards

    John

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 16, 2015 at 12:24 PM

    Hi John,

    What is your BW 7.31 SP level?

    Vadim

    Add a comment
    10|10000 characters needed characters exceeded

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.