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:
Unable to Interpret 0é`Xú_ as a number.
Anyone know how can i solve this issue?
Thanks in advance.

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

Similar Messages

  • Unable to interpret 1,000.000 as a number while posting IDOCs

    Hi All,
    I know this query has been asked multiple times but as of now I am unable to find the right match so posting this query again. We are posting an IDOC from SAP PI to SAP ECC using SAP PI IDOC Adapter. When the IDOC is sent there is one specific value in one of the fields which have value 1000.00. Now when the IDOC is received by SAP the value is received as 1,000.000. As far as I understand this is because the user configured in the RFC destination in SAP PI  (which sends the IDOC to SAP) is having in its default profile the Decimal Notation as 1,234,567.89 and hence we see the value as 1,000.00.
    But then the IDOC is not posted in SAP and the issue is: "Immediately processing not possible: Unable to interpret 1,000.000 as a number".
    As I am not much aware about ABAP being a PI consultant, would appreciate if experts can guide me on how to resolve this issue. Thanks for taking time to read through the issue.

    Please check at abap end for the inbound parameters.
    In we20 the message type will be assigned .Double click it and you will get the process code.Double click that and you will get the required FM.
    If the inbound function module is Z ,Please do the necessary change.
    Else try WE19 to process the idoc (Existing).
    Execute and then check the Inbound function module option and then call in debugging mode to check the where the error is happening.
    Hope it helps.

  • HR : Unable to interpret "40#6411000000#7" as a number

    We upgraded our system from 4.6C to ECC 6.0 Unicode.
    In HR, there is a problem after uploading a file.
    DATA total TYPE p DECIMALS 2.
    DATA : BEGIN OF itab OCCURS 1500,
       clco(2),      "Clé de comptabilisation
       compte(10),   "Numéro de compte
       c_cout(8),    "Center de coût
       montant(15),  "Montant
       texte(55),    "Texte du poste
    END OF itab.
    LOOP AT itab.
          ADD itab-montant TO  total.
    the output of itab-montant comes as 40#6411000000#7 so it can't be put in total...
    The error message is :
    Unable to interpret "40#6411000000#7" as a number.
    How can I solve this problem??
    It's very urgent! please help me...

    as far as i understood..u uploaded some data from a file....
    and it shows an error ....unable to interpret..but when exactly are u getting this error...
    and what should the value look like instead of 40#6411000000#7..can u be some more specific?
    shud there be some vlaues instead of #?
    Edited by: sampath pilla on Apr 29, 2008 8:06 PM

  • Unable to interpret 0.00.00 as a number

    Hi Gurus,
    We are facing issue peculiare issue while doing delta load of material master.
    We are bring materials form R/3 to CRM system as a delta load. We found in R/3, smq1 there are in material master queue stuck due to the error message of "Unable to interpret 0.00.00 as a number".
    Help us to resolve this issue, points are sure and thanks in advance.

    Hi Frederic,
    Thanks a lot, we are using crm 4.0 and R/3 4.7.
    We have checked the SAP Notes mentioned by you, we are getting the error in R/3 outbound queue.
    We have same patch level in the both the system.
    2005_1_620 SAPKIPYJ55
    In  R/3:
    2005_1_640 SAPKIPYJ65
    Do you have any idea?

  • Unable to interpret " 12,000.00 " as a number.

         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

  • Unable to interpret " 1,100.0 " as a number

    Hi all
    Im getting this error when I try to print a customized sapscript form. This sapscript call a form from include file.
    Here's the code:
    FORM Cal_weight tables in_tab structure itcsy             
                           out_tab structure itcsy.           
      DATA: mate TYPE STRING, "Material no                    
            umret TYPE MARM-LAENG, "Temp qty                  
            umrez LIKE MARM-UMREZ, "B.UOM qty                 
            umren LIKE MARM-UMREN. "A.UOM qty                                                                               
    READ table in_tab index 1.                              
      MOVE in_tab-value to mate.                                                                               
    READ table in_tab index 2.                              
      MOVE in_tab-value to mqty.        <--- the error is pointing to here.                        
      umret = mqty.                                                                               
    SELECT SINGLE UMREZ UMREN                               
      INTO (umrez, umren)                                     
      FROM MARM                                               
      WHERE MATNR = mate                                      
      AND MEINH = 'KG'.                                                                               
    umret = ( umret / umrez ) * umren.                      
      mqty = umret.                                                                               
    read table out_tab index 1.                             
      move mqty to out_tab-value.                             
      modify out_tab index sy-tabix.                          
    And this is the call code in sapscript:
    DEFINE &V_WEIGHT& = ''.
    Please advise

    Hi Santosh
    I've changed it to 'write' but I encounter this error in the include file.
    " "MQTY" must be a character-type field (data type C,N,D or T)"
    Any idea?

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

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

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

  • Unable to Interpret SSO Ticket Recieved.

    Hai ,
    While working in ESS , I tried to create travel request. While creating i recieved Error message.
    Error: System is Unable to Interpret SSO ticket recieved.
    Kindly Help me out.

    Please check tha SSO is configured correclty & test is fine from both Portal & Back-end side.
    Please refer to
    In case you still face an issue, then please let me know.

  • File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

    Hi All,
    Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
    Anyidea what might have gone wrong??
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      +<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
    Waiting for your answers.
    Thank You.

    Hi Seema,
    I think you are using mi_Orders05_In_Asyn as the IDOC interface.
    Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
    Let us know if that doesnt solve your problem.

  • Unable to interpret u3030u0081@ as a number - problem

    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 &#12336;@ 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

    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.

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

    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.

  • Unable to interpret IDoc interface ReplenishmentOrderNotification_In

    Hi All,
    I am trsfering orders03 idoc from r/3 4.5 B system to XI and from XI to SNC system using idoc adapter.
    In sxmb_moni, When I double click on particular XML message with errors
    I am getting error in call adapter
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ReplenishmentOrderNotification_In</SAP:Stack>

    I am creating JDBC to IDOC scenario but experiencing the same issue.
    Can you advise how you solved this?

  • RFC_ERROR_SYSTEM_FAILURE: Unable to interpret * as a number

    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.

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

  • Error:Unable to interpret "TABLE".

    When I use BTE, There is an error in FM Z_WRITE_TO_QUEUE in R/3.
    ""Local interface:
    *"  TABLES
    *"      I_T_DATA OPTIONAL
        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.
        <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>.
            i_datasource             = i_datasource
            i_isource                = ''
            i_updmode                = ''
            i_t_select               = l_t_select
            i_t_fields               = l_t_fields
            c_t_data                 = <e_t_data>
            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.
            i_isource     = i_datasource
            i_no_flush    = 'X'
            e_subrc       = l_subrc
            i_t_data      = <e_t_data>
            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.
          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.
    "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!

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

Maybe you are looking for