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
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
JayDear 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? -
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
PavanI 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 -
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 PMThis 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 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,
DucTVHi,
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... -
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
BaisakhiIt 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 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 -
error analysis as in ST22 TRANSACTION:
AN EXCEPTION OCCURED THE EXCEPTION ASSIGNED TO CLASS CX_SY_CONVERSION_NO_NUMBER WAS NOT CAUGHT WHICH LED TO AN ERROR. THE REASON FOR THIS EXCEPTION IS :
THE PROGRAM TRIED TO INTERPRET VALUE ':4' AS NUMBER SINCE THE VALUE CONTRAVENES THE CORRECT NUMBER FORMAT THIS WAS NOT POSSIBLE.
ATTACHED IS MY PROGRAM
REPORT ZVXR0303
LINE-COUNT 60(3)
LINE-SIZE 132
MESSAGE-ID VN.
Tables: VBEP, VBAP, NAST.
DATA: BEGIN OF HEADER,
ORDER(15) VALUE 'ORDER',
LINE(5) VALUE 'LINE',
MATERIAL(14) VALUE 'MATERIAL',
DUE(15) VALUE 'DUE (MAD)',
CREATED(10) VALUE 'CREATED',
QTY(10) VALUE 'QUANTITY',
KEY(5) VALUE 'KEY',
TYPE(5) VALUE 'TYPE',
END OF HEADER.
DATA: Begin of IDAT OCCURS 0,
VBELN LIKE VBAP-VBELN,
POSNR LIKE VBAP-POSNR,
werks LIKE VBAP-WERKS,
cuobj LIKE vbap-CUOBJ,
MBDAT LIKE vbep-mbdat,
ERDAT LIKE VBAP-ERDAT,
MATNR LIKE VBAP-MATNR,
KWMENG LIKE VBAP-KWMENG,
QTY TYPE I,
END of IDAT.
class cl_abap_char_utilities definition load.
constants: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
DATA: t_record(1000) TYPE C.
DATA: C_KWMENG(20) TYPE C.
data: OUTFILE(50) value '/usr/users/ftpsapfi/locks_540318'.
DATA: BEGIN OF TKOMCON OCCURS 50.
INCLUDE STRUCTURE CONF_OUT.
DATA: END OF TKOMCON.
DATA: iKEY TYPE I,
offset TYPE I,
KeyTypeLOC TYPE I,
KeyNumberLOC TYPE I,
type(15) TYPE C.
select-options: sVBELN FOR VBEP-VBELN obligatory,
sMAD FOR VBEP-MBDAT obligatory,
sERDAT FOR VBAP-ERDAT,
sMATNR FOR VBAP-MATNR,
sWERKS FOR VBAP-WERKS,
sKWMENG FOR VBAP-KWMENG.
SELECT
vbap~vbeln
vbap~POSNR
vbap~werks
vbap~cuobj
VBEP~MBDAT
VBAP~ERDAT
VBAP~MATNR
VBAP~KWMENG
INTO CORRESPONDING FIELDS of IDAT
FROM ( VBEP INNER JOIN VBAP ON vbepvbeln = vbapvbeln
AND vbepposnr = vbapposnr )
WHERE BMENG > 0
AND vbep~MBDAT IN sMAD
AND VBEP~VBELN in sVBELN
AND VBAP~werks IN sWERKS
AND VBAP~ERDAT IN sERDAT
AND VBAP~MATNR IN sMATNR
AND VBAP~KWMENG IN sKWMENG
AND VBAP~ABGRU = SPACE.
APPEND IDAT.
ENDSELECT.
PERFORM TOP-OF-PAGE.
if sy-batch = 'x'.
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER t_record TO OUTFILE.
endif.
IF SY-SUBRC = 0.
LOOP at IDAT.
write IDAT-KWMENG DECIMALS 0 TO C_KWMENG.
REFRESH TKOMCON.
CALL FUNCTION 'VC_I_GET_CONFIGURATION'
EXPORTING
INSTANCE = idat-cuobj
LANGUAGE = NAST-SPRAS
TABLES
CONFIGURATION = TKOMCON
EXCEPTIONS
OTHERS = 4.
LOOP AT TKOMCON
WHERE ATNAM = 'S_SK_SPEC_KEY' OR ATNAM = 'S_MK_SPEC_KEY'
OR ATNAM = 'S_SK_CONSC_KEY' OR ATNAM = 'S_MK_CONSC_KEY'.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
KeyTYPELOC = 0.
keynumberloc = 2.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
Else.
Offset = 0.
DO.
IF offset <= 9.
offset = offset + 1.
If TKOMCON-ATWRT+Offset(1) = ':'.
KeyTypeLOC = Offset + 1.
KeyNumberLOC = Offset + 3.
EXIT.
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
IDAT-KWMENG = TKOMCON-ATWRT(3).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDIF.
CLOSE DATASET OUTFILE.
FORM OUT-OF-RANGE-FOUND *
FORM OUT-OF-RANGE-FOUND.
WRITE: / IDAT-VBELN.
WRITE: 10 IDAT-POSNR.
WRITE: 20 IDAT-MATNR.
WRITE: 35 IDAT-MBDAT.
WRITE: 50 IDAT-ERDAT.
WRITE: 65(3) IDAT-KWMENG DECIMALS 0.
WRITE: 75 TKOMCON-ATWRT+KeyTypeLOC(6).
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
WRITE: 85 'Consecutive'.
ELSE.
WRITE: 85 'Specific'.
ENDIF.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
TYPE = 'Consecutive'.
ELSE.
TYPE = 'Specific'.
ENDIF.
* PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
IDAT-VBELN
IDAT-POSNR
IDAT-MATNR
IDAT-MBDAT
IDAT-ERDAT
C_KWMENG
TKOMCON-ATWRT+KeyTypeLOC(6)
TYPE
INTO t_record SEPARATED BY tab.
if sy-batch = 'x'.
TRANSFER t_record TO OUTFILE.
endif.
ENDFORM.
FORM TOP-OF-PAGE *
FORM TOP-OF-PAGE.
WRITE: / 'ORDER'.
WRITE: 10 'LINE'.
WRITE: 20 'MATERIAL'.
WRITE: 35 'DUE (MAD)'.
WRITE: 50 'CREATED'.
WRITE: 65 'QTY'.
WRITE: 75 'KEY'.
WRITE: 85 'TYPE'.
PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
header-ORDER
header-LINE
header-MATERIAL
header-DUE
header-CREATED
header-QTY
header-KEY
header-TYPE
INTO t_record SEPARATED BY tab.
ENDFORM.
THIS IS WORKING FINE WITH DIFFERENT RANGES BUT WHEN I USE RANGE
Sales Order 1250000 TO 2250000
MAD 01/18/2005 TO 03/02/2005
Material LOCK9250FR TO LOCK9250XF
PLANT 4500
IT GIVES THE RUNTIME ERROR I MENTIONED ABOVE
ANY HELP WOULD BE GREATLY APPRECIATED
THANKS.HI ROB YOUR REPLY LOOKS TO BE VERY CLOSE OTHER GUYS SAID IT MIGHT BE PROBLEM WITH VARIABLE C_KWMENG BUT I REMOVED THAT PIECE OF CODE WITH C_KWMENG BUT STILL I WAS GETTING THE ERROR ATTACHED IS THE COMPLETE ERROR DETAILS FROM ST22
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Occurred on 09/29/2005 at 14:33:21
Unable to interpret "04:" as a number.
What happened?
Error in ABAP application program.
The current ABAP program "ZVXR0303" had to be terminated because one of the
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 administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_CONVERSION_NO_NUMBER', was
not caught, which
led to a runtime error. The reason for this exception is:
The program attempted to interpret the value "04:" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Integers are represented in ABAP using a sequence of digits and, in some
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[mantissa]E[sign][exponent]
[whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC
"ZVXR0303" or "ZVXR0303"
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "grrsap54"
Network address.......... "10.80.96.102"
Operating system......... "HP-UX"
Release.................. "B.11.11"
Hardware type............ "9000/800"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "grrsap54"
Database type............ "ORACLE"
Database name............ "D01"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "Aug 28 2005 20:25:49"
Created in............... "HP-UX B.11.00 A 9000/800"
Database version......... "OCI_920 "
Patch level.............. "88"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 050
User................ "NSHAKER"
Language key........ "E"
Transaction......... "SE38 "
Program............. "ZVXR0303"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "ZVXR0303" in
"START-OF-SELECTION".
The main program was "ZVXR0303 ".
The termination occurred in line 156 of the source code of the (Include)
program "ZVXR0303"
of the source code of program "ZVXR0303" (when calling the editor 1560).
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
001260 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001270 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001280 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001290 ?
001300 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001310 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
001320 ? PERFORM OUT-OF-RANGE-FOUND.
001330 ? ENDIF.
001340 ? ENDIF.
001350 ? Else.
001360 ? Offset = 0.
001370 ? DO.
001380 ? IF offset <= 9.
001390 ? offset = offset + 1.
001400 ? If TKOMCON-ATWRT+Offset(1) = ':'.
001410 ? KeyTypeLOC = Offset + 1.
001420 ? KeyNumberLOC = Offset + 3.
001430 ? EXIT.
001440 ? ENDIF.
001450 ? ELSE.
001460 ? EXIT.
001470 ? ENDIF.
001480 ? ENDDO.
001490 ?
001500 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001510 ?
001520 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001530 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001540 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001550 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
? IDAT-KWMENG = TKOMCON-ATWRT(3).
001570 ? PERFORM OUT-OF-RANGE-FOUND.
001580 ? ENDIF.
001590 ? ENDIF.
001600 ? ENDIF.
001610 ? ENDLOOP.
001620 ? ENDLOOP.
001630 ? ENDIF.
001640 ? CLOSE DATASET OUTFILE.
001650 ?
001660 ? *----
001670 ? * FORM OUT-OF-RANGE-FOUND *
001680 ? *----
001690 ? * ........ *
001700 ? *----
001710 ? FORM OUT-OF-RANGE-FOUND.
001720 ?
001730 ? WRITE: / IDAT-VBELN.
001740 ? WRITE: 10 IDAT-POSNR.
001750 ? WRITE: 20 IDAT-MATNR.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 44
SY-TABIX 7 SY-DBCNT 1
SY-FDPOS 4 SY-LSIND 0
SY-PAGNO 2 SY-LINNO 18
SY-COLNO 94 SY-PFKEY
SY-UCOMM SY-TITLE Out of Range Keys
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
Chosen variables
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
%_SPACE
2
0
SY-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
TKOMCON-ATWRT 04:XF1260
333543333222222222222222222222
04A861260000000000000000000000
KEYNUMBERLOC 5
0000
0005
SYST-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
SY-LDBPG SAPDB__S
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
IKEY 1260
000E
004C
KEYTYPELOC 3
0000
0003
SY ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
SVBELN IBT00012500000002250000
44533333333333333333333
92400012500000002250000
IDAT-KWMENG ########
00000000
0000000C
TKOMCON-ATWRT+0(3) 04:
333
04A
SYST ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
OUTFILE /usr/users/ftpsapfi/locks_540318
2777277677267776766266667533333322222222
F532F53523F64031069FCF3B3F54031800000000
... + 40
2222222222
0000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_Move" of the SAP
Basis System, specifically in line 529 of the module
"//bas/640_REL/src/krn/runt/abmove1.c#6".
The internal operation just processed is "MOVE".
The internal session was started at 20050929142552.
Active calls in SAP kernel
( 0) 0x4000000001751924 CTrcStack2 + 0x2bc dw.sapD01_DVEBMGS00
( 1) 0x4000000001751658 CTrcStack + 0x18 dw.sapD01_DVEBMGS00
( 2) 0x4000000001db7478 rabax_CStackSave__Fv + 0x100 dw.sapD01_DVEBMGS00
( 3) 0x4000000001dc3abc ab_rabax + 0x1e1c dw.sapD01_DVEBMGS00
( 4) 0x4000000001b44cb4 ab_cnverr__FiPcPCvN21T2 + 0x18c dw.sapD01_DVEBMGS00
( 5) 0x40000000016c96f8 ab_Move + 0x1910 dw.sapD01_DVEBMGS00
( 6) 0x40000000016d4434 ab_jmove__Fv + 0x384 dw.sapD01_DVEBMGS00
( 7) 0x4000000001022348 ab_extri__Fv + 0x17a0 dw.sapD01_DVEBMGS00
( 8) 0x4000000001726dc8 ab_xevent__FPCc + 0x38 dw.sapD01_DVEBMGS00
( 9) 0x40000000019f7efc ab_trigg__Fv + 0x94 dw.sapD01_DVEBMGS00
(10) 0x40000000019dc9ec ab_run + 0xc4 dw.sapD01_DVEBMGS00
(11) 0x4000000000f65e0c N_ab_run + 0x14 dw.sapD01_DVEBMGS00
(12) 0x4000000000f5fa88 dynpmcal + 0x198 dw.sapD01_DVEBMGS00
(13) 0x4000000000f5d500 dynppai0 + 0x830 dw.sapD01_DVEBMGS00
(14) 0x4000000000f5b8b4 dynprctl + 0x43c dw.sapD01_DVEBMGS00
(15) 0x4000000000f56728 dynpen00 + 0x2118 dw.sapD01_DVEBMGS00
(16) 0x400000000102f1b4 Thdynpen00 + 0x69c dw.sapD01_DVEBMGS00
(17) 0x400000000102e1e4 TskhLoop + 0x523c dw.sapD01_DVEBMGS00
(18) 0x4000000001022f50 tskhstart + 0x1e0 dw.sapD01_DVEBMGS00
(19) 0x4000000000dce3c4 DpMain + 0x484 dw.sapD01_DVEBMGS00
(20) 0x40000000022784cc nlsui_main + 0x14 dw.sapD01_DVEBMGS00
(21) 0x4000000000a39534 main + 0x14 dw.sapD01_DVEBMGS00
(22) 0xc00000000000a588 $START$ + 0xa0 /usr/lib/pa20_64/dld.sl
List of ABAP programs affected
Type Program Gen. Date Time Load Size
Prg ZVXR0303 09/29/2005 14:25:42 39936
Prg SAPMSSY0 05/01/2005 00:21:19 66560
Prg SAPMSSYD 06/05/2002 17:09:33 16384
Prg SAPFSYSCALLS 02/14/2002 14:22:47 6144
Prg RSDBRUNT 06/13/2004 00:43:20 226304
Typ RSSCR / / : m:15 5120
Prg RSDBSPBL 01/07/2003 18:47:02 59392
Prg SAPDB__S 02/14/2002 14:22:47 15360
Typ VARID 05/12/1997 16:51:30 4096
Prg %_CSYDB0 02/14/2002 14:22:46 28672
Prg RSDBSPVA 09/06/2005 22:54:22 112640
Prg SAPLSVAR 09/06/2005 22:57:28 625664
Typ VARIS 05/12/1997 15:27:21 2048
Typ RSVAMEMKEY 05/07/1997 13:07:49 2048
Prg RSDBSPMC 06/05/2002 17:09:26 66560
Typ DDSHDESCR 09/03/1997 03:05:16 3072
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ RSSELINT 04/04/1995 16:12:37 2048
Prg SAPLICON 03/12/2004 06:57:52 23552
Prg %_CICON 02/14/2002 14:22:46 65536
Prg SAPLSABE 02/14/2002 14:22:47 11264
Prg SAPLSECU 05/23/2005 14:04:05 64512
Typ RSSUBINFO 10/14/1999 22:01:03 3072
Prg %_CRSDS 02/14/2002 14:22:46 8192
Typ RSDSEXPR 08/20/1998 10:57:18 2048
Prg SAPLDSYA 02/14/2002 14:22:47 39936
Prg SAPFSDS1 01/07/2003 18:32:17 47104
Typ TDCLD 11/02/1998 09:51:35 5120
Prg SAPLSDOD 04/30/2005 22:53:50 39936
Typ DOKIL 05/12/1997 16:46:17 3072
Prg SAPCNVE 02/14/2002 14:22:47 6144
Prg SAPLLANG 02/14/2002 14:22:47 8192
Typ T002 02/14/1998 10:24:58 2048
Typ RSEXFCODE 08/13/1997 12:52:57 1024
Prg SAPFSPOR 03/13/2004 19:20:44 12288
Prg SAPLOMCV 05/01/2005 00:14:10 16384
Prg CL_EXITHANDLER================CP 06/13/2004 00:40:58 26624
Prg SAPLSEXV 09/06/2005 22:55:26 107520
Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 05/01/2005 00:21:35 33792
Typ SXS_ATTR 08/20/2001 12:23:27 4096
Typ V_EXT_ACT 11/09/2000 14:27:05 2048
Typ SXC_EXIT 11/09/2000 14:23:43 2048
Prg CL_EX_BADI_MATN1==============CP 05/01/2005 00:14:04 22528
Prg IF_EX_BADI_MATN1==============IP 06/13/2004 00:48:55 4096
Typ TMCNV 02/24/1999 03:33:25 3072
Prg SAPLSCNT 02/14/2002 14:22:47 24576
Typ DYCBOX 08/20/1998 11:16:53 2048
Prg SAPLSVSM 01/07/2003 18:35:45 22528
Prg SAPLSGUI 01/09/2003 17:15:12 31744
Prg SAPLSTTM 05/01/2005 00:24:04 75776
Prg SAPLSBDC 05/23/2005 14:05:19 38912
Prg CL_DATAPROVIDER===============CP 02/14/2002 14:22:46 40960
Prg %_CCNTL 02/14/2002 14:22:46 13312
Typ OBJ_RECORD 02/14/1998 08:30:43 2048
Prg SAPLSTUP 05/23/2005 14:03:46 65536
Prg SAPLCNDP 05/23/2005 14:05:47 167936
Prg SAPFGUICNTL 01/09/2003 17:18:52 20480
Prg SAPLOLEA 05/23/2005 14:03:56 79872
Prg SAPLSFES 09/06/2005 22:53:55 191488
Prg SAPLSPLUGIN 02/14/2002 14:22:48 6144
Typ ARFCRDATA 11/09/2000 14:04:16 6144
Prg SAPLGRFC 02/14/2002 14:22:47 13312
Typ SWCBCONT 11/15/2000 17:55:11 3072
Typ OLE_VERBS 04/04/1995 16:02:20 2048
Typ OLE_PA 04/04/1995 16:02:19 2048
Prg SAPSHDTV 03/12/2004 06:40:27 28672
Typ SSCRTEXTS 09/03/1997 03:12:33 3072
Typ SSCRFIELDS 05/13/1997 12:54:26 4096
Prg CL_GUI_PROPS_CONSUMER=========CP 01/07/2003 18:26:56 26624
Prg SAPLTHFB 09/06/2005 22:52:48 306176
Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 02/14/2002 14:22:46 33792
Prg CL_GUI_DATAMANAGER============CP 05/01/2005 00:20:36 70656
Prg CL_ABAP_CHAR_UTILITIES========CP 05/01/2005 00:14:49 11264
Prg RSDBSPVD 05/01/2005 00:15:44 73728
Typ RVARI 03/30/1998 09:40:50 4096
Typ RSVARIVDAT 04/04/1995 16:12:54 2048
Typ VBEP 01/27/2003 16:50:17 10240
Typ VBAP 09/15/2005 11:15:36 44032
Prg SAPLCEI0 09/22/2005 14:34:40 936960
Typ API_VALUE 02/20/1998 08:46:47 2048
Prg SAPLCUEV 06/07/2001 18:26:56 10240
Prg SAPLSUNI 06/13/2004 00:42:30 131072
Typ TFDIR 07/29/1998 19:49:08 3072
Prg %_CIBCO2 03/13/2004 14:32:13 12288
Typ IBINCOM 06/01/1999 11:56:27 3072
Typ IBINCONF 06/01/1999 11:56:27 2048
Typ IBSTCONF 06/01/1999 11:56:28 1024
Prg SAPLCUCB 05/23/2005 15:20:17 192512
Typ TCUIBSPECIAL 06/07/2001 17:50:37 1024
Prg %_CIBXX 03/13/2004 14:38:45 49152
Typ BAL_S_MSG 12/04/2000 13:04:01 6144
Prg CX_CBASE_ERROR================CP 01/27/2003 16:58:10 10240
Typ SCX_SRCPOS 11/09/2000 14:12:15 2048
Typ BAL_S_CONT 11/02/1998 09:43:07 2048
Typ BAL_S_PARM 12/04/2000 12:45:14 3072
Typ BAL_S_CLBK 11/02/1998 09:43:07 2048
Prg CX_STATIC_CHECK===============CP 02/14/2002 14:22:47 8192
Prg CX_ROOT=======================CP 02/14/2002 14:22:47 9216
Prg CL_CBASE======================CP 05/23/2005 15:19:44 87040
Typ T371G 04/29/1998 10:42:48 2048
Prg SAPLIBCO 03/13/2004 15:32:40 269312
Prg %_CIBCO 03/13/2004 14:38:45 11264
Prg SAPLIBXX 03/13/2004 14:38:46 11264
Prg SAPLIBIBF 03/13/2004 14:38:46 179200
Prg %_CIBIB 03/13/2004 14:38:45 18432
Prg SAPLIBINF 06/12/2004 22:20:22 415744
Prg %_CIBIN 03/13/2004 15:32:40 48128
Prg CL_IBASE_STRUC================CP 06/07/2001 19:59:10 106496
Prg %_CIBST 03/13/2004 14:38:45 37888
Prg CL_IBASE_STRUC_BUF============CP 06/07/2001 19:59:10 89088
Prg CL_IBASE_STRUC_STAT===========CP 06/07/2001 19:59:10 8192
Prg CL_IBASE_STRUC_BUF_IBSTREF====CP 06/07/2001 19:59:10 35840
Prg %_CIBCO1 03/13/2004 14:38:45 14336
Typ IBINVAL 09/18/2001 10:02:52 2048
Prg SAPLIBCU 03/13/2004 14:38:46 12288
Prg SAPLIBCUT 06/07/2001 18:27:19 12288
Typ T371B 05/14/1998 22:58:43 2048
Typ V_IBINR 03/13/2004 15:32:40 5120
Typ V_IBINR_CM 03/13/2004 15:32:40 5120
Prg CL_IBASE_SERVICE==============CP 06/07/2001 19:59:10 13312
Prg CL_IBASE_T371D_BUF============CP 06/07/2001 19:59:10 12288
Typ T371D 08/27/1999 18:19:44 2048
Prg CL_IBASE_R3_MATERIAL==========CP 05/23/2005 15:08:24 59392
Typ MARA 05/23/2005 15:08:18 22528
Typ MAKT 08/28/1997 08:52:19 2048
Typ ICON 01/03/1996 15:34:02 3072
Prg CL_ABAP_TYPEDESCR=============CP 05/01/2005 00:20:10 21504
Prg CL_ABAP_ELEMDESCR=============CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_DATADESCR=============CP 03/12/2004 07:16:33 14336
Prg CL_ABAP_REFDESCR==============CP 03/12/2004 07:17:23 16384
Prg CL_ABAP_STRUCTDESCR===========CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_COMPLEXDESCR==========CP 03/12/2004 07:16:33 13312
Prg CL_ABAP_TABLEDESCR============CP 03/12/2004 07:17:23 17408
Prg CL_ABAP_CLASSDESCR============CP 03/12/2004 07:17:23 23552
Prg CL_ABAP_OBJECTDESCR===========CP 03/12/2004 07:17:23 25600
Prg CL_ABAP_INTFDESCR=============CP 03/12/2004 07:16:33 19456
Prg CL_ABAP_SOFT_REFERENCE========CP 03/29/2001 16:42:12 7168
Prg CL_ABAP_REFERENCE=============CP 02/14/2002 14:22:46 6144
Prg IF_EX_CM_BADI_VERSION=========IP 01/07/2002 16:09:04 3072
Prg %_CABAP 01/07/2003 18:31:23 23552
Typ SXS_INTER 11/30/1998 15:55:16 2048
Prg CL_EX_CM_BADI_VERSION=========CP 05/01/2005 00:14:04 13312
Prg %_CSXRT 06/13/2004 00:40:55 11264
Prg CL_EXIT_MASTER================CP 06/13/2004 00:40:58 13312
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ SXC_IMPSWH 11/09/2000 14:23:44 2048
Prg CL_IM_CM_BADI_VERSION_DEF=====CP 04/17/2002 11:01:00 6144
Prg SAPLASTAT_TRIG 02/14/2002 14:22:47 11264
Typ ASTAT_TYP2 11/10/1998 05:35:18 2048
Prg IF_CM_BASELINE================IP 05/23/2005 15:08:24 9216
Prg IF_IBASE_IBOF_TREE_OBJECT=====IP 05/23/2005 15:08:24 5120
Prg IF_IBASE_INSTALL==============IP 06/07/2001 20:08:54 4096
Prg IF_IBASE_MATERIAL=============IP 06/07/2001 20:08:54 3072
Prg IF_IBASE_OBJECT===============IP 06/07/2001 20:08:54 4096
Prg SAPLBOMA 02/14/2002 14:15:40 10240
Typ IONRA 03/12/2004 02:09:40 23552
Typ IBIBCOM 08/30/2001 17:56:57 4096
Typ IBIB 03/13/2004 14:32:13 5120
Prg CL_IBASE_STRUC_SERVICE========CP 06/07/2001 19:59:10 17408
Prg CL_CU_CBASE_ENQUEUE_CORE======CP 06/07/2001 19:58:59 11264
Prg CL_CU_CBASE_ENQUEUE===========CP 06/07/2001 19:58:59 16384
Typ T371F 06/01/1999 12:00:49 2048
Typ V_IBIN_SYVAL 03/13/2004 15:32:41 4096
Typ IBIN 09/18/2001 10:02:52 6144
Typ IBINOWN 02/01/2000 14:56:07 2048
Prg CL_IBASE_T371F_BUF============CP 06/07/2001 19:59:11 8192
Prg CL_IBASE_STRUC_FILT_02========CP 06/07/2001 19:59:10 11264
Prg CL_IBASE_STRUC_FILT===========CP 06/07/2001 19:59:10 10240
Typ IBST 09/18/2001 10:02:52 4096
Typ IBST 09/18/2001 10:02:52 4096
Typ IBSTREF 04/15/1998 00:20:43 2048
Typ IBSTREF 04/15/1998 00:20:43 2048
Prg IF_CBASE_E====================IP 06/07/2001 20:08:25 3072
Prg %_CCXTAB 02/14/2002 14:22:46 6144
Prg SAPLCUCQ 09/15/2005 11:15:38 79872
Typ CUCO 09/18/2001 10:02:34 18432
Typ CUCO_OBJ 09/18/2001 10:02:34 18432
Prg SAPLCLCA 09/06/2005 23:33:29 68608
Typ TCLA 03/13/2004 14:10:20 5120
Typ TCLAO 08/13/1997 13:57:22 4096
Prg SAPLCUOB 05/23/2005 14:31:35 31744
Typ INOB 09/03/1997 03:20:02 4096
Prg SAPLCLSE 05/23/2005 14:32:26 167936
Prg %_CCC01 05/01/2005 00:34:57 53248
Typ TABLEKEY 07/06/1998 21:01:06 2048
Typ KSSK 09/18/2001 10:02:58 3072
Prg SAPLCLEF -
Runtime error while executing t-code NWP1
Hi!
One of our users is getting the runtime error CONVT_NO_NUMBER when she tries to execute the t-code NWP1. This is only with this user whereas her colleagues are able to execute it without any issues. Her decimal notation value in her UMR is specified as 1234,567.89, I changed it to other settings but still no luck. Does it have anything to do with her user parameters because this issue is only for this one user. Please help and thank you very much in advance
Regards,
AjDid you compare her user with another one that is working properly?....
Does it have anything to do with her user parameters because this issue is only for this one user
Most likely, that's way I suggest to compare the user... also you can try recreating the user to see if theres something wrong with her user master record.
Regards
Juan -
Runtime error while executing transaction BDLS
Hello,
While executing BDLS transaction for converting logical system names I am getting following error
Runtime Errors CONVT_NO_NUMBER
Except. CX_SY_CONVERSION_NO_NUMBER
Short text
Unable to interpret "7,160 " as a number.
How to resolve the above problem?Hi Rachel,
BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly
lives in runtime only and is checked by syntax checker.
Now, sometimes tables have inconsistencies associated with them and you
will get this dump when a syntax check is performed on them.
So please check this and regenerate the culprit tables.
So please redo the steps for BDLS and check. There are
probably some tables which could be determined by you (syntax
check - in case program has already been saved only)
An easy way to check this is to run RBDLS2LS program (old BDLS) and
afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>
<<)>(>
<<(><<)>)>ClientName>) program.
Known tables which caused such dumps in the past are:
DFKKCOLFILE_P_W
DFKKKO
DFKKMKO
DFKKREP06
DFKKREP06_S
DFKKREP07
DFKKREV06
DFKKREV07
Simply reactivate the tables you find out in SE11.
Another thing which has lead to this dump in the past is
in your R/3-System the value ' x ' is
additionally added to the value of your current release in the basis
release table SVERS.
The table RSBASIDOC takes the release value from the table SVERS.
If you change value 'x' to your release in both tables (SVERS and
RSBASIDOC) and
and activate again your source system connection. This could solve the
dump too.
I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)
b.rgds, Bernhard -
Runtime error in off_cycle payroll
Hello Experts,
I have configured off-cycle payroll for both quality and production server, it is running sucessfully in quality server. But whenever i m trying to run off-cycle run in production server , there is showing runtime error with the following message"RUNTIME ERROR : CONVT_NO_NUMBER ,
EXCEPTN: CX_SY_CONVERSION_NONUMBER"
what might be the reason ?
Regards,
SlaxmiHi,
Please check the data to being processed during this run. The error message indicates that there is some data whose conversion into numeric type is failing. So there might be some field whose data is not convertable. One reason can be like even in numeric field, the thousands seperation characters are stored which might be the reason for this kind of issues.
Best Regards,
Venkat. -
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
Maybe you are looking for
-
How to read new vlaues in adobe form in ZSCENARIO in MSS
hey guys, i have created Zscenario in MSS.... it has a Adobe form in it... the form has certain fields editable and requires user entry.. i have to save the fields into R/3 now... how to do it? is it possible..?
-
How I find my iPod touch 4g without Internet acces.because my iPod lost on a trip so how I find that?
-
Stuttering Workaround (and iMovie observations)
I too had experienced stuttering issues once I really got into a project in iMovie HD. Here is what I found, and how I fixed it: I had dozens of short clips, sound files, and narration in the lower project bar, the area in which you make your linear
-
Visual Studio 2012 - Source Not Available After Pressing Pause While Debugging
Hi, In Visual Studio 2008, when we'd open a dialog in our application (Native C++, 64-bit) and pressed 'Pause', the debugger would automatically go to the location of the dialog in the code and the call stack would show the series of calls to arrive
-
Hi All ! 1) Loaded data from datasource 2LIS_11_VAITM to PSA. Successfully. 2) While loading PSA to data target, the activation fails due to invalid characters. I have few options: 1) It has 200 datapackets. Correcting manually is not possible due tw