<?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: hide statement in interactive reports in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282676#M785087</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HIDE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax &lt;/P&gt;&lt;P&gt;HIDE dobj. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;This statement stores the content of a variable dobj together with the current list line whose line number is contained in sy-linno in the hide area of the current list level. The data type of the variables dobj must be flat and no field symbols can be specified that point to rows of internal tables, and no class attributes can be specified. The stored values can be read as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For each user action in a displayed screen list that leads to a list result, all the row values stored using HIDE - that is, the row on which the screen cursor is positioned at the time of the event - are assigned to the respective variables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a list row of an arbitrary list level is read or modified using the statements READ LINE or MODIFY LINE, all the values of this row stored using HIDE are assigned to the respective variables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The HIDE statement works independently of whether the list cursor was set. In particular, variables for empty list rows can be stored - that is, rows in which the list cursor was positioned using statements like SKIP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The HIDE statement should be executed immediately at the statement that has set the list cursor in the row. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside of classes, prior to release 7.0, for dobj constants and literals could still be specified. However, it was not possible to read them at list events and in the READ LINE statement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example &lt;/P&gt;&lt;P&gt;Storing square numbers and cubic numbers for a list of numbers. The example shows that arbitrary variables can be stored independently of row content. In the real situation, one would more likely store only the number and execute the calculation, when required, in the the event block for AT LINE-SELECTION. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT ... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: square TYPE i, &lt;/P&gt;&lt;P&gt;      cube   TYPE i. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. &lt;/P&gt;&lt;P&gt;  FORMAT HOTSPOT. &lt;/P&gt;&lt;P&gt;  DO 10 TIMES. &lt;/P&gt;&lt;P&gt;    square = sy-index ** 2. &lt;/P&gt;&lt;P&gt;    cube   = sy-index ** 3. &lt;/P&gt;&lt;P&gt;    WRITE / sy-index. &lt;/P&gt;&lt;P&gt;    HIDE: square, cube. &lt;/P&gt;&lt;P&gt;  ENDDO. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT LINE-SELECTION. &lt;/P&gt;&lt;P&gt;  WRITE: square, cube.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Jan 2008 06:25:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-21T06:25:07Z</dc:date>
    <item>
      <title>hide statement in interactive reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282674#M785085</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;&lt;/P&gt;&lt;P&gt;can anybody please tell me , how many levels of interactive reports we can generates using HIDE statements.??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Answer will be rewarded.&lt;/P&gt;&lt;P&gt;Sandeep Yadav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 06:23:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282674#M785085</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-21T06:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: hide statement in interactive reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282675#M785086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;20 secondary lists can be created by using HIDE&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 06:24:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282675#M785086</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-21T06:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: hide statement in interactive reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282676#M785087</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HIDE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax &lt;/P&gt;&lt;P&gt;HIDE dobj. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;This statement stores the content of a variable dobj together with the current list line whose line number is contained in sy-linno in the hide area of the current list level. The data type of the variables dobj must be flat and no field symbols can be specified that point to rows of internal tables, and no class attributes can be specified. The stored values can be read as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For each user action in a displayed screen list that leads to a list result, all the row values stored using HIDE - that is, the row on which the screen cursor is positioned at the time of the event - are assigned to the respective variables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a list row of an arbitrary list level is read or modified using the statements READ LINE or MODIFY LINE, all the values of this row stored using HIDE are assigned to the respective variables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The HIDE statement works independently of whether the list cursor was set. In particular, variables for empty list rows can be stored - that is, rows in which the list cursor was positioned using statements like SKIP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The HIDE statement should be executed immediately at the statement that has set the list cursor in the row. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside of classes, prior to release 7.0, for dobj constants and literals could still be specified. However, it was not possible to read them at list events and in the READ LINE statement. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example &lt;/P&gt;&lt;P&gt;Storing square numbers and cubic numbers for a list of numbers. The example shows that arbitrary variables can be stored independently of row content. In the real situation, one would more likely store only the number and execute the calculation, when required, in the the event block for AT LINE-SELECTION. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT ... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: square TYPE i, &lt;/P&gt;&lt;P&gt;      cube   TYPE i. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. &lt;/P&gt;&lt;P&gt;  FORMAT HOTSPOT. &lt;/P&gt;&lt;P&gt;  DO 10 TIMES. &lt;/P&gt;&lt;P&gt;    square = sy-index ** 2. &lt;/P&gt;&lt;P&gt;    cube   = sy-index ** 3. &lt;/P&gt;&lt;P&gt;    WRITE / sy-index. &lt;/P&gt;&lt;P&gt;    HIDE: square, cube. &lt;/P&gt;&lt;P&gt;  ENDDO. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT LINE-SELECTION. &lt;/P&gt;&lt;P&gt;  WRITE: square, cube.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 06:25:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282676#M785087</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-21T06:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: hide statement in interactive reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282677#M785088</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi sandeep,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically we are using interactive reporting  to split the o/p in N no of lists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In interactive reporting we can have 1 basic list and  20 secoundry lists, After 20 it will go for dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;DVNS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 06:31:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282677#M785088</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-21T06:31:29Z</dc:date>
    </item>
    <item>
      <title>Re: hide statement in interactive reports</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282678#M785089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi..Sandeep...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIDE statement doesn't create any Interactive report.&lt;/P&gt;&lt;P&gt;It is used to hold the data, where you double clicked,&lt;/P&gt;&lt;P&gt;so that it is available for next level report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this way you can dispaly 20 levels of reports.&lt;/P&gt;&lt;P&gt;After that, if you try for next report,it will go to dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope, you understood.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;sandeep.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2008 07:15:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-statement-in-interactive-reports/m-p/3282678#M785089</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-21T07:15:40Z</dc:date>
    </item>
  </channel>
</rss>

