<?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: Modify a table with a secondry index in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625339#M1761205</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The explanation is present in ABAP keyword documentation of Modify statement.&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://help.sap.com/abapdocu_702/en/abapmodify_dbtab.htm" title="http://help.sap.com/abapdocu_702/en/abapmodify_dbtab.htm"&gt;http://help.sap.com/abapdocu_702/en/abapmodify_dbtab.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;Sy-subrc 4: When a work area was specified in source, no rows were processed, or when an internal table was specified in source, not all specified rows were processed because there is already a row with the same unique secondary index in the database table.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Modify statement can change non-key fields. Modify statement may fail with sy-subrc value 4 if field being changed is part of unique secondary index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try removing the Oracle hints from Modify statement and try changing field NACGNAME after making it part of unique secondary index.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Jul 2013 13:00:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-07-25T13:00:28Z</dc:date>
    <item>
      <title>Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625337#M1761203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hallo Dear folk,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently reading the book "Abap objects" of Hosrt Keller and Sascha Krüger. I have a question regarding secondary indices and the abap&lt;/P&gt;&lt;P&gt;statement "modify". First, let me please mention to you what is writte on page 807 (German version of the book):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;P&gt;MODIFY dbtab FROM TABLE itab.&lt;/P&gt;&lt;P&gt;.....&lt;/P&gt;&lt;P&gt;But even with MODIFY it could happen, that a line cannot be proccessed. For example can a line in the database table exist,&amp;nbsp; with the same unique secondary index ." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was woundering:&lt;/P&gt;&lt;P&gt; ist possible o to use secondary index along with the MODIFY statement? say like that (obviously this statement didn't compile):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;modify znames from lw_name where NACGNAME = lw_name-NACGNAME &lt;/P&gt;&lt;P&gt; %_HINTS ORACLE 'INDEX("ZNAMES" "ZNAMES~001")'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where the table 'znames' have the primary key field 'NAME'. The secondary index has the field 'NACGNAME'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm simply trying to write a simple program which would explain what was mentioned in the book.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope for your help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nido&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 12:32:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625337#M1761203</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T12:32:43Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625338#M1761204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nido,&lt;/P&gt;&lt;P&gt;You could use the below link which gives you more details of it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's simple to use secondary index but not recommended.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Revert if you find more questions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="active_link" href="https://answers.sap.com/message/4767495" title="http://scn.sap.com/message/4767495"&gt;http://scn.sap.com/message/4767495&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dinesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 12:57:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625338#M1761204</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T12:57:10Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625339#M1761205</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The explanation is present in ABAP keyword documentation of Modify statement.&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://help.sap.com/abapdocu_702/en/abapmodify_dbtab.htm" title="http://help.sap.com/abapdocu_702/en/abapmodify_dbtab.htm"&gt;http://help.sap.com/abapdocu_702/en/abapmodify_dbtab.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;Sy-subrc 4: When a work area was specified in source, no rows were processed, or when an internal table was specified in source, not all specified rows were processed because there is already a row with the same unique secondary index in the database table.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Modify statement can change non-key fields. Modify statement may fail with sy-subrc value 4 if field being changed is part of unique secondary index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try removing the Oracle hints from Modify statement and try changing field NACGNAME after making it part of unique secondary index.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 13:00:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625339#M1761205</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T13:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625340#M1761206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are a couple of things that are going on with the query that you have posted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) MODIFY dbtab FROM TABLE itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is a generic staement which will update db table using values from itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2)&amp;nbsp; modify znames from lw_name where NACGNAME = lw_name-NACGNAME &lt;/P&gt;&lt;P&gt; %_HINTS ORACLE 'INDEX("ZNAMES" "ZNAMES~001")'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here you are trying to update Db using lw_name. I guess the field lw_name is a work area here and along with that you are trying to use a secondary index. This is just a trial that are doing to test secondary index while updating a Db. Well my suggestion in real life situation would be that if this Db table is not that big and or the use of secondary index is not that much then do not use the decondary index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check syntax for table key use&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_702/en/abapmodify_itab_single.htm"&gt;http://help.sap.com/abapdocu_702/en/abapmodify_itab_single.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_702/en/abapmodify_itab_index.htm"&gt;http://help.sap.com/abapdocu_702/en/abapmodify_itab_index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please see this note from the SAP help of modify&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following limitations apply when modifying key fields of the&lt;A class="grey" href="https://community.sap.com/" title="Glossary Entry"&gt;primary&lt;/A&gt; and &lt;A class="grey" href="https://community.sap.com/" title="Glossary Entry"&gt;secondary table key&lt;/A&gt;s:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The key fields of the &lt;A class="grey" href="https://community.sap.com/" title="Glossary Entry"&gt;primary table key&lt;/A&gt; of&lt;A class="grey" href="https://community.sap.com/" title="Glossary Entry"&gt;sorted tables&lt;/A&gt; and&lt;A class="grey" href="https://community.sap.com/" title="Glossary Entry"&gt;hashed tables&lt;/A&gt; are read-only and must not be modified. This would lead to the invalidation of the internal table administration and attempts to do so usually raise non-handleable exceptions. &lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;The key fields of a &lt;A class="grey" href="https://community.sap.com/" title="Glossary Entry"&gt;secondary table key&lt;/A&gt;, however, are only read-only while the secondary table is being used. This is the case in &lt;A class="blue" href="https://community.sap.com/"&gt;&lt;SPAN class="qtext"&gt;LOOP&lt;/SPAN&gt;&lt;/A&gt; loops and during the use of the &lt;A class="blue" href="https://community.sap.com/"&gt;&lt;SPAN class="qtext"&gt;MODIFY&lt;/SPAN&gt;&lt;/A&gt; statement, in which the secondary key is specified after &lt;SPAN class="qtext"&gt;USING KEY&lt;/SPAN&gt;. Otherwise the key fields are not read-only.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please go through this link for use of secondary index.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_702/en/abenindices.htm"&gt;http://help.sap.com/abapdocu_702/en/abenindices.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Modify statement &lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/abapdocu_702/en/abapmodify_itab.htm"&gt;http://help.sap.com/abapdocu_702/en/abapmodify_itab.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards,&lt;/P&gt;&lt;P&gt;swanand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 13:31:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625340#M1761206</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T13:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625341#M1761207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hallo Manish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have experimented following your explanation.&lt;/P&gt;&lt;P&gt;I have created a table named "zadresses" with the primary key "Name"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;STRONG&gt;NAME&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; NACHNAME&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; STADT&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; CARINA&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INGENDAE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; REMSCHEID&lt;/P&gt;&lt;P&gt;&amp;nbsp; EMILIE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SAL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Duisburg&lt;/P&gt;&lt;P&gt;&amp;nbsp; Emilie&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Salorte&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Duisburg&lt;/P&gt;&lt;P&gt;&amp;nbsp; NIDAL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ZIDAN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HEIDELBERG&lt;/P&gt;&lt;P&gt;&amp;nbsp; RUZICA&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DJENADIC&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DARMSTADT&lt;/P&gt;&lt;P&gt;&amp;nbsp; salorte&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SALORTE&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Duisburg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have created the uniques secondary index '001' with the fields "NACHNAME"(lastname) and "STADT" (city).&lt;/P&gt;&lt;P&gt;With the entries above already exist, I have written the following program:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: lw_Address type zadresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;start-of-selection.&lt;/P&gt;&lt;P&gt;lw_Address-name = 'CARINA'.&lt;/P&gt;&lt;P&gt;lw_Address-nachname = 'INGENDAE'.&lt;/P&gt;&lt;P&gt;lw_Address-stadt&amp;nbsp; = 'Paris'.&lt;/P&gt;&lt;P&gt;Modify zadresses from lw_Address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would have expected that the program wouldn't be able to modify the first line of the above table (Value 'Paris' for column 'Stadt'), because based on the mentioned explanation, the field 'Stadt' is a part of the secondary index! sy-subrc was 0&amp;nbsp; and sy-dbcnt was 1 !!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do I understand something wrong here! Please give me your hint!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 16:07:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625341#M1761207</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T16:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625342#M1761208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please see the attached secondary index properties.&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/252025" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 16:43:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625342#M1761208</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T16:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625343#M1761209</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Modify statement will fail if there is already a row with same unique secondary index.&lt;/P&gt;&lt;P&gt;When you changed (INGENDAE,REMSCHEID) to (INGENDAE,Paris) for first record, new secondary index (INGENDAE,Paris) is still unique, not existing for any other record before your statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you try to change 2nd record (SAL,Duisburg) to (Salorte,Duisburg), Modify statement should fail because there is already a record (record 3) whose secondary key is (Salorte,Duisburg).&lt;/P&gt;&lt;P&gt;This is required to maintain the uniqueness of secondary index.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 18:06:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625343#M1761209</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T18:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: Modify a table with a secondry index</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625344#M1761210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks, you are very right and now I have sy-subrc = 4.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 18:32:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/modify-a-table-with-a-secondry-index/m-p/9625344#M1761210</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-07-25T18:32:14Z</dc:date>
    </item>
  </channel>
</rss>

