<?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: oops imp in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850816#M668024</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;&amp;lt;b&amp;gt;reason&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The fundamental idea behind object oriented programing (OOP) is to combine both DATA and the FUNCTION (METHODS) thoese operate on that data into a single unit.&lt;/P&gt;&lt;P&gt;such an unit is called OBJECT . i.e key principle of OOP is DATA controling Access to code &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;advantage&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;1)better programing structure &lt;/P&gt;&lt;P&gt;2)real world entity can be modeled very well&lt;/P&gt;&lt;P&gt;3)stress on data security and access &lt;/P&gt;&lt;P&gt;4)data encapsulation and abstraction&lt;/P&gt;&lt;P&gt;5)reduction in code redundancy &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Features&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;1) Modeling real wold entities and processes in a more natural way&lt;/P&gt;&lt;P&gt;2)Hiding date and its related logic behind well defined interfaces &lt;/P&gt;&lt;P&gt;3)Reausing attributes and methods while allowing for specialization &lt;/P&gt;&lt;P&gt;4)Simplofying by hiding varying implementations behind the same interface &lt;/P&gt;&lt;P&gt;5)Same code can be reused multiple times by using inheritances &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thats why SAP adivises to OOP ABAP than ABAP &lt;/P&gt;&lt;P&gt;now adays CRM and ISu modules are totally depending on the OOP ABAP &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Rewardif useful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Oct 2007 10:01:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-12T10:01:16Z</dc:date>
    <item>
      <title>oops imp</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850813#M668021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;can anybody say what is the main reason for implementing projects in oops rather than using normal programming.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Oct 2007 16:06:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850813#M668021</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-07T16:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: oops imp</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850814#M668022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do not understand ABAP Objects nor develop according to OO principles you are "&amp;lt;b&amp;gt;&amp;lt;i&amp;gt;&amp;lt;u&amp;gt;dead&amp;lt;/u&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/b&amp;gt;" as developer within the next 24 months. Why?&lt;/P&gt;&lt;P&gt;Starting with basis release 6.20 SAP has transformed the SAP basis from classical to OO programming. This shift is moving futher on to the business modules. Thus, without a decent understanding of ABAP-OO you will have no chance to understand the ABAP coding of the SAP standard anymore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For a comparison of classical vs. OO programming have a look at:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="https://wiki.sdn.sap.com/wiki/display/profile/2007/07/09/Understanding&lt;EM&gt;ABAP&lt;/EM&gt;Objects"&amp;gt;Understanding ABAP Objects&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&amp;lt;i&amp;gt;&amp;lt;/i&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Oct 2007 19:46:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850814#M668022</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2007-10-07T19:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: oops imp</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850815#M668023</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;The following lines explain the main Abap object oriented concepts that differs from traditional abap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have explained object orientation which is such an important aspect in SAP. The discussion began with the features of Object Orientation and includes the runtime environment, the language extension, the classes and the class components. Apart from that I have also discussed for new first time readers event handling, inheritance encapsulation and polymorphism. &lt;/P&gt;&lt;P&gt;&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;Padmam.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Oct 2007 14:46:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850815#M668023</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-08T14:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: oops imp</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850816#M668024</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;&amp;lt;b&amp;gt;reason&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The fundamental idea behind object oriented programing (OOP) is to combine both DATA and the FUNCTION (METHODS) thoese operate on that data into a single unit.&lt;/P&gt;&lt;P&gt;such an unit is called OBJECT . i.e key principle of OOP is DATA controling Access to code &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;advantage&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;1)better programing structure &lt;/P&gt;&lt;P&gt;2)real world entity can be modeled very well&lt;/P&gt;&lt;P&gt;3)stress on data security and access &lt;/P&gt;&lt;P&gt;4)data encapsulation and abstraction&lt;/P&gt;&lt;P&gt;5)reduction in code redundancy &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Features&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;1) Modeling real wold entities and processes in a more natural way&lt;/P&gt;&lt;P&gt;2)Hiding date and its related logic behind well defined interfaces &lt;/P&gt;&lt;P&gt;3)Reausing attributes and methods while allowing for specialization &lt;/P&gt;&lt;P&gt;4)Simplofying by hiding varying implementations behind the same interface &lt;/P&gt;&lt;P&gt;5)Same code can be reused multiple times by using inheritances &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thats why SAP adivises to OOP ABAP than ABAP &lt;/P&gt;&lt;P&gt;now adays CRM and ISu modules are totally depending on the OOP ABAP &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Rewardif useful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Oct 2007 10:01:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-imp/m-p/2850816#M668024</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-12T10:01:16Z</dc:date>
    </item>
  </channel>
</rss>

