Message type: E = Error
Message class: MC - Aggregate: views, matchcodes, lock objects
Message number: 735
Message text: The view ignores client-dependency of the base tables
The view is defined so that the data is selected from at least one
cross-client base table, event though the table is client-specific.
This could be caused by the first field of the view not being a client
field or if some of the client fields of the base tables are not linked
with join conditions.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check if this behavior is really desired. Usually it will not be
meaningful to make cross-client selections in client-specific tables.
You can define the view as client-specific by including the client
field of one of the base tables as the first field.
All the client fields of the base tables must be linked with join
conditions.
Error message extract from SAP system. Copyright SAP SE.
MC735
- The view ignores client-dependency of the base tables ?The SAP error message MC735, which states "The view ignores client-dependency of the base tables," typically occurs in the context of SAP's Material Management (MM) or other modules that involve client-dependent data. This error indicates that a database view is not properly handling client-specific data, which can lead to issues with data integrity and consistency.
Cause: The error is usually caused by one of the following reasons: View Definition: The database view is defined in such a way that it does not take into account the client field (usually MANDT) of the underlying tables. This can happen if the view is created without including the client field or if the client field is not properly handled in the view's logic. Client-Dependent Tables: The base tables used in the view are client-dependent, meaning they store data specific to each client in the SAP system. If the view does not account for this, it can lead
Get instant SAP help. Sign up for our Free Essentials Plan.
MC734
Selection condition & for field &-& not allowed
What causes this issue? The comparision value specified in a selection condition could not be interpreted.System Response The system issues an error...
MC733
Invalid foreign key dependency for lock objects
What causes this issue? The base tables of lock objects must be linked with a hierarchical foreign key relationship, i.e. the foreign key tables are ...
MC736
Not all the base tables are linked with join conditions
What causes this issue? When UNIONs are used, at least one field must be selected from each basis table. The system issues an error message and will ...
MC737
Invalid type in join &-& = &-&
What causes this issue? The field type does not permit you to define a join condition. Types for which a join condition cannot be defined are LRAW an...
Click on this link to search all SAP messages.