Quantcast
Channel: SCN : All Content - ABAP Development
Viewing all articles
Browse latest Browse all 8332

Short dump after executing ME23N

$
0
0

Hi all,

 

Nedd some expertise

 

When i am executing ME23N for a particular PO. I am getting this short dump. Cureently this is the only PO in which i am facing the issue. The table entry is there for this PO.

 

Short dump-

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not

caught in

procedure "ME_LOG_READ" "(FUNCTION)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The program attempted to interpret the value "#####" as a number, but

since the value contravenes the rules for correct number formats,

this was not possible.

 

 

How to correct the error
    Whole numbers are represented in ABAP as a sequence of numbers, possibly
     with an algebraic sign.
    The following are the possibilities for the representation of floating
    point numbers:
      [algebraic sign][mantissa]E[algebraic sign][exponent]
      [algebraic sign][whole number part].[fraction part]
    For example, -12E+34, +12E-34, 12E34, 12.34
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove 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:

    "CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"
    "SAPLMELOG" or "LMELOGU04"
    "ME_LOG_READ"


Viewing all articles
Browse latest Browse all 8332

Trending Articles



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