CONVT_NO_NUMBER , CX_SY_CONVERSION_NO_NUMBER dump in a zreport.

Hi gurus,
 we have a custom report which retrieves the data from table TSP03 from backend and synchronise if there is change in the data in SRM table ZHTSP03. currently this report is generating dump CONVT_NO_NUMBER , with short text
Unable to interpret "IlFQ" as a number.
i have checked all data in TSP03 but there is no string like "IlFQ" . in the code the dump is occuring at the below syntax.
 >>>>> CALL TRANSFORMATION id
SOURCE table = <tab>
RESULT table = data.
i have checked the entries of internal table <tab> which is the entries of table TSP03 and could not know why this dump is happening.
the data type for <tab> is type standard table AND
 data is type data.
Please help
Thanks and Regards
Aditya Shrivastava

Hi ,
 the code where the dump is getting is
call transformation id
 source table = <tab>
 result table = data.
Thanks
Aditya
Edited by: Aditya Shrivastava on Mar 16, 2010 4:17 PM
Edited by: Aditya Shrivastava on May 4, 2010 8:19 AM

Similar Messages

CX_SY_CONVERSION_NO_NUMBER dump coming

CX_SY_CONVERSION_NO_NUMBER dump appears when key is sleected in transaction WTYRCL.
Unable to interpret " " as a number.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMB
caught in
procedure "CONVERSION_IN2EX" "(FORM)", nor was it propagated by a R
clause.
Since the caller of the procedure could not have anticipated that t
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.
What could be possible reason for this ?

Theres 612 notes about this and 21 about CONVERSION_IN2EX
Did you look at them?...
Regards
Juan

CX_SY_CONVERSION_NO_NUMBER dump.

Hi all,
I have an issue while i move a string field to WRBTR field.
I have a form in which an int table is passed. It has a field of Char255 length.
This is moved to string field. All the commas and periods are replaced with spaces.
Later this is moved to WRBTR field. It gives dump here as
Unable to interpret "000 " as a number.
It seems there is an extra space at the end of the number in the string field.
I have tried CONDENSE WITH NO GAPS the string field and the same with the char255 field too with no success.
Eg code :
DATA : tt_inp TYPE STANDARD TABLE OF itcsy,
            ls_intab   TYPE itcsy,
           lv_wrbtr TYPE wrbtr,
            lv_wrbtr_char TYPE string.
FORM zztest TABLES itab TYPE tt_inp.
READ TABLE in_tab INTO ls_intab WITH KEY name = 'BSIK-WRBTR'.
IF sy-subrc EQ 0.
    lv_wrbtr_char = ls_intab-value.
ENDIF.
CONDENSE lv_wrbtr_char.
REPLACE ALL OCCURRENCES OF '.' IN lv_wrbtr_char WITH ''.
REPLACE ALL OCCURRENCES OF ',' IN lv_wrbtr_char WITH ''.
lv_wrbtr = lv_wrbtr_char. (giving dump in this statement)
ENDFORM.
Please find above the code which is resulting in error. when passing the data from ls_intab-value to lv_wrbtr_Char an extra blank is getting appended at the end. Tried all options as CONDENSE WITH NO GAPS, SHIFT, PACK etc.
Please help me in this regard.
Thanks,
Prasad

Hi,
The problem is not with the move statement but with thr replace logic you are using.
REPLACE ALL OCCURRENCES OF '.' IN lv_wrbtr_char WITH ','.
REPLACE ALL OCCURRENCES OF ',' IN lv_wrbtr_char WITH '.'.
First you replace . with ,. This time the string has values with comma.
next you replace comma with dots . this time the string may contain two or more dots converting the comma as changed recently also.
commas in inappropriate palces will cause the dump.
Try modfying the logic for proper separation.Make sure that the number you get after all replacement is a valid SAP number.
Like, 12,345.50 is your input.
your output to be put in wrbtr field should be 12.345,50.
With the current logic it becomes: 12,345,50
and then 12.345.50 which is not a valid number. that is why it gives dump.
change your logic like this.
DATA : tt_inp TYPE STANDARD TABLE OF itcsy,
ls_intab TYPE itcsy,
lv_wrbtr TYPE wrbtr,
lv_offset type i,
lv_numc type n length 16,
lv_wrbtr_char TYPE string,
itab like tt_inp,
result type MATCH_RESULT_TAB with header line.
lv_wrbtr_char = ' 12,456.00'.
CONDENSE lv_wrbtr_char no-gaps.
find '.' in lv_wrbtr_char match offset lv_offset.
REPLACE ALL OCCURRENCES OF ',' IN lv_wrbtr_char WITH '.'.
if lv_offset is not initial.
replace section offset lv_offset length 1 of lv_wrbtr_char with ',' .
endif.
lv_numc = lv_wrbtr_char.
lv_wrbtr = lv_numc.
write lv_wrbtr.
Here i have assumed that the user data in sAP system has decimal format as 1.234.456,00
Regards,
Kamini Rawat

ABAP Dump due to RFC Function module call in another thread

Hi,
I am facing some problem since yesterday. In one of my executable program I am calling a RFC fm as below mentioned
REPORT ZREPORT.
CALL FUNCTION 'Z_XXXXXXXXX'
 STARTING NEW TASK L_NAME
 DESTINATION IN GROUP 'TASK'
 PERFORMING RETURN_INFO ON END OF TASK
 EXPORTING
 P_exp1 = l_emp
 TABLES
 R_VBELN = r_it_vbeln
 EXCEPTIONS
 NO_DATA_TO_PROCESS = 1
 OTHERS = 2.
wait until v_task = 1.
update ztable.
Due to some data inconsistence one of the SAP function
module which I am calling in my function module Z_XXXXXXXXX
is generating dump with message type X. Since there is data inconsistence it is generating dump that's OK.
But the problem i am getting is, report ZREPORT is generating dump at WAIT statement saying illegal statement even though I am calling that function module
Z_XXXXXXXXX as a separate new task.
Can somebody help me.
Thanks,
Amara.

hi, Amara
I agree with Rich said, and do a simulate test in my server, here is the analysis.
Assume we have a RFC, like this:
FUNCTION ZGZL_DUMPTEST.
*"*"Local interface:
*" EXPORTING
*" VALUE(OUT) TYPE I
*" EXCEPTIONS
*" CONVERT_FAIL
data:a type i.
a = 'A'.
ENDFUNCTION.
And call this RFC like you way:
REPORT ZGZL_DUMPTEST .
DATA:
SEMAPHORE(1) VALUE SPACE,
LC_OUT TYPE I.
CALL FUNCTION 'ZGZL_DUMPTEST'
STARTING NEW TASK 'DUMP'
PERFORMING RETURN_INFO ON END OF TASK.
WAIT UNTIL SEMAPHORE = 'X'.
WRITE: 'OVER'.
FORM RETURN_INFO USING TASKNAME.
RECEIVE RESULTS FROM FUNCTION 'ZGZL_DUMPTEST'
 IMPORTING OUT = LC_OUT.
SEMAPHORE = 'X'.
ENDFORM. " RETURN_INFO
if we run the RFC in se37 directly, obviously it will occur a rumtime error CONVT_NO_NUMBER, and dump.
But if we run the above application to call the RFC, we will get a different runtime error CALL_FUNCTION_REMOTE_ERROR.
Error Analysis in ST22 like this:
An error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "CONVT_NO_NUMBER"
on the called page.
I think that means the application receive the runtime error from RFC when call RECEIVE RESULTS.
In normal CALL FUNCTION, the external application will accept the rumetime error throw from FM, that's correct, because it let the caller can handle these runtime errors.
In you case, you said RFC run in a new task, yes, that's true, so you can call the RFC like this:
CALL FUNCTION 'ZGZL_DUMPTEST'
STARTING NEW TASK 'DUMP'
PERFORMING RETURN_INFO ON END OF TASK.
WAIT UNTIL SEMAPHORE = 'X'.
WRITE: 'OVER'.
FORM RETURN_INFO USING TASKNAME.
SEMAPHORE = 'X'.
ENDFORM. " RETURN_INFO
It will goes well, no dump. Why? because we don't use RECEIVE RESULT. RECEIVE RESULT will bring the result from FM, also bring the runtime error from FM.
So if you want to call the FM and receive the result, handle the runtime error in FM inside at first.
like this:
CATCH SYSTEM-EXCEPTIONS CONVT_NO_NUMBER = 1.
 a = 'A'.
ENDCATCH.
IF SY-SUBRC = 1.
 RAISE CONVERT_FAIL.
ENDIF.
And then you call FM like this:
CALL FUNCTION 'ZGZL_DUMPTEST'
STARTING NEW TASK 'DUMP'
PERFORMING RETURN_INFO ON END OF TASK.
WAIT UNTIL SEMAPHORE = 'X'.
WRITE: 'OVER'.
FORM RETURN_INFO USING TASKNAME.
RECEIVE RESULTS FROM FUNCTION 'ZGZL_DUMPTEST'
 IMPORTING OUT = LC_OUT
 EXCEPTIONS CONVERT_FAIL = 1.
SEMAPHORE = 'X'.
ENDFORM. " RETURN_INFO
That's will be ok for your scenario.
Hope my reply is useful.
thanks

CX_SY_CONVERSION_NO_NUMBE

Hi All,
we are getting a short dump, can you please help me with this:
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', w
caught in
procedure "SEL_BINPUT" "(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 "1,131.64 " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
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"
"SAPMF05B" or "MF05BFS0"
"SEL_BINPUT"
I looked into the notes but couldn't find any.
any help will be really appreciated.
Thank you.
Rajeev Gupta

Hi Rajeev,
1,131.64 looks like the external (US-english) representation of a number. This cannot be implicitly converted to a numeric fomat.
You can convert the value before moving it to the target. We do this as follows (generic solution). Usulayy we use it for generic handling of editable grid input, but it could help in your context:
DATA:
 lv_type TYPE string,
 lr_dat TYPE REF TO data,
 ls_tabfield TYPE tabfield,
 lv_tabname TYPE tabname,
 lv_fieldname TYPE fieldname,
 lv_field TYPE scrfname.
FIELD-SYMBOLS:
 <dat> TYPE ANY.
* find any structure or table field with characteristics for the internal value
 ls_tabfield-tabname = <table or structure of target field>.
 ls_tabfield-fieldname = <fieldname in above structure or table>.
 CONCATENATE <tbn> <col>
 INTO lv_type SEPARATED BY '-'.
* create a data object of the required type
 CREATE DATA lr_dat TYPE (lv_type).
 ASSIGN lr_dat->* TO <dat>.
 CALL FUNCTION 'RS_CONV_EX_2_IN'
 EXPORTING
 input_external = <Input value in external representation>
 table_field = ls_tabfield
* CURRENCY = CURRENCY
 IMPORTING
 output_internal = <dat>
 EXCEPTIONS
* handle any error
Regards,
Clemens

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.

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

Purchase order print program error

hi experts!
am facing a problem in my purchase order print program. the problem is that when i am trying to see the print preview the following dump error is throughing, which am not able to understand.
the P.O total amount should be change into words( like one million then thousand thirty three kuwait dinars)
but the total amount is not converting into as mentioned, instead the dump is encountered.
please give me solution,
thnaks
*DUMP*
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Date and Time 05.05.2008 19:04:43
Short text
Unable to interpret "1760,778.71 " as a number.
What happened?
Error in the ABAP Application Program
The current ABAP program "ZMM_SUBROUTINES" 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 "GET_AMT_IN_WORDS" "(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 "1760,778.71 " 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"
 "ZMM_SUBROUTINES" or "ZMM_SUBROUTINES"
 "GET_AMT_IN_WORDS"
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.
The exception must either be prevented, caught within proedure
 "GET_AMT_IN_WORDS" "(FORM)", or its possible occurrence must be declared in the
 RAISING clause of the procedure.
 To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "EHPAP1"
 Network address...... "10.100.150.103"
 Operating system..... "AIX"
 Release.............. "5.3"
 Hardware type........ "00C3B3F04C00"
 Character length.... 16 Bits
 Pointer length....... 64 Bits
 Work process number.. 1
 Shortdump setting.... "full"
Database server... "EHPDB"
 Database type..... "DB6"
 Database name..... "EHP"
 Database user ID.. "SAPEHP"
Char.set.... "C"
SAP kernel....... 700
 created (date)... "Mar 19 2007 20:40:49"
 create on........ "AIX 2 5 005DD9CD4C00"
 Database version. "DB6_81 "
Patch level. 102
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
 SAP database version. 700
 Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory consumption
Roll.... 16192
EM...... 29328936
Heap.... 0
Page.... 1359872
MM Used. 19180992
MM Free. 1764848
User and Transaction
Client.............. 400
 User................ "FADISULAIMAN"
 Language key........ "E"
 Transaction......... "ME22N "
 Program............. "ZMM_SUBROUTINES"
 Screen.............. "SAPLMEGUI 0014"
 Screen line......... 22
Information on where terminated
 Termination occurred in the ABAP program "ZMM_SUBROUTINES" - in
 "GET_AMT_IN_WORDS".
The main program was "RM_MEPO_GUI ".
In the source code you have the termination point in line 398
 of the (Include) program "ZMM_SUBROUTINES".
 The termination is caused because exception "CX_SY_CONVERSION_NO_NUMBER"
 occurred in
procedure "GET_AMT_IN_WORDS" "(FORM)", but it was neither handled locally nor
 declared
in the RAISING clause of its signature.
The procedure is in program "ZMM_SUBROUTINES "; its source code begins in line
 358 of the (Include program "ZMM_SUBROUTINES ".
Source Code Extract
Line SourceCde
368 DATA: lt_spell LIKE spell.
369
370 READ TABLE in_tab WITH KEY 'CURR'.
371 IF sy-subrc = 0.
372 lf_curr = in_tab-value.
373 ENDIF.
374
375 READ TABLE in_tab WITH KEY 'NETWR'.
376 IF sy-subrc = 0.
377 lf_netpr_01 = in_tab-value.
378 REPLACE ',' IN lf_netpr_01 WITH ' '.
379 CONDENSE lf_netpr_01 NO-GAPS.
380
381 IF lf_curr = 'KWD'.
382 lf_netpr_kwd = lf_netpr_01.
383
384 CALL FUNCTION 'SPELL_AMOUNT'
385 EXPORTING
386 amount = lf_netpr_kwd
387 currency = lf_curr
388 filler = ''
389 language = sy-langu
390 IMPORTING
391 in_words = lt_spell
392 EXCEPTIONS
393 not_found = 1
394 too_large = 2
395 OTHERS = 3.
396
397 ELSE.
>>>>> lf_netpr = lf_netpr_01.
399 CALL FUNCTION 'SPELL_AMOUNT'
400 EXPORTING
401 amount = lf_netpr
402 currency = lf_curr
403 filler = ''
404 language = sy-langu
405 IMPORTING
406 in_words = lt_spell
407 EXCEPTIONS
408 not_found = 1
409 too_large = 2
410 OTHERS = 3.
411 ENDIF.
412 IF sy-subrc <> 0.
413 * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
414 * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
415
416 ELSE.
417
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 17
SY-TABIX 1
SY-DBCNT 18
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY NORMAL
SY-UCOMM PREVOUTPUT
SY-TITLE Held Imp. Pur. O r - ESG 5000000021 Created by Fadi Sulaiman
SY-MSGTY A
SY-MSGID TD
SY-MSGNO 426
SY-MSGV1 NEXTPAGE
SY-MSGV2 ZMEDRUCK_PO
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080505
SY-UZEIT 190441
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT

Hi Prasad,
Check the FM's
SPELL_AMOUNT --> for display in millions
HR_IN_CHG_INR_WRDS --> for display in lakhs and crores

Report Output for Currency Field--EKBE-WRBTR

Hello ABAP Experts
Since the Issue is related with Related Report output. Thought ABAP General Forum would be right place to post.
If not Suggest an appropriate forum for the same. I shall post them in Correct Forum.
Currently the report display Currency value From EKBE- WRBTR field
Actual Record Stored in EKBE is like this
0,00
400,00
1.600,00
client requirement is
0, 00
400,00
1600, 00
Option-1
I have tried option for conversion to CHAR & printing in Output, the issue I face is when I export to Excel I am getting an ABAP Error CONVT_NO_NUMBER(Short Dump)-This dump is due to conversion while exporting to excel.
Option-2(from SDN)
Give a logic based on T005 table i.e. this table has the decimal place setting for a each country (this I need to Verify)u2014But the I fear that report output can be confusing.
Expecting all your expert inputs!!
BR
Bharath

Hi Bharat,
You can set it using user--profile I guess.
For own data go to
system>user profile>own data---> defaults.
There you can select the currency format.
Hope this helps you.
Thanks,
Arun

BAPI_PO_CREATE1 SAP Package EHP5 MM/FI DPC integration Dump CONVT_NO_NUMBER

Hi,
we are starting to use SAP Package EHP5 for MM/FI DPC integration and we have the following effect: BAPI BAPI_PO_CREATE1 (same as BAPI_PO_CREATE) creates 2 short dumps while running.
The program stops at the following point:
i = h-group - 1 in SAP-standard code, cause the variable h-group contains no number ("0EY"), so that it is not possible to add "-1" and the program stops with short dump "CONVT_NO_NUMBER".
If I change content of h-group by debugger to "1" at two points of code:
LMEXFU04 line 67 and
LMEXFF01 line 116
the program goes on running and creates the complete purchase order including services and DPC-chain-number.
Sourc Code at this point:
h-group(1) = '1'.
ENDIF.
i = h-group - 1.
Is this short dump caused by wrong SAP MM/FI DPC Customizing ?
Any Experiences ?
Regards K.A.

Atul,
The first thing to check whether you already have them installed - ask your ABAP/Basis Team.
If not, you then need to determine whether they are include in any hot packs that you may be installing in the near future - again ask your ABAP/Basis Team..
Lastly - and probably most difficult - check whether you actually need them..
Also be aware that these notes may require that other notes be installed first (i.e. prerequisite notes).
PeteA

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

Function EXCEL_OLE_STANDARD_DAT Dump CX_SY_CONVERSION_NO_NUMBER

Hi everybody,
We are migrating R/3 from 4.6 to 5.0, when executing Z's programs using function 'EXCEL_OLE_STANDARD_DAT' in the new version it ends in a short dump CX_SY_CONVERSION_NO_NUMBER, that's because de field of the data table for the column in excel is an integer, and de the header for this column is text, can anybody help with this problem.
Thanks in advance,
Julio Cesar

Please refer to Note 721793 - Problems with MS_EXCEL_OLE_STANDARD_DAT.
- Guru
Reward points for helpful answers

ABAP dump CONVT_NO_NUMBER

Hi,
One of our program is going into dump in production server giving convt_no_number error. Inside the form the value is calculating by the program and storing it in a variable which is declared as INT4.
This value is moved to another variable which is declared as char. This is moved to another varibale which is declared as integer. The value which is showing in ST22 is *123.
The * is creating problem and I dnt knw where it is coming from. As this value is just a calculated one, how can the * be entered here.
As the system cant be replicated in development finding it more difficult.
The following are the variable declared.
data: out_treated_item_ct type int4,
          w_treated_item_ct(4),
          i_treated_item_count type i.
LOOPAT.                                                            " in the form called from function module
    ADD 1 to i_treated_item_count.
ENDLOOP.
w_treated_item_ct = i_treated_item_count.       " in the form called from function module
out_treated_item_ct = w_treated_item_ct.        " this is in main function module
Please help me in this.

Hi,
Try this..
data: out_treated_item_ct type int4,
w_treated_item_ct(4) TYPE N,                  " Change
i_treated_item_count type i.
LOOPAT. " in the form called from function module
ADD 1 to i_treated_item_count.
ENDLOOP.
w_treated_item_ct = i_treated_item_count. " in the form called from function module
out_treated_item_ct = w_treated_item_ct. " this is in main function module " Short Dump should be here change the type of w_treated_item_ct to N.

ZReport getting dump in Production but not in Quality and development

Hi,
There isa Zreport which displays daily stock in PP module.
It is getting dump in Production not in quality and development.
Since four days it is getting dump. Before that it is fine.
Please any one guide How to resolve.
Advance Thanks.

Runtime Error SAPSQL_IN_ITAB_ILLEGAL_OPTION
 Occurred on 29.08.2007 at 08:50:13
Invalid value in OPTION field of value table for IN itab operator.
What happened?
Error in ABAP application program.
The current ABAP program "ZPPRDR417" had to be terminated because o
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and admin
termination messages, especially those beyond their normal deletio
date.
Error analysis
The current ABAP/4 program attempted to execute an ABAP/4 Open SQL
statement in which the WHERE condition contains an IN itab operator
The IN itab operator is used with internal tables which
have the following structure:
 SIGN(1) OPTION(2) LOW LIKE db_field HIGH LIKE db_field
The OPTION column should contain only one of the following values:
 "EQ LE GE CP BT NE LT GT NP NB"
The value " " is not allowed here.
How to correct the error
Use only one of the permitted values in the OPTION column.
Information on where terminated
The termination occurred in the ABAP program "ZPPRDR417" in "WIP_STOCK_REP
The main program was "ZPPRDR417 ".
The termination occurred in line 330 of the source code of the (Include)
program "ZPPRDR417_FORM"
of the source code of program "ZPPRDR417_FORM" (when calling the editor 33
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
003000 ? r_bwart-low = '106'.
003010 ? append r_bwart.
003020 ?
003030 ? r_bwart-low = '124'.
003040 ? append r_bwart.
003050 ?
003060 ? r_bwart-low = '125'.
003070 ? append r_bwart.
003080 ?
003090 ? select matnr
003100 ? werks
003110 ? into table i_marc
003120 ? from marc
003130 ? where ( matnr LIKE 'BILC%'
003140 ? OR matnr LIKE 'LGN%'
003150 ? OR matnr LIKE 'BRN%'
003160 ? OR matnr LIKE 'EBB%' )
003170 ? AND matnr NE 'BRN_DECLASSE'
003180 ? AND matnr NE 'BRN_SAF'
003190 ? and werks in r_werks.
003200 ?
003210 ? r_material-sign = 'I'.
003220 ? r_material-option = 'EQ'.
003230 ?
003240 ? loop at i_marc into wa_marc.
003250 ? r_material-low = wa_marc-matnr.
003260 ? append r_material.
003270 ? endloop.
003280 ? clear r_material.
003290 ?
 > ? if not i_matdoc is initial.
003310 ? select MBLNR
003320 ? MJAHR
003330 ? ZEILE
003340 ? BWART
003350 ? MATNR
003360 ? WERKS
003370 ? SHKZG
003380 ? MENGE
003390 ? UMWRK
003400 ? into table i_mseg_qty
003410 ? from mseg
003420 ? for all entries in i_matdoc
003430 ? where MBLNR eq i_matdoc-MBLNR
003440 ? and MJAHR eq i_matdoc-MJAHR
003450 ? and BWART in r_bwart
003460 ? and matnr in r_material
003470 ? and werks in r_werks.
003480 ?
003490 ? sort i_mseg_qty by matnr.

CONVT_NO_NUMBER dump while filling PURCHASING setup tables

hi experts,
I have deleted the setup tables in lbwg and try to fill the setup tables again, it is running like 6-7 secons and giving the the below dump,
CONVT_NO_NUMBER. dont understand why it is giving the dump.
plz provide the solution to solve the above dump,i need to fill the setup tables and extract the data into PRODUCTION SYSTEM.
pl check the below error analysis.
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 "P" as a number, but
    since the value contravenes the rules for correct number formats,
    this was not possible.
Regards
venuscm

Hi,
I received the same runtime error "CONVT_NO_NUMBER" after I start the application specific setup of statistical data - perform setup purchasing. The short text of the runtime error describes that "P" is not recognized as a number.
In my case the ABAP-program "SAPLEINS" was interrupted because the function module "ME_STATISTICS_LIS_NEW" could not be processed successfully in line "341".
So I set a break point in this line and start the perform setup for purchasing (LIS-application 02) again. The debugging mode showed me the dataset of purchasing document that was responsible for the program abort. In the table "ekbe" (History per Purchasing Document) exists one or more purchasing documents who has as transaction/event type (ekbe-vgabe) an alphabetic character. But alphabetic and numeric characters are absolutely correct for the data maintenance of transaction/event type in the purchasing document.
In my case the ABAP statement in line 341 (... WHERE vgabe = 1.) could not be interpreted the dataset with the alphabetic transaction/event type "P" (invoice parking).
The sap-Note 1548467 resolved my problem and I was able to perform the setup for purchasing successfully.
* LOOP at t_ekbe WHERE vgabe = 1.                      " 1548467
LOOP at t_ekbe WHERE vgabe = '1'.                    " 1548467
Best regards
Michael

CONVT_NO_NUMBER , CX_SY_CONVERSION_NO_NUMBER dump in a zreport.

Similar Messages

Maybe you are looking for