<?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 Re: BAPI Error Message Handling in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964031#M396079</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI ,&lt;/P&gt;&lt;P&gt;ITS SIMPLE TRY THIS CODE &lt;/P&gt;&lt;P&gt;AWARD PTS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: gt_ret     TYPE TABLE OF bapiret2,&lt;/P&gt;&lt;P&gt;           ls_ret    TYPE bapiret2,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BAPI_SALESORDER_CHANGE'&lt;/P&gt;&lt;P&gt;    EXPORTING&lt;/P&gt;&lt;P&gt;      salesdocument     = p_vbeln&lt;/P&gt;&lt;P&gt;      order_header_in   = gt_hdr&lt;/P&gt;&lt;P&gt;      order_header_inx  = gt_hdrx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    TABLES&lt;/P&gt;&lt;P&gt;      return            = gt_ret -&lt;/P&gt;&lt;HR originaltext="--------" /&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;.&amp;lt;b&amp;gt;IMPORTANT&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;      order_item_in     = gt_itm&lt;/P&gt;&lt;P&gt;      order_item_inx    = gt_itmx&lt;/P&gt;&lt;P&gt;      schedule_lines    = gt_sched&lt;/P&gt;&lt;P&gt;      schedule_linesx   = gs_schedx&lt;/P&gt;&lt;P&gt;      order_text        = gs_stdtxt.&lt;/P&gt;&lt;P&gt;      PARTNERS          = gs_partner&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  LOOP AT gt_ret INTO ls_ret.&lt;/P&gt;&lt;P&gt;    WRITE:/ ls_ret-type.&lt;/P&gt;&lt;P&gt;    WRITE:/ ls_ret-message.&lt;/P&gt;&lt;P&gt;  ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Feb 2007 12:08:42 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-02-09T12:08:42Z</dc:date>
    <item>
      <title>BAPI Error Message Handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964030#M396078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Group,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using BAPI ,How to display the BAPI  Error Message (eg:BAPIRET1) which is returning by BAPI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2007 12:06:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964030#M396078</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-09T12:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Error Message Handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964031#M396079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI ,&lt;/P&gt;&lt;P&gt;ITS SIMPLE TRY THIS CODE &lt;/P&gt;&lt;P&gt;AWARD PTS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: gt_ret     TYPE TABLE OF bapiret2,&lt;/P&gt;&lt;P&gt;           ls_ret    TYPE bapiret2,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BAPI_SALESORDER_CHANGE'&lt;/P&gt;&lt;P&gt;    EXPORTING&lt;/P&gt;&lt;P&gt;      salesdocument     = p_vbeln&lt;/P&gt;&lt;P&gt;      order_header_in   = gt_hdr&lt;/P&gt;&lt;P&gt;      order_header_inx  = gt_hdrx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    TABLES&lt;/P&gt;&lt;P&gt;      return            = gt_ret -&lt;/P&gt;&lt;HR originaltext="--------" /&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;.&amp;lt;b&amp;gt;IMPORTANT&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;      order_item_in     = gt_itm&lt;/P&gt;&lt;P&gt;      order_item_inx    = gt_itmx&lt;/P&gt;&lt;P&gt;      schedule_lines    = gt_sched&lt;/P&gt;&lt;P&gt;      schedule_linesx   = gs_schedx&lt;/P&gt;&lt;P&gt;      order_text        = gs_stdtxt.&lt;/P&gt;&lt;P&gt;      PARTNERS          = gs_partner&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  LOOP AT gt_ret INTO ls_ret.&lt;/P&gt;&lt;P&gt;    WRITE:/ ls_ret-type.&lt;/P&gt;&lt;P&gt;    WRITE:/ ls_ret-message.&lt;/P&gt;&lt;P&gt;  ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2007 12:08:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964031#M396079</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-09T12:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Error Message Handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964032#M396080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The return message will be stored in the table BAPIRET1. so you have a Internal table realted to this one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;after calling that function moduel... &lt;/P&gt;&lt;P&gt;LOOP AT IT_BAPIRET1&lt;/P&gt;&lt;P&gt;Write:/ IT_BAPIRET1-msgv1,IT_BAPIRET1-MESSAGE.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2007 12:10:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964032#M396080</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-09T12:10:23Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Error Message Handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964033#M396081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;declare itab like BAPIRET1.&lt;/P&gt;&lt;P&gt;and after execution of BAPi..&lt;/P&gt;&lt;P&gt;u can do a loop at this internqal table to display its records and find out the erroneos records.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2007 12:10:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964033#M396081</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-09T12:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Error Message Handling</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964034#M396082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Swabap,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say the return parameter name is GV_RETURN, paste this code after the BAPI call&lt;/P&gt;&lt;P&gt;if not gv_return is initial.&lt;/P&gt;&lt;P&gt;      MESSAGE ID gv_return-id&lt;/P&gt;&lt;P&gt;               TYPE gv_return-type&lt;/P&gt;&lt;P&gt;               NUMBER gv_return-number&lt;/P&gt;&lt;P&gt;               WITH gv_return-message_v1&lt;/P&gt;&lt;P&gt;                    gv_return-message_v2&lt;/P&gt;&lt;P&gt;                    gv_return-message_v3&lt;/P&gt;&lt;P&gt;                    gv_return-message_v4.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will build &amp;amp; display the message along with type on the status bar at the bottom of the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Aditya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Feb 2007 12:19:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-error-message-handling/m-p/1964034#M396082</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-09T12:19:43Z</dc:date>
    </item>
  </channel>
</rss>

