View cluster contains multiple views with primary table &.

What causes this issue?

The view cluster contains several views with primary table &V1&. This
can cause data inconsistencies.
In the view cluster maintenance, the data is kept per subobject
(table/view) in an internal table. Changes made while maintaining one
subobject do not affect the internal data of another subobject in the
maintenance dialog, but when you save the changed data of these
subobjects is written consecutively to the same database table &V1&. If
the same records are involved, the database table &V1& contains the
data of the last subobject to be saved.
This can cause the following problems in the view cluster:
when deleting
When a data record is deleted in a subobject, the entire record is
deleted from the database table when you save, so the record in the
other subobjects with primary table &V1& is deleted from the database,
but is still in the internal data. This record only stops being
displayed in the other subobjects when you leave and reenter the
maintenance dialog.
when creating a new record:
When a new record is created in a subobject, it is not in the other
subobjects with primary table &V1& until you save and reenter the
maintenance dialog.
The same applies when you copy without dependent records.
If a table field which is in several subobjects is changed in one
subdialog, its value in the other subdialogs does not change. Whether
the new or the old value is in the database tables after saving depends
on the save sequence.
This problem also occurs if this field can only be changed in one
subdialog, and is 'read only' in the others. Primary table 'read only'
fields are also saved in the database if any fields in the record have
been changed.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

You should not have several subobjects with the same primary table in a
view cluster. Create one view with all the primary table attributes.
If you do have several views with the same primary table in the view
cluster, you must ensure in your logic that these problems cannot
occur. In particular, data changes in one subobject should also be made
in the internal data of the other subobjects by subdialog and view
cluster modification, as described in the help in transaction 'Generate
table maintenance dialog'.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.