Error :CONVT_NO_NUMBER

Hi
My coding is like below :
var_EXBED TYPE MAXBT .
Error: (Dump)
Unable to interpret " 980,000.00 " as a number.
READ TABLE T_IN9 WITH KEY 'J_1IEXCHDR-EXBED'.
CHECK SY-SUBRC = 0.
---> MOVE T_IN9-VALUE TO var_EXBED . " Error at this point
CLEAR T_IN9 .
later am converting var_EXBED value AMT to WORDS by calling FM spell_amount.
the error is due to ',' symbol
pls suggest how to resolve it out .
Thanks in Advance
SATYA

Hi Sahoo,
Try to use REPLACE keyword and replace all ,s(commos) before passing the value to Read statement.
REPLACE ALL OCCURRENCES OF ',' in T_IN9 WITH ''.
Read.....
Cheers!!
VEnk@
Edited by: Venkat Reddy on Nov 1, 2008 3:15 PM

Similar Messages

ABAP Runtime Error CONVT_NO_NUMBER

Dear all,
I am calling transaction F-02 for posting G/L Account from an FM. I tried with the Header Data and Account and Cost Centre but it says ABAP Runtime Error CONVT_NO_NUMBER. I undersood that its because of the Number interpretation and coded accordingly but still it throws the same error.
Can you please help me in this....
With Regards
Jay

Dear all,
Thanks for giving me some hope. I tried the possiblities but still it says the same error. I have pasted the FM in nutshell. Can you please see that and help me.
FUNCTION ZUPLOAD_XLS.
""Local interface:
*" IMPORTING
*"     REFERENCE(P_BUKRS) LIKE BKPF-BUKRS
*"     REFERENCE(P_BLDAT) LIKE BKPF-BLDAT
*"     REFERENCE(P_BUDAT) LIKE BKPF-BUDAT
*"     REFERENCE(P_MONAT) LIKE BKPF-MONAT
*"     REFERENCE(P_WAERS) LIKE BKPF-WAERS
*"     REFERENCE(P_BKTXT) LIKE BKPF-BKTXT
*" TABLES
*"      IN_JE_XLS STRUCTURE ZFGI_JE_STR
ITAB-BSCHL = 40.
ITAB-SAKNR = '812070'.
ITAB-WRBTR = '30881.00'.
ITAB-KOSTL = '11620009'.
APPEND ITAB.
MOVE P_BUDAT(4) TO TEM+4(4).
MOVE P_BUDAT+4(2) TO TEM(2).
MOVE P_BUDAT6(2) TO TEM2(2).
MOVE P_BUDAT(4) TO TEM+4(4).
MOVE P_BUDAT+4(2) TO TEM(2).
MOVE P_BUDAT6(2) TO TEM2(2).
MOVE P_BLDAT(4) TO TEM1+4(4).
MOVE P_BLDAT+4(2) TO TEM1(2).
MOVE P_BLDAT6(2) TO TEM12(2).
MOVE P_BLDAT(4) TO TEM1+4(4).
MOVE P_BLDAT+4(2) TO TEM1(2).
MOVE P_BLDAT6(2) TO TEM12(2).
WRITE ITAB-WRBTR TO WRBTR.
CONDENSE WRBTR NO-GAPS.
WRITE ITAB-BSCHL TO T_BSCHL NO-GROUPING LEFT-JUSTIFIED.
IF ITAB-KOSTL+8(2) EQ SPACE.
    MOVE ITAB-KOSTL       TO HOLD_KOSTL+2(8).
    MOVE '00'      TO HOLD_KOSTL(2).
ELSE.
    MOVE ITAB-KOSTL       TO HOLD_KOSTL.
ENDIF.
FIELD_LENGTH = STRLEN( ITAB-SAKNR ).
IF FIELD_LENGTH EQ 10.
    MOVE ITAB-SAKNR      TO   HOLD_SAKNR.
ELSE.
    MOVE ITAB-SAKNR(6)     TO   HOLD_SAKNR+4(6).
    MOVE '0000'      TO   HOLD_SAKNR(4).
ENDIF.
PERFORM NEW_DYNPRO USING 'SAPMF05A' '0100'.
PERFORM NEW_FIELD USING 'BKPF-BUDAT' TEM.
PERFORM NEW_FIELD USING 'BKPF-BLDAT' TEM1.
PERFORM NEW_FIELD USING 'BKPF-MONAT' P_MONAT.
PERFORM NEW_FIELD USING 'BKPF-WAERS' 'USD'.
PERFORM NEW_FIELD USING 'BKPF-BUKRS' P_BUKRS.
PERFORM NEW_FIELD USING 'BKPF-BKTXT' P_BKTXT.
PERFORM NEW_FIELD USING 'RF05A-NEWBS' T_BSCHL.
PERFORM NEW_FIELD USING 'RF05A-NEWKO' HOLD_SAKNR.
PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
PERFORM NEW_DYNPRO USING 'SAPMF05A' '0300'.
PERFORM NEW_FIELD USING 'BSEG-WRBTR' WRBTR.
PERFORM NEW_FIELD USING 'RF05A-NEWKO' '          '.
PERFORM NEW_FIELD USING 'RF05A-NEWBS' ' '.
PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
PERFORM NEW_DYNPRO USING 'SAPLKACB' '0002'.
PERFORM NEW_FIELD USING 'COBL-KOSTL' HOLD_KOSTL.
CALL TRANSACTION 'F-02' USING BDCDATA MODE 'A' UPDATE 'S'.

Runtime error CONVT_NO_NUMBER has occurred

Dear experts,
I am using BAPI -- 'HR_MAINTAIN_MASTERDATA' to maintain infotype 8(Basic pay).
I debugged the code. The data is coming in IT (that is of type PPROP) from my text file. But it gives runtime error in the FM saying --
"Runtime error CONVT_NO_NUMBER has occurred"
Please guide,
Sumit.

hi,
I checked in ST22. It says unable to interpret 4B as a number. Now I went to transaction PA30 and checked it's possible values. There were only 2- 8A and 8B. so I changed it to 8B. But still gives same error, as unable to interpret 8B as a number.
This is my int table while debugging--
line infty(c4) fname(c132)   fval(c255)   seqnr(n2)
1     0008     P0008-PERNR     40083005     00
2     0008     P0008-BEGDA     01012010     00
3     0008     P0008-ENDDA     31129999     00
4     0008     P0008-TRFAR     A1     00
5     0008     P0008-TRFGR     ASST.GM     00
6     0008     P0008-TRFST     MA     00
7     0008     P0008-BSGRD     8B     00       " here is my 8B
8     0008     P0008-TRFGB     10     00
9     0008     P0008-DIVGV     01     00
10     0008     P0008-ANSAL     192     00
11     0008     P0008-ANCUR     18437     00
12     0008     P0008-WAERS     INR     00
13     0008     P0008-LGA01     INR     00
14     0008     P0008-BET01     4000     00
15     0008     P0008-LGA02     4657     00
if fval is of c255, why doen it interpret it's fields as a number?

Error "CONVT_NO_NUMBER" while performing user measurement with USMM

Hi,
While running user measurement with USMM I am getting following run
time error.
To be specific - After preselections in USMM->system measurement->while
checking Green Check mark this error is screaming up.
Ae per Note - 1230640 :- You call transaction USMM and want to cancel
the user measurement using the cancel button (red 'X') on the dialog
box of the user measurement. However, the measurement continues and is
completed as if you had chosen the ok button (green check mark).
Above note is applied if the problem comes if we check red button
rather than green check mark.
Please suggest us the best way to procees.
ST22 details:-
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Date and Time 09/16/2008 07:42:32
Short text
Unable to interpret " 1,410 " as a number.
What happened?
Error in the ABAP Application Program
The current ABAP program "RSUVM001" 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 and
therefore caused a runtime error.
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:
[mantissa]E[algebraic sign][exponent]
[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"
"RSUVM001" or "RSUVM001"
"START-OF-SELECTION"
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)
Information on where terminated
Termination occurred in the ABAP program "RSUVM001" - in "START-OF-
SELECTION".
The main program was "RSUVM001 ".
In the source code you have the termination point in line 96
of the (Include) program "RSUVM001".
85 * Analyze the user records.
86 CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
87 EXPORTING
88 text = 'Die Benutzerstammsätze werden analysiert.'(002).
89 * PERFORM analyze_user_records.
90
91 CALL FUNCTION 'SLIM_USER_MEASUREMENET'
92 CHANGING
93 SLIM_TUREP = LT_TUREP.
94 .
95 LOOP AT LT_TUREP INTO LS_TUREP .
>>>>> MOVE-CORRESPONDING LS_TUREP TO ITUREP.
97 APPEND ITUREP.
98 ENDLOOP.
99
100 * Submit Application measurements as batch jobs.
101 * Save additional data about this analysis in the DB.
102 * we need meas-no ,v-date at the batch
any ideas?

Hi Srikanth,
The below Notes helps you to solve the issue.
Please review the below Notes.
Note 1117010 - Runtime error CONVT_NO_NUMBER in RSUVM001
Note 1115924 - USMM composite SAP Note: Problems after importimg new SPs
Thanks & Regards,
Pradeep Srigiri

Error "CONVT_NO_NUMBER" When testing Nisto e-orders for Dow integration,

Hi..
When testing Nisto e-orders for Dow integration, a runtime error is generated when the IDOC processes to produce an order.
ST22 details:-
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Date and Time 11/21/2008 13:58:03
Short text
Unable to interpret "IC5001" as a number.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLXVED" had to be terminated because
it has come across a statement that unfortunately cannot be executed.
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 "EXIT_SAPLVEDA_011" "FUNCTION" nor was it propaged by a RAISING clause .since the caller of the procedure couldnot have anticipated that the exception could occur,the program is terminated .
The reason for the Exception is :
The program is attemted to interpret the Value"IC5001"as a number but since the value contravenes the rule for correct number format,this was not possible.
How to correct the error pls help me
Thanks,

Hi Sanjith,
The error message is very clear and says IC---- can not be interpreted as number.
this may be
while passing the data IC are treated as numbers and processed furhter may be arthimatic operatons.
or it may passed to a NUMERIC type FIELD.
please check once.
regards
Ramchander Rao.K

Runtime Error: CONVT_NO_NUMBER with MM01 BDC

Hi All,
I am creating Material Master using Call transaction Method for MM01 Tcode.
I am passing the value called Standard Price (MBEW-STPRS) in the BDC.
Standard price will be like 100.00 (Hundred Rupees)
While passing this value, I am getting Runtime Error with the following details.
Runtime Error: CONVT_NO_NUMBER
Unable to interpret "/" as a number.
258 ----
259 *        Insert field                                                  *
260 ----
261 FORM BDC_FIELD USING FNAM FVAL.
>>>   IF FVAL <> NODATA.
263     CLEAR BDCDATA.
264     BDCDATA-FNAM = FNAM.
265     BDCDATA-FVAL = FVAL.
266     APPEND BDCDATA.
267   ENDIF.
268 ENDFORM.
How to resolve this type of error???
Regards
Pavan

I have defined field STPRS as char(13 length) in the internal table as char.
The field NODATA is having value ' \ ' in the debugging mode.
The code mentioned in my above post is from the standard perform statement.
Even if i provide value as "100" in the flat file, while reaching the statment
perform bdc_field       using 'MBEW-STPRS'
it_mm01-stprs.
it shows as "100.00" in the debugger.
Any idea....????
Regards
Pavan

Run-time error "CONVT_NO_NUMBER" occurred

Hi,
   When I checked my Development System for logs (using SM21)I got the logs
which are as follows :
02:16:33 DIA 001 100 KMENON       VF02 AB0 Run-time error "CONVT_NO_NUMBER" occurred
02:39:27 DIA 000 100 KMENON            AB0 Run-time error "OBJECTS_NOT_CHAR" occurred
Can someone please help me to know what the above logs describe and what are the reasons for these Run-time errors and suggest the solution for these runtime errors.
Below is the description of the above logs which I can see in my Development System:
Details Page 2 Line 7 System Log: Local Analysis of SAPECCDEV                 1
Time     Ty. Nr Cl. User         Tcod MNo Text                                                                   Date : 10.09.07
02:16:33 DIA 001 100 KMENON       VF02 AB0 Run-time error "CONVT_NO_NUMBER" occurred
Details
Recording at local and central time........................ 10.09.2007 02:16:33
Task................ 05532 / Dialog work process No. 01
User................ KMENON
Client.............. 100
Terminal............ alpha-pa
Session............. 2
Transaction code.... VF02
Program name........ SAPMV60A
Problem class....... T    Transaction Problem
Development class... SABP
Further details for this message type
Module name......... abmove1
Line................ 1892
Error text.......... ab_Zappy
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
a.. CONVT_NO_NUMBER
Technical details
File................ 000008
Position............ 0000235800
Entry type.......... l      ( Error (Module, Row)            )
Message ID.......... AB 0
Variable parts...... ab_Zappy                                            abmove1 1892
Details Page 2 Line 10 System Log: Local Analysis of SAPECCDEV                1
Time     Ty. Nr Cl. User         Tcod MNo Text                                                                   Date : 10.09.07
02:39:27 DIA 000 100 KMENON            AB0 Run-time error "OBJECTS_NOT_CHAR" occurred
Details
Recording at local and central time........................ 10.09.2007 02:39:27
Task................ 05576 / Dialog work process No. 00
User................ KMENON
Client.............. 100
Terminal............ alpha-pa
Session............. 2
Transaction code....
Program name........
Problem class....... T    Transaction Problem
Development class... SABP
Further details for this message type
Module name......... abtchk
Line................ 0543
Error text.......... ab_jtychk
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
a.. OBJECTS_NOT_CHAR
Technical details
File................ 000008
Position............ 0000236520
Entry type.......... l      ( Error (Module, Row)            )
Message ID.......... AB 0
Variable parts...... ab_jtychk                                           abtchk 0543

Hi Joerg,
         Actually I don't know about ABAP Programming but I can send you the ABAP source code which is as follows:
       Modulpool zur Fakturierung
       Report-Header / Tabellen / Daten / Field-Symbols
         INCLUDE MV60ATOP.
       PBO - Module alphabetisch geordnet
         INCLUDE MV60AO0C.
         INCLUDE MV60AO0D.
         INCLUDE MV60AO0F.
         INCLUDE MV60AO0I.
         INCLUDE MV60AO0R.
         INCLUDE MV60AO0S.
         INCLUDE MV60AO0T.
         INCLUDE MV60AO0V.
         INCLUDE MV60AO0X.
         INCLUDE MV60AOTX.             "Textverarbeitung
       PAI - Module alphabetisch geordnet
         INCLUDE MV60AI0B.
         INCLUDE MV60AI0D.
         INCLUDE MV60AI0F.
         INCLUDE MV60AI0K.
         INCLUDE MV60AI0N.
         INCLUDE MV60AI0R.
         INCLUDE MV60AI0V.
         INCLUDE MV60AI0X.
         INCLUDE MV45AITX.             "Textverarbeitung
       PAI - Module alphabetisch geordnet
         include mv60av0v.
       FORM-Routinen alphabetisch geordnet
         INCLUDE MV60AF0B.
         INCLUDE MV60AF0C.
         INCLUDE MV60AF0E.
         INCLUDE MV60AF0F.
         INCLUDE MV60AF0K.
         INCLUDE MV60AF0N.
         INCLUDE MV60AF0S.
         INCLUDE MV60AF0T.
         INCLUDE MV60AF0V.
         INCLUDE MV60AF0X.
       INCLUDE-Baustein zur Nachrichtensteuerung
         INCLUDE FV61BF00.
INCLUDE MV60AI0P_PASS_FCODE.
INCLUDE MV60AI0G_GET_FCODE.
INCLUDE MV60AO0P_PRICING_SET_DATA.
INCLUDE MV60AI0P_PRICING_GET_DATA.
INCLUDE MV60AI0S_STATUS_6900.
INCLUDE MV60AO0F_TABLECONTR.
INCLUDE MV60AO0P_PBO_TABSTRIP.
INCLUDE MV60AF0P_PBO_TABSTRIP.
INCLUDE MV60AI0P_PAI_TABSTRIP.
INCLUDE MV60AF0P_PAI_TABSTRIP.
INCLUDE MV60AO0R_REGULIERER_ADRESSE.
INCLUDE MV60AI0X_XVBRP_INIT.
INCLUDE MV60AF0X_XVBRP_INIT.
INCLUDE MV60AF0P_PBO_TABSTRIP_EXPORT.
INCLUDE MV60AF0P_PBO_TABS_INIT_EX_ITEM.
INCLUDE MV60AF0P_PBO_TABS_EX_ITEM.
INCLUDE MV60AI0P_PAI_EXPORT_HEADER.
INCLUDE MV60AF0P_PAI_EXPORT_HEADER.
INCLUDE MV60AI0P_PAI_EXPORT_ITEM.
INCLUDE MV60AF0P_PAI_EXPORT_ITEM.
INCLUDE TCRTDATA.
INCLUDE MV60AF0K_KURGV_TXTPA_ERMITTELN.
INCLUDE MV60AI0S_SD_PARTNER_GET_FCODE.
INCLUDE MV60AF0S_SD_PARTNER_GET_FCODE.
*INCLUDE MV60AF0X_XVBRP_TCTRL_SCROLLEN.
INCLUDE MV60AO0X_XVBRP_CTRL_INIT.
INCLUDE MV60AO0X_XKOMFK_TCTRL_INIT.
INCLUDE MV60AF0X_XKOMFK_TCTRL_SCROLLEN.
*INCLUDE MV60AO0X_XVBRK_TCTRL_INIT.
INCLUDE MV60AF0X_XVBRK_TCTRL_SCROLLEN.
*INCLUDE MV60AO0X_XKOMFK_TCTRL_INIT.
INCLUDE MV60AO0X_XVBRK_TCTRL_INIT.
*INCLUDE MV60AF0X_XVBRK_TCTRL_SCROLLEN.
*INCLUDE MV60AO0X_XVBRP_CTRL_INIT.
INCLUDE MV60AF0X_XVBRP_TCTRL_SCROLLEN.
INCLUDE MV60AF0X_XVBPA_KURGV_ERMITTELN.
INCLUDE MV60AO0C_CUST_HEAD_SET_DATA.
INCLUDE MV60AF0C_CUST_HEAD_SET_DATA.
INCLUDE MV60AI0C_CUST_HEAD_PASS_FCODE.
INCLUDE MV60AF0C_CUST_HEAD_PASS_FCODE.
INCLUDE MV60AI0C_CUST_HEAD_GET_DATA.
INCLUDE MV60AF0C_CUST_HEAD_GET_DATA.
INCLUDE MV60AO0C_CUST_ITEM_SET_DATA.
INCLUDE MV60AF0C_CUST_ITEM_SET_DATA.
INCLUDE MV60AI0C_CUST_ITEM_PASS_FCODE.
INCLUDE MV60AF0C_CUST_ITEM_PASS_FCODE.
INCLUDE MV60AI0C_CUST_ITEM_GET_DATA.
INCLUDE MV60AF0C_CUST_ITEM_GET_DATA.
INCLUDE MV60AO0C_CUST_HEAD_ACTIVATE.
INCLUDE MV60AF0C_CUST_HEAD_ACTIVATE.
INCLUDE MV60AO0C_CUST_ITEM_ACTIVATE.
INCLUDE MV60AF0C_CUST_ITEM_ACTIVATE.
Regards,
Ashish Thakkar

Bapi_pr_create,, error - convt_no_number

Hi   expert !
i was trying to post pr docu by using bapi_pr_create, but i got dump error /;convt_no_number
searched notes , but didn't find related notes.
i did deleted some source not needed in the whole source, because convt_no_number comes up.
i hoped that return table from bapi_pr_create, but dump error came up with convt_no_number,
humm,,, very strange issue,   please get back to me with good advise.
my source code is not complete to post docu ,, just hope not dump error comes up, but dump error as convt_no number.....
someone can execute this source whether dump error or return bapi return table with some error message ?
System environment
    SAP-Release 700
    SAP kernel....... 700
    created (date)... "Aug 24 2008 21:47:28"
     Patch level. 175
    Database............. "ORACLE
    SAP database version. 700
    APPL SP 18
data : g_mereqheader like bapimereqheader,
         g_mereqheaderx like bapimereqheaderx,
         g_mereqitem    like bapimereqitemimp occurs 0 with header line,
         g_mereqitemx   like bapimereqitemx occurs 0 with header line,
         g_mereqacc     like bapimereqaccount occurs 0 with header line,
         g_mereqaccx    like bapimereqaccountx occurs 0 with header line,
         g_te_meqitem   type bapi_te_mereqitem,
         g_te_meqitemx type bapi_te_mereqitemx,
         g_ext_in       like bapiparex occurs 0 with header line,
         g_ext_out      like bapiparex occurs 0 with header line,
         g_prnumber     like bapimereqheader-preq_no,
         gt_return      like bapiret2 occurs 0 with header line,
         wa_valuepart(960),
         wa_valuepartx(960).
data : ex_value type me_max_container.
data : lv_item like eban-bnfpo,
            lv_sn like bapimereqaccount-serial_no.
g_mereqheader-pr_type = 'NB'.
g_mereqheaderx-pr_type = 'X'.
lv_sn = '01'.
loop at gt_itab where check = 'X'.
    clear : g_mereqitem, g_mereqitemx.
    lv_item = lv_item + 10.
    g_mereqitem-preq_item = lv_item.
    g_mereqitem-acctasscat = '1'.                " 1 is used for stock material
    g_mereqitem-material = gt_itab-matnr.    " valuse 00000123   or 123 both tried ,,
    g_mereqitemx-preq_item = lv_item.
    g_mereqitemx-preq_itemx = 'X'.
    g_mereqitemx-acctasscat = 'X'.
    g_mereqitemx-material = 'X'.
    g_mereqacc-preq_item = lv_item.
    g_mereqacc-serial_no = lv_sn.
    g_mereqaccx-preq_item = lv_item.
    g_mereqaccx-serial_no = lv_sn.
    g_mereqaccx-serial_nox = 'X'.
    append g_mereqacc.   append g_mereqaccx.
    append g_mereqitem. append g_mereqitemx.
endloop.
call function 'BAPI_PR_CREATE'
     exporting
      prheader                    = g_mereqheader
      prheaderx                   = g_mereqheaderx
TESTRUN                     =
     importing
      number                      = g_prnumber
PRHEADEREXP                 =
    tables
      return                      = gt_return
      pritem                      = g_mereqitem
      pritemx                     = g_mereqitemx
PRITEMEXP                   =
PRITEMSOURCE                =
      praccount                   = g_mereqacc
PRACCOUNTPROITSEGMENT       =
      praccountx                  = g_mereqaccx
PRADDRDELIVERY              =
PRITEMTEXT                  =
PRHEADERTEXT                =
      extensionin                 = g_ext_in
     extensionout                = g_ext_in
PRVERSION                   =
PRVERSIONX                  =
ALLVERSIONS                 =
Edited by: venjamin on Sep 10, 2010 10:15 AM
Edited by: venjamin on Sep 10, 2010 10:18 AM

Hi there
as you see the above source, there is no one you worry about.
could you test the above source if dump error comes up or get return table included error message without dump error?
Best & Regards;
venjamin

Runtime Errors         CONVT_NO_NUMBER Exception              CX_SY_CONVERS

Hi Experts
I am getting a dump as follows
Short text
    Unable to interpret "/ 000000" as a number.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSZA19" 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 "ADDR_TIMESTAMP_IS_VALID" "(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 "/ 000000" 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, poss
     with an algebraic sign.
    The following are the possibilities for the representation of floati
    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
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the followi
    keywords:
    "CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"
    "SAPLSZA19" or "LSZA19U01"
    "ADDR_TIMESTAMP_IS_VALID"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
Please advise.
Thanks in advance
Baisakhi

It would appear that your program is looking for a timestamp, which are stored in SAP tables as DEC 15 fields. They display like 10/20/2011 07:36:00, but they are stored like 20111020073600. It is quite obvious that / 00000000 is not a number, because it contains both a slash and a space.   From your display, it appears that you have a timestamp that is not populated, and therefore the display looks like:      /    /       000000.
Somewhere the program is not converting a date and time to a timestamp, or you have a time stamp field displayed for user input, and the user doesn't understand how to input a time stamp, which would be keyed into a screen variablelike:
10/20/2011 07:36:00
If you are just starting with a date, look at your CONVERT DATE....TIME into TIMESTAMP .... TIME ZONE statement.... for example, if the user has a variable on screen that contains only a type D field, I would do something like:
get time.
convert date p_datefield "or sy-datum
              time sy-uzeit
     into time stamp time_stamp_var
           time zone sy-zonlo.
regardless, the error you posted occurs on a true numeric field which has had characters other than digits, a decimal and a sign input to the field.

Runtime Errors         CONVT_NO_NUMBER

Hi Experts,
we got a runtime error in program CONVT_NO_NUMBER ,here are the details of the error ,could not find a sap note on this.
same program is ran with same variant recently but got this runtime error today ,please suggest how to correct this
The termination occurred in the ABAP program "/SAPAPO/SAPLMSDP_CAP" in
"PROD_LIST_RESULT".
The main program was "/SAPAPO/RMSDPCAP ".
The termination occurred in line 1078 of the source code of the (Include)
program "/SAPAPO/LMSDP_CAPF02"
of the source code of program "/SAPAPO/LMSDP_CAPF02" (when calling the editor
10780).
The program "/SAPAPO/SAPLMSDP_CAP" was started as a background job.
Processing was terminated because the exception "CX_SY_CONVERSION_NO_NUMBER"
occurred in the
procedure "PROD_LIST_RESULT" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "/SAPAPO/SAPLMSDP_CAP ". Its source code starts
in line 1001
of the (Include) program "/SAPAPO/LMSDP_CAPF02 ".
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER',
     was neither
    caught nor passed along using a RAISING clause, in the procedure
     "PROD_LIST_RESULT" "(FORM)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    The program attempted to interpret the value "*08" as a number, but
    since the value contravenes the rules for correct number formats,
    this was not possible.
Thanks in Advance.
Edited by: Brahamananda reddy Arikatla on Aug 23, 2010 7:05 AM

Hi
"*08
1. I think this is some chararater that you have declared and the value is shooting to bypass the length. It is not able to handle the
value and a * is in place.
declare with appropriate data type by int or quan.. or char(xx) length to handle this.
SInce this is dealing with some background job its not clear loading of the data type . But u you can place the breakpoint at the code of line mentioned and observe the value .
2.
if u r doing a char comparision then see that RHS is in quotes .
Ex : ZB eq 11 will go for a dump
ZB eq '11' - > no dump
BR,
Vijay

Unable to interpret "650.00u00A0 " as a number. Runtime Error : CONVT_NO_NUMBER

Hi ,
This is a issue which has to be resolved ASAP as all the checks are being thrown Dump in Production.
It would be great if any of you could help me in this regard.
I have been encountering a runtime error as "CONVT_NO_NUMBER" with
short text as "Unable to interpret "650.00 " as a number."
System versio : SAP ECC 6.0
The problem is occuring at the below code
    FORM XXXXXXXX TABLES t_XXX_in STRUCTURE itcsy
                                   t_XXX_out STRUCTURE itcsy.
      DATA: $_swnet     LIKE regud-swnet.
      DATA: $_rwbtr     LIKE reguh-rwbtr.
      DATA: $_zbukr     TYPE bukrs.
      READ TABLE t_XXXX_in WITH KEY 'REGUH-RWBTR'.
      CONDENSE t_XXXX_in-value NO-GAPS.
make sure the amount field is an amount.
      IF t_XXXX_in-value CA 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
        $_rwbtr = 0.
      ELSE.
>>>>>     $_rwbtr = t_XXXX_in-value.
      ENDIF.
Can you please help me in this regard.
regards,
bhima
Moderator message: number formatting questions = FAQ, please search before posting, do not use the term "ASAP", all threads have the same priority.
Edited by: Thomas Zloch on Nov 17, 2010 6:19 PM

This is a FAQ. Please search before posting.
Just to avoid dump catch the exception cx_sy_conversion_no_number . But you have to do some other changes like replacing the unwanted characters like comma,dot etc and then move it.

Runtime Error = CONVT_NO_NUMBER ; Exception = CX_SY_CONVERSION_

Hi,
May we ask for your assitance, why we are getting this error:
Error analysis:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER',
was neither
caught nor passed along using a RAISING clause, in the procedure
"CONVERT_FISCPER_SELECTION" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The program attempted to interpret the value "XXXX" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
Information on where terminated:
The termination occurred in the ABAP program "SAPLGUSL" in
"CONVERT_FISCPER_SELECTION".
The main program was "SBIE0001 ".
The termination occurred in line 406 of the source code of the (Include)
program "LGUSLF01"
of the source code of program "LGUSLF01" (when calling the editor 4060).
The program "SAPLGUSL" was started as a background job.
Processing was terminated because the exception "CX_SY_CONVERSION_NO_NUMBER"
occurred in the
procedure "CONVERT_FISCPER_SELECTION" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLGUSL ". Its source code starts in line 350
of the (Include) program "LGUSLF01 ".
Thanks.

Hi Jay,
This is a common dump actually, Because sometimes there is a chance to input wrong decimal format by end user, in this situation system can not convert that decimal notation to other one.
If this is happening only for end user, doesnt matter. But it is coming for any particular TCODE or REPORT for all users you may have to contact ABAPER to set the decimal notation.
Regards
Nick Loy

Runtime Errors CONVT_NO_NUMBER = IF mode(1) = 'I'.

Hi all,
When creating logical database, runtime errors while saving it. The details as below:
"Unable to interpret "I" as a number.
   Error in the ABAP Application Program
   The current ABAP program "SAPLSEUQ" had to be terminated because
   come across a statement that unfortunately cannot be executed.
    FM RS_CORR_INSERT.
         IF mode(1) = 'I'."
Please advise. Thank you very much!!!
Regards,
DucTV

Hi,
if this issue happens in standard programm (not caused by userexit) search oss for bugfix. check ST22 to get the keywords you could search for.
if its your own z-programm fix the bug yourself...
regards
Stefan Seeburger

Runtime Error - CONVT_NO_NUMBER

Hi All,
I am trying to get data based on time and date input....
In the table the filed is having the value like this: 30.07.2010 11:48:51
so i concatenated the input by user and bought it to same format......
but i am gettin an runtime error as
"Error analysis
    An exception occurred that is explained in detail below.
    This exception cannot be caught in the context of the current statement.
    The reason for the exception is:
    The program attempted to interpret the value "27.07.2009 14:22:06" as a num
     but
    since the value contravenes the rules for correct number formats,
    this was not possible."
Please let me know.. how to proceed..

Please see this:
finaldt_low(10) type c ,
lv_crtat_low(19) type c,
pa_frmtm TYPE sy-uzeit,
CONCATENATE finaldt_low pa_frmtm INTO lv_crtat_low SEPARATED BY space.
I am using a concatenate so the final field will be of character value....
then i am doing a select
      SELECT lgnum
             procty
             tostat
             altme
             vsola
             weight
             rdocid
             confirmed_by
      FROM /scwm/ordim_c
      INTO TABLE it_ordim
      FOR ALL ENTRIES IN it_actype
      WHERE procty EQ it_actype-procty
        AND rdoccat = 'PDI'
        AND created_at GE lv_crtat_low
        AND created_at LE lv_crtat_high .
here the bold one is a problem...
CREATED_AT -> /SCWM/DE_CREATED_DT... is of this type...

CONVT_NO_NUMBER Dump error in Process Chain Abap Program

Hi Experts,
The daily running process chain is failed at ABAP program with the error CONVT_NO_NUMBER.
The reason for the exception is:
The program attempted to interpret the value "40-799" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
I am not familiar with ABAP.
Please suggest me how to proceed..
Thanks
<BMP>

Hi,
In ST22
Short text
    Unable to interpret "40-799" as a number.
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 "FM_DIR_LIST" "(FORM)", 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 "40-799" as a number, but
    since the value contravenes the rules for correct number formats,
    this was not possible.
I am trying post the code but SDN is not accepting more than 15000Char's
So can i get ur (mail) details
So that i can send u the exact code...
Thanks,
BMP

Error :CONVT_NO_NUMBER

Similar Messages

Maybe you are looking for