<?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 text example Doubt in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283186#M1388660</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Max my concern is the same..............&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is nothing code in the method.......what it means?&lt;/P&gt;&lt;P&gt;It onlyhave &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;method aysncronous.&lt;/P&gt;&lt;P&gt;try.&lt;/P&gt;&lt;P&gt;raise event,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endtry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endmethod.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It means callng Method  itself   raise event?(Raising error ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Nov 2009 01:37:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-11-06T01:37:05Z</dc:date>
    <item>
      <title>OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283184#M1388658</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 am training on OOPS which one of the concept is really trouble-shooting to understand.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the class ...CL_SEND_BCS_EXAMPLE....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is one Method called ASYNCHRONUS.&lt;/P&gt;&lt;P&gt;When i am chekcing the code inside the mehtod it has written as&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRY.&lt;/P&gt;&lt;P&gt;RAISE EVENT IP_OPS_METHOD~RAISE_ERROR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDTRY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i KNOW raise event is just like rasing the error which can be caught by &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But when i double click..there is notjhing code it is written inside that event&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just want to know why this event is used here???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Nov 2009 14:10:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283184#M1388658</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-05T14:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283185#M1388659</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 event is like an exception....a traffic light....no code there , the code is in the method is triggered as soon as the event is raised&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Nov 2009 14:15:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283185#M1388659</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-05T14:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283186#M1388660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Max my concern is the same..............&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is nothing code in the method.......what it means?&lt;/P&gt;&lt;P&gt;It onlyhave &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;method aysncronous.&lt;/P&gt;&lt;P&gt;try.&lt;/P&gt;&lt;P&gt;raise event,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endtry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endmethod.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It means callng Method  itself   raise event?(Raising error ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Nov 2009 01:37:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283186#M1388660</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-06T01:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283187#M1388661</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Max said, raising an event is like setting a traffic light, or running a flag up a flagpole - you have to decide within your code how you want to react to that event - and you may chose to do nothing by not implementing a handler for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An example of this would be the ALV grid (class CL_GUI_ALV_GRID) where when the user double-clicks on a cell, the ALV grid class raises an event "double_click" - however your report may not support drill-down or similar processing, thus you won't implement code to handle that event... actually that CL_GUI_ALV_GRID class has over 40 events, and it's rare to need to trap more than a couple of them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take a look at the ABAP help on "set handler" and "raise event" - both have code examples in them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jonathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Nov 2009 04:44:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283187#M1388661</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-06T04:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283188#M1388662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="sad"&gt;&lt;/SPAN&gt; Not Satisficatory.....................&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But Jonathan thanks for taking pain to explain me......Is it mean that method which doesnt have any code except the raising events is nothing but &lt;STRONG&gt;calling the the method means raising the events???&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any Hint pls?????&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: saslove sap on Nov 8, 2009 3:32 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Nov 2009 05:25:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283188#M1388662</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-06T05:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283189#M1388663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI saslove;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not on the system now. so I can't check the details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In OO RAISE EVENT ans RAISE EXCEPTION is a big difference. If an event is raised, it will look what method of what class (instance) is registered for this event. Then this method (the 'listener') is executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Events are used in OO to establish the communication between instances of classes, 'notifiers' and 'listeners'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Class-based Exceptions are raised to leave the current processing block immediately. They can (and should) be caught in a calling block.&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>Sun, 08 Nov 2009 09:41:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283189#M1388663</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2009-11-08T09:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283190#M1388664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want an example, take a look at BCALV_TEST_GRID_EVENTS - the selection screen gives you options for turning on "listening" logic for events that the ALV grid class may raise.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jonathan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Nov 2009 23:02:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283190#M1388664</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-09T23:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283191#M1388665</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi saslove,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I really wonder where you do what kind of training. In our ECC600 system we have no class&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;CL_SEND_BCS_EXAMPLE&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We don't even have &lt;STRONG&gt;any&lt;/STRONG&gt; method called &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ASYNCHRONUS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Questions and answers are lot more helpful if they refer to something that exists.&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>Tue, 10 Nov 2009 08:22:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283191#M1388665</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2009-11-10T08:22:24Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283192#M1388666</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Clemens...Here i go with clear example which should exists in all the Systems..&lt;/P&gt;&lt;P&gt;Sorry for wrong input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please go to class se24 class: CL_BCS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we can see one attribute send_request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the method select asynchronous doube clikc we can see code :&lt;/P&gt;&lt;P&gt;method asynchronous.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call method: send_request -&amp;gt;get_asynshronus.&lt;/P&gt;&lt;P&gt;Receiving&lt;/P&gt;&lt;P&gt;Result = Result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endmethod.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when we double click get_asynchronous it will refer to send_request type cls_send_request_bcs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the method get_asynchronus we have code as below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;method get_asynchronus.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;state read acess.-&amp;gt; this is amacro&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;result  = result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endmethod.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MACRO.&lt;/P&gt;&lt;P&gt;define read&lt;/P&gt;&lt;P&gt;Raise event if_os_state~read_access.----&lt;/P&gt;&lt;HR originaltext="-----" /&gt;&lt;P&gt;&amp;gt;Here is the problem what i am discussing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;end of definition.&lt;/P&gt;&lt;P&gt;i know ~ stands for interface ...when i check read_acess it doenst have code it doenst have paramters.it is a event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So my point is calling asynchronous method in CL_BCS class measn Raising the event?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Nov 2009 16:17:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283192#M1388666</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-10T16:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283193#M1388667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Clemens...Here i go with clear example which should exists in all the Systems..&lt;/P&gt;&lt;P&gt;Sorry for wrong input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please go to class se24 class: CL_BCS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we can see one attribute send_request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the method select asynchronous doube clikc we can see code :&lt;/P&gt;&lt;P&gt;method asynchronous.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call method: send_request -&amp;gt;get_asynshronus.&lt;/P&gt;&lt;P&gt;Receiving&lt;/P&gt;&lt;P&gt;Result = Result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endmethod.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when we double click get_asynchronous it will refer to send_request type cls_send_request_bcs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the method get_asynchronus we have code as below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;method get_asynchronus.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;state read acess.-&amp;gt; this is amacro&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;result  = result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endmethod.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MACRO.&lt;/P&gt;&lt;P&gt;define read&lt;/P&gt;&lt;P&gt;Raise event if_os_state~read_access.----&lt;/P&gt;&lt;HR originaltext="-----" /&gt;&lt;P&gt;&amp;gt;Here is the problem what i am discussing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;end of definition.&lt;/P&gt;&lt;P&gt;i know ~ stands for interface ...when i check read_acess it doenst have code it doenst have paramters.it is a event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So my point is calling asynchronous method in CL_BCS class measn Raising the event?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Nov 2009 16:18:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283193#M1388667</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-10T16:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283194#M1388668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi saslove,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sometimes it is not required to understand everything.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Method &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ASYNCHRONOUS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; returns &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;VALUE( RESULT )	TYPE OS_BOOLEAN&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; which is a flag that informs you if the send request of the BCS object instance is created for asynchronous (background) processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This  &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ASYNCHRONOUS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;  is called a functional method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To determine the RESULT,  a functional method of class &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;CL_SEND_REQUEST_BCS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; is called: Method&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;GET_ASYNCHRONOUS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; also returns boolean value RESULT, this is just taken from the attribute, so &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;result = ASYNCHRONOUS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the main function of the method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The macro &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;state_read_access&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; raises event &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;READ_ACCESS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; which is defined in interface &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;IF_OS_STATE&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If in the class or an inherited class a handler for this event has been implemented and set for this event, this will automatically be triggered without any changes to the class.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I tried to explain about the &lt;EM&gt;Notifier - Listener&lt;/EM&gt; concept.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case to summarize: The function of Method &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ASYNCHRONOUS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; is just to return a flag about the processing function (SYNCHRONOUS/ASYNCHRONOUS). As a side-effect, event  &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;READ_ACCESS&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; is triggered. This may be useful if any listeners are configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &lt;EM&gt;Notifier - Listener&lt;/EM&gt; concept is used when objects have to inform other objects about state changes: This is not hard-coded but implemented via so called loose-coupling. This allows you to exchange classes and objects freely.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Page 44 ff - the observer pattern|http://books.google.com/books?id=LjJcCnNf92kC&amp;amp;printsec=frontcover&amp;amp;dq=design&lt;EM&gt;patterns&lt;/EM&gt;head+first&amp;amp;hl=de#v=onepage&amp;amp;q=&amp;amp;f=false]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is just an idea for further studies.&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>Tue, 10 Nov 2009 17:07:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283194#M1388668</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2009-11-10T17:07:12Z</dc:date>
    </item>
    <item>
      <title>Re: OOPS text example Doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283195#M1388669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hy Clemens&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wirklich dankt für den hilfreichen infomation ................. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Von Morgen Arbeiten Arbeiten: (hat nur gebunden. ..............get zurück Sie tomorow&lt;/P&gt;&lt;P&gt;Noch einmal Dankt alot&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Nov 2009 17:14:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oops-text-example-doubt/m-p/6283195#M1388669</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-10T17:14:48Z</dc:date>
    </item>
  </channel>
</rss>

