<?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: Badi Implementation : Declaration type automatically changes in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/badi-implementation-declaration-type-automatically-changes/m-p/12316052#M1990980</link>
    <description>&lt;P&gt;well, if it is a changing parameter now, use changing when calling badi:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Call badi ... ( ... 
changing e_result ).
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;PS: in case of modern BADIs, you can use exporting/returning only if it is a single-use BADI. if several BADI implementations can be called after oneanother (multiple use), then only CHANGING parameters can be used to "produce the result". &lt;/P&gt;&lt;P&gt;It's a very long time ago I defined a classic BADI (did I ever? if I did, then only for excercise purpose), but assume that something very similar is happening here. &lt;/P&gt;</description>
    <pubDate>Thu, 11 Feb 2021 07:06:08 GMT</pubDate>
    <dc:creator>sergei-u-niq</dc:creator>
    <dc:date>2021-02-11T07:06:08Z</dc:date>
    <item>
      <title>Badi Implementation : Declaration type automatically changes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/badi-implementation-declaration-type-automatically-changes/m-p/12316051#M1990979</link>
      <description>&lt;P&gt;I'M trying to implement a classic badi to divide 2 numbers. While defining methods i gave 2 importing parameters and 1 exporting parameter. While activating this BADI a popup displays that Interface for BAdI definition is not valid and changes will be made. The declaration type of 'exporting' parameter changes to 'changing' parameter which gives me a run time error while calling the method in SE80 program. Ss for references attached.&lt;/P&gt;
  &lt;P&gt;&lt;A href="https://answers.sap.com/storage/temp/1892461-capture.png"&gt;capture.png&lt;/A&gt;&lt;A href="https://answers.sap.com/storage/temp/1892462-q3-5.png"&gt;q3-5.png&lt;/A&gt;&lt;A href="https://answers.sap.com/storage/temp/1892463-capture.png"&gt;capture.png&lt;/A&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 06:20:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/badi-implementation-declaration-type-automatically-changes/m-p/12316051#M1990979</guid>
      <dc:creator>former_member728645</dc:creator>
      <dc:date>2021-02-11T06:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: Badi Implementation : Declaration type automatically changes</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/badi-implementation-declaration-type-automatically-changes/m-p/12316052#M1990980</link>
      <description>&lt;P&gt;well, if it is a changing parameter now, use changing when calling badi:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Call badi ... ( ... 
changing e_result ).
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;PS: in case of modern BADIs, you can use exporting/returning only if it is a single-use BADI. if several BADI implementations can be called after oneanother (multiple use), then only CHANGING parameters can be used to "produce the result". &lt;/P&gt;&lt;P&gt;It's a very long time ago I defined a classic BADI (did I ever? if I did, then only for excercise purpose), but assume that something very similar is happening here. &lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 07:06:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/badi-implementation-declaration-type-automatically-changes/m-p/12316052#M1990980</guid>
      <dc:creator>sergei-u-niq</dc:creator>
      <dc:date>2021-02-11T07:06:08Z</dc:date>
    </item>
  </channel>
</rss>

