SAP Knowledge Base Article - Preview

2629145 - Accessing Business Criticality UI link, in CCLM setup in Solution Manager 7.2 SP06 results in a termination 500 SAP Internal Server error


  • In Solution Manager 7.2 SP06 in Custom Code Management setup, the following error appear when accessing Business Criticality UI link:

    500 SAP Internal Server Error
    ERROR: Invalid index 2 when setting lead selection; context node: COMPONENTCONTROLLER.1.DDI_PERIOD (termination: RABAX_STATE)

  • Following dump might be produced:

    Category                      ABAP Programming Error
    Runtime Errors             UNCAUGHT_EXCEPTION
    Except.                        CX_WD_CONTEXT
    ABAP Program              CL_WDR_CONTEXT_NODE_VAL=======CP
    Application Component  BC-WD-ABA-RUN

    Short Text
     An exception has occurred that was not caught.

    What happened?
     Exception 'CX_WD_CONTEXT' was raised, but it was not caught anywhere along the call hierarchy.
     Since exceptions represent error situations, and this error was not
     adequately responded to, ABAP program 'CL_WDR_CONTEXT_NODE_VAL=======CP' had to be terminated.

    Error analysis
     An exception has occurred which is explained in more detail below. The
     exception, which is assigned to class 'CX_WD_CONTEXT' was not caught and
     therefore caused a runtime error. The reason for the exception is:
     Invalid index 2 when setting lead selection; context node: COMPONENTCONTROLLER.1.DDI_PERIOD



Solution Manager 7.2 SP06


SAP Solution Manager 7.2


500 SAP Internal Server Error, Invalid index 2, COMPONENTCONTROLLER.1.DDI_PERIOD, Business Criticality, pools intersection , KBA , SV-SMG-CCM , Custom Code Management , 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.