Symptom
- 500 Internal Server Error with context node: V_GRID.1.ROW_2_ROWS error message in FPM applications
e.g., Value 28 is not a valid index, context node: V_GRID.1.ROW_2_ROWS
Value 10 is not a valid index, context node: V_GRID.1.ROW_2_ROWS - Below dump is observed in ST22 on the backend system:
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 28 is not a valid index; context node: V_GRID.1.ROW_2_ROWS
Read more...
Environment
FPM applications
Product
Keywords
FIS_FPM_OVP_AA_AHS1, F1615, Value 28 is not a valid index, context node: V_GRID.1.ROW_2_ROWS, UNCAUGHT_EXCEPTION, CX_WD_CONTEXT, CL_WDR_CONTEXT_NODE_RANGE , KBA , BW-RUI-FPM , FPM Analytical GUIBB , 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.
SAP Knowledge Base Article - Preview