<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Dump problem while remote FM call in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178775#M756648</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Experts,&lt;/P&gt;&lt;P&gt;In R3 system there is a RFC Fm Z_SALESORDER_CREATE which is wrapper of standard FM SD_SALESDOCUMENT_CREATE. When we do remote call from CRM system for Z_SALESORDER_CREATE. Its given dump as follows:&lt;/P&gt;&lt;P&gt;Short text                                                                         &lt;/P&gt;&lt;P&gt;    "Unable to interpret 2,00 as a number."                                                                                &lt;/P&gt;&lt;P&gt;What happened?                                                                     &lt;/P&gt;&lt;P&gt;    Error in the ABAP Application Program                                                                                &lt;/P&gt;&lt;P&gt;The current ABAP program "Z_CREATE_ORDER_WITH_JOB_VRNT" had to be terminated   &lt;/P&gt;&lt;P&gt;     because it has                                                                &lt;/P&gt;&lt;P&gt;    come across a statement that unfortunately cannot be executed.                                                                                &lt;/P&gt;&lt;P&gt;The error occurred during an RFC call to another system.                       &lt;/P&gt;&lt;P&gt;    In the target system, a short dump has been written as well.                   &lt;/P&gt;&lt;P&gt;    More detailed information on the error cause can be found there.                                                                                &lt;/P&gt;&lt;P&gt;Error analysis                                                                     &lt;/P&gt;&lt;P&gt;    An error occurred when executing a REMOTE FUNCTION CALL.                       &lt;/P&gt;&lt;P&gt;    It was logged under the name "CONVT_NO_NUMBER"                                 &lt;/P&gt;&lt;P&gt;    on the called page.                                                                                &lt;/P&gt;&lt;P&gt;We are not using 2,00 anymore...it is something changed format while compiling..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It cause dump in R3  also..dump desc in r3 as follows&lt;/P&gt;&lt;P&gt;                                                                            &lt;/P&gt;&lt;P&gt;Unable to interpret " 2,00" as a number.                                                                                &lt;/P&gt;&lt;P&gt;What happened?                                                                                &lt;/P&gt;&lt;P&gt;Error in ABAP application program.                                                                                &lt;/P&gt;&lt;P&gt;The current ABAP program "SAPLSTS4" had to be terminated because one of the &lt;/P&gt;&lt;P&gt;statements could not be executed.                                                                                &lt;/P&gt;&lt;P&gt;This is probably due to an error in the ABAP program.                                                                                &lt;/P&gt;&lt;P&gt;Error analysis                                                                                &lt;/P&gt;&lt;P&gt;An exception occurred. This exception is dealt with in more detail bel&lt;/P&gt;&lt;P&gt;. The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER&lt;/P&gt;&lt;P&gt; was neither                                                          &lt;/P&gt;&lt;P&gt;caught nor passed along using a RAISING clause, in the procedure      &lt;/P&gt;&lt;P&gt; "CONVERSION_EXIT_TSTRG_OUTPUT" "(FUNCTION)"                          &lt;/P&gt;&lt;P&gt;.                                                                     &lt;/P&gt;&lt;P&gt;Since the caller of the procedure could not have expected this excepti&lt;/P&gt;&lt;P&gt; to occur, the running program was terminated.                        &lt;/P&gt;&lt;P&gt;The reason for the exception is:                                      &lt;/P&gt;&lt;P&gt;The program attempted to interpret the value " 2,00" as a number, but &lt;/P&gt;&lt;P&gt;since the value contravenes the rules for correct number formats,     &lt;/P&gt;&lt;P&gt;this was not possible.                                                                                &lt;/P&gt;&lt;P&gt;How to correct the error                                                                                &lt;/P&gt;&lt;P&gt;The exception must either be prevented, caught within the procedure   &lt;/P&gt;&lt;P&gt; "CONVERSION_EXIT_TSTRG_OUTPUT"                                       &lt;/P&gt;&lt;P&gt;"(FUNCTION)", or declared in the procedure's RAISING clause.          &lt;/P&gt;&lt;P&gt;To prevent the exception, note the following:                         &lt;/P&gt;&lt;P&gt;Integers are represented in ABAP using a sequence of digits and, in so&lt;/P&gt;&lt;P&gt; cases, a preceding sign.                                             &lt;/P&gt;&lt;P&gt;The system offers the following options for displaying floating point &lt;/P&gt;&lt;P&gt;numbers:                                                              &lt;/P&gt;&lt;P&gt;  [sign][mantissa]E[sign][exponent]                                   &lt;/P&gt;&lt;P&gt;  [sign][whole number part].[fractional part]                         &lt;/P&gt;&lt;P&gt;e.g. -12E+34, +12E-34, 12E34, 12.34                                                                                &lt;/P&gt;&lt;P&gt;If the error occurred in one of your own programs or in an SAP program           &lt;/P&gt;&lt;P&gt;that you modified, try to correct it yourself.                                                                                &lt;/P&gt;&lt;P&gt;You may able to find an interim solution to the problem                          &lt;/P&gt;&lt;P&gt;in the SAP note system. If you have access to the note system yourself,          &lt;/P&gt;&lt;P&gt;use the following search criteria:                                                                                &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----------------------------------------------------------------------" /&gt;&lt;P&gt;         &lt;/P&gt;&lt;P&gt;"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC                                    &lt;/P&gt;&lt;P&gt;"SAPLSTS4" or "LSTS4U01"                                                         &lt;/P&gt;&lt;P&gt;"CONVERSION_EXIT_TSTRG_OUTPUT"                                                   &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----------------------------------------------------------------------" /&gt;&lt;P&gt;    &lt;/P&gt;&lt;P&gt;Please help me to solve ths problem as soon as possible..&lt;/P&gt;&lt;P&gt;thanks in advance for you quick response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anutosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Dec 2007 06:25:56 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-07T06:25:56Z</dc:date>
    <item>
      <title>Dump problem while remote FM call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178775#M756648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Experts,&lt;/P&gt;&lt;P&gt;In R3 system there is a RFC Fm Z_SALESORDER_CREATE which is wrapper of standard FM SD_SALESDOCUMENT_CREATE. When we do remote call from CRM system for Z_SALESORDER_CREATE. Its given dump as follows:&lt;/P&gt;&lt;P&gt;Short text                                                                         &lt;/P&gt;&lt;P&gt;    "Unable to interpret 2,00 as a number."                                                                                &lt;/P&gt;&lt;P&gt;What happened?                                                                     &lt;/P&gt;&lt;P&gt;    Error in the ABAP Application Program                                                                                &lt;/P&gt;&lt;P&gt;The current ABAP program "Z_CREATE_ORDER_WITH_JOB_VRNT" had to be terminated   &lt;/P&gt;&lt;P&gt;     because it has                                                                &lt;/P&gt;&lt;P&gt;    come across a statement that unfortunately cannot be executed.                                                                                &lt;/P&gt;&lt;P&gt;The error occurred during an RFC call to another system.                       &lt;/P&gt;&lt;P&gt;    In the target system, a short dump has been written as well.                   &lt;/P&gt;&lt;P&gt;    More detailed information on the error cause can be found there.                                                                                &lt;/P&gt;&lt;P&gt;Error analysis                                                                     &lt;/P&gt;&lt;P&gt;    An error occurred when executing a REMOTE FUNCTION CALL.                       &lt;/P&gt;&lt;P&gt;    It was logged under the name "CONVT_NO_NUMBER"                                 &lt;/P&gt;&lt;P&gt;    on the called page.                                                                                &lt;/P&gt;&lt;P&gt;We are not using 2,00 anymore...it is something changed format while compiling..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It cause dump in R3  also..dump desc in r3 as follows&lt;/P&gt;&lt;P&gt;                                                                            &lt;/P&gt;&lt;P&gt;Unable to interpret " 2,00" as a number.                                                                                &lt;/P&gt;&lt;P&gt;What happened?                                                                                &lt;/P&gt;&lt;P&gt;Error in ABAP application program.                                                                                &lt;/P&gt;&lt;P&gt;The current ABAP program "SAPLSTS4" had to be terminated because one of the &lt;/P&gt;&lt;P&gt;statements could not be executed.                                                                                &lt;/P&gt;&lt;P&gt;This is probably due to an error in the ABAP program.                                                                                &lt;/P&gt;&lt;P&gt;Error analysis                                                                                &lt;/P&gt;&lt;P&gt;An exception occurred. This exception is dealt with in more detail bel&lt;/P&gt;&lt;P&gt;. The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER&lt;/P&gt;&lt;P&gt; was neither                                                          &lt;/P&gt;&lt;P&gt;caught nor passed along using a RAISING clause, in the procedure      &lt;/P&gt;&lt;P&gt; "CONVERSION_EXIT_TSTRG_OUTPUT" "(FUNCTION)"                          &lt;/P&gt;&lt;P&gt;.                                                                     &lt;/P&gt;&lt;P&gt;Since the caller of the procedure could not have expected this excepti&lt;/P&gt;&lt;P&gt; to occur, the running program was terminated.                        &lt;/P&gt;&lt;P&gt;The reason for the exception is:                                      &lt;/P&gt;&lt;P&gt;The program attempted to interpret the value " 2,00" as a number, but &lt;/P&gt;&lt;P&gt;since the value contravenes the rules for correct number formats,     &lt;/P&gt;&lt;P&gt;this was not possible.                                                                                &lt;/P&gt;&lt;P&gt;How to correct the error                                                                                &lt;/P&gt;&lt;P&gt;The exception must either be prevented, caught within the procedure   &lt;/P&gt;&lt;P&gt; "CONVERSION_EXIT_TSTRG_OUTPUT"                                       &lt;/P&gt;&lt;P&gt;"(FUNCTION)", or declared in the procedure's RAISING clause.          &lt;/P&gt;&lt;P&gt;To prevent the exception, note the following:                         &lt;/P&gt;&lt;P&gt;Integers are represented in ABAP using a sequence of digits and, in so&lt;/P&gt;&lt;P&gt; cases, a preceding sign.                                             &lt;/P&gt;&lt;P&gt;The system offers the following options for displaying floating point &lt;/P&gt;&lt;P&gt;numbers:                                                              &lt;/P&gt;&lt;P&gt;  [sign][mantissa]E[sign][exponent]                                   &lt;/P&gt;&lt;P&gt;  [sign][whole number part].[fractional part]                         &lt;/P&gt;&lt;P&gt;e.g. -12E+34, +12E-34, 12E34, 12.34                                                                                &lt;/P&gt;&lt;P&gt;If the error occurred in one of your own programs or in an SAP program           &lt;/P&gt;&lt;P&gt;that you modified, try to correct it yourself.                                                                                &lt;/P&gt;&lt;P&gt;You may able to find an interim solution to the problem                          &lt;/P&gt;&lt;P&gt;in the SAP note system. If you have access to the note system yourself,          &lt;/P&gt;&lt;P&gt;use the following search criteria:                                                                                &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----------------------------------------------------------------------" /&gt;&lt;P&gt;         &lt;/P&gt;&lt;P&gt;"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC                                    &lt;/P&gt;&lt;P&gt;"SAPLSTS4" or "LSTS4U01"                                                         &lt;/P&gt;&lt;P&gt;"CONVERSION_EXIT_TSTRG_OUTPUT"                                                   &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----------------------------------------------------------------------" /&gt;&lt;P&gt;    &lt;/P&gt;&lt;P&gt;Please help me to solve ths problem as soon as possible..&lt;/P&gt;&lt;P&gt;thanks in advance for you quick response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anutosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 06:25:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178775#M756648</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-07T06:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: Dump problem while remote FM call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178776#M756649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check your input whether it is numeric or alpha numeric. The problelm in the dumb is kind of convertion problem. Check before the rfc strts to work&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suku&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 06:28:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178776#M756649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-07T06:28:38Z</dc:date>
    </item>
    <item>
      <title>Re: Dump problem while remote FM call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178777#M756650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check your defined data types which you are passing to FM and exact FM data types.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope that's the problem .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sree&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 06:30:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178777#M756650</guid>
      <dc:creator>sreeramkumar_madisetty</dc:creator>
      <dc:date>2007-12-07T06:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: Dump problem while remote FM call</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178778#M756651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it would be happening in condition statement.....the incoming parameter would be character type ......declare the parameter in CHAR format and check.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Dec 2007 07:02:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-problem-while-remote-fm-call/m-p/3178778#M756651</guid>
      <dc:creator>kesavadas_thekkillath</dc:creator>
      <dc:date>2007-12-07T07:02:02Z</dc:date>
    </item>
  </channel>
</rss>

