<?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: Doubt in Table Controll in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346618#M802510</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rudra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this standard report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;demo_dynpro_tabcont_loop_at&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in this report  code check the condition&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WHEN 'TOGGLE'.&lt;/P&gt;&lt;P&gt;      LOOP AT flights-cols INTO cols WHERE index GT 2.&lt;/P&gt;&lt;P&gt;        IF  cols-screen-input = '0'.&lt;/P&gt;&lt;P&gt;          cols-screen-input = '1'.&lt;/P&gt;&lt;P&gt;        ELSEIF  cols-screen-input = '1'.&lt;/P&gt;&lt;P&gt;          cols-screen-input = '0'.&lt;/P&gt;&lt;P&gt;        ENDIF.&lt;/P&gt;&lt;P&gt;        MODIFY flights-cols FROM cols INDEX sy-tabix.&lt;/P&gt;&lt;P&gt;      ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Analyise these and write in your code..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For screen modification...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check this report...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;demo_dynpro_modify_screen&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;execute these two reports... analyise u ll understand easily..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward if useful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;sunil kairam.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Feb 2008 12:17:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-07T12:17:27Z</dc:date>
    <item>
      <title>Doubt in Table Controll</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346615#M802507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a table control..&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;option  add/delete  suboption&lt;/STRONG&gt;  value&lt;/P&gt;&lt;P&gt;A           add             A1          &lt;/P&gt;&lt;P&gt;B           delete          A2 &lt;/P&gt;&lt;P&gt;                                B1&lt;/P&gt;&lt;P&gt;                                B2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there is a drop down at coloumn add/delete. Now after we select &lt;STRONG&gt;add&lt;/STRONG&gt; I want to enable the input field near A1,A2....Suppose Delete is selected for B...I want to disable the input field near B1,B2.....&lt;/P&gt;&lt;P&gt;One thing to note is that.The disabling or enabling of the last button depends on the selection of add/delete from the drop down...&lt;/P&gt;&lt;P&gt;Hw to achieve this fuctionality???????&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2008 08:47:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346615#M802507</guid>
      <dc:creator>former_member195383</dc:creator>
      <dc:date>2008-02-07T08:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt in Table Controll</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346616#M802508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Rudra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Iam just repeating the requirement corrcet me if iam wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have a table control with field say 5 columns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have the add/delete column in column 4. If you select "add" it needs to enable and "delete" its to disabled some thing like this, am i right.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here we needs to trigger some code when ever you change the value in ADD/DELTE column which are drop down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So to get the code triggered you need to give some function code for that particular field in the screen painter. Double click the field and give some value in "FctCode".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In coding &lt;/P&gt;&lt;P&gt;you need to mention this piece of code for that particluar coulmn,   field "fieldname" module "m" on input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kiran I&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2008 09:55:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346616#M802508</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-07T09:55:56Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt in Table Controll</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346617#M802509</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;Use the &lt;STRONG&gt;modify screen&lt;/STRONG&gt; statement to enable/disable screen fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax &lt;/P&gt;&lt;P&gt;MODIFY SCREEN &lt;A href="FROM wa"&gt;&lt;/A&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;Effect &lt;/P&gt;&lt;P&gt;This statement can be used in the statement block after LOOP AT SCREEN only and makes sense only during PBO processing. If FROM is not specified, MODIFY SCREEN modifies the attributes of the current screen element with the values from the predefined screen work area. If a wa work area is specified, its contents are used for the modification. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The wa work area must have the same data type as screen. The name component must contain the name of the current screen element, otherwise the statement is not executed. nweisung nicht ausgeführt. Up to the group1 to group4 and length components, all remaining components of screen and wa must contain either the value 0 or 1. The value 0 deactivates the corresponding field attribute, and 1 activates it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If MODIFY SCREEN is executed during PBO processing, the modified attributes for the display of the screen affect the current dynpro after PBO processing. The attributes of the screen element of the dynpro are reset to their static attributes at the start of each PBO processing, so that the execution of MODIFY SCREEN during PAI processing does not effect the display of the following screen. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The active component &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The active component is used to set the input, output and invisible components at once. At the start of PBO processing, the active component always has the value 1. If active is set to 0 with MODIFY SCREEN, input and output are automatically set to 0 and invisible is set to 1. Other values in input, output and invisible are ignored. Conversely, setting input and output to 0 and invisible to 1 automatically sets active to 0 and a different value in active is ignored. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modifications in Table Controls and Step Loops &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During processing of a table control or a step loop, the changes affect the current line of the table control or the current step loop group. Before the processing of a table control, the change to the attributes of a screen element that is part of a line in the table control does not effect the table control, since the values are transferred from the structure created using CONTROLS. Before a step loop is processed, the change to the attributes of a screen elements that is part of a step loop group affects all groups in the step loop. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modifications to Tabstrip Controls &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the active component for a tab title of a tabstrip control is set to 0, the whole tabstrip page is hidden. &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;In the following PBO module, an input field called val is made mandatory and converted to display in the foreground. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MODULE modify_0100 OUTPUT. &lt;/P&gt;&lt;P&gt;  LOOP AT SCREEN. &lt;/P&gt;&lt;P&gt;    IF screen-name = 'VAL'. &lt;/P&gt;&lt;P&gt;      screen-required    = '1'. "to make required&lt;/P&gt;&lt;P&gt;      screen-intensified = '1'. &lt;/P&gt;&lt;P&gt;screen-input = 0. "to dsplay mode&lt;/P&gt;&lt;P&gt;screen-active = 0. "to hide&lt;/P&gt;&lt;P&gt;      MODIFY SCREEN. &lt;/P&gt;&lt;P&gt;    ENDIF. &lt;/P&gt;&lt;P&gt;  ENDLOOP. &lt;/P&gt;&lt;P&gt;ENDMODULE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls reward points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Renjith Michael.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2008 11:25:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346617#M802509</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-07T11:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: Doubt in Table Controll</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346618#M802510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rudra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this standard report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;demo_dynpro_tabcont_loop_at&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in this report  code check the condition&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WHEN 'TOGGLE'.&lt;/P&gt;&lt;P&gt;      LOOP AT flights-cols INTO cols WHERE index GT 2.&lt;/P&gt;&lt;P&gt;        IF  cols-screen-input = '0'.&lt;/P&gt;&lt;P&gt;          cols-screen-input = '1'.&lt;/P&gt;&lt;P&gt;        ELSEIF  cols-screen-input = '1'.&lt;/P&gt;&lt;P&gt;          cols-screen-input = '0'.&lt;/P&gt;&lt;P&gt;        ENDIF.&lt;/P&gt;&lt;P&gt;        MODIFY flights-cols FROM cols INDEX sy-tabix.&lt;/P&gt;&lt;P&gt;      ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Analyise these and write in your code..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For screen modification...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check this report...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;demo_dynpro_modify_screen&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;execute these two reports... analyise u ll understand easily..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward if useful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;sunil kairam.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2008 12:17:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt-in-table-controll/m-p/3346618#M802510</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-07T12:17:27Z</dc:date>
    </item>
  </channel>
</rss>

