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

Similar Messages

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 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...

Abap dump (Unable to interpret "65000.00u00A0 " as a number.)

hi everyone,
                       im getting the following dump error.
Unable to interpret "65000.00 " as a number.
previously it worked fine. after some patches moved from production server to quality server
and from quality to production this report alone getting dump.
DATA: pono LIKE ekko-ebeln,
      poit LIKE ekpo-ebelp,
      SNO LIKE ESSR-LBLNI,
      PIT LIKE EKPO-EBELP,
       dis LIKE konv-kbetr,
      frg LIKE konv-kbetr,
      VAL LIKE KONV-KBETR,
FORM tax TABLES intab
STRUCTURE itcsy outtab
STRUCTURE itcsy.
READ TABLE intab INDEX 1.
pono = intab-value.
READ TABLE intab INDEX 2.
poit = intab-value.
READ TABLE intab INDEX 3.
SNO = intab-value.
READ TABLE intab INDEX 4.
L_CHAR1 = intab-value.
REPLACE all occurrences of ',' in l_char1 with ' '.
VAL = L_CHAR1.      <----
this is the line im getting dump. l_char1 = 65,000.00
thanks in advance
karthe

KARTHE wrote:
> Unable to interpret "65000.00 " as a number.
>   VAL = L_CHAR1.      <----
this is the line im getting dump. l_char1 = 65,000.00
you mention "65000.00 " and "65,000.00" and i guess L_CHAR1 contains "65,000.00".
If that's the case, remove the thousand separator from L_CHAR1, so 65,000.00 becomes 65000.00
edit: basically what Pawan mentioned.
Edited by: Maen Anachronos on Oct 5, 2010 1:48 PM

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.

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

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

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!

FM SO_NEW_DOCUMENT_SEND_API1 short dump

hello experts,
im using the FM SO_NEW_DOCUMENT_SEND_API1 to send email. my program encounters short dump.
here is my code:
* p_text_alert = The Maximum Blocked Time limit has been exceeded for DL13LT. in 0082
* lt_receptores-rec_id = AVISOLOG0082
* text-006 = doesnt matter
Data: lv_obj_desc TYPE SODOCCHGI1.
Data: lt_receptores TYPE somlreci1 OCCURS 0 WITH HEADER LINE,
           lt_cuerpo     TYPE solisti1 OCCURS 0 WITH HEADER LINE.
REFRESH lt_receptores.
concatenate 'AVISOLOG' p_werks Into lt_receptores-receiver.
lt_receptores-rec_id   = lt_receptores-receiver.
lt_receptores-rec_type = 'U'.
APPEND lt_receptores.
REFRESH lt_cuerpo.
lt_cuerpo-line = ( p_text_alert ).
APPEND lt_cuerpo.
Clear lv_obj_desc.
lv_obj_desc-obj_descr = text-006.
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
    EXPORTING
      document_data           = lv_obj_desc
      commit_work             = 'X'
    TABLES
      object_content          = lt_cuerpo
      receivers               = lt_receptores.
this is the description of the dump:
"    Unable to interpret "The Maximum Blocked Time limit has been " as a number.    "
error analysis:
" An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not
   caught in
procedure "F_SEND_VIOLATION_MAIL" "(FORM)", nor was it propagated by a RAISING
   clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The program attempted to interpret the value "The Maximum Blocked Time limit
   has been " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible. "
what canbe the cause of the dump?
thanks a lot for future replies.

Hi,
This code might be helpful...
CLEAR: gs_packing_list,
         gs_reclist.
REFRESH: gt_packing_list[],
           gt_reclist[].
* Fill the document data.
DESCRIBE TABLE gt_message LINES gv_cnt.
READ TABLE gt_message INTO gs_message
                                INDEX gv_cnt.
gs_doc_chng-doc_size   = ( gv_cnt - 1 ) * 255 + STRLEN( gs_message ).
gs_doc_chng-obj_langu = sy-langu.
gs_doc_chng-obj_name   = 'CONJOB'.
gs_doc_chng-obj_descr = text-017.
gs_doc_chng-sensitivty = 'F'.
* Fill the receiver list
gs_reclist-rec_date    = sy-datum.
gs_reclist-rec_type    = 'U' .         " For Internet Address
gs_reclist-com_type    = 'INT'.
gs_reclist-notif_ndel = c_x.
gs_reclist-receiver    = p_email.       "Email addr of Recip
APPEND gs_reclist TO gt_reclist.
CLEAR gs_reclist.
gs_packing_list-transf_bin = space.
gs_packing_list-head_start = 1.
gs_packing_list-head_num   = 0.
gs_packing_list-body_start = 1.
DESCRIBE TABLE gt_message LINES gs_packing_list-body_num.
gs_packing_list-doc_type   = 'RAW'.
APPEND gs_packing_list TO gt_packing_list.
gs_packing_list-transf_bin = c_x.
gs_packing_list-head_start = 1.
gs_packing_list-head_num   = 0.
gs_packing_list-body_start = 1.
DESCRIBE TABLE pt_attachment LINES gs_packing_list-body_num.
gs_packing_list-doc_type   = 'RAW'.
gs_packing_list-obj_descr = gv_atch_name.
gs_packing_list-obj_name   = gv_atch_name.
gs_packing_list-doc_size   = gs_packing_list-body_num * 255.
APPEND gs_packing_list TO gt_packing_list.
* Send the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
       EXPORTING
            document_data              = gs_doc_chng
            put_in_outbox              = c_x
       TABLES
            packing_list               = gt_packing_list
            contents_txt               = gt_message
            contents_bin               = pt_attachment
            receivers                  = gt_reclist
       EXCEPTIONS
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8.
Regards
Milan

Short dump transferring more than 99 items from catalog to shopping cart

Hi
I'm encountering a short dump when trying to transfer any more than 99 items from the internet sales catalog to an EBP shopping cart.
The error states "Unable to interpret "*0" as a number" - the code in the error suggests that the system is attempting to populate field LCNT with *0.
Any ideas greatly appreciated.
Regards
David

Hi both
Thanks for the replies. I've already checked the usual channels (OSS, Google etc) without success, hence my thread here.
The business reasons for having 99 catalogue items are not particularly strong, but it would be a 'nice to have' as one or two users have fallen foul of it. They can obviously raise separate carts if necessary.
If the consensus is there's no solution then we'll just have to put up with it as a catalog limitation!
Regards
David

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

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.

Short dump on calculating percentage

hi experts,
   i'm trying to calculate for the total salary based on the reference value.
but when i'm retrieving the PTOT(totalsalary) for calculation ,i got into short dump CONVT_NO_NUMBER or CX_SY_CONVERSION_NO_NUMBER.
It's unable to interpret "PTOT(ASSUME '134,475.81')" as a number.
HERE i've given my logic what i used.
if anyone knows plz help me.
Table for collection of data. Used in hr_basic_display_list.
DATA: BEGIN OF DATA_TAB OCCURS 20,
        PERNR(8), WGTYP(10), WTEXT LIKE T512T-LGTXT,
        APR(12), MAY(12), JUN(12), JUL(12),AUG(12), SEP(12),
        OCT(12), NOV(12), DEC(12),JAN(12), FEB(12), MAR(12), ptot(15),
        LANGTEXT1(60), LANGTEXT2(60), LANGTEXT3(60), LANGTEXT4(60),
        SORTEXT(250),
END OF DATA_TAB.
DATA:BEGIN OF ITAB_PER OCCURS 0,
     PERCENT(15),         The field to be added in the output ALV screen                                                                                END OF ITAB_PER.              to calulate percentage
.enhanced fields in            .                                              selection screen of report HINCANN0
PARAMETERS : P_PERCEN(15) , the reference field
LOOP AT DATA_TAB.                                       "changes
ITAB_PER-PERCENT = ( DATA_TAB-PTOT / P_PERCEN ) * 100.
    APPEND ITAB_PER.
    CLEAR ITAB_PER.
    ENDLOOP.

Hi Siva
Change the type of PERCENT to dec instead of Char.
~BiSu

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

Similar Messages

Maybe you are looking for