Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error Message MC732 & MC763

HI

While i tried to activate a standard SAP table J_1I_EWT_RETURN i got some warning messages

<i>Check view J_1I_EWT_RETURN

Check view J_1I_EWT_RETURN (ADMIN/25.10.07/12:54)

Key field J_1IEWTCHLN-BELNR missing

All fields are evaluated as key field

Search help J_1IEWT_CHALLAN not inherited: Basis field J_1IEWTCHLN-AUGBL missing in view

View J_1I_EWT_RETURN is consistent

</i>

<b>Key field J_1IEWTCHLN-BELNR missing</b>

Message no. MC763

<b>Diagnosis</b>

In the view, not all of the mandatory fields were included as key fields. The key of the view therefore is not unique.

<b>System Response</b>

All the fields are regarded as key fields in order to guarantee that the key lengths are unique.

<b>Procedure</b>

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.

<b>Notes</b>

The key information is relevant for the ABAP/4 language constructs SELECT SINGLE, SELECT ... ORDER BY PRIMARY KEY and SELECT ... FOR ALL ENTRIES.

In these cases, SELECT SINGLE is handled like a simple SELECT ... ENDSELECT, where the first (random) record found is returned.

ORDER BY PRIMARY KEY and (indirect) SELECT FOR ALL ENTRIES sort according to all fields in these cases.

<b>All fields are evaluated as key field</b>

Message no. MC732

<b>Diagnosis</b>

In the view, not all of the mandatory fields were included as key fields. The key of the view therefore is not unique.

<b>System Response</b>

All the fields are regarded as key fields in order to guarantee that the key lengths are unique.

<b>Procedure</b>

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.

<b>Notes</b>

The key information is relevant for the ABAP/4 language constructs SELECT SINGLE, SELECT ... ORDER BY PRIMARY KEY and SELECT ... FOR ALL ENTRIES.

In these cases, SELECT SINGLE is handled like a simple SELECT ... ENDSELECT, where the first (random) record found is returned.

ORDER BY PRIMARY KEY and (indirect) SELECT FOR ALL ENTRIES sort according to all fields in these cases

This is the warning message i got how to correct this error

Regards

Krishna

Message was edited by:

krishna kumar

Message was edited by:

krishna kumar

Tags:
Former Member
Former Member replied

Hi

Its a general error everywhere

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.

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

Regards

Pavan

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question