<?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 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792481#M912192</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;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;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;PRE&gt;&lt;CODE&gt;TABLES: spfli, sbook.

DATA: num TYPE i,
      dat TYPE d.

START-OF-SELECTION.

  num = 0.
  SET PF-STATUS 'FLIGHT'.

GET spfli.

  num = num + 1.
  WRITE: / spfli-carrid, spfli-connid,
           spfli-cityfrom, spfli-cityto.
  HIDE:    spfli-carrid, spfli-connid, num.

END-OF-SELECTION.

  CLEAR num.

TOP-OF-PAGE.

  WRITE 'List of Flights'.
  ULINE.
  WRITE 'CA  CONN FROM                 TO'.
  ULINE.

TOP-OF-PAGE DURING LINE-SELECTION.

  CASE sy-pfkey.
    WHEN 'BOOKING'.
      WRITE sy-lisel.
      ULINE.
    WHEN 'WIND'.
      WRITE:  'Booking', sbook-bookid,
           /  'Date   ', sbook-fldate.
      ULINE.
  ENDCASE.

AT USER-COMMAND.

  CASE sy-ucomm.
    WHEN 'SELE'.
      IF num NE 0.
        SET PF-STATUS 'BOOKING'.
        CLEAR dat.
        SELECT * FROM sbook WHERE carrid = spfli-carrid
                            AND   connid = spfli-connid.
          IF sbook-fldate NE dat.
            dat = sbook-fldate.
            SKIP.
            WRITE / sbook-fldate.
            POSITION 16.
          ELSE.
            NEW-LINE.
            POSITION 16.
          ENDIF.
          WRITE sbook-bookid.
          HIDE: sbook-bookid, sbook-fldate, sbook-custtype,
                sbook-smoker, sbook-luggweight, sbook-class.
        ENDSELECT.
        IF sy-subrc NE 0.
          WRITE / 'No bookings for this flight'.
        ENDIF.
        num = 0.
        CLEAR sbook-bookid.
      ENDIF.
    WHEN 'INFO'.
      IF NOT sbook-bookid IS INITIAL.
        SET PF-STATUS 'WIND'.
        SET TITLEBAR 'BKI'.
        WINDOW STARTING AT 30 5 ENDING AT  60 10.
        WRITE: 'Customer type   :', sbook-custtype,
             / 'Smoker          :', sbook-smoker,
             / 'Luggage weigtht :', sbook-luggweight UNIT 'KG',
             / 'Class           :', sbook-class.
      ENDIF.
  ENDCASE.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kannaiah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 May 2008 11:21:51 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-16T11:21:51Z</dc:date>
    <item>
      <title>HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792478#M912189</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;why we use hide in lists please explain in detail&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:14:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792478#M912189</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792479#M912190</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HIDE dobj. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This statement stores - in the current list level - the content of the variable dobj together with the current list line whose line number is contained in sy-linno. 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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:16:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792479#M912190</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:16:52Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792480#M912191</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;HIDE is the statament to store in memory the data u need to show or get by a doubleclick in the event AT LINE-SELECTION or AT USER-COMMAND.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It creates a link beetween the data and the line selected, in this way you'll have the variable filled with the data of the line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:18:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792480#M912191</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792481#M912192</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;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;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;PRE&gt;&lt;CODE&gt;TABLES: spfli, sbook.

DATA: num TYPE i,
      dat TYPE d.

START-OF-SELECTION.

  num = 0.
  SET PF-STATUS 'FLIGHT'.

GET spfli.

  num = num + 1.
  WRITE: / spfli-carrid, spfli-connid,
           spfli-cityfrom, spfli-cityto.
  HIDE:    spfli-carrid, spfli-connid, num.

END-OF-SELECTION.

  CLEAR num.

TOP-OF-PAGE.

  WRITE 'List of Flights'.
  ULINE.
  WRITE 'CA  CONN FROM                 TO'.
  ULINE.

TOP-OF-PAGE DURING LINE-SELECTION.

  CASE sy-pfkey.
    WHEN 'BOOKING'.
      WRITE sy-lisel.
      ULINE.
    WHEN 'WIND'.
      WRITE:  'Booking', sbook-bookid,
           /  'Date   ', sbook-fldate.
      ULINE.
  ENDCASE.

AT USER-COMMAND.

  CASE sy-ucomm.
    WHEN 'SELE'.
      IF num NE 0.
        SET PF-STATUS 'BOOKING'.
        CLEAR dat.
        SELECT * FROM sbook WHERE carrid = spfli-carrid
                            AND   connid = spfli-connid.
          IF sbook-fldate NE dat.
            dat = sbook-fldate.
            SKIP.
            WRITE / sbook-fldate.
            POSITION 16.
          ELSE.
            NEW-LINE.
            POSITION 16.
          ENDIF.
          WRITE sbook-bookid.
          HIDE: sbook-bookid, sbook-fldate, sbook-custtype,
                sbook-smoker, sbook-luggweight, sbook-class.
        ENDSELECT.
        IF sy-subrc NE 0.
          WRITE / 'No bookings for this flight'.
        ENDIF.
        num = 0.
        CLEAR sbook-bookid.
      ENDIF.
    WHEN 'INFO'.
      IF NOT sbook-bookid IS INITIAL.
        SET PF-STATUS 'WIND'.
        SET TITLEBAR 'BKI'.
        WINDOW STARTING AT 30 5 ENDING AT  60 10.
        WRITE: 'Customer type   :', sbook-custtype,
             / 'Smoker          :', sbook-smoker,
             / 'Luggage weigtht :', sbook-luggweight UNIT 'KG',
             / 'Class           :', sbook-class.
      ENDIF.
  ENDCASE.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kannaiah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:21:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792481#M912192</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792482#M912193</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 the below link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/ABAP/HIDE_Technique.html" target="test_blank"&gt;http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/ABAP/HIDE_Technique.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks and rewards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:24:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792482#M912193</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792483#M912194</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;HIDE Concept:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The HIDE statement is one of the fundamental statements for interactive reporting. You use the HIDE technique when creating a basic list. It defines the information that can be passed to subsequent detail lists.&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;Kumar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:26:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792483#M912194</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792484#M912195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;    hide ias an alternativ eto read statement.&lt;/P&gt;&lt;P&gt;     whenever you are dealing with interactive reports, you want to display some particular rcords in detail , in such acase hide is useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Hide is an internal table which consists of the following fields:&lt;/P&gt;&lt;P&gt;  1. List number&lt;/P&gt;&lt;P&gt;  2. line number&lt;/P&gt;&lt;P&gt;  3.field name&lt;/P&gt;&lt;P&gt;  4. field value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if suppose basic list is having 200 records  in 4 pages.&lt;/P&gt;&lt;P&gt; if you have hided two fields let us say.&lt;/P&gt;&lt;P&gt;then  hide table consists of  400 records. That much memory is occupied. So it is recommended genarally when there are  not so many records in the basic list.&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;for example , if you click on  135 th record  in 3rd basic list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sy-lsind = 3, sy-linno = 135.&lt;/P&gt;&lt;P&gt;So that particular record's field name is passed to field value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the help of this we can avoid couple of string staements in the basic list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rgds&lt;/P&gt;&lt;P&gt;umakanth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 11:40:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792484#M912195</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T11:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792485#M912196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In ABAP HIDE is an important technique and is used in interactive reporting. The HIDE statement defines the information that needs to be passed to the subsequent lists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Consider this simple example of the HIDE statement to understand the concept. In this example I want to select the Header data of all the sales order into an internal table. I will then display only the customer numbers. Once the user clicks on the customer number the Following information will be displayed as the Secondary list.&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;CUSTOMER NUMBER&lt;/P&gt;&lt;P&gt;PURCHASE ORDER NUMBER&lt;/P&gt;&lt;P&gt;SALES ORDER NUMBER&lt;/P&gt;&lt;P&gt;SALES ORGANIZATION&lt;/P&gt;&lt;P&gt;DISTRIBUTION CHANNEL&lt;/P&gt;&lt;P&gt;DIVISION&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To achieve this we will hide the above mentioned fields using the HIDE statement. The Program is given below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT ZEX_HIDE .&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;amp;----&lt;/STRONG&gt;&lt;/P&gt;&lt;HR originaltext="----------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*&amp;amp; ABAPLOVERS THE HIDE STATEMENT&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;amp;----&lt;/STRONG&gt;&lt;/P&gt;&lt;HR originaltext="----------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Tables&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;TABLES VBAK.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Internal table&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;DATA int_VBAK LIKE VBAK OCCURS 100&lt;/P&gt;&lt;P&gt;                   WITH HEADER LINE.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Processing data&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; SELECT * FROM VBAK INTO TABLE INT_VBAK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  LOOP AT int_vbak.&lt;/P&gt;&lt;P&gt;    WRITE / int_vbak-kunnr HOTSPOT ON.&lt;/P&gt;&lt;P&gt;    HIDE: int_VBAK-VBELN,&lt;/P&gt;&lt;P&gt;          int_VBAK-KUNNR,&lt;/P&gt;&lt;P&gt;          int_VBAK-BSTNK,&lt;/P&gt;&lt;P&gt;          int_VBAK-VKORG,&lt;/P&gt;&lt;P&gt;          int_VBAK-VTWEG,&lt;/P&gt;&lt;P&gt;          int_VBAK-SPART.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Secondary List&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;AT LINE-SELECTION.&lt;/P&gt;&lt;P&gt;  WRITE: / 'Sales Order Details',&lt;/P&gt;&lt;P&gt;         int_VBAK-KUNNR,&lt;/P&gt;&lt;P&gt;         int_VBAK-BSTNK,&lt;/P&gt;&lt;P&gt;         int_VBAK-VBELN,&lt;/P&gt;&lt;P&gt;         int_VBAK-VKORG,&lt;/P&gt;&lt;P&gt;         int_VBAK-VTWEG,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 12:12:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide/m-p/3792485#M912196</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T12:12:24Z</dc:date>
    </item>
  </channel>
</rss>

