<?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: Design Method's in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535407#M1264441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nina,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think, there is no need to use two methods for your requirement.&lt;/P&gt;&lt;P&gt;You should use one method instead of two.&lt;/P&gt;&lt;P&gt;Design that in this way.&lt;/P&gt;&lt;P&gt;If you pass User ID parameter value -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;&amp;gt; displays corresponding user only.&lt;/P&gt;&lt;P&gt;If you won't pass any User ID  value -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;&amp;gt; displays all users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it should work with minor changes  to your logic in the same method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;by&lt;/P&gt;&lt;P&gt;Prasad gvk.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 May 2009 05:44:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-05-01T05:44:24Z</dc:date>
    <item>
      <title>Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535404#M1264438</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;I had to build two method's &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Method that bring user name for specific ID and one that bring .&lt;/P&gt;&lt;P&gt;2. Method that bring all the user when it execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to build it in OO ,any tips for good design will be helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Nina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Apr 2009 20:17:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535404#M1264438</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-30T20:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535405#M1264439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check Forum &amp;amp; Google for Code optimizations, Performace Tuning and similar words. You will get lots of helpful replie.&lt;/P&gt;&lt;P&gt;Always search the forum before posting the query.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Apr 2009 21:41:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535405#M1264439</guid>
      <dc:creator>amit_khare</dc:creator>
      <dc:date>2009-04-30T21:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535406#M1264440</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;I don't want help with the code i want help to do code design,&lt;/P&gt;&lt;P&gt;For that i need something specific not generic.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Apr 2009 21:46:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535406#M1264440</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-30T21:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535407#M1264441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nina,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think, there is no need to use two methods for your requirement.&lt;/P&gt;&lt;P&gt;You should use one method instead of two.&lt;/P&gt;&lt;P&gt;Design that in this way.&lt;/P&gt;&lt;P&gt;If you pass User ID parameter value -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;&amp;gt; displays corresponding user only.&lt;/P&gt;&lt;P&gt;If you won't pass any User ID  value -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;&amp;gt; displays all users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it should work with minor changes  to your logic in the same method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;by&lt;/P&gt;&lt;P&gt;Prasad gvk.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2009 05:44:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535407#M1264441</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-01T05:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535408#M1264442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nina,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to create only one method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with 4 parameters&lt;/P&gt;&lt;P&gt;First parameter = single user id&lt;/P&gt;&lt;P&gt;second par = low range&lt;/P&gt;&lt;P&gt;third     par = high range&lt;/P&gt;&lt;P&gt;fourth   par = 'X'              (Note: mark it X to work with single id and leave it blank for range of ids.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this will solve your problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2009 06:26:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535408#M1264442</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-01T06:26:01Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535409#M1264443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As described above, you can only achieve this by creating a single method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create method, GET_USER_INFO&lt;/P&gt;&lt;P&gt;Signature&lt;/P&gt;&lt;P&gt;Importing   R_USERID   (Range of User ID)&lt;/P&gt;&lt;P&gt;Exporting  IT_USER_INFO (Table to hold the user Info)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you call this method, pass I EQ user_name in the range to get only one User Info. Leave it blank when you want all user info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naimesh Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2009 13:11:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535409#M1264443</guid>
      <dc:creator>naimesh_patel</dc:creator>
      <dc:date>2009-05-01T13:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535410#M1264444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Nina,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;               You can achive this in one method, though you need two methods for this just follow as below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET_USER_RECORD&lt;/P&gt;&lt;P&gt; with parameters as below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          IMPORTING &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                     ID and TYPE &amp;lt;DataelementType&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;         EXPORTING &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                  DETAILS_REC TYPE &amp;lt;StructureType  Of USER RECORD&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and implement this method by retriving from table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET_USER_RECORDS&lt;/P&gt;&lt;P&gt;    EXPORTING  &lt;/P&gt;&lt;P&gt;          USER_DETAILS TYPE &amp;lt;Table Type Of USER RECORD&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and implement the menthod where you need to assign the records to this intername table USER_DETAILS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thats it..and use it as per your requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prasanna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2009 13:27:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535410#M1264444</guid>
      <dc:creator>prasannakrishna_mynam</dc:creator>
      <dc:date>2009-05-01T13:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535411#M1264445</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Naimesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U think for this I need to build interface or just use class ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR &lt;/P&gt;&lt;P&gt;Nina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2009 19:47:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535411#M1264445</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-01T19:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: Design Method's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535412#M1264446</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Nina,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you require this method to be redefined in different classes, then it makes sense to define an interface for it. So you could add your interface in the different classes and this would enable you to have a generic calling method for the different implementations of the same method. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if you have only one implementation then I would suggest you define it in your class 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>Sun, 03 May 2009 14:09:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/design-method-s/m-p/5535412#M1264446</guid>
      <dc:creator>Ramneek</dc:creator>
      <dc:date>2009-05-03T14:09:37Z</dc:date>
    </item>
  </channel>
</rss>

