Do you have any question about this error?
Message type: E = Error
Message class: ESH_SQL_SEARCH - ESH SQL Search
Message number: 071
Message text: Last change of CDS entity &1 (connector: &2) has been done by user &3
Last change of CDS-entity <(>&<)>1 (connector name:<(>&<)>2) has been
done by user <(>&<)>3
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you want to check the CDS entity you can display the DDL definition
in the Data Dictionary (DDIC) as follows:
Open the Data Dictionary (SE11)
Select the radio button 'View' and enter the name of the corresponding
SQL view which is associated with the CDS entity.
You can derive the SQL view name as follows:
Get the corresponding search connector name, for example
CD$ALL~ESH_U_MATERIAL~, and take the name part which is delimited by the
characters '~', e.g. in the example: ESH_U_MATERIAL
Display the CDS view. The Data Dictionary will display the fields of the
search connector.
With double click on the content of the DDL source you can jump into the
definition of the CDS entity
Error message extract from SAP system. Copyright SAP SE.
ESH_SQL_SEARCH071
- Last change of CDS entity &1 (connector: &2) has been done by user &3 ?The SAP error message ESH_SQL_SEARCH071 indicates that there is an issue related to the last change of a Core Data Services (CDS) entity in the context of the SAP Enterprise Search (SAP ESH). This message typically arises when there is a discrepancy in the metadata of the CDS entity, particularly in relation to the user who last modified it.
Cause:
- User Modification: The error suggests that the CDS entity was last modified by a user who may not have the necessary permissions or is not recognized in the current context.
- Metadata Inconsistency: There may be inconsistencies in the metadata of the CDS entity, possibly due to changes made in the underlying database or in the CDS definition itself.
- Transport Issues: If the CDS entity was transported from one system to another (e.g., from development to production), there might be issues related to the transport that could lead to this error.
Solution:
- Check User Permissions: Ensure that the user who last modified the CDS entity has the appropriate permissions to make changes. If necessary, have an authorized user re-save or re-activate the CDS entity.
- Re-activate the CDS Entity: Sometimes, simply re-activating the CDS entity in the ABAP Development Tools (ADT) can resolve the issue. This can refresh the metadata and ensure that it is consistent.
- Review Transport Logs: If the issue arose after a transport, review the transport logs for any errors or warnings that might indicate problems with the CDS entity.
- Check for Updates: Ensure that your SAP system is up to date with the latest support packages and notes, as there may be fixes available for known issues related to CDS entities.
- Consult SAP Notes: Look for relevant SAP Notes that might address this specific error message. SAP frequently publishes notes that provide solutions or workarounds for known issues.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
ESH_SQL_SEARCH070
Transient connector for CDS entity &1 not found in runtime buffer
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_SQL_SEARCH069
Executing test search for CDS entity &1 returned: &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_SQL_SEARCH072
CDS Entity &1 not searchable. No test is possible. Check the validation.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_SQL_SEARCH073
Inputs do not match. Specify either a CDS entity or a Connector ID.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.