convt_no_number. About this page This is a. convt_no_number

 
 About this page This is aconvt_no_number  However the exception is thrown, if I use the condense function for the table term and

07. see the dump analysis and clcik on ABAP Editor. Please go to SE91 trransaction and enter RSM in message class and 000 as message number . Short text. Dear Experts, I have created new Data source in SRM system, with FM. Follwoing dump message-. Recently for the purpose of Implementing PR approval we have configured the standard workflow for Overall PR approval (WS20000077) as per Release Strategy. Thanks in Advance. please help. 2528613-Exception CX_SY_CONVERSION_NO_NUMBER when selecting '(De-)Activate Content' date in AGS_UPDATE. I am facing this dump in production client 000 "CONVT_NO_NUMBER" Category ABAP programming error. As this value contravenes the rules for displaying numbers correctly, this was. SP01, user dump, An attempt was made to interpret value "NONE" as a number, As this value contravenes the rules for displaying numbers correctly, this was not possible. then move it to other data types. An exception has occurred which is explained in more detail below. PCKG_NO Package number PACKNO NUMC 10 ESLH: 120 PCKG_NO Package number PACKNO NUMC 10 ESLH: 121 BATCH Batch Number CHARG_D CHAR 10 121 BATCH Batch Number CHARG_D CHAR 10 122. CONVT_NO_NUMBER: An attempt was made to interpret value &P1 as a number. Source Code Extract. 3167 * text. Short text. DATA gv_2 TYPE i. Visit SAP Support Portal's SAP Notes and KBA Search. DUMP 'CX_SY_CONVERSION_NO_NUMBER'. 000&quo So I did some research in SCN or internet, but I did not find anything about that topic. SAP Portfolio and Project Management 6. Same dump may appear in RZ10. I have successfully been able to complete the workflow on development environment however I have the following Questions / Observations. TRY. makde previously in a Unicode program to set the field symbol using . : DYNP_COMPRESS_ILLEGAL_VALUE &INCLUDE INCL_INTERNAL_ERROR: Messages related to OBY6 MESSAGE Description;. About this pageThe second example is fine, but the exception occurs in the first example did not be caught and the program terminated. The abap message says 'Unable to interpret. Cause: The. Data we are passing from excel for amount is 277,333,280. Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERSION_NO_NUMBER Date and Time 28. l_num = l_barcode(1). 2. Endif. ' with space into it_final-length. Message "Unable to interpret XXX as a number" occurs as shown below: SAP ERP Project System (PS) SAP R/3. "540689 System measrmnt: Shrt dump. I called it ZTOAD, in reference of a famous query builder in the SQL world. The w_ret-impret has the value "0,00" before get compared to zero. As you know, SAP don’t give to developper tools to execute query (there is a crappy tool for admin, and some function modules for devs, but not so. CONVT_OVERFLOW: Overflow when converting &P1: CONVT_REPL_CHAR:. " You get the dump with runtime errors CONVT_NO_NUMBER for /SSA/STA. 258 ----259 * Insert field * 260 ----261 FORM BDC_FIELD USING FNAM FVAL. About this page This is a preview of a SAP Knowledge Base Article. I go some errors. own-developed code), can usually be fixed by the programmer. cannot be interpreted as a number, CONVT_NO_NUMBER, CL_HRSFEC_HIRE, Dump full replication ECP, EVSUP, full replication PTP , KBA , LOD-EC-GCP-PY , Payroll Integration EC to Employee Central Payroll , LOD-SF-INT , Integrations , How To . SCRR_IUUC_STATS, SCRR_REPL_STATS, CONVT_NO_NUMBER , KBA , BC-UPG-TLS-TLA , Upgrade tools for ABAP , Problem . then remove the ',' from the value. The folowing dump occurs when executing Data Consistency check in Usage Logging Scenario in Solution Manager system:CX_SY_CONVERSION_NO_NUMBER. User is trying to display a spool in SP01 Following dump occurs: Category. 10 characters required. About this page This. exception would occur, the current. no differences found. dump, convt no number, nicht als Zahl interpretierbar, cannot be interpreted as a number,cl gui frontend services. Cause: Overflow in arithmetic operation (type p, with specified length) Runtime Error: BCD_FIELD_OVERFLOW; Cause: Operand too big or (interim) result too big Runtime Error: CONVT_OVERFLOW; CX_SY_PRECISION_LOSS Dump in transaction CNS41 when using a specific Variant. Dear experts, I am getting a Dump when I use Tcode TRIP. Regards, Sana Khan. Click more to access the full version on SAP for Me (Login required). Cause: Operand cannot be interpreted as a number Runtime error: CONVT_NO_NUMBER; CX_SY_CONVERSION_OVERFLOW. * IF WA_CHAR = 0. CONVT_NO_NUMBER Value to be converted cannot be interpreted as a number . It seems that the requirement you got is that the net value of billing documents should be shown in 1 format, not respecting the settings of the user which control the decimal notation. procedure "SEL_BINPUT" "(FORM)", nor was it propagated by a RAISING clause. Need urgent help to solve it. That eats Unfortunately across a statement can not be execute. Clearly says that there is some value of non-numeric type (like ' ' or , etc. Hi Friends, In the ST22 transaction dump is taking place every five minutes, the dump is as follows. SAP ERP 6. Cause: Target field is too short to display a decimal floating point number. Paste the complete dump so that we can tell you the exact issue. 552. Runtime Errors CONVT_NO_NUMBER ABAP Program SAPLSPOOL_SP01R Application Component BC-CCM-PRN. : Messages related to MD05 MESSAGE Description; 0K533: Value & is not allowed for the parameter I_SAVE: BD100: No TABLES statement for & found: BD101: Table & is not an active table: Table Fields related to MD05 TABLE FIELDThe program attempted to interpret the value "*0" as a number, but. This Knowledge Base Article describes two different symptoms: Symptom 1. Most of the obsolete catchable runtime errors are assigned to exception groups. Runtime error: CONVT_NO_NUMBER; CX_SY_CONVERSION_OVERFLOW. The abap message says 'Unable to interpret "*'. Thanks in Advance. TR. In transaction ST22, a short dump CONVT_NO_NUMBER is shown with following information: Category ABAP Programming ErrorRuntime Errors CONVT_NO_NUMBER ABAP Program /1WDA/C8STANDARD=====CP (or similar) Short Text "x" cannot be interpreted as a number. Other users are able to execute the transaction without any short dump. Hi, I am below dump. Click more to access the full version on SAP for Me (Login required). Not yet a member on the new home? Join today and start participating in the discussions! The GS_EXCEL-AMOUNT field brings a value “3 , which you want to move to the WA_UPLOAD-WRBTR field, by bringing quotes” the field sends dump. After filtering, we transfer ALV table mode to edit mode, CL_SALV_TABLE=>REFRESH is executed, call. Ou seja, você vai associar um número para o return code (sy-subrc), exatamente como você já faz quando chama alguma função. . PARAMETERS: *Article Data p_ano. 00’as a number. All BDC field updates call this subroutine, and example of which is below. . Cause: Operand cannot be interpreted as a number Runtime error: CONVT_NO_NUMBER; CX_SY_CONVERSION_OVERFLOW. to occur, the running. When we click on the button "View result", we got a dump (see below extract of ST22). 2. Hello Experts, I have configured off-cycle payroll for both quality and production server, it is running sucessfully in quality server. Date and Time 17. OPEN_DATASET_NO_AUTHORITY. I monitored from last 4 - 5 days the job is getting cancelled and providing a dump like ABAP/4 processor: CONVT_NO_NUMBER. What hapformatting, tab, mitigation description, CONVT_NO_NUMBER, CL_GRAC_SOD_REPORTS, CX_SY_CONVERSION_NO_NUMBER , KBA , GRC-SAC-ARA , Access Risk Analysis , Problem . it give soCX_SY_CONVERSION_NO_NUMBER. data c1 (2) type c. Short Text. Local fix ITXCQ - ITX00059971 PB / CN Circumvention: Type trees imported with ITX 9. data name (10) type c. 11 SAP Netweaver 7. CONVT_NO_NUMBER: An attempt was made to interpret value &P1 as a number. 560. Not yet a member on the new home? Join today and start participating in the discussions!(Remote shortdump: CONVT_NO_NUMBER in system [XX1|abcdef01|00]) The same operation using a type tree imported using IBM Transformation Extender 9. Following is the syntax for using TRY –. 00002 'Enter a valid value' might be displayed, or Dump 'CONVT_NO_NUMBER' might be displayed just after entering the transaction. I have also deleted some files form server and after that loading one file at a time ,then also facing same issue in step -DTP of the process Chain. Runtime Errors CONVT_NO_NUMBER. 0 /. . Cause: No authorization for access to file Runtime Error: OPEN_DATASET_NO_AUTHORITY; Cause: Authorization for access to this file is missing in OPEN DATASET with the addition FILTER. Exception CX_SY_CONVERSION_NO_NUMBER. DATA gv_char1 TYPE char128 VALUE 'TEST1'. g. DS, IDOC, CONVT_NO_NUMBER, CX_SY_CONVERSION_NO_NUMBER, "X,XXX" cannot be interpreted as a number, "0. Read more. Exception class: CX_SY_CODEPAGE_CONVERTER_INIT. 0000. Log In. RAISING clause. 12. Since the caller of the procedure could not have expected this exception. SAP_HRCMY 604 604 2151122 Enhancement for note 2149869 PY-MY. The report takes process order numbers as input and updates a Z-Table accordingly. 00 " as a number. A dump similar to the one below is raised after running Consistency Check functionality in Soamanager:The reason could be any of the below two reasons: 1) You are trying to store a character Value in a Number field due to which it is not able to interpret this value with ',' as a number. In the assignment, the field symbol has the type i , however the field number is created with the type decfloat34 when the program is generated. For example, assume that a shop order is for. CALL FUNCTION 'MOVE_CHAR_TO_NUM' EXPORTING CHR = lv_chr IMPORTING NUM = lv_num EXCEPTIONS CONVT_NO_NUMBER = 1 CONVT_OVERFLOW = 2 OTHERS = 3. It’s very clear from the dump error, and through debug can find out that one specific column which is a long text with TAB inside the specific cell. Lavanya. in your case, i am guessing) this will also cause a problem. We. data integer type i. DATA: lv_check LIKE STPOI-MENGE. The current ABAP program "RSDSPROC" had to be terminated Because it has. REPORT ZGULLA_SALES_ORDER_DYNAMIC. since the value contravenes the rules for correct number formats, this was not possible. : CX_SY_CONVERSION_NO_NUMBER. 263 CLEAR BDCDATA. CX_SY_CONVERSION_NO_NUMBER Programa ABAP SAPLFWTH Anwendungskomponente FI-AP-AP Fecha y hora 02. But when i execute the same transaction from the Admin user , i am able to execute it successfully . TEM1: Help/Wiki, Q&A, and More SAP TCode: TEM1 - Master Data Exposure Plng Profile Suggestion: Use browser's search (Ctl+F) function to find reference/help linksI am getting CONVT_NO_NUMBER dump in one of my delete statements. CONVT_NO_NUMBER, "<empty>" cannot be interpreted as a number , KBA , GRC-SAC-ARQ , Access Request , Problem . The list displays SFC numbers the operator. Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERSION_NO_NUMBER Short text. Cause: Invalid format of the source field in the output of a decimal floating point number. e. As this value contravenes the rules for displaying numbers correctly,this was not possible. 0000. 2. Click to access the full version on SAP for Me (Login required). Job SM:SELFDIAGNOSIS fails with a CONVT_NO_NUMBER dump. About this page This is a preview of a SAP Knowledge Base Article. APPEND bdcdata. Dumps that happen in the customer namespace ranges (i. na execução da VF01 acontece Short Dump no programa SAPLJ_1B_NFE o erro esta relacionado com converção de numeros "CONVT_NO_NUMBER", se desativar a NFe 2. The program attempted to interpret the value "*381" as a number, but. Is it related to 'call level'?The exception assigned to class: CX_SY_CONVERSION_NO_NUMBER Runtime error: CONVT_NO_NUMBER. Symptom. Cause: Target field is too short to display a decimal floating point number. CATCH cx_sy_conversion_no_number. ) that the program is getting. catch system-exceptions convt_no_number = 1. the reason for this. ST22 Dumps getting generated with runtime error: CONVT_NO_NUMBER Following is the detailed ST22 dump that was constantly getting generated: Category ABAP. OPEN_DATASET_NO_AUTHORITY &INCLUDE INCL_AUTHORITY_MISSING: CALL_FUNCTION_SIGNON_INCOMPL: The logon data for user &P1 is incomplete. This article explains further how to enter values for Parameter 'FO3' at mentioned SU* transactions to avoid these errors. CX_SY_CONVERSION_NO_NUMBER ABAP Program CL_SWNC_CONSTANTS=====CP Application Component BC-CCM-MON Date and Time 19. Please provide a distinct answer and use the comment option for clarifying purposes. A TRY - CATCH block is placed around the code that might generate an exception. To do this, call the. But first of all I'm checking if the value of the field symbol is initial. 1 (wr3slog) generates dumps on a SAP system: Dump titel : CONVT_NO_NUMBER Impacted program : SAPLSL04 Function Module : J_8C1_SYSLOG_INFO Detailed info: CONVT_NO_NUMBER: SAPLSLO4 Runtime. to occur, the running program was terminated. Dictionary object consistency must be checked in the system. As you can see at the green block of code for some reason the program changes the dot per comma. This Knowledge Base Article describes two different symptoms: Symptom 1. if it is character. If I use include bdcrecx1 then I am getting dump CONVT_NO_NUMBER --- Unable to interpret "/" as a number, on field EINE-APLFZ. 553. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program. However Dump CONVT_NO_NUMBER occurred during table conversion. data: v_adofficer type string. since the value contravenes the rules for correct number formats, this was not possible. Please help me. I've found that solution: DATA: gv_to_convert TYPE string VALUE 'abc', gv_int TYPE p LENGTH 6 DECIMALS 3. Cause: Invalid format of the source field in the output of a decimal floating point number. DUMP, CONVT_NO_NUMBER, Parameter 2010, Request type for default roles, default roles, Component GRAC_UIBB_ACCESS_REQUEST, V_REQUEST_ITEMS, GET_DEFAULT_ROLE_CONFIG. Short text. ECC, Invoice Number Range, CONVT_NO_NUMBER , KBA , MM-IV-LIV-CRE , Entry MIRO , Problem . You can follow WIKI page Dump CONVT_NO_NUMBER occurred during table conversion to continue the conversion. CA-GTF-D Data. 0 ; SAP enhancement package 1 for SAP. When changing a customer with XD99 (MASS), the following dump is raised: Category ABAP Programming Runtime Errors CONVT_NO_NUMBER ABAP Program SAPLVV02 Application Component LO-MD-BPSee more of SAP and ABAP Development on Facebook. Problem with CATCH CX_SY_CONVERSION_NO_NUMBER. Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERSION_NO_NUMBER Date and Time 28. "<==== Here exception BCD_OVERFLOW occurs and is handled by the. UC_OBJECTS_NOT_CHARLIKE: In statement &P1: Table Fields related to FLTP_CHAR_CONVERSION TABLE FIELD Description; FLTP:. 001070 set locale language cur_system_lang. Runtime error: CONVT_OVERFLOW; Non-Handleable ExceptionsMS_EXCEL_OLE_STANDARD_DAT shortdump. SY-LINNO (number of lines in an ABAP list) and SY-COLNO (number of columns in an ABAP list) show how much memory a large ABAP list consumes, if you are having memory problems with a large list. Read more. An exception occurred that is explained in detail below. About this page This is a preview of a SAP Knowledge Base Article. An exception occurred that is explained in detail below. For the rest of the transaction types, the process is very similar. Cause: Overflow in arithmetic operation (type p, with specified length) Runtime error: BCD_FIELD_OVERFLOW; Cause: Operand too big or (interim) result too big2445888-CONVT_NO_NUMBER (CL_SWNC_CONSTANTS) Symptom. : CONVT_OVERFLOW: An overflow occurred while attempting to convert value &P1. if sy-subrc = 1. ST22, ABAP Programming Error, SAPLACHD, "LACHDU01", "DOCHEADERFIELD_MODIFY", SAPMF05A, 1099, 'The program attempted to interpret the value "X" as a number, but since the value contravenes the rules for correct number formats, this was not possible', enjoy, Stucture RFOPTE (Accounting User Options (Single-Screen Transactions) Package. "CONVERT_FISCPER_SELECTION" " (FORM)" . Dump snapshot: The program attempted to interpret the value "000000000000000051 R100" as a. All the steps are fine. LGNUM CHAR 3 T300: 65 LISPL Split to warehouse number required LNSPL_LIKP CHAR 1 66. The current ABAP program 'XXXX' had to be terminated because it has. ZTOAD – Open SQL editor. I find it weird because 0. 1) For the purpose of Evaluation of. catch system-exceptions convt_no_number = 1. : Messages related to F-44 MESSAGE Description; BD100: No TABLES statement for & found: BD101: Table & is not an active table: SG105: Enter rate & / & rate type & for & in the system settings: D2007: No transport request exists:Not yet a member on the new home? Join today and start participating in the discussions!An exception occurred that is explained in detail below. Runtime Errors CONVT_NO_NUMBER Except. <fs_check> is now "R12022". . While carrying out some task in the web ui, like creating a business. Getting Short Dump CONVT_NO_NUMBER. payment proposal and payment run also created. Reason for error: Overflow in arithmetic operation. i try this simple code and get allways a short dump with CONVT_NO_NUMBER. 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 ""ATUALIZA_CALC"" ""(FORM)"" . WRITE: 'is 0'. Cause: Overflow in arithmetic operation (type p, with specified length) Runtime error: BCD_FIELD_OVERFLOW;When creating a vehicle from transaction code VELO action the system will throw ABAP dump CONVT_NO_NUMBER due to value of counter feild MSTA-ZHLER exceeds 99999. The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', w. there is message popped up say"" Old and new exceptions cannot be used at the same time . for my code i am getting a dump CONVT_NO_NUMBER for the values whose decimal places are above 4. Date and Time 29. SAP Help, Wiki, Q&A and other resources for CONVT_NO_NUMBER Click here for the full list of resources and help pages, only the first few are posted below . . 3 : bit, little a fraction closer. Message "Unable to interpret XXX as a number" occurs as shown below: SAP ERP Project System (PS) SAP R/3. 34. CONVT_NO_NUMBER, Unable to interpret as a number,POWN,PPOWN,other dimension filter,ownership_filter,BPC 340 , KBA , EPM-BPC-NW , NetWeaver Version , Problem . Follow RSS Feed Hi All, While executing queries in RSRT as well as Bex Analyzer i am getting the following Dump. This worked fine with SAP BW 3. Boa tarde pessoal, estou fazendo os testes da NF-e 2. SAP ABAP Report : SAPLRHP1 - Personnel Data for Shift Planning. I'm receiving abap dump CONVT_NO_NUMBER when data is being extracted into an infocube from an ods. 2010 05:13:01. store_results, STATISTICS_PROPERTIES, self-monitoring , KBA , BC-DB-HDB-CCM , CCMS /. ST22, ABAP Programming Error, SAPLACHD, "LACHDU01", "DOCHEADERFIELD_MODIFY", SAPMF05A, 1099, 'The program attempted to interpret the value "X" as a number, but since the value contravenes the rules for correct number formats, this was not possible', enjoy, Stucture RFOPTE (Accounting User Options. Runtime error: CONVT_OVERFLOW; Non-Handleable ExceptionsCONVT_NO_NUMBER: An attempt was made to interpret value &P1 as a number. 7 to ECC6. The description of the problem (short dump) To do this, choose System -> List -> Save -> Local File (unconverted) on the screen you are in now. Closed juansebastiansoto opened this issue Feb 4, 2015 · 6 comments Closed Dump in BIND_ALV -> CONVT_NO_NUMBER #357. Could you please suggest what needs to be done? Regards. SAP Transportation Management 9. Runtime Errors CONVT_NO_NUMBER. or0EMPLOYEE_ATTR extraction issue. Unable to interpret " CS080509" as a number. I work for an upgrade project (4. CX_SY_CONVERSION_NO_NUMBER. CX_SY_CONVERSION_NO_NUMBER Cause: Operand cannot be interpreted as number when assigned to a numeric data type Runtime Error: CONVT_NO_NUMBER CX_SY_CONVERSION_OVERFLOW Cause: Overflow in arithmetic operation (type p, with specified length) Runtime Error: BCD_FIELD_OVERFLOW Cause: Operand too big or. A feature that allows users to easily create and edit web pages using a text editor. ENDCATCH. Below is the one you should use to create the delivery. Thanks. The short dump details are as below: SAP ERP 6. CONVT_NO_NUMBER. How can i solve the issue at if line?. SAP ERP Central Component. 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. As field values are displayed in CHAR17 format, a filter is also applied to the table using value of CHAR17 (for example: equal to "001. SAP Landscape Transformation replication server 1. Thank you in advance for all your replies. CONVT_NO_NUMBER: An attempt was made to interpret value &P1 as a number. CA-GTF-D Data Reten 1402453 1 FTWH: Termination CONVT_NO_NUMBER in the form EX. own-developed code), can usually be fixed by the programmer. 2012 08:00:36. Universal worklis, UWL, , KBA , BC-FES-ITS , SAP Internet Transaction Server , Problem . Cause: Target field is too short to represent a decimal floating point number. Click more to access the full version on SAP for Me (Login required). CONVT_NO_NUMBER Value to be converted cannot be interpreted as a number . Answer: 1a : a numerical representation (such as ³/₄, ⁵/₈, or 3. ' mandatory? - SAP Q&A Relevancy Factor: 1. DATA: WA_CHAR TYPE CHAR128 VALUE 'TEST'. IF sy-subrc = 7. value = l_num. Short dump occurs when entering a project ID in app e. I work for an upgrade project (4. Environment. From time to time, the CCMS inftrastructure will raise. LOAD_PROGRAM_INTF_MISMATCH. Include name: LSTXKFRI. Cause: Operand cannot be interpreted as a number Runtime Error: CONVT_NO_NUMBER; CX_SY_CONVERSION_OVERFLOW. For each of the catchable runtime errors, a predefined exception class is specified that can be used to handle the runtime. Runtime Error: CONVT_NO_NUMBER; CX_SY_CONVERSION_OVERFLOW. 10 SAP Netweaver 7. Dear all. Sometime the job log says : 1. 2331235-Dump CONVT_NO_NUMBER occurs in RFZALI20 Symptom After upgrade, when you execute program RFFZALI20 with a variant created before upgrade, below dump occurs. CX_SY_CONVERSION_NO_NUMBERNot yet a member on the new home? Join today and start participating in the discussions!*Printing of Export Invoice, Packing List,Enclosure to Packing List & * *Case Marking in one SMART FORMS Layout *----Not yet a member on the new home? Join today and start participating in the discussions!Runtime Errors: CONVT_NO_NUMBER. Dump CONVT_NO_NUMBER occurs in CX_SY_CONVERION_NO_NUMBER when running CNSXX reports, such as CNS41. About this page This is a preview of a SAP Knowledge Base Article. PY-MY : Split in Borang E form and EA form issues PY-MY. Normally, the issue is because the entered Project ID does not match the coding mask maintained in the SSCUI 102881. Hello all, I have to create one BDC session program for change in valuation price. Other users in Other systems are not getting anyZTOAD – Open SQL editor. Just go to excel sheet and chech whether numeric fields are coming with ',' (comma) sign for number greater than 999. CONVT_NO_NUMBER dump occurs when calling RZ04 transaction (maintain operation modes and instances). How can i solve the issue at if line?. Updated May 18, 2018. therefore caused a. 0 CONVT_NO_NUMBER, CL_HDB_SYSCHK, internal. 2128984-Short dump CX_SY_CONVERSION_NO_NUMBER for ST12. caught in. CS080509 is the batch used in two deliveries. Symptom. CONVT_OVERFLOW Overflow after. 2023 16:04:19. : TIME_OUT:8 Answers. The description of the problem (short dump) To do this, choose System -> List -> Save -> Local File (unconverted) on the screen you are in now. CONVT_CODEPAGE_INIT Conversion of texts from code page to code page not supported . If I call an RFC with out any input from the frontend, it is giving dump. condense it_final. CONVT_NO_NUMBER: An attempt was made to interpret value &P1 as a number. 1 with LA08 patch applied Problem Description: The problem is that in the execution of ITM function module /IBMMON/ITM_WORK_PROCESSES causes the ABAP dump CONVT_NO_NUMBER with exception CX_SY_CONVERSION_NO_NUMBER. Using the name of an exception group, all catchable runtime errors of the group can be caught simultaneously using CATCH SYSTEM-EXCEPTIONS. code fails at this line: l_total_amount = <l_credit_amount> + l_vat_amount. while sy-subrc = 0. Edited by: janani sekaran on Jan 7, 2009. Most of the obsolete catchable runtime errors are assigned to exception groups. 001050 perform pdfcnv_save_otf_tospool tables otf . When changing field "Customs Value" in item tab "Customs Value" in a customer declaration the processing terminates with a dump "CONVT_NO_NUMBER" with short text info ". where sum is of type P of lenght 7. When doing so, you receive a dump like below. Else use the equivalent from xekkn LOOP AT knt. Cannot configure parameter X in task Y. Runtime error: CONVT_OVERFLOW; Uncatchable. 2449471-CX_SY_CONVERSION_NO_NUMBER dump in. SAP Knowledge Base Article - Preview.