Symptom
When running a WebDynpro report and adding a field to the row axis the below error appears:
"500 internal server error"
Value <nn> is not a valid index; context node: <example>
A dump similar to the below one is raised in ST22:
Category ABAP programming error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_WD_CONTEXT
ABAP Program CL_WDR_CONTEXT_NODE_RANGE=====CP
Application Component BC-WD-ABA-RUN
Short Text
An exception has occurred that was not caught.
What happened?
The exception of class "CX_WD_CONTEXT" was triggered but not caught anywhere
in the
call hierarchy.
Since exceptions represent error situations, and this error was not
adequately responded to, ABAP program "CL_WDR_CONTEXT_NODE_RANGE=====CP" had
to be terminated.
Error analysis
An exception has occurred in class "CX_WD_CONTEXT". As this exception was not
caught, a runtime error occurred. The reason for the exception
occurring was:
Value <nn> is not a valid index; context node: <example>
Read more...
Environment
- SAP BW/4HANA 2.0 (DW4CORE 200)
- SAP BW/4HANA 2010 (DW4CORE 300)
- ABAP PLATFORM 1809 - Application Server ABAP (SAP_BW 7.53)
- ABAP PLATFORM 1909 - Application Server ABAP (SAP_BW 7.54)
- ABAP PLATFORM 2020 - Application Server ABAP (SAP_BW 7.55)
- ABAP PLATFORM 2021 - Application Server ABAP (SAP_BW 7.56)
- ABAP PLATFORM 2022 - Application Server ABAP (SAP_BW 7.57)
- ABAP PLATFORM 2023 - Application Server ABAP (SAP_BW 7.58)
Product
Keywords
WDA, Web Dynpro ABAP, multidimensional report, analytical report, add, field, row axis, 500 internal server error, Value, is not a valid index, context node, ABAP programming error, Runtime Errors, UNCAUGHT_EXCEPTION, CX_WD_CONTEXT, CL_WDR_CONTEXT_NODE_RANGE=====CP, BICS Grid, FPM_BICS_OVP , KBA , BW-RUI-FPM , FPM Analytical GUIBB , BC-WD-ABA-RUN , Web Dynpro ABAP Runtime , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.