<?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 AREA in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416137#M820472</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;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;The HIDE Technique&lt;/P&gt;&lt;P&gt;The example below presents some of the essential features of interactive reporting. The basic list contains summarized information. With the HIDE technique, it is possible to branch to more detailed information on subsequent lists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following program is connected to the logical database F1S.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT demo_list_hide NO STANDARD PAGE HEADING.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLES: spfli, sbook.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: num TYPE i,&lt;/P&gt;&lt;P&gt;dat TYPE d.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;num = 0.&lt;/P&gt;&lt;P&gt;SET PF-STATUS 'FLIGHT'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET spfli.&lt;/P&gt;&lt;P&gt;num = num + 1.&lt;/P&gt;&lt;P&gt;WRITE: / spfli-carrid, spfli-connid,&lt;/P&gt;&lt;P&gt;spfli-cityfrom, spfli-cityto.&lt;/P&gt;&lt;P&gt;HIDE: spfli-carrid, spfli-connid, num.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;END-OF-SELECTION.&lt;/P&gt;&lt;P&gt;CLEAR num.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE.&lt;/P&gt;&lt;P&gt;WRITE 'List of Flights'.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;WRITE 'CA CONN FROM TO'.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE DURING LINE-SELECTION.&lt;/P&gt;&lt;P&gt;CASE sy-pfkey.&lt;/P&gt;&lt;P&gt;WHEN 'BOOKING'.&lt;/P&gt;&lt;P&gt;WRITE sy-lisel.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;WHEN 'WIND'.&lt;/P&gt;&lt;P&gt;WRITE: 'Booking', sbook-bookid,&lt;/P&gt;&lt;P&gt;/ 'Date ', sbook-fldate.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;ENDCASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT USER-COMMAND.&lt;/P&gt;&lt;P&gt;CASE sy-ucomm.&lt;/P&gt;&lt;P&gt;WHEN 'SELE'.&lt;/P&gt;&lt;P&gt;IF num NE 0.&lt;/P&gt;&lt;P&gt;SET PF-STATUS 'BOOKING'.&lt;/P&gt;&lt;P&gt;CLEAR dat.&lt;/P&gt;&lt;P&gt;SELECT * FROM sbook WHERE carrid = spfli-carrid&lt;/P&gt;&lt;P&gt;AND connid = spfli-connid.&lt;/P&gt;&lt;P&gt;IF sbook-fldate NE dat.&lt;/P&gt;&lt;P&gt;dat = sbook-fldate.&lt;/P&gt;&lt;P&gt;SKIP.&lt;/P&gt;&lt;P&gt;WRITE / sbook-fldate.&lt;/P&gt;&lt;P&gt;POSITION 16.&lt;/P&gt;&lt;P&gt;ELSE.&lt;/P&gt;&lt;P&gt;NEW-LINE.&lt;/P&gt;&lt;P&gt;POSITION 16.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;WRITE sbook-bookid.&lt;/P&gt;&lt;P&gt;HIDE: sbook-bookid, sbook-fldate, sbook-custtype,&lt;/P&gt;&lt;P&gt;sbook-smoker, sbook-luggweight, sbook-class.&lt;/P&gt;&lt;P&gt;ENDSELECT.&lt;/P&gt;&lt;P&gt;IF sy-subrc NE 0.&lt;/P&gt;&lt;P&gt;WRITE / 'No bookings for this flight'.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;num = 0.&lt;/P&gt;&lt;P&gt;CLEAR sbook-bookid.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;WHEN 'INFO'.&lt;/P&gt;&lt;P&gt;IF NOT sbook-bookid IS INITIAL.&lt;/P&gt;&lt;P&gt;SET PF-STATUS 'WIND'.&lt;/P&gt;&lt;P&gt;SET TITLEBAR 'BKI'.&lt;/P&gt;&lt;P&gt;WINDOW STARTING AT 30 5 ENDING AT 60 10.&lt;/P&gt;&lt;P&gt;WRITE: 'Customer type :', sbook-custtype,&lt;/P&gt;&lt;P&gt;/ 'Smoker :', sbook-smoker,&lt;/P&gt;&lt;P&gt;/ 'Luggage weigtht :', sbook-luggweight UNIT 'KG',&lt;/P&gt;&lt;P&gt;/ 'Class :', sbook-class.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;ENDCASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the event START-OF-SELECTION, the system sets the status FLIGHT for the basic list. In status FLIGHT, function code SELE (text SELECT) is assigned to function key F2 and to a pushbutton. So the event AT USER-COMMAND is triggered if the user double-clicks, presses F2, or chooses the pushbutton SELECT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The three fields spfli-carrid, spfli-connid, and num are stored in the HIDE area while creating the basic list. After selecting a line, the system displays the detail list defined in the AT USER-COMMAND event for function code SELE. In the AT USER-COMMAND event, the system refills all fields of the selected line that were stored in the HIDE area. You use num to check whether the user selected a line from the actual list. The detail list has status BOOKING, where F2 is assigned to function code INFO (text: Booking Information). The detail list presents data that the program selected using the HIDE fields of the basic list. For each list line displayed, the system stores additional information in the HIDE area.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the user selects a line of the detail list, the system displays the stored information in a dialog box with the status WIND. For the WIND status, the default values for the status type Dialog box have been adopted with the list status adjustment. The program uses sbook-bookid to check whether the user selected a valid line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The program itself sets all page headers and the title bar of the dialog box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 23 Feb 2008 09:25:06 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-23T09:25:06Z</dc:date>
    <item>
      <title>HIDE AREA</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416135#M820470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can anyone tell the details of Hide command.What will happn if we use that command before write statement  Is write statement necessary for using that command  Actually what is happening when we are using that? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Feb 2008 09:19:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416135#M820470</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-23T09:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE AREA</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416136#M820471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hide statement mainly used in interactive reports, it is used to export field informations from basic list to secondare list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;say for eg hide it_mara-matnr,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you give this statement in basic list on click the basic list , the particuler matnr value will be stored in buffer, so that it can be used to select appropriate values in the secondary list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Babu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Feb 2008 09:21:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416136#M820471</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-23T09:21:44Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE AREA</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416137#M820472</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;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;The HIDE Technique&lt;/P&gt;&lt;P&gt;The example below presents some of the essential features of interactive reporting. The basic list contains summarized information. With the HIDE technique, it is possible to branch to more detailed information on subsequent lists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following program is connected to the logical database F1S.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT demo_list_hide NO STANDARD PAGE HEADING.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TABLES: spfli, sbook.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: num TYPE i,&lt;/P&gt;&lt;P&gt;dat TYPE d.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;num = 0.&lt;/P&gt;&lt;P&gt;SET PF-STATUS 'FLIGHT'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GET spfli.&lt;/P&gt;&lt;P&gt;num = num + 1.&lt;/P&gt;&lt;P&gt;WRITE: / spfli-carrid, spfli-connid,&lt;/P&gt;&lt;P&gt;spfli-cityfrom, spfli-cityto.&lt;/P&gt;&lt;P&gt;HIDE: spfli-carrid, spfli-connid, num.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;END-OF-SELECTION.&lt;/P&gt;&lt;P&gt;CLEAR num.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE.&lt;/P&gt;&lt;P&gt;WRITE 'List of Flights'.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;WRITE 'CA CONN FROM TO'.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TOP-OF-PAGE DURING LINE-SELECTION.&lt;/P&gt;&lt;P&gt;CASE sy-pfkey.&lt;/P&gt;&lt;P&gt;WHEN 'BOOKING'.&lt;/P&gt;&lt;P&gt;WRITE sy-lisel.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;WHEN 'WIND'.&lt;/P&gt;&lt;P&gt;WRITE: 'Booking', sbook-bookid,&lt;/P&gt;&lt;P&gt;/ 'Date ', sbook-fldate.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;ENDCASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AT USER-COMMAND.&lt;/P&gt;&lt;P&gt;CASE sy-ucomm.&lt;/P&gt;&lt;P&gt;WHEN 'SELE'.&lt;/P&gt;&lt;P&gt;IF num NE 0.&lt;/P&gt;&lt;P&gt;SET PF-STATUS 'BOOKING'.&lt;/P&gt;&lt;P&gt;CLEAR dat.&lt;/P&gt;&lt;P&gt;SELECT * FROM sbook WHERE carrid = spfli-carrid&lt;/P&gt;&lt;P&gt;AND connid = spfli-connid.&lt;/P&gt;&lt;P&gt;IF sbook-fldate NE dat.&lt;/P&gt;&lt;P&gt;dat = sbook-fldate.&lt;/P&gt;&lt;P&gt;SKIP.&lt;/P&gt;&lt;P&gt;WRITE / sbook-fldate.&lt;/P&gt;&lt;P&gt;POSITION 16.&lt;/P&gt;&lt;P&gt;ELSE.&lt;/P&gt;&lt;P&gt;NEW-LINE.&lt;/P&gt;&lt;P&gt;POSITION 16.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;WRITE sbook-bookid.&lt;/P&gt;&lt;P&gt;HIDE: sbook-bookid, sbook-fldate, sbook-custtype,&lt;/P&gt;&lt;P&gt;sbook-smoker, sbook-luggweight, sbook-class.&lt;/P&gt;&lt;P&gt;ENDSELECT.&lt;/P&gt;&lt;P&gt;IF sy-subrc NE 0.&lt;/P&gt;&lt;P&gt;WRITE / 'No bookings for this flight'.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;num = 0.&lt;/P&gt;&lt;P&gt;CLEAR sbook-bookid.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;WHEN 'INFO'.&lt;/P&gt;&lt;P&gt;IF NOT sbook-bookid IS INITIAL.&lt;/P&gt;&lt;P&gt;SET PF-STATUS 'WIND'.&lt;/P&gt;&lt;P&gt;SET TITLEBAR 'BKI'.&lt;/P&gt;&lt;P&gt;WINDOW STARTING AT 30 5 ENDING AT 60 10.&lt;/P&gt;&lt;P&gt;WRITE: 'Customer type :', sbook-custtype,&lt;/P&gt;&lt;P&gt;/ 'Smoker :', sbook-smoker,&lt;/P&gt;&lt;P&gt;/ 'Luggage weigtht :', sbook-luggweight UNIT 'KG',&lt;/P&gt;&lt;P&gt;/ 'Class :', sbook-class.&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;ENDCASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the event START-OF-SELECTION, the system sets the status FLIGHT for the basic list. In status FLIGHT, function code SELE (text SELECT) is assigned to function key F2 and to a pushbutton. So the event AT USER-COMMAND is triggered if the user double-clicks, presses F2, or chooses the pushbutton SELECT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The three fields spfli-carrid, spfli-connid, and num are stored in the HIDE area while creating the basic list. After selecting a line, the system displays the detail list defined in the AT USER-COMMAND event for function code SELE. In the AT USER-COMMAND event, the system refills all fields of the selected line that were stored in the HIDE area. You use num to check whether the user selected a line from the actual list. The detail list has status BOOKING, where F2 is assigned to function code INFO (text: Booking Information). The detail list presents data that the program selected using the HIDE fields of the basic list. For each list line displayed, the system stores additional information in the HIDE area.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the user selects a line of the detail list, the system displays the stored information in a dialog box with the status WIND. For the WIND status, the default values for the status type Dialog box have been adopted with the list status adjustment. The program uses sbook-bookid to check whether the user selected a valid line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The program itself sets all page headers and the title bar of the dialog box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Feb 2008 09:25:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416137#M820472</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-23T09:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: HIDE AREA</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416138#M820473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;we use 'hide' keyword exclusively in interactive reports.&lt;/P&gt;&lt;P&gt;if we select one of the value in the output of the interactive report, 'hide' keyword take that value keep it in their internal table .with that value next interactive report output screen will be displayes&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Feb 2008 10:20:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hide-area/m-p/3416138#M820473</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-23T10:20:24Z</dc:date>
    </item>
  </channel>
</rss>

