CONVT_NO_NUMBER Unable to interpret "*0" as a number.

Hi gurus,
I am encountering this dump while running a report in background. The report takes process order numbers as input and updates a Z-Table accordingly. However, this dump occurs only when the report is run in background. When run in foreground the report executes flawlessly.
Also, when the report is run for multiple process orders in background the dump is displayed.. On debugging the job i  found the process order number relevant to the dump. However, when i executed the job in background for just this process order, the report was executed successfully.
Deparately in need of help!!!
Regards,
Xineohpi.

SAP has precisely pointed out the problem, so ignore the background noise and  concentrate your efforts on finding precisely the field and the data value that causes your error.
Since '*0' is NOT a number, find the field in the dump that has that value in it and figure out how that value is getting there...the asterisk would appear to indicate an overflow condition, in which the input value exceeds the length of the numeric field. For example, I would expect to see this happen if I had a field(2) type n and my input was '100'.   Check to see if that is what is happening to you, and why, based upon your input.
See other posts re: CONVT_NO_NUMBER errors....it's because a numeric field contains something other than digits, a decimal and a sign.
Edited by: DaveL on Jun 29, 2011 2:28 PM

Similar Messages

  • Unable to interpret u3030u0081@ as a number - problem

    Hi,
    We've got problem with BPMs which use graphical (java) mapping. In SXI_MONITOR such processes have "Message being sent" status. In process engine workflow log it stops at mapping step with "In process" status. Technical details show that there is a tRFC call which fails with "Unable to interpret 〰@ as a number.". This is also visible in ST22. BPM without mapping works without any problems. Test mapping in integration repository works fine.
    Has anyone got any ideas?
    Kind regards,
    Michal Krawczyk

    Hi,
    Have you tested your mapping using the actual source message that caused the error in BPM?
    From the BPE monitor copy-n-paste the actual message into the Interface Mapping test tool.
    Regards,
    Bill

  • TRFC Queue Error "Unable to interpret BGUA as a number"

    Hi all,
    I am getting the below error message in TRFC queue
    "Unable to interpret BGUA as a number" when i do a datamart dataload from ODS to Cube. ODS is getting data from datasource 0CO_OM_CCA_9. Can anyone help how to resolve this issue?.
    Thanks & Regards,
    Muruganand. K

    What is  BGUA ??
    I think you have mapped this field (BGUA holding infoobject) to number or key figure field.
    Check your  mapping in transformation form ODS to CUBE.
    Hope this helps.

  • Error Unable to interpret C00 as a number while doing intial download

    Hi Guys
    When I am doing the initial download of DNL_CUST_CNDALL the following error has occurred in the Inbound Queue of CRM “Unable to interpret C00 as a number Message no. SR053”
    Can anybody suggest me how to over come?
    Thanks

    Here is the solution. (SAP Note 1042818 pointed me in the right direction...even though I'm not working with CRM.)
    CONVERT_OTF export parameter BIN_FILESIZE has no type and is pass by value.  You must code this parameter into your importing parameters in the calling program even if you don't use it.  The receiving variable should be of type integer.
    DATA: BIN_FILESIZE TYPE I.
      CALL FUNCTION 'CONVERT_OTF'
        EXPORTING
          FORMAT                      = 'PDF'
        IMPORTING
          BIN_FILESIZE                = BIN_FILESIZE
        TABLES
          otf                         = otf
          lines                       = it_pdfdata
        EXCEPTIONS
          ERR_MAX_LINEWIDTH           = 1
          ERR_FORMAT                  = 2
          ERR_CONV_NOT_POSSIBLE       = 3
          ERR_BAD_OTF                 = 4
          OTHERS                      = 5.
    I guess I figured I didn't need bin_filesize, so I didn't include in my original call...

  • Short dump - Unable to interpret "USD " as a number

    Hi,
    I am trying to pass 'price unit' to BAPI -> BAPI_PO_CREATE1
    But while executing below statement, i got a short dump -> Unable to interpret "USD " as a number
    wa_poitem-price_unit    = wa_data-peinh
    here wa_poitem of type BAPIMEPOITEM-PRICE_UNIT, which is DEC. legth 5
    and wa_data-peinh of type CHAR, which is uploaded data from excel

    Hi
    Something is uncorrect in your file or in your program
    It seems you're transfering the currency (USD) to the field for unit price: here u need to indicate which the unit price is
    The Unite Price should be = Net Price / Quantity
    The currency should be transfered in the header data: BAPIMEPOHEADER-CURRENCY
    Max

  • SMQ2 failure during Initial load - Unable to interpret 9.990. as number

    hi All,
    I perform the initial download of customizing objects from R/3(4.6C) to CRM 7.0.
    For object DNL_CUST_BASIS2 I received the "Unable to interpret 9.990.  as a number" error message.
    Could you give some hints how to solve this problem?
    I checked several posts with similar error messages, but none of them seemed to be related to my case.
    We just implemented note 777944 to update SMOFPARSFA in CRM to neglect the unicode check.
    I was able to download other customizing objects like DNL_CUST_BASIS, DNL_CUST_ACGRPB, DNL_CUST_ACGRPP, DNL_CUST_ADDR.
    My next step is to debug the queue, if you have further suggestions let me know.
    Thanks

    Hi,
    Please check my reply in the link
    Loading DNL_CUST_BASIS2: Unable to interpret "9.990. " as a number.
    Hope this will help.
    Thanks,
    Vikash.

  • ABAP Dump:  CONVT_NO_NUMBER  Unable to interpret "1.96432  " as a number

    Dear SAP friends,
    I am an FI functional consultant.  Our ABAP developer is unable to resolve this issue so I am hoping you may be able to steer me into the right direction.
    We just upgraded out SAP to SP18 and this issue exists only in production.  Our development and quality system are fine.
    We receive this error when the user executes a customer statement and a AP check run.  The ABAP program is ZFORM_SCRIPT.
    I have reviewed the forum and found a lot of helpful information including checking the user settings under SU01, etc.  Our developer has been unsuccessful in finding the solution.  Our database analyst confirmed the data is identical in all systems so that eliminates a data issue.
    Our ABAP understands there is a space behind the number.  The space character is making the new variable think it's not a number.  How do we fix it?
    Furthermore, I am confused as to how or why the 3 systems could be different?  Why do we have this issue in production and not quality, etc?  They have been upgraded and they are all a copy of production.
    If you anyone can shed some light, it would be greatly appreciated.  We are unable to print AP checks because the print program fails.  The financial posting happens but no check number is created.
    Very frustrating.  Thank you.

    From ST22
    Source Code Extract
    Line
    SourceCde
    27
    28
         -->IN_PAR     text
    29
         -->OUT_PAR    text
    30
    31
    FORM ovr_udr TABLES in_par STRUCTURE itcsy
    32
    out_par STRUCTURE itcsy.
    33
    34
    DATA: amt(20),
    35
    namt TYPE netwr.
    36
    DATA: signature(1),
    37
    len TYPE i,
    38
    pos TYPE i.
    39
    40
    LOOP AT in_par.
    41
    CASE in_par-name.
    42
    WHEN 'REGUD-SWNET'.
    43
    amt = in_par-value.
    44
    ENDCASE.
    45
    ENDLOOP.
    46
    CONDENSE amt NO-GAPS.
    47
    len = STRLEN( amt ).
    48
    pos = len - 3.
    49
    IF amt+pos(1) = '.'.
    50
    TRANSLATE amt USING ', '.
    51
    CONDENSE amt NO-GAPS.
    52
    ELSE.
    53
    TRANSLATE amt USING '. '.
    54
    CONDENSE amt NO-GAPS.
    55
    TRANSLATE amt USING ',.'.
    56
    ENDIF.
    >>>>>
    namt = amt.
    58
    IF namt > 10000.
    59
    signature = 'X'.
    60
    ENDIF.
    61
    62
    LOOP AT out_par.
    63
    CASE out_par-name.
    64
    WHEN 'SIGNATURE'.
    65
    out_par-value = signature.
    66
    ENDCASE.
    67
    MODIFY out_par.
    68
    ENDLOOP.
    69
    |   70|ENDFORM.                    "ovr_udr

  • Unable to interpret "M" as a number.

    data: l_period(6) type n.
    data:        g_cols type i ,                     " number of columns
                 g_rows type i,                      " Number of Lines
                 g_dc(5) type c,                     " Date format
                 g_count type n,                     "Period Value Count
                 g_sta_col(6) type i.                   "Start Column
    move g_sta_col to l_period.
          move g_sta_col to wa_colno.
         move wa_colno to wa_flname.
          concatenate g_dc wa_colno into wa_flname.
    Set up fieldvalue
          read table it_total
              with key matnr = gk_final_ok-plantno customerno = gk_final_ok-customerno+gk_final_ok-custcolor spmon = l_period.
          if sy-subrc eq 0.
            fieldvalue = it_total-kwmeng.
          else.
            fieldvalue = ''.
          endif.
    当我调试时此行报错,哪位大哥知道是什么原因呀?
    read table it_total
              with key matnr = gk_final_ok-plantno customerno = gk_final_ok-customerno+gk_final_ok-custcolor spmon = l_period.

    你说的对,+ 的地方错了,
    不知道你的 gk_final_ok-custcolor 是个什么东西,为什么要把颜色字段当作一个偏移量来使用?
    我这里是客款+客色加错了,两个字段不能直接连接.中间有个#分隔,
    thanks!

  • Unable to Interpret "32" as a number

    Hi all,
    I am getting # into the internal table despite am using follwoing code
    ECC 6.0
    FORM DATA_SELECTION .
      DATA : L_MENGE(17).
      OPEN DATASET P_FILE FOR INPUT IN TEXT MODE ENCODING UTF-8.
      IF SY-SUBRC = 0.
        DO.
          READ DATASET P_FILE INTO WA_ITAB.
          IF SY-SUBRC = 0.
            SPLIT WA_ITAB AT CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB INTO ITAB-WERKS
            ITAB-MATNR
            ITAB-EKGRP
            ITAB-LIFNR
            ITAB-EVERS
            L_MENGE.
            TRANSLATE L_MENGE USING '# '.
            CONDENSE L_MENGE.
            ITAB-MENGE = L_MENGE.
            APPEND ITAB.
            CLEAR  ITAB.
          ELSE.
            EXIT.
          ENDIF.
        ENDDO.
      ENDIF.
      CLOSE DATASET P_FILE.

    Hi,
    Check that this may be because of UNICODE related problems.
    Regards,
    Anji

  • Data Type Conversion - DUMP - Unable to interpret "ABC1234 " as a number.

    Hi Experts,
    Am getting dump, my code is,
    data:
    it_asset-anln1 type anla-anln1. (here its CHAR 12).
    unpack it_asset-anln1 to it_asset-anln1.
    here, when am getting the the values as ABC1234 into it_asset-anln1----
    > am getting DUMP, so, let me know that, How to fix it?
    thanq

    Pretty sure that you can not unpack a value when it has non-numeric characters, so you will want to check it before doing the UNPACK.
    if it_asset-anln1 CO '1234567890. '.
    unpack it_asset-anln1 to it_asset-anln1.
    endif.
    Regards,
    Rich Heilman

  • Unable to Interpret 0é`Xú_ as a number in CJ20N

    Hi experts,
    I have only one user with this problem, every time she tries to get into the Tcode CJ20N, she receives a DUMP, saying this:
    CONVT_NO_NUMBER
    Unable to Interpret 0é`Xú_ as a number.
    SAP Program is SAPLCNPB_W
    Anyone know how can i solve this issue?
    Thanks in advance.

    Hello,
    if this is happening just for one user, you might want to check her parameters in SU01...
    Rgds
    Martina

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

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

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

  • Error: Unable to interpret / as a number

    We have an R/3 Infoset that is used as a source for some Crystal Report queries -- basically it is pulling some revenue recognition data from GLPCA and pairing it with supporting tables such as billing documents, orders, customer, material, etc.  This has been available in Production for a few months, but recently a user has started encountering the following messages at runtime:
    Crystal Reports
    Failed to retrieve data from the database.
    Database Connector Error: 'Unable to interpret / as a number.'
    Database Connector Error: 'RFC_INVALID_HANDLE'
    So we were able to even track down the error to one specific billing document and can recreate the error when selecting only the one document number.  The report errors whenever it pulls that data and if a certain amount field is brought in to the listing.  Looking at the underlying data through an SQL query, we don't see a problem with the data and have been unable to figure out why only certain records are causing this short dump.  The abend info in ST22 shows it is related to a CONVT_NO_NUMBER runtime error in ABAP program /CRYSTAL/SAPLFLAT - procedure /CRYSTAL/BUILD_STRING.  Looking through the details did not uncover much information that would point to the problem.
    Has anyone encountered this type of problem with Crystal integration to SAP data? Any suggestions on troubleshooting or identifying the problem would be appreciated.

    Hi,
    would suggest you open a case with support and provide the details on the steps so that the support folks can directly look at your system.
    thanks
    Ingo

  • RFC_ERROR_SYSTEM_FAILURE: Unable to interpret * as a number

    Hi,
    I facing a strange problem while executing a query in bex analyzer and WAD. When I open a query it is throwing error as 'Unable to interpret * as a number'. I am getting this error before the pop-up menu itself. But all other reports are working fine. Please guide me to solve this issue.
    Regards
    Githen

    hi Githen Ronney  ,
    Is that query Standard OR customized one.
    If it is standard once check the SAP-EXIT variables.
    Thanks,
    KIran Manyam

  • ABAP DF Unable to interpret as a number

    I have a very simply ABAP data flow which joins SAP tables PA0001 and T528T together using PLANS.  If I use PA0001.PLANS in my output schema I receive the following error message:
    "RFC CallReceive error <Function Z_AW_ABAP_RUN: RFC_ABAP_MESSAGE- Unable to interpret 0    0.00 as a number."
    If I select T528T.PLANS in the output schema it works fine, but I have no idea what is causing this error message.

    Hi Tom,   If the error si correcto, it seems to be a string trying to be saved on a integer field. Change the target data type or validate it before be loaded. I amnot sure if the error is "0    0.00 " >string or "0.00 " >number,but not a integer. Regards.

Maybe you are looking for