How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

Hi all,
In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
I think ur data is worng,if it is wrong then only u will get this type of errors.
Regards,
Phani

Similar Messages

Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Hi all,
       In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump. I noticed that this error cannot be caught by CX_ROOT exception class.
       Some told me I can use the CATCH SYSTEM-EXCEPTIONS sentence to catch this runtime error, but it is a old-way syntax and cannot be used with the "try" and "catch".
       So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
You are not checking for conversion.
You are checking ofr logical expression.
Try below code, it works
DATA error_ref TYPE REF TO cx_sy_conversion_no_number.
DATA err_text TYPE string.
DATA a TYPE i.
TRY.
    MOVE 'A' TO a.
CATCH cx_sy_conversion_no_number INTO error_ref.
    err_text = error_ref->get_text( ).
    WRITE err_text.
ENDTRY.
Regards,
Atish

How to delete the runtime error in st22

Hi all,
How to delete the runtime error in ST22. I want to clear
the list of short dump in st22
is there any T.code or any table to clear?
thanks in advance
sundar.c

Hi
you cannot delete the dumps through any tcode.
All the dumps are stored in table called SNAP, If there are more dumps the table gets filled therefore u have to reorganize the table.
Run the report RSSNAPDL in SE38.
or
You have the default SAP background jobs, SAP_REORG_ABAPDUMPS which deletes the past dumps raised in the system.
Scheduling the jobs in regular is very important
For more information
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7ede505211d189550000e829fbbd/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/d8/a58b4275160d53e10000000a155106/frameset.htm
Regards
Bhaskar

How to avoid time out error in abap program

How to avoid time out error in abap program
based on performance wise i want please help

Timeout occurs when a statement exceeds its time limit.To avoid this we need to tune the statements.
I can give give you few tips for tune a select stament.
1.The order of the feilds in the select statement should be same as the order of fields in the database table.
2.It is always advisible to use the key fields when you are using the where clause.
3. Sort the internal table while using the for all entreis statements.
4.Use index in where clause if necessary.
5.When you have a read statement user binary search but before this a sort statement should be there.
6. Check your program with the Tcode ST05 and check which statement takes much time based on that tune that.

Catching a runtime error

Hi,
A runtime error for overflow (type p) occurs with the following details:
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          06/12/2007 11:33:13
Instead of displaying the dump screen, i'd like to catch the runtime error and display a message instead. The following is the code that causes the error (onhand is too large):
      REQRMENT = FORECAST - ONHAND - OPENQTY.
Please help,
Points will be rewarded and all help will be greatly appreciated.
Thanks,
John

According to help, these are the catchable exceptions for a form call:
Catchable Exceptions
CX_SY_PROGRAM_NOT_FOUND
Cause: The specified program was not found.
Runtime Error: LOAD_PROGRAM_NOT_FOUND
Cause: The specified program cannot exist because the program name is longer than 40 characters.
Runtime Error: PERFORM_PROGRAM_NAME_TOO_LONG
CX_SY_DYN_CALL_ILLEGAL_FORM
Cause: The specified subroutine was not found.
Runtime Error: PERFORM_NOT_FOUND
Cause: The specified index was too small.
Runtime Error: PERFORM_INDEX_0
Cause: The specified index was negative.
Runtime Error: PERFORM_INDEX_NEGATIVE
Cause: The specified index was too large.
Runtime Error: PERFORM_INDEX_TOO_LARGE
CX_SY_DYN_CALL_PARAM_MISSING
Cause: The called FORM expects more parameters than were specified.
Runtime Error: PERFORM_PARAMETER_MISSING
CX_SY_DYN_CALL_PARAM_NOT_FOUND
Cause: More parameters were specified than expected by FORM.
Runtime Error: PERFORM_TOO_MANY_PARAMETERS
CX_SY_DYN_CALL_ILLEGAL_TYPE
Cause: In the parameter transfer using the addition STRUCTURE, the addressing offsets/> do not match in the current and target structures.
Runtime Error: PERFORM_BASE_WRONG_ALIGNMENT
Cause: The deep components contained in the current and target structures cannot be passed to each other. This error can only occur in parameter transfer using STRUCTURE.
Runtime Error: PERFORM_CAST_DEEP_MISMATCH
Cause: During the transfer of a generically defined type to the form, a type conflict occurred.
Runtime Error: PERFORM_CONFLICT_GENERIC_TYPE
Cause: The table type of the current parameter does not match the table type of the parameter defined in the form.
Runtime Error: PERFORM_CONFLICT_TAB_TYPE
Cause: The type of current parameter does not match the type of parameter defined in the form.
Runtime Error: PERFORM_CONFLICT_TYPE
Cause: The current parameter occupies less storage space than the target parameter defined in the form. This error occurs only with parameter specification using STRUCTURE.
Runtime Error: PERFORM_PARAMETER_TOO_SHORT
Cause: During parameter transfer with the addition STRUCTURE, the fragment views of the current and target parameters do not match. This error only occurs in Unicode programs in
Runtime Error: PERFORM_CONFLICT_UC_STRUCT
Cause:When the form is called, an internal table is expected as current parameter.
Runtime Error: PERFORM_TABLE_REQUIRED
Cause: A hash table was passed to a parameter defined using TABLES.
Runtime Error: PERFORM_STD_TAB_REQUIRED

Convt_no_number runtime error

Hi abapers,
When i execute my zprog convt_no_number runtime error coming.
in program i declared rebzg as bsid-rebzg which is char 10.
this field should be either blank or vbeln value , but in table rebzg is stored as ' v ' single char value.
please provide the infrmation
regards,
Hari priya

hi Henri,
Thank for for ur reply.
Actually orginal invoice is cancelled in VF11.
when they cancelled orginal invoice in vf11 another cancelled invoice is generated. when i checked this cancelled invoice in fb03 , in invoice ref field ( rebzg ) it is showing '' v'' .
Because of this my zprog is showing convt_to_number runtime error.
please help me its urgent.
regards,
Hari priya

OSB - how to handle poll file error in FTP Proxy Service

I configed a proxy service to poll file from a FTP server.
How can I capture the error when the proxy service cannnot poll? (FTP server is down, folder not found, username invalid, etc )
I want to make it show in the Operations >Message Reports table.

It is not possible. Those errors will only be logged to logfile.
Manoj

Runtime error in abap report

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

How to catch SAP application errors in BPM.

Hi,
I have a IDOC to Soap Sync Scenario where I send the message to a Webservice. I have used a BPM since we need to catch the resposne of this message and map it to a RFC. For ex if I get a success resposne I need to map success if not than I need to catch the error and map it to the RFC. Now here in some cases like if the target system (webservice) is down than XI raises a sap application error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Normally XI stops the process in these cases and does not proceed to the next step but I need to catch this message and map the content in the AdditionalText to the target RFC. Can anyone let me know how to catch this SAP Application Error in BPM and map it to the RFC.
Thanks,
Bhargav

Hi Gaurav,
As I have mentioned I need to catch the application error in the BPM. If you see the discussion that is mentioned after the blog you have mentioned it is stated that the fault messages or the application error cannot be caught in BPM.
In the blog that you stated we can catch the fault message and map it to a message structure but only to that extent after that it would stop the BPM process at that step but would not proceed further as shown in the screenshot given in the blog it would fail as "application error restart not possible".
I need to proceed further and capture this error to an RFC Structure and call a proxy.
Here after the error it does not proceed to the next step.
Thanks,
Bhargav

How can I handle runtime errors in Java

Please some one tell me what are runtime errors and How can I handle them using java code
This is important
Thanks in Advance
Chowdary AK

The java equivalent of function pointers is the one-instance class, as used to pass handlers to swing components, for example. Often an anonymous class is used.
Put your function signature in an interface, and pass an object that implements that interface:
public Class1 {
public interface CallBack {
    void myMethod(String arg1);
CallBack callb;
public Class1(CallBack callb) {
   this.callb = callb;
callb.myMethod("A string");
class2 {
   first = new Class1(new Class1.CallBack() {
     public void myMethod(String arg1) {
       ... do something ...

How To Handle Labview Runtime Error in Teststand

Hi,
I am working NI-CAN device to transfer CAN frames through the VI's using TestStand. Before transmission took place, we need to choose for the port, in case if the port is selected wrong, Labview take it as a runtime error and handles accordingly while teststand keeps on running i.e. if I have 7 steps that are calling that VI, the runtime error from the labview will appear that many times also. Is there any way to handle labview runtime errors directly through TestStand. I have a sequence that will take care of the Runtime Errors in my sequence file.
Please help me soon.
Thanks in Advance,
Vivek

Hi Vivek,
If the LabVIEW VI is handling the error, then what you probably want to do is make the VI have an Error Out output terminal. You'd have to wire the appropriate error out wires to the terminal of course.
This way, when you call the VI from TestStand, you can check the value of the Error Out and decide in TestStand how to handle it (skip the remaining steps, popup a message, etc).
Jervin Justin
NI TestStand Product Manager

Reg the CONVT_NO_NUMBER Runtime Error

Dear all,
I have been trying to upload the G/L account information and using BDC. I have reduced my input fields to Header Data, PK, Acct Number, Amount and KOSTL. When I call the transaction I get the runtime Error. I learnt its because of the Number Interpretation, and so did the coding. But still it says the same error.
I declared a character field and moved the amount, filled the zeros for SAKNR and KOSTL but still throws the error.
Any help will be appreciated, plss..
Thanks in advance,
Leo

Dear all,
Here I have pasted the code. Can you please check with amount.... The code is in FM.
INPUT VALUES
ITAB-BSCHL = '40'.
ITAB-SAKNR = '812070'.
ITAB-WRBTR = '30881.00'.
*ITAB-GSBER = '1162 '.
ITAB-KOSTL = '11620009'.
Date Validations
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).
AMOUNT
WRBTR IS CHARACTER OF LENGHT 16.
WRITE ITAB-WRBTR TO WRBTR.
translate WRBTR USING ','.
CONDENSE WRBTR NO-GAPS.
SAKNR AND KOSTL Validations
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.
BDC
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' ITAB-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_DYNPRO USING 'SAPLKACB' '0002'.
PERFORM NEW_FIELD USING 'COBL-KOSTL' HOLD_KOSTL.
PERFORM NEW_DYNPRO USING 'SAPMF05A' '0300'.
PERFORM NEW_FIELD USING 'RF05A-NEWKO' ' '.
PERFORM NEW_FIELD USING 'RF05A-NEWBS' ' '.
PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
CALL TRANSACTION 'F-02' USING BDCDATA MODE 'A' UPDATE 'A'.
It says CONVT_NO_NUMBER occurs.
Please help me in this, I know its simple but couldnt find the place of the error. Your help will be appreciated.
Thanks & Regards
Jay

Noob question, how to avoid this runtime error,please help..

Im new to java. Im using a JOptionPane in getting the user an input/a number, which is in String,. and to use it, im converting it by Integer.parseInt. When I run it everything seems ok, but whenever i inputted other data types other than integer(e.g char), i get a runtime error message "exception in main thread java.lang.NumberFormatException blah blah.....,. Is theres a way or a method or something that i can filter the users input when they type a character or when they inputted nothing that will not resulted to a runtime error, instead, an error message box will said that it is an invalid input. thanks in advance

Ah, well, after an evening of rest and reflection, I have to conclude that we are all partially correct. I never meant to imply that NumberFormatException should not be caught. I have had to repair too many classes in which just-in-case or programming-by-exception was a rule, rather than a valuable technique for handling exceptional or error situations.
As far as this example, I was not attempting to write a parser, or even start one. We are talking about a very simple situation ... determine if a String represents an integer. My example was overly simple, too. As pointed out, too simple. *\d+* would have eliminated empty strings, and with a few relatively minor changes, could handle all legal integers easily, including '-' and ',' characters, while excluding floating point and other invalid inputs. I did mention that regexes were an advanced technique. A Scanner could be used to test for the existence of an integer in a string. None of these rise to the level of parsing, IMO, but, as I have frequently said in these fora, the arguments of the mages are infinite. Of course, that implies that I consider myself a mage, which is not actually the truth.
In any case, as pointed out, this is an example where catching a runtime exception is probably a good idea, as long as we don't give the OP the idea that this is the only technique, or that code can be written to ignore the causes of exceptional situations, because we can always handle them in the catch block. I have seen way too much of this to be comfortable with even the suggestion of this.
I come here to learn. Sometimes, I learn interesting, complex things. Sometimes, I learn interesting, simple things.
Sincerely, thanks for helping me to learn.
? {?

How to catch SMPP gateway error type ?

Hi,
How can i catch different SMPP error type return by SMSC server ?
I want to catch result like 0x45,0x01,0x0B,0x58,0x15.... in my code. I can see eventgateway.log logging the error message but how do i get error type in my code ?
Thanks

Hi,
There are different approaches, you can use a validate activity or you can check the validate check box in an assign activity...
Have a look on the links bellow...
http://docs.oracle.com/cd/E23943_01/dev.1111/e10224/bp_appx_ref.htm#SOASE86011
http://docs.oracle.com/cd/E23943_01/dev.1111/e10224/bp_manipdoc.htm#SOASE1824
http://docs.oracle.com/cd/E23943_01/dev.1111/e10224/bp_manipdoc.htm#SOASE87095
Hope this helps...
Cheers,
Vlad

HT1349 How do you fix runtime error r6034 caused by downloading itune upgrade?

itunes offered me an upgrade. I accepted the upgrade. Now itunes is dead and all I get is a runtime error R6034? I am running an HP with vista. How do I fix it?

iTunes RunTime Error R6034 > http://support.apple.com/kb/TS5376
Also see Here... https://discussions.apple.com/docs/DOC-6562

How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

Similar Messages

Maybe you are looking for