<?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: ALV Grid vs Table Control in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-grid-vs-table-control/m-p/4713036#M1107035</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Laurie&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may have a look at my sample report &lt;STRONG&gt;ZUS_SDN_THREE_ALV_GRIDS&lt;/STRONG&gt; in thread &lt;SPAN __jive_macro_name="thread" id="286895"&gt;&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;If you make these ALV grids editable you are already halfway finished.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, besides this sample report you are probably interested in pros and cons. Well, here is my story.&lt;/P&gt;&lt;P&gt;Three years ago I worked (as external consultant) for a big retailer here in Switzerland. The task was to add a subscreen with a table control into the material master data where they could store seasonal data to their products. In addition, they wanted to have a separate report for mass-maintenance of theses seasonal data for many products.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I decided to go for an editable ALV grid (partly because I cannot program table controls anymore). I managed to use the very same logic for the masterial master maintenance (where the ALV list allowed to enter data just for a single product) and in the report (where you could mantain all selected materials).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the beginning the customer was very sceptical about this because ALV grids are rather unusual in master data. However, when they saw that it worked and they realized the power of the ALV grid (e.g. colouring, drop-down lists, validations, etc.) they flushed me with additional requirements that all could be implemented easily using the ALV approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Nov 2008 17:03:08 GMT</pubDate>
    <dc:creator>uwe_schieferstein</dc:creator>
    <dc:date>2008-11-13T17:03:08Z</dc:date>
    <item>
      <title>ALV Grid vs Table Control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-grid-vs-table-control/m-p/4713035#M1107034</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm needing to implement screen with data in 3 related tables.  (Product, Product Detail, Detail Sales) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The user needs the standard insert/update/edit/delete functionality on one to many records in these tables.  I've read where the Table control us useful for editing data in tables, (in is the method if going to Web dynpro - which we aren't yet.  We are at ECC 5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are your opinions - pluses and minueses - about these two methods of working with data in an ABAP program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Laurie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2008 16:45:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-grid-vs-table-control/m-p/4713035#M1107034</guid>
      <dc:creator>laurie_mcginley</dc:creator>
      <dc:date>2008-11-13T16:45:22Z</dc:date>
    </item>
    <item>
      <title>Re: ALV Grid vs Table Control</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-grid-vs-table-control/m-p/4713036#M1107035</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Laurie&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may have a look at my sample report &lt;STRONG&gt;ZUS_SDN_THREE_ALV_GRIDS&lt;/STRONG&gt; in thread &lt;SPAN __jive_macro_name="thread" id="286895"&gt;&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;If you make these ALV grids editable you are already halfway finished.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, besides this sample report you are probably interested in pros and cons. Well, here is my story.&lt;/P&gt;&lt;P&gt;Three years ago I worked (as external consultant) for a big retailer here in Switzerland. The task was to add a subscreen with a table control into the material master data where they could store seasonal data to their products. In addition, they wanted to have a separate report for mass-maintenance of theses seasonal data for many products.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I decided to go for an editable ALV grid (partly because I cannot program table controls anymore). I managed to use the very same logic for the masterial master maintenance (where the ALV list allowed to enter data just for a single product) and in the report (where you could mantain all selected materials).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At the beginning the customer was very sceptical about this because ALV grids are rather unusual in master data. However, when they saw that it worked and they realized the power of the ALV grid (e.g. colouring, drop-down lists, validations, etc.) they flushed me with additional requirements that all could be implemented easily using the ALV approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2008 17:03:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-grid-vs-table-control/m-p/4713036#M1107035</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2008-11-13T17:03:08Z</dc:date>
    </item>
  </channel>
</rss>

