Diagnosis
Automatic data model synchronization is not possible due to theimminence of serious inconsistency.
This situation can occur, for example, if the compound of one field toan independent field is to be revoked and the system still containsambiguous data with regards to the compound to be deleted. Anuncontrolled conversion of this data would most likely lead to seriousand unreconcilable inconsistencies.

System Response
The data model synchronizer and the generation of the application areawill be terminated.

Procedure
Manual steps need to be taken before you can proceed with the action inthe data model:
Start by temporarily reversing the decisive change that was made in thefield definition. This is to allow you to relaunch the application onthe basis of the unchanged data model. For example, insert again thecompound of fields that was deleted, and activate the characteristic inits original state.
Launch the application. Now, delete all ambiguous masterdata values of the respective field. If you remove a compound, make surethat, for example, all master data values being retaining have a
uniform value for the independent characteristic to be deleted.
All other values need to be deleted. The system will inform youif these values are still in use. These uses also need to be deleted.
Once you have deleted all ambiguous master data values, repeat thechange to the data model you made earlier (for example, delete thecompound of fields again). If the system no longer reports any potentialdata inconsistencies, you should be able to run the data modelsynchronizer successfully.