Unable to interpret 15.09.2010 08:55:00 as a number.

Hi,
■The following error text was processed in the system  : Unable to interpret 15.09.2010 08:55:00 as a number.
■The error occurred on the application server *** and in the work process 1 .
■The termination type was: RABAX_STATE
■The ABAP call stack was:
Method: IF_BOL_BO_PROPERTY_ACCESS~GET_PROPERTY_AS_STRING of program CL_CRM_BOL_ABSTR_BO===========CP
Method: GET_ENDTIME of program ZL_BT126H_A_APPTDETAILS_CN0412CP
Method: IF_BSP_MODEL_BINDING~GET_ATTRIBUTE of program CL_BSP_MODEL==================CP
Method: RESOLVE_MODEL_BINDING of program CL_THTMLB_SELECTION_BOX=======CP
Method: IF_BSP_ELEMENT~DO_AT_BEGINNING of program CL_THTMLB_SELECTION_BOX=======CP
when i am creating activity if i select category is call i need to add 10 min to end time based on start time .
ex: end time = start time + '600'.
technical information :
UI Component : BT126H_APPT
View : BT126H_APPT/ApptDetails
Context Node : BTACTIVITYH
Attribute : CATEGORY
for Start Time :
Contex node : BTDATE
Attribute : TIME
for End Time :
Context node : BTDATE
Attribute : ENDTIME
please advice me how to procedue  below the code i redefine get_endtime
method GET_ENDTIME.
*CALL METHOD SUPER->GET_ENDTIME
*  EXPORTING
*    ATTRIBUTE_PATH =
**    ITERATOR       =
*  RECEIVING
*    VALUE          =
***************************************************************8888
DATA lr_btactivityh TYPE REF to cl_crm_bol_entity.
DATA lr_endtime TYPE REF to cl_crm_bol_entity.
  DATA : lv_time TYPE p,
         value1 type p,"TZNTSTMPL,
        lv_category type string.
  lr_endtime ?= owner->ztyped_context->BTDATE->collection_wrapper->get_current( ).
************read category
  lr_btactivityh ?= owner->ztyped_context->btactivityh->collection_wrapper->get_current( ).
CALL METHOD lr_btactivityh->get_property_as_string
  EXPORTING
    iv_attr_name = 'CATEGORY'
  receiving
    rv_result    = lv_category
  IF lv_category = 'Y10'. " check the actual value
CALL METHOD lr_endtime->get_property_as_string
  EXPORTING
    iv_attr_name =  'TIMESTAMP_FROM' " 'TIME' "DATE
  receiving
    rv_result    = lv_time
CALL METHOD cl_abap_tstmp=>add
        EXPORTING
          tstmp   = lv_time   "-->20100404100000  ( input details 2010/04/04 10:00:00)
          secs    = 600      " -->600 seconds
        RECEIVING
          r_tstmp = value1."  -->20100404101000
  ENDIF.
value = value1.
endmethod.
jemmi.

Hi,Harshit Kumar.
Thanks for your valuable support
i changed   DATA : lv_time TYPE  string,
and also change to
CALL METHOD lr_endtime->get_property_as_string
  EXPORTING
    iv_attr_name =      'TIME'
  receiving
    rv_result    = lv_time
value = lv_time + 500.
but it's showing error like
 
Cannot display view BT126H_APPT/ApptDetails of UI Component BT126H_APPT
An exception has occurred Exception Class  CX_CRM_CIC_PARAMETER_ERROR - Entry parameter of method CL_CRM_BOL_ENTITY->GET_PROPERTY contains value TIME, which is not allowed 
Method:  CL_CRM_BOL_ENTITY=>IF_BOL_BO_PROPERTY_ACCESS~GET_PROPERTY 
Source Text Row:  19
please guide me how to solve this issue.
jemmi.

Similar Messages

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

  • 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

  • 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.
    Regards
    ArunRajan,
    Hosur

    Hi,
    Please check tha SSO is configured correclty & test is fine from both Portal & Back-end side.
    Please refer to
    [http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm|http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm]
    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:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      +<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
      <SAP:Retry>M</SAP:Retry>
    Waiting for your answers.
    Thank You.
    Seema.

    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.
    Regards,
    Sumit

  • 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 &#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

    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

  • 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 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
    details:
    <?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:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>ReplenishmentOrderNotification_In</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ReplenishmentOrderNotification_In</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

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

  • 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

  • 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 IDoc interface  Error

    Hi All,
    We are getting the following error while trying to translate a X12 to IDOC , we are using Seeburger Adapters for the translation.
    <?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:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to interpret IDoc interface I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The Reason we are using a Interface rather than using a IDOC directly is because our the IDOC Structure is 867.ORDERS01.ZORDRS1x and this is a custom IDOC in ECC and when we try to directly use the structure in the Interface Determination we get the error
    Check Result for Object ARROWUS | ARROWUS_IN_AS2 | A_867_V4010_ABS | | BS_ECC_D03_DEV
    First character invalid: 8 Only a(A)-z(Z), 0-9, and "/" and "_" are permitted
    Has anyone faced a similar problem ? If so please let me know how you fixed it.
    Appreciate your help
    Regards,
    Madhu

    have you seend below threads:
    [link1|Unable to interpret IDoc interface ZSHIPDEL_packageRD;
    [link2|IDOC Error;

  • Unable to interpret IDoc interface ZSHIPDEL_packageRD

    Hi,
    I am doing a file-xi-idoc scenerio.
    I've exported my custom idoc as an xsd and modified the schema to allow for multiple idocs to be generated for each file - as per note 814393.
    However I get the following error message at runtime (Call Adapter):
    <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>ZSHIPDEL_packageRD</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ZSHIPDEL_packageRD</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Has anyone else experienced this error?
    Regards
    leenor

    I have a scenario exactly like the above one.
    My file structure is like
    TransactionDetailList
             TransactionDetail (1:N)
                    Transaction_Type (0:1)
                    Transaction_Date (0:1)
                    Add_Revise_Cancel_USER_ID (0:1)
                    Add_Revise_Cancel_Date_Time (0:1)
    My IDOC has the below structure,
    ZIDOC_BDS_DIVERSION
                       IDOC
                          ZSEGL_DIVERSION_HEADER
                                           SEGMENT
                                           NOMNR
                                           NOMIT
                                           EVENT_DATE
                                  ZSEGL_ DIVERSION_ITEM
                                            SEGMENT
                                            WHO_PAYS_DIVERSI
                                            LOCID
                                            DEST_CITY
    so i have to generate multiple idocs in the target side.
    I have created external defination based on my IDOC.Defined mapping between File and the external defination crerated from the IDOC. also defiined interface mapping between file and external defination.
    In the Integration Directory ->Interface Defination, I have used the actual Idoc as Inbound interface for which there is no mapping as we have not defined anything for this. This is exactly what you have defined above.
    I am getting the following errors like,
    "Error: MSGGUID A5EE4A305B4111DABFBE0002551F08EE: Tag TransactionDetailList found instead of tag IDOC BEGIN="
    Please let me know if I am missing some steps while configuring or I have to do something else.
    Thanks & Regards,
    Mukesh

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

  • Unable to interpret IDoc interface

    Hi,
    I have a File to multiple IDOC scenario. I have change the IDOC occurance by creating ED.
    I have developed everything but the following error is coming during my end to end testing.
    Unable to interpret IDoc interface
    Thanks,
    Raj

    Raj Says..
    I have change the IDOC occurance by creating ED.
    Hi Raj,
    Since you have changed the IDOC occurrences by creating an ED so you have to make sure that IDOC and ED has been used properly in your scenario.
    1. MM = use ED
    2. IM = use original IDOC
    3. ID = use original IDOC
    Regards,
    Madan Agrawal

  • 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

  • How can I download to my pc a conversation recorded in my iPod Touch using the voice notes??

    How can I download to my pc a conversation recorded in my iPod Touch using the voice notes????

  • Missing shared libraries?

    Hi all, I tried to install j2ee 1.4.2 Beta on my redhat linux 9 machine. After I downloaded and unzipped the zip file, I follow the installation instruction by typing ./setup in the extract folder. However, the follow error comes out: error while loa

  • Is Safari 5.0.1 safe to download?

    I got the Software Update alert a few weeks ago, but when I saw some of the horror stories on this discussion board, I was afraid to download it and do the update. Are the problems people are having few and far between, or are the problems with 5.0.1

  • Making text mandatory in outbound delivery

    HI, I want to make text mandatory in outbound delivery at item level. I have tried through VOTXN but it is not working. I have checked the forum but could not find any answer can some body provide me a solution.i have asked ABAPer to try this but he

  • Cannot turn off predicted searches

    I cannot turn off predicted searches in FF and every time i fire up FF it goes to the search preferences page and i have to save my setting before i can get to the home page, this happens EVERY time. I have done all the cookie stuff, cleared them ena