Do you have any question about this error?
Message type: E = Error
Message class: ESH_ENG_CDS_ABAP - ES-CDS/ABAP
Message number: 064
Message text: Inconsistent model &1 deleted: Orphaned model data
On generating an Enterprise Search connector, the system creates some
model data for it. Model &V1& was detected to be redundant, as there is
no corresponding connector for it.
The redundant model data was removed.
No action required.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
ESH_ENG_CDS_ABAP064
- Inconsistent model &1 deleted: Orphaned model data ?The SAP error message ESH_ENG_CDS_ABAP064 indicates that there is an inconsistency in the model data related to the SAP Enterprise Search (SAP ESH) framework. Specifically, it suggests that a model has been deleted because it was found to be orphaned, meaning that it no longer has a valid reference or relationship to the underlying data or structures it was supposed to represent.
Cause:
- Model Deletion: The model referenced in the error message has been deleted from the system, but there are still references or data that are trying to access it.
- Inconsistent Data: There may be inconsistencies in the data model, such as missing or corrupted entries in the database that the model relies on.
- Transport Issues: If the model was transported from one system to another, there may have been issues during the transport process that led to inconsistencies.
- Configuration Changes: Changes in the configuration of the underlying data sources or the model itself can lead to orphaned references.
Solution:
- Check Model Status: Verify the status of the model in the SAP ESH configuration. If it has been deleted, you may need to recreate it or restore it from a backup if available.
- Rebuild the Model: If the model is essential, consider rebuilding it using the appropriate tools in the SAP ESH framework.
- Data Consistency Check: Perform a consistency check on the underlying data sources to ensure that all necessary data is present and correctly configured.
- Review Transport Logs: If the issue arose after a transport, review the transport logs for any errors or warnings that could indicate what went wrong.
- SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on resolving inconsistencies in the ESH framework.
- Consult Documentation: Refer to the official SAP documentation for Enterprise Search and the specific model you are working with to ensure that all configurations are correct.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a solution to restore consistency in your SAP ESH models.
Get instant SAP help. Start your 7-day free trial now.
ESH_ENG_CDS_ABAP063
Inconsistent connector &1 deleted: Basis missing
What causes this issue? Either the underlying DDL-source of Enterprise Search connector &V1& was deleted, or its @EnterpriseSearch-annotation...
ESH_ENG_CDS_ABAP062
No authorization
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_ENG_CDS_ABAP065
Inconsistent connector &1 deleted: System-/ client copy remainders
What causes this issue? Enterprise Search connector &V1& was detected to be a remainder of the previous system after a system-copy or a clien...
ESH_ENG_CDS_ABAP066
Invalid connector &1 deleted
What causes this issue? The DDL-source Enterprise Search connector &V1& is based on was changed in way that renders it invalid, from the pers...
Click on this link to search all SAP messages.