<?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 Events in reports in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028587#M716206</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Want all the events that are used in reports (order wise)&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;Stanley&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Nov 2007 04:11:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-01T04:11:02Z</dc:date>
    <item>
      <title>Events in reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028587#M716206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Want all the events that are used in reports (order wise)&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;Stanley&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2007 04:11:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028587#M716206</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-01T04:11:02Z</dc:date>
    </item>
    <item>
      <title>Re: Events in reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028588#M716207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Report Structure :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data dclaration part&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;selection -screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;initialization First event to fill the default values&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At selection-screen . Second event - Validation on selection-screen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Top-of-page - Third event- header&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;end-of-page - fourth event - footer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;start-of-selection -fifth event- main processing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use logical database then two events you need to use&lt;/P&gt;&lt;P&gt;get,get late.&lt;/P&gt;&lt;P&gt;end-of-selection -last event -output formatting&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2007 04:12:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028588#M716207</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-01T04:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: Events in reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028589#M716208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Classical Reports&lt;/P&gt;&lt;P&gt;These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a loop. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT. &lt;/P&gt;&lt;P&gt;Events In Classical Reports. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INTIALIZATION: This event triggers before selection screen display. &lt;/P&gt;&lt;P&gt;AT-SELECTION-SCREEN: This event triggers after proccesing user input still selection screen is in active mode. &lt;/P&gt;&lt;P&gt;START OF SELECTION: Start of selection screen triggers after proceesing selection screen. &lt;/P&gt;&lt;P&gt;END-OF-SELECTION : It is for Logical Database Reporting. &lt;/P&gt;&lt;P&gt;[Edit section] Interactive Reports&lt;/P&gt;&lt;P&gt;As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Events associated with Interactive Reports are: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT LINE-SELECTION &lt;/P&gt;&lt;P&gt;AT USER-COMMAND &lt;/P&gt;&lt;P&gt;AT PF&amp;lt;key&amp;gt; &lt;/P&gt;&lt;P&gt;TOP-OF-PAGE DURING LINE-SELECTION. &lt;/P&gt;&lt;P&gt;HIDE statement holds the data to be displayed in the secondary list. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sy-lisel : contains data of the selected line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sy-lsind : contains the level of report (from 0 to 21) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interactive Report Events: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sublist is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sublist. &lt;/P&gt;&lt;P&gt;AT PFn: For predefined function keys... &lt;/P&gt;&lt;P&gt;AT USER-COMMAND : It provides user functions keys. &lt;/P&gt;&lt;P&gt;TOP-OF-PAGE DURING LINE-SELECTION :top of page event for secondary list. &lt;/P&gt;&lt;P&gt;[Edit section] Logical Database Reports&lt;/P&gt;&lt;P&gt;Logical database is another tool for ABAP reports. Using LDB we can provide extra features for ABAP reports. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While using LDB there is no need for us to declare Parameters. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Selection-screen as they will be generated automatically. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have to use the statement NODES in ABAP report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there are many tables the Performance will be slow as all the table data will be read from top node to bottom node . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Edit section] ABAP Query Reports&lt;/P&gt;&lt;P&gt;ABAP query is another tool for ABAP. It provides efficency for ABAP reports. These reports are very accurate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transaction Code : SQ01 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   The advantage with ABAP QUERY is logic required for classic &amp;amp; interactive reports system design automatically 80%.&lt;/P&gt;&lt;P&gt;For ABAP QUERY handle these &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SQ01 ; QUERY&lt;/P&gt;&lt;P&gt;SQ02 : INFOSET OR FUNCTIONAL AREA&lt;/P&gt;&lt;P&gt;SQ03: USER GROUP.&lt;/P&gt;&lt;P&gt;[Edit section] Report Writer&lt;/P&gt;&lt;P&gt;Key Concept : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Super users and end users can use Report Painter/Report Writer tools to write their own reports. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Giving them the ability to report on additional fields at their discretion shifts the report maintenance burden to them, saving SAP support groups time and effort normally spent creating and maintaining the reports. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead of using ABAP code to write a report in FI and CO, many users build a Report Painter/ Report Writer library using transaction MC27. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, this workaround has some drawbacks. Little known transaction GRCT solves these problems in most cases, and eliminates the need to use transaction MC27. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[Edit section] ABAP Report Types&lt;/P&gt;&lt;P&gt;ABAP report types are those ones available in some report's attributes screen, i.e. : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Executable program &lt;/P&gt;&lt;P&gt;Function group (containing function modules) &lt;/P&gt;&lt;P&gt;Include &lt;/P&gt;&lt;P&gt;Interface pool &lt;/P&gt;&lt;P&gt;Class pool &lt;/P&gt;&lt;P&gt;Module pool &lt;/P&gt;&lt;P&gt;Subroutine pool &lt;/P&gt;&lt;P&gt;Also ALV means ABAP List Viewer. Most convenient way to use it is through reuse library (cf. transaction se83) available from release 4.6 of SAP R/3. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALV is available in two modes: list and grid. List mode is good old list processing with standard functionnalities, and grid mode is using a new OCX object displaying grids.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2007 04:14:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028589#M716208</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-01T04:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: Events in reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028590#M716209</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;&lt;/P&gt;&lt;P&gt;INITIALIZATION.   Before the selection screen is displayed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN OUTPUT. Before painting the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT SELECTION-SCREEN. Used for validations..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. When pressed execute button in the selection-screen. If no selection-screen then executes automatically&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;END-OF-SELECTION. Generally used in the logical database. But in normal reporting triggers after start-of-selection. and is the last event triggered before displaying the report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT USER-COMMAND. when user presses button in the list. then this event is triggered&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT LINE-SELECTION. when double clicked on the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE. when first write statement is triggered in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;END-OF-PAGE. triggered at the end of the page..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Naren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2007 04:16:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028590#M716209</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-01T04:16:05Z</dc:date>
    </item>
    <item>
      <title>Re: Events in reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028591#M716210</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;Refer to this link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;http://help.sap.com/saphelp_nw04/helpdata/en/9f/dba3ae35c111d1829f0000e829fbfe/content.htm&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Vasudha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2007 04:16:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/events-in-reports/m-p/3028591#M716210</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-01T04:16:11Z</dc:date>
    </item>
  </channel>
</rss>

