<?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: D/B interactive reporting &amp; classical reporting in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354817#M520171</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jayasree,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A classic report is a program that generates a single list, which must contain all of the required detail information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) This procedure may result in extensive lists from which the user has to pick the relevant data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) For background processing, this is the only possible method. After starting a background job, there is no way of influencing the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) The desired selections must be made beforehand and the list must provide detailed information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) For dialog sessions, there are no such restrictions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5) The user is present during the execution of the program and can control and manipulate the program flow directly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6) To be able to use all advantages of the online environment, classical reporting was developed into interactive reporting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interactive reports :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interactive reports is the drill down reports means u can navigate by double click on any line item to the secondry list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interactive reports needs only se38 abap editor for programming.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reward If Helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Jun 2007 05:51:47 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-07T05:51:47Z</dc:date>
    <item>
      <title>D/B interactive reporting &amp; classical reporting</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354813#M520167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;can u tell the D/B interactive reporting &amp;amp; classical reporting?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Points will be rewarded.&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 05:46:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354813#M520167</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-07T05:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: D/B interactive reporting &amp; classical reporting</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354814#M520168</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;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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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;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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if it is helpful...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Omkar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 05:47:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354814#M520168</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-07T05:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: D/B interactive reporting &amp; classical reporting</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354815#M520169</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;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;TOP-OF-PAGE:this event triggers before the first write statement. It provides header for abap reports. &lt;/P&gt;&lt;P&gt;END-OF-PAGE:triggers before the new page starts. It provides footer for page. &lt;/P&gt;&lt;P&gt;AT PFn: For predefined function keys... &lt;/P&gt;&lt;P&gt;END-OF-SELECTION : It is for Logical Database Reporting. &lt;/P&gt;&lt;P&gt;AT USER-COMMAND : It provides user functions keys. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. 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). Events associated with Interactive Reports are: 1. AT LINE-SELECTION 2. AT USER-COMMAND 3. AT PF&amp;lt;key&amp;gt; 4. TOP-OF-PAGE DURING LINE-SELECTION. HIDE statement holds the data to be displayed in the secondary list. sy-lisel : contains data of the selected line. sy-lsind : contains the level of report (from 0 to 21) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sree&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 05:49:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354815#M520169</guid>
      <dc:creator>sreeramkumar_madisetty</dc:creator>
      <dc:date>2007-06-07T05:49:02Z</dc:date>
    </item>
    <item>
      <title>Re: D/B interactive reporting &amp; classical reporting</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354816#M520170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interactive report-&amp;gt;&lt;/P&gt;&lt;P&gt;An interactive report generally works in the following fashion: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Basic list is displayed. &lt;/P&gt;&lt;P&gt;2. User double clicks on any valid line &lt;/P&gt;&lt;P&gt;    or &lt;/P&gt;&lt;P&gt;    User selects a line and presses as button on the tool bar. &lt;/P&gt;&lt;P&gt;3. The corresponding event is triggered &lt;/P&gt;&lt;P&gt;4. Then in the code, the line on which action was done, is read. &lt;/P&gt;&lt;P&gt;5. Depending on the values in that selected line, a secondary list is displayed. &lt;/P&gt;&lt;P&gt;6. Steps from 2-5 are repeated till the end. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Classical Report-&amp;gt;&lt;/P&gt;&lt;P&gt;The lines of basic list of a drilldown report when clicked, will take the user to the corresponding (standard) object's display. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;For eg: Suppose your report's primary component is purchase requisition, (assume you are printing PR details), and the basic list displays details of many PRs. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Eg: when clicked on a particular line of the PR basic list, it takes you to std t-code me53 (display of purchase requisition). This is the 'Drill-down' functionality. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;For this, in the at-line selection of your program, as per the above ex: you'll set the parameter ID of PR number BAN (that you can get from Data element) in memory (using set parameter id) and then calling the corresponding transaction (usually skipping initial screen of the std t-code).    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 05:50:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354816#M520170</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-07T05:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: D/B interactive reporting &amp; classical reporting</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354817#M520171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jayasree,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A classic report is a program that generates a single list, which must contain all of the required detail information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) This procedure may result in extensive lists from which the user has to pick the relevant data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) For background processing, this is the only possible method. After starting a background job, there is no way of influencing the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) The desired selections must be made beforehand and the list must provide detailed information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) For dialog sessions, there are no such restrictions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5) The user is present during the execution of the program and can control and manipulate the program flow directly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6) To be able to use all advantages of the online environment, classical reporting was developed into interactive reporting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Interactive reports :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interactive reports is the drill down reports means u can navigate by double click on any line item to the secondry list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interactive reports needs only se38 abap editor for programming.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reward If Helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 05:51:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354817#M520171</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-07T05:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: D/B interactive reporting &amp; classical reporting</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354818#M520172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi jayasree,&lt;/P&gt;&lt;P&gt;   go thro this link or search in the sdn itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2834916"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="468952"&gt;&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;Arun.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2007 05:52:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/d-b-interactive-reporting-classical-reporting/m-p/2354818#M520172</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-07T05:52:25Z</dc:date>
    </item>
  </channel>
</rss>

