CONVT_NO_NUMBER dump in Production Server. 'Unable to interpret "'1 " as a number.'

[ANSHUMAN10]

Hi Experts,

Today i got CONVT_NO_NUMBER error in Production Server  (the same error i got  248 times).

the details :

Runtime Errors         CONVT_NO_NUMBER
Exception              CX_SY_CONVERSION_NO_NUMBER
Date and Time          25.07.2012 11:45:35

Short text
     Unable to interpret "'1 " as a number.

What happened?
     Error in the ABAP Application Program

     The current ABAP program "SAPLEPD_EVENT_FUNCTION" had to be terminated because
      it has
     come across a statement that unfortunately cannot be executed.

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 that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not
      caught in
     procedure "ISU_MDG_EVT_CREATE_PC" "(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 "'1 " as a number, but

     since the value contravenes the rules for correct number formats,

     this was not possible.

Information on where terminated
    Termination occurred in the ABAP program "SAPLEPD_EVEN
     "ISU_MDG_EVT_CREATE_PC".
    The main program was "SAPMSSY1 ".

    In the source code you have the termination point in l
    of the (Include) program "LEPD_EVENT_FUNCTIONU07".
    The termination is caused because exception "CX_SY_CON
     occurred in
    procedure "ISU_MDG_EVT_CREATE_PC" "(FUNCTION)", but it
     locally nor declared
    in the RAISING clause of its signature.

    The procedure is in program "SAPLEPD_EVENT_FUNCTION ";
     in line
    1 of the (Include program "LEPD_EVENT_FUNCTIONU07 ".

<removed by moderator>

Thanks in advance !

Regards,

Anshuman.

Message was edited by: Thomas Zloch

[laurent_fournier2]

Hi,

Not very sure about this but I suppose that this is related to data entry problem. The message says that cannot convert '1 to a number. I suppose that somehow , a wrong value was entered in this filed that it was not handled by the calling program and leads to this dump. I searched very quickly in OSS and nothing came up so I believe that you must investigate how value '1 was populated.

Regards.

[Former Member]

Anshuman ,such kind of dumps occur when a type conversion error happens ( when moving a char to num etc).

In the source code of the dump ,there will be a line pointing to the error raised. Check the data types of the source and target . Is there any Userecit/Enhancement passing values to the Standard DBUpdate.. ???

[ThomasZloch]

Is there anything you researched yourself so far, e.g. applicable SAP notes?

Any transports that were recently imported in production?

Thomas

[Former Member]

Hi,

by looking at the detail.

'Short text
     Unable to interpret "'1 " as a number.'

you can see theat there is an oppening quotes ( ' ) is there in the start of 1. so please try to see the value in the variable that is getting passed as 1 or ( '1 ).

Thanks,

Raj Gupta

[ANSHUMAN10]

Information on where terminated
    Termination occurred in the ABAP program "SAPLEPD_EVENT_FUNCTION" - in
     "ISU_MDG_EVT_CREATE_PC".
    The main program was "SAPMSSY1 ".

    In the source code you have the termination point in line 165
    of the (Include) program "LEPD_EVENT_FUNCTIONU07".
    The termination is caused because exception "CX_SY_CONVERSION_NO_NUMBER"
     occurred in
    procedure "ISU_MDG_EVT_CREATE_PC" "(FUNCTION)", but it was neither handled
     locally nor declared
    in the RAISING clause of its signature.

    The procedure is in program "SAPLEPD_EVENT_FUNCTION "; its source code begins
     in line
    1 of the (Include program "LEPD_EVENT_FUNCTIONU07 ".

[Clemenss]

Hi Anshu,

the dump has a 'Source Code Extract' section (under 'ABAP developer view '). Here you can see the exact field name, i.e. "sv_zwnummer = wa_container-value". This may give you a hint where the input (file) is corrupt.

It is true: The string '1 can not be converted to a number due to the leading quote.

But this is a lousy function not taking care of this.

Regards

Clemens

[ANSHUMAN10]

Resolved by self.

The problem is coming because the incorrect periodic consumption entered in CRM system during move-in as i saw in table DBTAB_TEMPPC and as per standard SAP functionality there is no check
present to check data type of periodic consuption.To clear this stuck entry we need to manually correct periodic consumption in table DBTAB_TEMPPC.