We generally use transaction SE11 to create/update/delete dictionary objects in development systems.
Dictionary objects with runtime objects only:
Except table and database views, most of the dictionary objects (data element, structure, table types) have the runtime objects only, no database objects existing for them. So for such objects, inconsistency would happen on the runtime object check only. If the runtime object is inconsistent with dictionary definition, you can just activate the dictionary object via transaction SE11 -> Activate. Then, the runtime object will be newly created based on the dictionary definition for these dictionary objects.
Dictionary objects with both database objects and runtime objects:
As for tables and database views, both the database objects and the runtime objects are existing for them. Depending on whether the inconsistency occurs on the database object check or the runtime object check, the solution is different.
There is one exception, DDL SQL View which is also called ABAP CDS view, is a special kind of dictionary object. A ABAP CDS views also has the corresponding runtime object and database object. But you cannot use SE11/SE14 to update them. For details, please refer to Inconsistencies on ABAP CDS Views for details.