<?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: Table control in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932406#M61145</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sanjay, thanx for your patience.. This is what I have been doing from the start, let me know where I am going wrong.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I defined the KBETR field using KONWA field (also available on the screen) as reference and KBETR is right justified.. I am getting the kbetr and konwa values from condition tables .. When I populate it on the table control (through PBO), if konwa supports four decimal places, the value gets displayed perfectly on the table control (for example 1.0000) the first time.. But when I press enter or page down, it gives an error I had referred to earlier... When KONWA has currency like USD which supports two decimal places, it works perfectly...When I change the currency to one that supports multiple decimal places, value '1.00' gets converted to '1.0000' but the error message is also thrown...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Oct 2005 13:11:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-10-03T13:11:27Z</dc:date>
    <item>
      <title>Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932389#M61128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need two table controls in one screen... &lt;/P&gt;&lt;P&gt;Can I put two table control in one screen without using subscreen? Is there any danger in doing this? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or is it better to put the second table in a subscreen?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 04:37:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932389#M61128</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T04:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932390#M61129</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; You can go ahead using those in a single screen.&lt;/P&gt;&lt;P&gt; The advantage of using a subscreen for another Table &lt;/P&gt;&lt;P&gt; control will make you easier to hide the entire &lt;/P&gt;&lt;P&gt; functionality. &lt;/P&gt;&lt;P&gt; i.e say you are using a sub screen for the 2nd Table &lt;/P&gt;&lt;P&gt; control.If you don't call that Subscreen the code &lt;/P&gt;&lt;P&gt; written for the entire subscreen will not get triggered &lt;/P&gt;&lt;P&gt; thereby providing a transparency fo one over the &lt;/P&gt;&lt;P&gt; other.   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Please reward points if this explanation useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt; Siva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 04:42:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932390#M61129</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T04:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932391#M61130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi SSG,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why dont you go for TAB Strips.&lt;/P&gt;&lt;P&gt;You can define 2 Tab strips so that 1 table control in one and the other in 2and Tab strip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SUB&gt;CHEERS&lt;/SUB&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 04:53:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932391#M61130</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T04:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932392#M61131</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;I agree with deepak, if you occupied more than one table control in one screen it will be climpsy ( if your requirement is like that then go ahead for ex they want to see all the two table control data at a same time )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead of the define one tabstrip with two tabs and each tab has separate subscreen then you place the table control in that screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;sasi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 05:07:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932392#M61131</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T05:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932393#M61132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes you should go for tabstrip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it will be very useful, if you have to add one more table, customer demands always increase, so be prepared for that and create it in tabstrip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 05:59:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932393#M61132</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T05:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932394#M61133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with sasi,&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;But instead of two subscreens we can go for only one and and assign the same for both tabs. so, again we have to create two screens (as subscreens ) for table controls and assign it to the tabstrip.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if it helps u and close the thread if ur problem is solved&lt;/P&gt;&lt;P&gt;&lt;SUB&gt;CHEERS&lt;/SUB&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 06:06:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932394#M61133</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T06:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932395#M61134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for all the replies.. the user needs to see the data simultaneously(based on the row selected in first table control).. so tabstrip is not an option.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both table controls should always be visible .. In such a scenario, do you think a separate subscreen area is useful ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 21:27:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932395#M61134</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T21:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932396#M61135</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no problem at all...use as many table control as u need on single screen..i have been into module pools development for long now and it is completly safe.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arpit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2005 23:09:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932396#M61135</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-29T23:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932397#M61136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Arpit, thanks.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have another question regarding chain endchain.. is it okay to define a same field in two different chain-request?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Sep 2005 16:52:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932397#M61136</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-30T16:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932398#M61137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello SSG,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes you can define the same fields in different chain-requests.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Sep 2005 16:53:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932398#M61137</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-30T16:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932399#M61138</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;Yes you can, there isn't a particular problem...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can do it if you want to use a screen field in several control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally you can repeat the same screen field in all controls you need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: max bianchi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Sep 2005 16:55:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932399#M61138</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-09-30T16:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932400#M61139</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to populate decimal field on the table control.. I have defined it with reference to unit field.. For some units, 6 decimal places is allowed and when I choose that unit, than my screen converts '1' to 0.000100 and gives invalid input message.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But when the unit is for 2 places (say like USD), it display this perfectly&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Oct 2005 16:38:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932400#M61139</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-02T16:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932401#M61140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi SSG,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;USD is currency and not unit.&lt;/P&gt;&lt;P&gt;You have to use a field of type CURR ( like ekpo-netpr ) and reference to a field of type CUKY ( Like EKKO-WAERS )&lt;/P&gt;&lt;P&gt;on the screen to display your value correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Oct 2005 17:07:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932401#M61140</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-02T17:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932402#M61141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i meant currency field, sorry for the confusion.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for Certain currency fields , the display is 6 decimal places.. But my screen spits it out, with message 088 (class 00).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Oct 2005 17:31:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932402#M61141</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-02T17:31:43Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932403#M61142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have already given the answer. Use a field CURR with a reference field CUKY . If you use a type P field with 2 decimals you will get that error. Your screen field has to refer to a Dictionary/ Porgram field which has type CURR and there should be another field of type CUKY .&lt;/P&gt;&lt;P&gt;( For example see PO create / change screen ME21/ME22 and see how they define net price and currency field in item overview )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;( Dont forget to reward if answers were helpful )&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Oct 2005 18:34:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932403#M61142</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-02T18:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932404#M61143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my case, it may not always be currency (i am using kbetr for condition record value) - depending on the record type it could also be percentage field.. So I cannot use CURR field all the time..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Oct 2005 20:07:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932404#M61143</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-02T20:07:32Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932405#M61144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok So KBETR is a currency field . Goto SE51 -&amp;gt; Element list . Goto references tab. Here you will see a CUKY field. You will have to define this field as a Currency field  on screen or else chanage this field to the fieldname which you have defined as currency field on screen( you will have to remove the Dict Ref Check box to do this ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After this for the KBETR field in display attributes click on the right justified checkbox. Then try your transaction again. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you dont put a currency value the input should have no more than 2 decimal places ( suits for percentage ) otherwise it will take the formatting of respective currency. Suppose USD has 2 decimals in currency setting and you try input 1.234 , it will again throw an error . So you have to input with correct decimal places . Try with different currency and the error message will change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Oct 2005 02:29:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932405#M61144</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-03T02:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: Table control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932406#M61145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sanjay, thanx for your patience.. This is what I have been doing from the start, let me know where I am going wrong.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I defined the KBETR field using KONWA field (also available on the screen) as reference and KBETR is right justified.. I am getting the kbetr and konwa values from condition tables .. When I populate it on the table control (through PBO), if konwa supports four decimal places, the value gets displayed perfectly on the table control (for example 1.0000) the first time.. But when I press enter or page down, it gives an error I had referred to earlier... When KONWA has currency like USD which supports two decimal places, it works perfectly...When I change the currency to one that supports multiple decimal places, value '1.00' gets converted to '1.0000' but the error message is also thrown...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Oct 2005 13:11:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-control/m-p/932406#M61145</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-10-03T13:11:27Z</dc:date>
    </item>
  </channel>
</rss>

