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.

Similar Messages

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

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

Error:Unable to interpret "TABLE".

When I use BTE, There is an error in FM Z_WRITE_TO_QUEUE in R/3.
FUNCTION Z_WRITE_TO_QUEUE.
""Local interface:
*" IMPORTING
*"     REFERENCE(I_DATASOURCE) TYPE ROOSOURCE-OLTPSOURCE
*" TABLES
*"      I_T_DATA OPTIONAL
TYPE-POOLS:
    sbiwa.
DATA:
    l_exstruct TYPE roosource-exstruct,
    l_initflag TYPE roosprmsc-initstate,
    l_subrc    TYPE sy-subrc,
    lr_is_data TYPE REF TO data,
    lr_es_data TYPE REF TO data,
    lr_et_data TYPE REF TO data,
    l_t_fields TYPE sbiwa_t_fields,
    l_t_select TYPE sbiwa_t_select.
FIELD-SYMBOLS:
    <i_s_data> TYPE ANY,
    <e_s_data> TYPE ANY,
    <e_t_data> TYPE STANDARD TABLE.
Check to see if Delta initialization has been performed.
SELECT SINGLE initstate FROM roosprmsc INTO l_initflag
         WHERE oltpsource = i_datasource
         AND    rlogsys     NE space
         AND    slogsys     NE space
         AND    initrnr     NE space.
If initialization has taken place continue
IF sy-subrc EQ 0 AND l_initflag EQ 'X'.
grab the extraction structure from roosource based on the
datasource parameter input.
    SELECT SINGLE exstruct FROM roosource INTO l_exstruct
           WHERE oltpsource = i_datasource
           AND    objvers     = 'A'.
    CHECK sy-subrc = 0.
    CREATE DATA lr_is_data LIKE LINE OF i_t_data.
    ASSIGN lr_is_data->* TO <i_s_data>.
    CREATE DATA lr_es_data TYPE (l_exstruct).
    ASSIGN lr_es_data->* TO <e_s_data>.
    CREATE DATA lret_data TYPE STANDARD TABLE OF (l_exstruct)._
      ASSIGN lr_et_data->* TO <e_t_data>.
    LOOP AT i_t_data ASSIGNING <i_s_data>.
      CLEAR <e_s_data>.
      MOVE <i_s_data> TO <e_s_data>.
     MOVE-CORRESPONDING <i_s_data> TO <e_s_data>.
      INSERT <e_s_data> INTO TABLE <e_t_data>.
    ENDLOOP.
    CALL FUNCTION 'EXIT_SAPLRSAP_001'
      EXPORTING
        i_datasource             = i_datasource
        i_isource                = ''
        i_updmode                = ''
      TABLES
        i_t_select               = l_t_select
        i_t_fields               = l_t_fields
        c_t_data                 = <e_t_data>
      EXCEPTIONS
        rsap_customer_exit_error = 1
        OTHERS                   = 2.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    CALL FUNCTION 'RSC1_TRFC_QUEUE_WRITE'
      EXPORTING
        i_isource     = i_datasource
        i_no_flush    = 'X'
      IMPORTING
        e_subrc       = l_subrc
      TABLES
        i_t_data      = <e_t_data>
      EXCEPTIONS
        name_too_long = 1
        OTHERS        = 2.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDIF.
ENDFUNCTION.
      FORM abs_type_to_rel_type                                     *
      The purpose of this subroutine is to convert an absolute type *
      name into a relative type name.                               *
--> TYPE_NAME                                                     *
form abs_type_to_rel_type changing type_name.
data junk(100) type c.
split type_name at '\TYPE=' into junk type_name.
endform.
"CREATE DATA lr_et_data TYPE STANDARD TABLE OF (l_exstruct)" makes an Error "Unable to interpret "TABLE"."
I don't why!
So anbody can help me?
Thank you!

Hi,
Use this statement.
data:begin of lr_et_data occurs 0,
include l_exstruct.
end of lr_et_data.
Ravi

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

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

Error "Unable to interpret '\' as number" whe run a BDC for integer data

Dear All,
I am trying for the BDC of the user define table and have to upload data but the system is giving error for the field whose domain i have made as QUAN Error is : "Unable to interpret '\' as number".
Please clarify the situation and solution for the problem
Regards,
vishal.

Hi Vishal,
Check whether '\' is getting populated in any of the field on the screen in which it is giving an error. I think it is not because of your QUAN field. The error may be in some other field on the same screen.
Regards,
Swapna.

Error ' unable to interpret "*601" as number ' when using CONVERT_OTF

Hi All ,
I am converting a Smartform to PDF in 4.7 version and I am getting an error like " unable to interpret "*601" as number ' in Convert_otf function module here the importing parameter BIN_FILESIZE is getting *601 value in back ground of FM . Can any one help me in solving this error . Did i miss any parameter's .
Thanks and Regards
Syed Akbar .

Hi.
The asterisk can appear when field length inconsistency takes place at value assignment between two variables.
Example:
DATA:
p_amount TYPE c length 15,
l_amount TYPE p DECIMALS 2.
WRITE: l_amount CURRENCY l_waers TO p_amount.
If value of L_AMOUNT equal '103276149119,40-', then value of P_AMOUNT will be equal '*3276149119,40-' (asterisk appears).
Best regards,
George Shlyahov.

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

Dump Error : Unable to Interpret '/'

Hello,
         we are trying to upload Material Master, where we have a Custom Field, this custom field is defined as NUMC(10) data type in BMMH1-YYD_YMANU and also in MARC table. And this field has been customized in Material Master in a seperate screen, our client our in production from long time, now we are getting problem only when migrating data. Manually it works fine.
And this field was configured in the below LSMW Program,
Object               0020   Material master
Method               0000
Program Name         RMDATIND
Program Type         D   Direct Input
Now while uploading we are getting error at statement MOVE_FIELD_SLASH statement saying cannot interpret slash(/).
But we are passing Number '1000000012' into this field. And if we pass blank then we are not getting this error, cannot reallly find what the problem is.
Can any one help.

Murali R wrote:
Hi Anand,
>
> Thanks for yor reply.
>
> The field FKDAT in source system is in YYYYMMDD format only. The date values coming in is like 12.08.2011.
>
> Regards,
> Murali
Try this..
data:l_date type sy-datum.
l_date0(4) = FKDAT5(4).
l_date4(2) = FKDAT3(2).
l_date6(2) = FKDAT0(2).
Now use l_date to subtract from sy-datum.

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!

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 " 12,000.00 " as a number.

Hi,
can some one help me with this error:
Unable to interpret " 12,000.00 " as a number.

Hi Sanjay,
[unable to interpret as number|unable to interpret as number]
Here is a post in SCN which describes all the possible ways to solve your problem..
Thanks & regards,
Dileep .C

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

Similar Messages

Maybe you are looking for