<?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: Caller method in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647242#M1572753</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok, but what would be a good design for this problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Feb 2011 11:36:53 GMT</pubDate>
    <dc:creator>Denis_Mller</dc:creator>
    <dc:date>2011-02-09T11:36:53Z</dc:date>
    <item>
      <title>Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647240#M1572751</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;is there a way to read the caller method of my actual method?&lt;/P&gt;&lt;P&gt;I know that i can use a parameter but it is a third-party software.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Method A calls method C&lt;/P&gt;&lt;P&gt;Method B calls method C&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Methode A and Method B are third-party and method C is my code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now i have to read in method C if the caller is method A or B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way in standard? A SAP method?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 10:18:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647240#M1572751</guid>
      <dc:creator>Denis_Mller</dc:creator>
      <dc:date>2011-02-09T10:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647241#M1572752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Denis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suppose you could use the function module 'SYSTEM_CALLSTACK' to find the caller method. But I would like to add that this would be bad design and I would use it as the last resort only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Ramneek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 11:32:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647241#M1572752</guid>
      <dc:creator>Ramneek</dc:creator>
      <dc:date>2011-02-09T11:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647242#M1572753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok, but what would be a good design for this problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 11:36:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647242#M1572753</guid>
      <dc:creator>Denis_Mller</dc:creator>
      <dc:date>2011-02-09T11:36:53Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647243#M1572754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How does the third party software know that it should call your method C from their methods A and B? Exits, enhancement points?&lt;/P&gt;&lt;P&gt;Isn't there anything passed through that would let you make the distinction?&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S. good design is to not work with global variables or tricks like "SYSTEM_CALLSTACK", but rather have all necessary data locally available through the method interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Thomas Zloch on Feb 9, 2011 12:38 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 11:37:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647243#M1572754</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2011-02-09T11:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647244#M1572755</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it was only an example. All methods are implemented by an third-party programmer in our system.&lt;/P&gt;&lt;P&gt;but we don't want to modify more than method C. If we modify method A, B, ... there is a high risk for this process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Feb 2011 11:49:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647244#M1572755</guid>
      <dc:creator>Denis_Mller</dc:creator>
      <dc:date>2011-02-09T11:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647245#M1572756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alternative would be adding and optional parameter where you pass caller name. This way you can adjust all the callers you need and leave those not relevant untouched. It isn't however good design as you make your callee in strong coupling with its callers. Imagine you add another caller, which entails modification of the callee (to interact with new method/object). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should always program to [Loose coupling|http://en.wikipedia.org/wiki/Loose_coupling] even in relevance to different methods (not only objects). The more independent objects are the less modification their require. If you have method C built in a way it needs to distinguish which object/method it's worknig with, introduction of new similar method should probably be considered, or controlling that differentation on object level itself (i.e. by setting object's attribute).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Feb 2011 08:31:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647245#M1572756</guid>
      <dc:creator>MarcinPciak</dc:creator>
      <dc:date>2011-02-10T08:31:14Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647246#M1572757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dennis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;without discussing design questions you can use function module SYSTEM_CALLSTACK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Feb 2011 17:01:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647246#M1572757</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2011-02-11T17:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647247#M1572758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Hi Dennis,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; without discussing design questions you can use function module SYSTEM_CALLSTACK.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Regards,&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Clemens&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Ramneek Sharma said in the first response...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Feb 2011 06:07:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647247#M1572758</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2011-02-14T06:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: Caller method</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647248#M1572759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This message was moderated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Mar 2011 06:15:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/caller-method/m-p/7647248#M1572759</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-03-12T06:15:40Z</dc:date>
    </item>
  </channel>
</rss>

