Symptom
- When opening the table from story in Data Analyzer (current/new tab), the data does not load and give an error message as below.
The query executed with errors.
Caught exception : exception 42556: Extended dimension processing error : Can't read view '21962074-6611-4927-b175-110659917449'
Correlation ID: 17043462-9529-4074-8590-360348186124 - There are multiple models used in the story and also have applied linked analysis. But the table is created on a single model
- If we open any other table in the same story, which have the another model as source, there is no issue.
- When trying to remove the table (problematic table) and create a simple table with same model, this also have the same problem (tried in same page and new page).
- There is a calculated measure with formula. When trying to recreate the same formula in new story, we could not see same measures, but are available in the model.
Environment
- SAP Analytics Cloud (Enterprise) 2024.21.10
Resolution
The fix of the issue is included in SAC 2024.21.13 and later version.
- But in somes cases, the fix doesn't fully resolve the scenario in a specific story, if the story contains a calculated dimension which is required due to being referred to in a formula: both formula "Active Customer" and "Inactive Customer" use Calculated Dimension Active/Inactive Customer, which in turn depends on formula Active/Inactive Flag.
- Processing this calculated dimension involves over 4 million records on the HANA side, which exceeds the max result records limit.
- You can already see this limitation in the story, if you add the calculated dimension 'Active/Inactive Customer' directly to the rows axis, or if you select to show the formula measure 'Active Customer'.
- In general if a calculated dimension is too expensive to use directly in story, it will also be unusable in Data Analyzer - it's just that this is surfaced earlier in Data Analyzer due to a difference in how resultsets are processed.
- As the calculated dimension is not usable in story or Data Analyzer, it doesn't help for us to attempt to prune this calculated dimension in data analyzer requests, as it will still break as soon as the user tried to add it directly or via the derived formula measures.
- Therefore the recommendation would be to remove the calculated dimension from the story (because unusable), or redesign it to be less expensive, and to verify that the calculated dimension can be added to the table directly in story without breaking, as this is a prerequisite to use it in Data Analyzer after the jump from Story.
See Also
- 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
- Have a question? Ask it here and let our amazing SAP community help! Or reply and share your knowledge!
- 2487011 - What information do I need to provide when opening a case for SAP Analytics Cloud?
- 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
- Search for SAP Analytics Cloud content using SAP for Me, Google or Bing:
- https://me.sap.com/servicessupport/search#?q=SAP%20Analytics%20Cloud%20OR%20SAC&tab=All
- https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
- https://www.bing.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
- Note: Add relevant text or warning/error messages to the text search field to filter results.
- SAP Analytics Cloud Connection Guide
- Getting Started with SAP Analytics Cloud Expert Community page
- SAP Analytics Cloud Get More Help and SAP Support
- Need More Help? Contact Support or visit the solution finder today!
Your feedback is important to help us improve our knowledge base.
Keywords
Caught, exception 42556, Data Analyzer , KBA , LOD-ANA-DAN , SAC Data Analyzer , Problem
Product
SAP Analytics Cloud all versions
SAP Knowledge Base Article - Public