Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8526

Re: EWA report not being generated - PLEASE HELP !!!

$
0
0

Hello and many thanks,

 

no, the header of the dump is like this:

 

Category           ABAP Programming Error
Runtime Errors     UNCAUGHT_EXCEPTION
Except.            CX_DSVAS_API_TEXT_PROPERTIES
ABAP Program       CL_DSVAS_PROC_CHECK_GROUP=====CP

Application Component  SV-SMG-SVD-SWB

Date and Time     

29.10.2014 12:54:04


And the body of the dump goes like this:

 

Short text

    An exception occurred that was not caught.

 

 

 

What happened?

    The exception 'CX_DSVAS_API_TEXT_PROPERTIES' 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, the running ABAP program

     'CL_DSVAS_PROC_CHECK_GROUP=====CP' has to be

    terminated.

 

 

 

What can you do?

    Note down which actions and inputs caused the error.

 

 

    To process the problem further, contact you SAP system

    administrator.

 

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

 

 

 

Error analysis

    An exception occurred which is explained in detail below.

    The exception, which is assigned to class 'CX_DSVAS_API_TEXT_PROPERTIES', was

     not caught and

    therefore caused a runtime error.

    The reason for the exception is:

    Type conflict saving to check table (Value=&MAXSIZE&, Type=&R&)

 

 

 

 

How to correct the error

 

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

 

 

   "UNCAUGHT_EXCEPTION" "CX_DSVAS_API_TEXT_PROPERTIES"

   "CL_DSVAS_PROC_CHECK_GROUP=====CP" or "CL_DSVAS_PROC_CHECK_GROUP=====CM00A"

   "EXECUTE_ACTION"

 

 

   If you cannot solve the problem yourself and want to send an error

   notification to SAP, include the following information:

 

   1. The description of the current problem (short dump)

 

      To save the description, choose "System->List->Save->Local File

   (Unconverted)".

 

   2. Corresponding system log

 

      Display the system log by calling transaction SM21.

      Restrict the time interval to 10 minutes before and five minutes

   after the short dump. Then choose "System->List->Save->Local File

   (Unconverted)".

 

   3. If the problem occurs in a problem of your own or a modified SAP

   program: The source code of the program

      In the editor, choose "Utilities->More

   Utilities->Upload/Download->Download".

 

   4. Details about the conditions under which the error occurred or which

   actions and input led to the error.


Viewing all articles
Browse latest Browse all 8526

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>