<?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: Error Message MC732 &amp; MC763 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975261#M702281</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I checked on OSS, but there is nothing... I think you have to open an OSS cal on your own, because this is an error in the standard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Oct 2007 07:52:52 GMT</pubDate>
    <dc:creator>JozsefSzikszai</dc:creator>
    <dc:date>2007-10-25T07:52:52Z</dc:date>
    <item>
      <title>Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975257#M702277</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;While i tried to activate a standard SAP table J_1I_EWT_RETURN i got some warning messages &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;i&amp;gt;Check view J_1I_EWT_RETURN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;           Check view J_1I_EWT_RETURN (ADMIN/25.10.07/12:54)&lt;/P&gt;&lt;P&gt;           Key field J_1IEWTCHLN-BELNR missing&lt;/P&gt;&lt;P&gt;           All fields are evaluated as key field&lt;/P&gt;&lt;P&gt;           Search help J_1IEWT_CHALLAN not inherited: Basis field J_1IEWTCHLN-AUGBL missing in view&lt;/P&gt;&lt;P&gt;           View J_1I_EWT_RETURN is consistent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/i&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Key field J_1IEWTCHLN-BELNR missing&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Message no. MC763&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Diagnosis&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;In the view, not all of the mandatory fields were included as key fields. The key of the view therefore is not unique.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;System Response&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;All the fields are regarded as key fields in order to guarantee that the key lengths are unique.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Procedure&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;For views with a large number of fields, this could have a negative effect on the performance for the language construction described below. In this case, all the mandatory key fields should be included in the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Notes&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The key information is relevant for the ABAP/4 language constructs SELECT SINGLE, SELECT ... ORDER BY PRIMARY KEY and SELECT ... FOR ALL ENTRIES.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In these cases, SELECT SINGLE is handled like a simple SELECT ... ENDSELECT, where the first (random) record found is returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ORDER BY PRIMARY KEY and (indirect) SELECT FOR ALL ENTRIES sort according to all fields in these cases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;All fields are evaluated as key field&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Message no. MC732&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Diagnosis&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;In the view, not all of the mandatory fields were included as key fields. The key of the view therefore is not unique.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;System Response&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;All the fields are regarded as key fields in order to guarantee that the key lengths are unique.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Procedure&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;For views with a large number of fields, this could have a negative effect on the performance for the language construction described below. In this case, all the mandatory key fields should be included in the view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Notes&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The key information is relevant for the ABAP/4 language constructs SELECT SINGLE, SELECT ... ORDER BY PRIMARY KEY and SELECT ... FOR ALL ENTRIES.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In these cases, SELECT SINGLE is handled like a simple SELECT ... ENDSELECT, where the first (random) record found is returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ORDER BY PRIMARY KEY and (indirect) SELECT FOR ALL ENTRIES sort according to all fields in these cases&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the warning message i got how to correct this error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Krishna&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        krishna kumar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        krishna kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 06:23:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975257#M702277</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T06:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975258#M702278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any one plz suggest me some idea&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 06:48:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975258#M702278</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T06:48:17Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975259#M702279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Krishna,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in our system the table looks like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;MANDT&lt;/P&gt;&lt;P&gt;BUKRS&lt;/P&gt;&lt;P&gt;BELNR&lt;/P&gt;&lt;P&gt;GJAHR&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;J_1IINTCHLN&lt;/P&gt;&lt;P&gt;J_1IINTCHDT&lt;/P&gt;&lt;P&gt;J_1IEXTCHLN&lt;/P&gt;&lt;P&gt;J_1IEXTCHDT&lt;/P&gt;&lt;P&gt;BANKL&lt;/P&gt;&lt;P&gt;AUGDT&lt;/P&gt;&lt;P&gt;AUGCP&lt;/P&gt;&lt;P&gt;AUGBL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I bolded the fields which are key fields, pls. check if it the same in your system.&lt;/P&gt;&lt;P&gt;On the other hand, I don't understand why did you activate this table, did not exist in your system before?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ec&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 06:56:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975259#M702279</guid>
      <dc:creator>JozsefSzikszai</dc:creator>
      <dc:date>2007-10-25T06:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975260#M702280</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply Eric. Actually when i observed that table it is an View created by Joining 4 tables BKPF,WITH_ITEM,J_1IEWT_CERTIF,J_1IEWTCHLN for Annual returns - Documemnt  View so there i got this error. Actually in our company upgrade is going on so  while upgrading to ECC 6 i got this error and when i checked the same error in the previous version that is 4.7 i got the same error as specified above and one more important thing i had noticed during this issue is in the table WITH_ITEM while i was activating i got the same error &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; TABL WITH_ITEM activated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt; Adjustment of active dependent objects&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; ENQU EJ_1I_WITH_ITEM was adjusted&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; TABL FMWTITEM was adjusted&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; TABL VWITH_ITEM was adjusted&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; TABL WITH_ITEMX was adjusted&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; TTYP FM_WT_ITEM was adjusted&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; TTYP WITH_TEM_TAB was adjusted&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; VIEW TXW_J_WITH was adjusted&lt;/P&gt;&lt;P&gt; Check view TXW_J_WITH (ERPADMIN/25.10.07/13:55)&lt;/P&gt;&lt;P&gt; Key field BSAK-UMSKS missing&lt;/P&gt;&lt;P&gt; Key field BSAK-UMSKZ missing&lt;/P&gt;&lt;P&gt; Key field BSAK-ZUONR missing&lt;/P&gt;&lt;P&gt; All fields are evaluated as key field&lt;/P&gt;&lt;P&gt; View TXW_J_WITH is consistent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt; End of activation of worklist&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and when i click on the message &amp;lt;i&amp;gt; &amp;lt;b&amp;gt;All fields are evaluated as key field&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt; then i got the same error message of number MC732 as i explained above &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and one more Table view is also having the same problem and the table name is TXW_J_WITH this table is Join of BSAK and WITH_ITEM for DART when i tried to activated i got the error as shown below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Technical log for mass activation&lt;/P&gt;&lt;P&gt;    See log ADMIN20071025135834:ACT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; VIEW TXW_J_WITH activated&lt;/P&gt;&lt;P&gt; Check view TXW_J_WITH (ERPADMIN/25.10.07/13:58)&lt;/P&gt;&lt;P&gt; Key field BSAK-UMSKS missing&lt;/P&gt;&lt;P&gt; Key field BSAK-UMSKZ missing&lt;/P&gt;&lt;P&gt; Key field BSAK-ZUONR missing&lt;/P&gt;&lt;P&gt; All fields are evaluated as key field&lt;/P&gt;&lt;P&gt; View TXW_J_WITH is consistent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt; End of activation of worklist&lt;/P&gt;&lt;P&gt; =========================================================================&lt;/P&gt;&lt;P&gt;You can notice the same error is repeating every where  &amp;lt;b&amp;gt;All fields are evaluated as key field&amp;lt;/b&amp;gt; in these views. Though it was an warning not an error but as u know upgrade is a sensitive issue so we have to minimize the errors&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So thats is my issue. Please help me &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 07:26:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975260#M702280</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T07:26:10Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975261#M702281</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I checked on OSS, but there is nothing... I think you have to open an OSS cal on your own, because this is an error in the standard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 07:52:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975261#M702281</guid>
      <dc:creator>JozsefSzikszai</dc:creator>
      <dc:date>2007-10-25T07:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975262#M702282</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes i know this error( warning ) is every where. But how to correct the error. Even i too checked so many notes but i havnt found any one relevant to this. If u find any solution plz provide me waiting for your solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 07:58:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975262#M702282</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T07:58:56Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975263#M702283</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The error regarding the object "J_1I_EWT_RETURN", can be ignored. Simplychoose 'Ignore errors' in order to progress onto the next phase. &lt;/P&gt;&lt;P&gt;You can activate them in SE11 after the upgrade. &lt;/P&gt;&lt;P&gt;Be sure to make a note of the views, tables and search helps &lt;/P&gt;&lt;P&gt;in question so you can activate them later. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 08:12:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975263#M702283</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T08:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975264#M702284</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 too adivced my basis to team to ignore that as that one is an warnings but there are stressing tominise that warnings also &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards&lt;/P&gt;&lt;P&gt;Krishna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2007 08:14:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975264#M702284</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-25T08:14:37Z</dc:date>
    </item>
    <item>
      <title>Re: Error Message MC732 &amp; MC763</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975265#M702285</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;Its a general error everywhere&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cant say that as an error also its just an warning only that warning has been ignored by SAP itself only so there is no need to take care of that warnings you can easily proceed for your further Upgrade of your SAP. If your basis team is insisting you to solve that warnings also then explain them it may result in several short dumps for that table using any where in your coding. As an abaper its your duty to explain them what are the different situations u may face if it is reseted. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even though after listening to all this then ask your basis team to provide you access key and make modifications in it. In which it will asks to add you some fields to add those it will solve those warnings also&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Oct 2007 05:56:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-mc732-mc763/m-p/2975265#M702285</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-26T05:56:50Z</dc:date>
    </item>
  </channel>
</rss>

