An exception has occurred that was not caught.

Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                /INCASP/CX_ASP_TAX
ABAP Program           /INCASP/CL_EWB_UTILITY========CP
Application Component  Not assigned



 What happened?
     Exception '/INCASP/CX_ASP_TAX' 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 '/INCASP/CL_EWB_UTILITY========CP' had
      to be terminated.

Error analysis
    An exception has occurred which is explained in more detail below. The
    exception is assigned to class '/INCASP/CX_ASP_TAX' and was not caught in
     procedure
    "OW_RUN_EWB_AUTOMATION" "(METHOD)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated this
    exception, the current program was terminated.
    The reason for the exception is:
     1111111111  Invoice Could not find in VBRK

How to correct the error
    The exception must either be prevented, caught in procedure
     "OW_RUN_EWB_AUTOMATION" "(METHOD)", or
    the possibility of it occurring must be declared in the RAISING clause
    in the procedure.
    To prevent the exception, note the following:

    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:

    "UNCAUGHT_EXCEPTION" /INCASP/CX_ASP_TAX
    "/INCASP/CL_EWB_UTILITY========CP" bzw. ZENH_CL_EWB_UTILITY===========EM002
    "OW_RUN_EWB_AUTOMATION"


Comments

Popular posts from this blog

all user exit mv45afzz (implicit user exit )

MB_MIGO_BADI THIS BADI USED TO POSTING DATA IN MIGO

Long Text in input and output field in module pool