<?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: Definitin in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285574#M785886</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;transaction: transaction is nothing but a series of dialog screens or simply &lt;/P&gt;&lt;P&gt;we can say that as application.But strictly speaking it is a series of screens&lt;/P&gt;&lt;P&gt;used in a module pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Event : Event is nothing but the situational control passing from one block of&lt;/P&gt;&lt;P&gt;code to another block of code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;start-of-selection will trigger automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use any other event like initialization it will trigger befor selection&lt;/P&gt;&lt;P&gt;screen display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;means according to situation this will fire.Once the event is trigger then the&lt;/P&gt;&lt;P&gt;code below that will execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;swami&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jan 2008 05:11:19 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-10T05:11:19Z</dc:date>
    <item>
      <title>Definitin</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285572#M785884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts &lt;/P&gt;&lt;P&gt;Please let me know the Exact technical definition of TRANSACTION and EVENT.&lt;/P&gt;&lt;P&gt;Explain it ?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 05:04:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285572#M785884</guid>
      <dc:creator>former_member329386</dc:creator>
      <dc:date>2008-01-10T05:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: Definitin</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285573#M785885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Transaction&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To emulate a business transaction, a program may need to perform several steps. A financial program, for example, might transfer funds from a checking account to a savings account with the steps listed in the following pseudocode: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;begin transaction &lt;/P&gt;&lt;P&gt;debit checking account &lt;/P&gt;&lt;P&gt;credit savings account&lt;/P&gt;&lt;P&gt;update history log &lt;/P&gt;&lt;P&gt;commit transaction&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either all three of these steps must complete, or none of them at all. Otherwise, data integrity is lost. Because the steps within a transaction are a unified whole, a transaction is often defined as an indivisible unit of work. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A transaction can end in two ways: with a commit or a rollback. When a transaction commits, the data modifications made by its statements are saved. If a statement within a transaction fails, the transaction rolls back, undoing the effects of all statements in the transaction. In the pseudocode, for example, if a disk drive crashed during the credit step, the transaction would roll back and undo the data modifications made by the debit statement. Although the transaction failed, data integrity would be intact because the accounts still balance. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the preceding pseudocode, the begin and commit statements mark the boundaries of the transaction. When designing an enterprise bean, you determine how the boundaries are set by specifying either container-managed or bean-managed transactions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d329d190-0201-0010-e7a1-96a9f893b40b" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d329d190-0201-0010-e7a1-96a9f893b40b&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Events:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let us take you developed a program then LOAD-OF-PROGRAM and INITIALIZATION these will be fired first when running the program, before the selection screen, if there is one, is fired. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is a selection screen, AT SELECTION-SCREEN OUTPUT event will be fired automatically before the screen is shown. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if there is a selection screen, the START-OF-SELECTION event will only be fired when the user clicks the "Execute" button on the selection screen. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE will automically be fired when you use the first WRITE statement as well as anytime the line count is reached.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_scm50/helpdata/en/69/b4393c95b04325e10000000a11405a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_scm50/helpdata/en/69/b4393c95b04325e10000000a11405a/frameset.htm&lt;/A&gt;&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;Edited by: Sravan Prakash.V on Jan 10, 2008 10:38 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 05:07:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285573#M785885</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T05:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: Definitin</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285574#M785886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;transaction: transaction is nothing but a series of dialog screens or simply &lt;/P&gt;&lt;P&gt;we can say that as application.But strictly speaking it is a series of screens&lt;/P&gt;&lt;P&gt;used in a module pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Event : Event is nothing but the situational control passing from one block of&lt;/P&gt;&lt;P&gt;code to another block of code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;start-of-selection will trigger automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use any other event like initialization it will trigger befor selection&lt;/P&gt;&lt;P&gt;screen display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;means according to situation this will fire.Once the event is trigger then the&lt;/P&gt;&lt;P&gt;code below that will execute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;swami&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 05:11:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/definitin/m-p/3285574#M785886</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T05:11:19Z</dc:date>
    </item>
  </channel>
</rss>

