on 2015 Sep 30 8:35 AM
Hello all, URGENT
With EPM ADDIN SP23, BPC10.0 .NET4.0 build 9256 we suffer from exotic and wide-scale BASIS abnormal end ABENDS like
UJ0_READ_EXCEPTION_016 and
Data Length exceeds digit limit of current model..
on big scale..
See the enclosure please.
Do you have any suggestions and for Notes? We are really suffering in our project because of this!
Your remarks are highly appreciated!
Request clarification before answering.
Hello BPC stars
Please be carefull with MDX calculations in BPC10.0, when Null, 0 positions are multiplied.
MDX has challenges working with NULL, as they result in Data Overflow , because NULL can be mathematically defined as 1/billion trillion.... And BPC10.0 has data limit challenges with that.
Creating UJ0_READ_EXCEPTION abends around.
So check to prevent NULL conditions entered in you data and write MDX code checking like
When <> NULL before any MDX RECs
Just some very very hard learned lessons from recent practice!
kind greetz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, but what MDX calculations you are talking about?
What do you mean by "So check to prevent NULL conditions entered in you data and write MDX code checking like
When <> NULL before any MDX RECs"???
What is MDX REC??
Vadim
P.S. When we use syntax like *WHEN/*IS/*REC/*ENDWHEN - this is not MDX syntax at all!
Hello Vadim,
Yes , I have to expand. It is during very simple MDX #account = acct1 x acct2 x 30 calculations
and
with SQL Script *WHEN/*IS/*REC/*ENDWHENs
In both cases BPC crashes and creates DATA LENGTH EXCEEDS DIGIT LIMIT OF CURRENT MODEL errors. Even if we have a simple Planning Model with Statistical Accounts.
SAP Platinum Support told me that BPC MDX and SQL has difficulty with Multiplications involving NULL positions [that is having key figure 0, Null]...
We are investigating since two weeks now, without any resolution!
kind regards, eager for other reactions
Dear Alexander,
Can you please check the following SAP Note:
1829297 - Large Key Figure support for Planning and Consolidation
10.0
I hope it helps.
Best regards,
Nedra.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nedra,
The issue is not about enabling "Large Key Figure support..." but about the report execution generating very long number. Possible reason is dimension member formula that has to be analyzed and corrected.
Vadim
P.S. If we look on the error screenshot we can see that the value is 28 integers and 4 decimals - even more then allowed after Large Key Figure: 24 integers and 7 decimals
Hi Alexander,
Do you use dimension member formulas in this model?
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.